
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2015 03:34 PM
Is there any way to schedule a deployment task to run at the next startup ?
That would be interesting for tasks like update software like Microsoft Office, this way you ensure that the users aren't working on any file preventing lose they work.
Many thanks
That would be interesting for tasks like update software like Microsoft Office, this way you ensure that the users aren't working on any file preventing lose they work.
Many thanks
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-13-2015 02:28 PM
Setting up a deployment package execution after the next reboot is not currently supported.
The best way might be under Deployment\Schedules to configure a deployment schedule with execution after scanning. Then set up LsPush or LsClient on your computers in a startup script through group policy or use Active scanning. However, a small delay will happen in any case until the computer was scanned and the package gets deployed.
The best way might be under Deployment\Schedules to configure a deployment schedule with execution after scanning. Then set up LsPush or LsClient on your computers in a startup script through group policy or use Active scanning. However, a small delay will happen in any case until the computer was scanned and the package gets deployed.
4 REPLIES 4

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2015 06:31 PM
I found a way to achieve it, creating a command step like:
This creates a scheduled task and will run at OS start up using the system account.
The batch file "install.bat" contains the commands to run.
"MSO 2013 install" is the name I choosed for this task.
more info:
https://msdn.microsoft.com/en-us/library/windows/desktop/bb736357(v=vs.85).aspx
Regards
schtasks /create /tn "MSO 2013 install" /tr C:\apps\Office2013\install.bat /sc onstart /RU SYSTEM /F
This creates a scheduled task and will run at OS start up using the system account.
The batch file "install.bat" contains the commands to run.
"MSO 2013 install" is the name I choosed for this task.
more info:
https://msdn.microsoft.com/en-us/library/windows/desktop/bb736357(v=vs.85).aspx
Regards

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-13-2015 04:40 PM
Another option would be to run the package at night.
Deploying the package with the 'Wake On Lan' option and shutting them down after.
Deploying the package with the 'Wake On Lan' option and shutting them down after.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-13-2015 02:28 PM
Setting up a deployment package execution after the next reboot is not currently supported.
The best way might be under Deployment\Schedules to configure a deployment schedule with execution after scanning. Then set up LsPush or LsClient on your computers in a startup script through group policy or use Active scanning. However, a small delay will happen in any case until the computer was scanned and the package gets deployed.
The best way might be under Deployment\Schedules to configure a deployment schedule with execution after scanning. Then set up LsPush or LsClient on your computers in a startup script through group policy or use Active scanning. However, a small delay will happen in any case until the computer was scanned and the package gets deployed.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-13-2015 02:23 PM
Maybe you can post it in the Lansweeper wishlist part
