When a full software update point synchronization runs, updates are expired.Ī full software update point synchronization is a scheduled synchronization, not one initiated through the console, which is a delta synchronization Let’s walk through the process at a detailed level so you understand how it works. There is no specific or configurable maintenance task to do this-it’s an automated process that crosses multiple ConfigMgr components. At a high level, updates that have been expired and that aren’t part of an active deployment will be deleted 7 days after they are expired. Next, there are four phases to removing expired updates and its related content, and those are: the expiration action, tomb-stoning, deletion, and then source cleanup, which is a scripted action. Simply uncheck the selected check boxes.Ĭlick OK to remove all of the expired updates from the selected Update Groups, and they’ll be ready for deletion through the process outlined in the next step. You will then see a list of all Update Groups where any of the selected updates from the list view are members. The search results will include all of your expired updates, so simply select all updates in the list view (CTRL+A), right-click, and choose Edit Membership. Navigate to the All Software Updates node under Software Library, and search for all expired updates.Īdd the value for expired updates to search, leave the default value as “Yes”, and click search. Note: When using Auto Deployment Rules to deliver definition updates, where you should be re-using the same update group each time the rule runs, expired updates are automatically removed from the update group each time the rule runs. To remove expired updates from all deployments in only a couple of clicks, do the following. The step to make expired updates removable, however, is straightforward, and it should be part of a monthly process. It could be disconcerting if updates simply disappeared from your deployments and you had no idea why, so we just don’t do it. First, weĭelete any expired update associated with an active deployment, as we don’t want to removeĪssociated with your deployments. The first part of the process for managing content related to expired updates is getting expired updates out of any deployed update groups. In this blog, I’m going to walk you through exactly how the process works, and I’m also going to provide a script you can use to clean up source locations related to obsolete updates, as our out-of-box process does not manage source content. It’s particularly helpful for Endpoint Protection definition updates, given their frequency of release, deployment, and expiration. This process helps manage drive space on your distribution points by removing any content you no longer need. In System Center 2012 Configuration Manager, we’ve added the capability to automatically remove software update content from distribution points when that content is related to expired updates. First published on CLOUDBLOGS on Apr 12, 2012Ĭleanup script updated to fix reported issues
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |