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 ends the connection. The task is then run 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. However, 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 Deployment > Security options section of the web console, but you can specify another run mode when manually initiating or scheduling a deployment as well.
Deployments are performed in batches. The number of concurrent deployments is determined by the Deployment Threads value configured in the Configuration > Server Options > Service Options section of the web console.
Deploying a package manually
To deploy a package manually, choose either of the options listed below. A pop-up will confirm which package you would like to deploy. Optionally, you can choose to perform a Wake-on-LAN of offline computers before 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.
- Go to the Assets section of the web console, tick the checkboxes of the target computers of your choice and select Deploy Package.
- You can search through the columns to find specific assets easily.
- You can tick the top checkbox to select all assets in the current search results.
- Select a computer report under Reports > View All Reports and select Deploy Package. Remember that the deployment button only appears in asset reports, i.e., reports that include the tblAssets.AssetID field.
- Hover over the Assets section at the top of the web console, select an entry in one of the available asset overviews and select Deploy Package.
- Browse to the Deployment > Deployment packages section of the console, select your package on the left and select Deploy Now. 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 perform a Wake-on-LAN of offline computers before deployment, wherein 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.
- Browse to the Deployment > Scheduled deployments section of the web console.
- Select New Schedule in the Schedules section of the page. Specify a name for your schedule, 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.
- Select New Deployment Configuration 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.
Was this post helpful? Select Yes or No below!
Did you have a similar issue and a different solution? Or did you not find the information you needed? Create a post in our Community Forum for your fellow IT Heroes!
More questions? Browse our Quick Tech Solutions.
