Should have said 3 sets of ad groups… From: [email protected] [mailto:[email protected]] On Behalf Of Jimmy Martin Sent: Friday, May 01, 2015 8:54 AM To: [email protected] Subject: [mssms] RE: OT: Quick poll on Windows server patching
We have taken a highly granular way to automate where we can… we created 3 AD groups: · Week of the month (1st, 2nd, 3rd, 4th) · Day of the week · 2 hour window of the day 7p-9p We built out collections limited to each other… First Monday 7p-9p limited to first Monday limited to 1st week Added a maintenance window to each of those hour window collections (yeah, I know it can be a lot…) then each of those collections is an include collection on a collection where the software updates are deployed. This is working well for those servers where we have no dependencies. It also makes it easy for the server owner to set the update window for the server just by adding the server to some ad groups. Jimmy Martin (901) 227-8209 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gushue, William Sent: Friday, May 01, 2015 8:45 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: OT: Quick poll on Windows server patching Quarterly, but we divide them up and have maintenance windows every month. So, Group 1 this month, Group 2 next month and so on. I’m oversimplifying because it changes so much, but that’s the idea. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Friday, May 1, 2015 9:33 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] OT: Quick poll on Windows server patching Just curious to see if folks patch windows servers monthly, quarterly, yearly, as needed, etc. Desktops I’m sure are done monthly across the board, for most shops. Thanks. Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State ________________________________ ******************************************************************** This e-mail message is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited. Le contenu du présent courriel est privilégié, confidentiel et soumis à des droits d'auteur. Il est interdit de l'utiliser ou de le divulguer sans autorisation. ******************************************************************** This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
