I am trying to create a scheduled task to reboot all PCs at 5pm on Sundays. I tried playing with the reboot agent settings, but that does not seem to be the correct route to take for this. Is there a way to create a scheduled task that just says reboot at 5pm on Sundays? I am using Management Suite 9.6.
1 of 1 people found this helpful
You can schedule a software distribution package to run shutdown.exe /r at 5 pm on Sundays, the easyest way is a batch
This worked, as in I could create a reboot task. The problem I am having now is when I test it, the device does not reboot. The results say successful, reboot not needed. Is there a way to override that? I want it to reboot regardless.
Which didn't work? I always recommend the reboot task as done from Patch and Security Manager as suggested above: https://help.landesk.com/docs/help/en_US/LDMS/9.6/Default.htm#Windows/patch_t_create_reboot_task.htm
Additionally you need to look through the Reboot Settings from the Agent Settings tool and make sure that all of the options are set as desired.
Make sure that under the General Settings that it says "Act as if reboot is ALWAYS needed".
I double checked and I did have all of those settings configured correctly. I am going to open a support ticket and I will post the results here in case it can help anyone else.
You can also create a batch file with Shutdown /R /T 0..... BE Careful... Accidental distributions could be a career ending move
The problem was the global never reboot setting.
Thanks for all the help.
Always use a time value of some sort (/t 300 buys you 5 minutes).
Create another Package that runs shutdown -a (abort pending shutdown) and set it's targets as all computers in the org. Ensure your Helpdesk knows how/where to run this package.
This can save your career.
For anyone interested, what I had to do was create 2 different reboot agent settings. The problem I was having with using one agent config was that the users were getting a reboot notification pop up days before the task and it would not minimize or close.
The one used by my agent config is set to:
Act as if a reboot is always needed
Suppress Windows Update reboot notifications,
Do NOT prompt user before rebooting (if you do not do this, the user gets a pop up notification days before the weekend reboot.)
Set a auto reboot window to the timeframe you want the reboot to happen on the weekend. (Only so it does not decide to reboot during the week.)
The second agent config is the one used by the scheduled task.
Act as if reboot is always needed
Suppress Windows Update reboot notifications
Prompt user before rebooting
Set your auto reboot options for logged out times, locked time, etc.
Do NOT set the auto reboot to a specific time window (the scheduled task will do that)
I had to create two scheduled tasks, one for Saturday reboot and one for Sunday reboot.
After that, the reboots worked perfectly.
I've setup my scheduled tasks in a similar way. It might even be identical. Were you able to get Landesk to run a scheduled task a certain time and actually keep it running at that time? My reboot scheduled task was initially set for 8:00am on Thursday (weekly reboot). Each week the start time changes by the amount of time the task took to run. So week #2 the job will start at 8:06am (6 minutes to run the task on week #1). I have read about time creep but you don't mention any problems with that.
Curious to hear if you're experiencing this issue as well.
I do have some creep, but not excessive. My reboots are set for 7pm Saturday and some happen as late as 7:30ish. I am ok with that, so I have not tried anything to resolve it.