It’s important to know that SUG’s are limited to 1000 updates. It’s an entire strategy how to make Software Updates Groups. You need to make SUG’s in order to apply more updates to collections. Each server/workstation chose what needs from entire SUG When I make my SUG I put all security updates for all OS clients and all security updates for all OS servers. Always I put in same collection all type of OS (XP, W7, W8, etc.). O For workstations is not important to group them after OS. Of course I start my process with less important and finish with critical Usually I have also collections not important, important, highly important and critical. So if something is wrong not all my servers are affected. O For servers for example I have more collections and I’ve tried to put servers with same roles in different collections with different installing schedules. With collections you can group your servers and workstations in different category. The time is compliant with customer strategy

Some customers update the server at every three months, other at every 6 months, etc. One month I think it’s enough for community and Microsoft to discover if some software updates are dangerous. So when the updates are applied the software updates has already one month age and it’s stable. Usually the deployment time is Friday after 17:00 for workstations and Saturday at 02:00 for regular servers. O After three weeks from release I made the updates Mandatory and deployed them with one week time deployment deadline. So everybody can see the available updates, Department managers can download on a few less important workstations and see if they are casing issues or not. O After one week if nothing it’s wrong I published the updates on my environment and make them Available for two weeks.

I made this operation Friday in case that some updates released Tuesday are dangerous and Microsoft retried them. NEVER install updates for the first time in a production environment. Usually I download the updates in same week Friday and install on my testing environment.

When to apply Software Updates? Until now Microsoft release updates in every second Tuesday of each month.You can have same action linked to more collections. In SCCM any actions like Software Updates installing are linked with collections. In any strategy you need to consider more elements. I will describe my own Software Updates Strategy made after I analyse more “best practices” strategy. Today I will describe how I do make my SSCM software updates strategy.įirst Software Updates Strategy is a collection of procedures and can be very different for different customers.

Sccm software update group