Skip to content
  • Why Lansweeper
    • Why Lansweeper?
    • Our ITAM 2.0 Vision
    • Customers
    • Use Cases
      • Cybersecurity
      • Software Asset Management
      • Cloud Migration Assessment
      • Replacing Spreadsheets
      • View All
  • Product
    • Product Overview
    • IT Discovery
    • IT Inventory
    • IT Analytics
    • Features
  • Pricing
  • Resources
    • Blog
    • Learn
      • Customer Stories
      • Product Demo
      • Webinars
      • Tutorials
    • Help Center
      • Support Knowledge Base
      • Community
    • Report Library
      • All Reports
      • Patch Tuesday
      • Vulnerability Audits
      • Windows 7 End of Life Audit
    • Partners
      • Find a Partner
      • Become a Partner
    • Download
      • Lansweeper
      • LsAgent
    • Integrations
  • Contact Us
  • Try for Free
Menu
  • Why Lansweeper
    • Why Lansweeper?
    • Our ITAM 2.0 Vision
    • Customers
    • Use Cases
      • Cybersecurity
      • Software Asset Management
      • Cloud Migration Assessment
      • Replacing Spreadsheets
      • View All
  • Product
    • Product Overview
    • IT Discovery
    • IT Inventory
    • IT Analytics
    • Features
  • Pricing
  • Resources
    • Blog
    • Learn
      • Customer Stories
      • Product Demo
      • Webinars
      • Tutorials
    • Help Center
      • Support Knowledge Base
      • Community
    • Report Library
      • All Reports
      • Patch Tuesday
      • Vulnerability Audits
      • Windows 7 End of Life Audit
    • Partners
      • Find a Partner
      • Become a Partner
    • Download
      • Lansweeper
      • LsAgent
    • Integrations
  • Contact Us
  • Try for Free

Deploying a package, manually or based on a schedule

Home > KB Articles > Deploying software and other changes > Deploying a package, manually or based on a schedule

A package can be deployed manually or based on a schedule. When a deployment is initiated, Lansweeper uses your scanning credentials to access the Task Scheduler on your machines, creates a task on your computers that will run the deployment steps and then ends the connection. The task is then run either under your computer's system account, the scanning credential mapped to the computer or the user currently logged into the computer. It is generally recommended that you use the system account to run the task, which is the most secure, though the other two options may be useful if your deployment requires special permissions or is meant to make changes to a specific user's installed software or registry keys.

The default run mode is configured in the following section of the web console, but you can specify another run mode when manually initiating or scheduling a deployment as well: Deployment\Security Options

Three credentials come into play when performing a deployment:
• Your scanning credentials are used to create tasks on your machines that will run the deployment.
• Your share credentials are used by the tasks to access files stored in your package shares and referenced in your deployment package, nothing else.
• The tasks are run under your system accounts, scanning credentials or currently logged on users, depending on which run mode you choose.

Deployments are performed in batches. The number of concurrent deployments is determined by the Deployment Threads value configured in the Service Options section of the following page: Configuration\Server Options

Server Options menu
Deployment thread changes won't take effect until you restart the Lansweeper Server service on your Lansweeper server.

Deploying a package manually

To deploy a package manually, choose either of the options listed below. A popup will confirm which package you would like to deploy. Optionally, you can choose to perform a Wake-on-LAN of offline computers prior to deployment, in which case you'll need to specify an estimated boot time per asset. You can also have the deployment automatically retried for offline machines.

  • Click the Assets link at the top of the web console, tick the checkboxes in front of the target computers of your choice and hit the Deploy Package button on the left.
    - You can perform a search on one of the columns to more easily find specific assets.
    - You can also tick the checkbox at the very top to select all assets in the current search results.
  • Left-click on a computer report under Reports\View All Reports and hit the Deploy Package button on the left. Keep in mind that the deployment button only appears in asset reports, i.e. reports that include the tblAssets.AssetID field.
  • Hover over the Assets link at the top of the web console, select an entry in one of the available asset overviews and hit the Deploy Package button on the left.
  • Browse to the Deployment\Installer Packages section of the console, select your package on the left and hit the Deploy Now button on the right. This will also allow you to manually select assets or run a deployment on computers included in a specific (static or dynamic) group or report.

Deploying a package based on a schedule

To deploy a package based on a schedule, follow the steps below. Optionally, you can choose to perform a Wake-on-LAN of offline computers prior to deployment, in which case you'll need to specify an estimated boot time per asset. You can also have the deployment automatically retried for offline machines or triggered by a successful scan.

  1. Browse to the following section of the web console: Deployment\Scheduled Deployments
  2. Hit the New Schedule button in the Schedules section of the page. Specify a name for your schedule, a start date and time and schedule type. You can run your deployment once, based on an interval (every X number of minutes, hours, days), daily, weekly or monthly. Daily, weekly and monthly deployments can be run once or every X hours as well.
  3. Hit the New Deployment Configuration button in the Configurations section of the page. Select your schedule, select your package and choose either a (static or dynamic) asset group, a report or an individual selection of assets to run the deployment on.

Related Articles

Creating a deployment package

From version 5.2 onward, Lansweeper includes a deployment module that allows you to deploy changes on Windows computers. You can

Read More »

Deployment requirements

From version 5.2 onward, Lansweeper can deploy changes on Windows computers. You can create deployment packages, series of conditions and

Read More »

Checking the status of a deployment

From version 5.2 onward, Lansweeper can deploy changes on Windows computers. You can now create deployment packages, series of conditions

Read More »

Importing and exporting deployment packages

Lansweeper includes a deployment module that allows you to remotely make changes to the Windows computers in your network. You

Read More »

Product

  • Why Lansweeper
  • Use Cases
  • Product Overview
  • Pricing
  • Features
  • Changelog
  • Beta

Company

  • About
  • Contact
  • Careers
  • News
  • Brand Assets

Partners

  • Find a Partner
  • Become a Partner

Resources

  • Blog
  • Customer Stories
  • Product Demo
  • Report Library
  • Download Lansweeper
  • Download LsAgent
  • Integrations

Contact

Talk to Sales

Help Center

  • Knowledge Base
  • Community
  • Contact Support

Newsletter

Get your hands on the latest news, vulnerability updates & network reports.
  • This field is for validation purposes and should be left unchanged.
Facebook
Twitter
Youtube
Linkedin
Reddit
  • Copyright © 2021 Lansweeper
  • Privacy Policy
  • Cookie declaration
  • Terms of use