Deploying Windows Updates

[AaronBISSELL]

This may be a silly question - but I was just curious if anyone had any comments on grouping the deployments into a single install on the client side.

 

Reason being - we are getting ready to deploy a large number of updates to our users (50+) and want to give them the ability to kick them off on their own for a bit before they go mandatory. Problem is - it can become tedious to select 50 different deployments (Updates) and install them one at a time... Does anyone have any thoughts on being able to clump them together in "September Updates" rather than having them display 50 different updates in their Software Center?

 

Thanks

Aaron

[Steve G.]

I think you'll find that pretty much nobody deploys updates one by one. They are typically either grouped into software update groups by month, or lumped into a larger "overall compliance" software update group.

[AaronBISSELL]

This is true - And I am speaking in regards to what the user sees on the client machine. My end is organized nicely into Software Update groups. The users see each update. My single update group could contain up to 500 updates, the user will see each of these updates listed individually. So I was wondering if anyone knew anything about grouping the updates into a single deployment on the client side - so they see only 1 update

[wilbywilson]

I could be wrong, but I don't think what you're asking for is possible.

[Peter van der Woude]

I would prefer the normal way of deploying updates, but in case you really want something different you could use a task sequence to deploy those updates. That way the user will only need to select the task sequence to deploy the updates.