James,
One tip: If you're running ConfigMgr 2012 R2, make sure you make your Maintenance Windows of type Software Updates, not All Deployments, otherwise you will likely run into issues with your servers not rebooting automatically at the scheduled time. I spent a few hours with a customer on that recently. :) Cheers, Trevor Sullivan Microsoft PowerShell MVP <http://mms.mnscug.org/> From: [email protected] [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Thursday, August 7, 2014 2:53 PM To: [email protected] Subject: [mssms] Maintenance Windows For the past several years, I've only managed the PC environment and so I've never really had a reason to use maintenance windows. We just push out updates and they get installed as soon as possible. I'd like for that process to change but that's the way we've always done it. However, I'm now going to be taking over the responsibility for updating servers as well - which were previously done with plain ol' WSUS and they were all done at once on a Sunday morning. I've got the SCCM client loaded on some test servers and I'm looking into setting up some MW's for testing. Does anyone have a good guide on the recommended way of 1) setting up the collections and 2) setting MW's on those collections? Is there a certain structure I should use? I'm sure there are many different ways to do it but just curious what others are doing. Thanks, James _____ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
