Wednesday, November 26, 2014

Maintaining Software Updates


The Software Update in Configmgr 2012 is much easyer to maintain and keep tidy than the old 2007.
But still you have to think through, how do you want to update your machines and servers. What Updates, how often, reboots, and what about packages and perhaps low bandwidth Distribution Point far away. How and where will the clients pick up the packages they need, and how can I be sure my system runs as optimized as possible.

Anyhow you do it, you have to do some manually cleanup from time to time.
Updates gets superseeded and automatically Expired depending on you setting.
Now, Configmgr 2012 will Automatically fix this for you, but it will not cleanup the packages containing Expired Updates until you remove them from the jobs, the Software Update Groups.
Once this is done, it will delete those updates from the packages and update all your Distribution Points automatically.

There are some solutions out there with scripts that could do this, but if you prefere some manual work to be in controll. This is how.

On the "All Software Updates" tab, add Criteria "Depoyed" and Expired both to Yes.
This will give you a list of updates that are part of a deployment and is expired.
Then mark all of them and choose Edit.
Uncheck from all of the Software Update Groups, wait a bit and your Done.

Depending on the load on your servers and amount of updates this could take a few minutes.




Also if you have System Center Update Publisher installed you can Run the Software Update CleanUp Wizard in Options.



Read more in Kents blog:
http://blog.coretech.dk/kea/why-system-center-updates-publisher-aka-scup-is-still-a-great-tool/

No comments:

Post a Comment