Client Management Suite

OK simple one here for you guys :-)

 - I'm planning on creating a scheduled reboot for some machines once a month. Is is as simple as creating a 'managed software delivery' and using a 

reboot PC task with this Policy. I'm pretty sure this is the case but the 'managed software delivery' sort of throws me and just asking in case theres a better way.

Joe.

Do you plan to force a reboot regardless of any running processes, (which may make your users very unhappy if they lose work they have not got around to saving), or in some other way?  Are they all windows machines?

Running the windows utility shutdown.exe with the switches -f -r -t 0  (that's a zero) should provide a forced reboot in most cases.

yeah - was planning to do it at 2:00am - force reboot. (only some slected machines) on a fixed monthly basis.

HI,

You can also try the "Power management" task from:
Jobs and Task -> System Jobs and Tasks -> Real Time console infrastructure -> Power managemet.

To use this task you should have acces to clients WMI from the NS Server, or clients should support the out-of-band technologies (Intel vPro(AMT); ASF;DASH)

.

Ok - ive setup a test policy to test this reboot. I have the task reboot PC. Which I've added to a policy. When its time to run this policy it says on the agent compliant and doesn't run - as its already run before. How do I stop complinace check ?

Joe.

OK - found it - all I had to do was right click the task and set schedule !!! just need to test it now...

Are you only applying this to desktops? 

If you will be including laptops that might be put into hibernation or standby at some point, you should look into using maintenance windows along with your task.  If you have a task set at 2AM and the machine goes into hibernation after receiving the task, if it comes back online after that 2AM reboot time, it will still receive the reboot at the time it comes back up, even if you check to only run at exact scheduled time. 

Good point - I've never used a maintenance window so I guess I should start now if I'm scheduling a reboot. 

p.s. Just using it on desktops only, but probably best get used to using mantenance windows.

Thnks

Joe.

Be a little careful if you'll have it on all the time... if you use other policies and patching, etc. that you still want to run, you'll need to make sure to say in the policies (or any tasks you manually run) that you want to ignore maintenance windows.  For 7.1, I ended up just using an ASDK vbs script to turn my reboot policy and maintenance window on Friday and off Sunday so that I didn't have to worry about any implications of the maintenance window on other items.