Regarding WOL and updates

[birz]

I have one quick question,

 

When you enable the Wake On Lan feature for a update deployment and the computer which is targeted to receive it's updates is powered off, will the wake on lan wake the computer, installs the updates and shutdown the computer or restart it?

 

It's regarding powersaving and my management want to know. Basically I would like the computer to shut back down and not reboot and stay at the login screeen.

 

I hope it's understandable, thanks

[anyweb]

good question, the wol feature is used to wake the computers up if they actually need an update targetted in the deployment management task, if they don't need one or more updates they are not woken up,

 

also, once woken up the update(s) are applied and that is all, you'd have to leave them on or package some other solution to power them off again, or wait for R3 which will have several power management features revealed

[birz]

good question, the wol feature is used to wake the computers up if they actually need an update targetted in the deployment management task, if they don't need one or more updates they are not woken up,

 

also, once woken up the update(s) are applied and that is all, you'd have to leave them on or package some other solution to power them off again, or wait for R3 which will have several power management features revealed

 

 

Thanks for the information, I'll wait R3 in that case

[Gorilla]

Thanks for the information, I'll wait R3 in that case

 

I'm using WOL enabled updates and it works great. Given that you can be very granular with Collections, the sky is the limit and I recommend basing your design on what the business outcome is. So for example, if you have a work group that shows up at 8:00 AM, setting a maint. window from say 7:00 - 7:45 should see most updates installed before they show up leaving 15 minutes for reboots and early risers. You can tweak down the start time if you need longer windows, and the job won't start if there isn't time to complete the install in the maint. window.

 

Eventually there will be options for powering off clients but that can be part of continual service improvement and is a great benefit to market later. Getting your SCCM collections / search folders / templates / and update lists dialed in so that the right groups cache downloads and exhibit the end-user experience (notification and reboots) you're striving to deliver can take a bit of time and testing. I would recommend not waiting because maint. windows can minimize how long a computer is on after you deploy software. You can consider making a task sequence to look for logged on users and then issue a shutdown to the client if it isn't in use. Hard to know since it will be based on what your customer wants to occur. But there are enough tools. SCCM will let you deliver anything you can imagine pretty much. It just takes some creativity at times. :>)