SCCM Windows Update Collections

[jertsy]

Hi

 

I was wondering how you have setup your collections for windows updates, is it best to setup a collection for one O/S or type of update, I was thinking one collection for Windows 7 32 bit, one for 2012R2, one for office 2013 and one for exchange 2013 etc... Or is there a better way of doing it?

Any suggestions greatly appreciated.

 

Cheers,

Jertsy

[gjefferies]

Hi,

 

It depends really on how many updates you need to deploy, i've used the Operating System collection method in the past, but you will find some updates apply to more than one o/s so you end up deploying them multiple times.

 

I basically just create one package and deploy it out to all systems, then the computers work out which updates they need.

 

Thanks

Gareth

[Gatt]

Updates - Workstations = All Client OSs (in My case Win7 and Windows 8.1)

Updates - Servers = All Server OSs (eg Server 2008 R2 and Server 2012)

Updates - Global = I use this for all Application updates (eg Office, Sharepoint, etc etc etc) - this is bascially the 1st two combined together

[jertsy]

Updates - Workstations = All Client OSs (in My case Win7 and Windows 8.1)

Updates - Servers = All Server OSs (eg Server 2008 R2 and Server 2012)

Updates - Global = I use this for all Application updates (eg Office, Sharepoint, etc etc etc) - this is bascially the 1st two combined together

 

So if I set up 3 collections, for arguments sake like yours. I would then create an update package from the applicable updates and deploy to the collection, does that sound about right?

[Gatt]

Yeah. I create a package for alk win7 and win8.1 updates and deploy that to the workstation collection. The client will only pick the updates that it need ( win8.1 updates wont be sent to a Win7 pc) same for servers and so on...

[jertsy]

Yeah. I create a package for alk win7 and win8.1 updates and deploy that to the workstation collection. The client will only pick the updates that it need ( win8.1 updates wont be sent to a Win7 pc) same for servers and so on...

 

Do you have a test group first? I thought I may do one with a non critical server in and another with a few win 7 clients to test the updates before pushing out to the main collections.

[sonofsanta]

I have a test group including the PCs in our office and the lobby immediately outside, and new updates are deployed here for a week and a half for testing.

 

Assuming all is well, updates are then just sent to All Windows 7 machines.

 

Servers I still do manually so I can see what is going on with them and control when they restart - I go through the updates every holiday.

[Gatt]

Do you have a test group first? I thought I may do one with a non critical server in and another with a few win 7 clients to test the updates before pushing out to the main collections.

 

Not in my "lab" (we do at work due to the size of our environment though) - though it is prudent to create a test collection though!

[jaminben]

Ours is pretty much the same as Gatt's... Workstations, Servers and Applications. We roll out updates to the library first (20 machines) then the rest of the school a month later if all is ok.

[jertsy]

Cheers guys, I will follow this approach I think. I will have 3 collections for testing and 3 for production.