Cleaning up expired updates

I read the following article and it is quite old and I just wanted to know if this is still the best way to go about cleaning up expired updates in SCCM 2012, or is there another more improved method?
Software Update Content Cleanup in System Center 2012 Configuration Manager

Also note that the blog post linked in the question (http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx#pi168308=2)
is only for content and not for the updates within the groups themselves. That's where Nickolaj's script in the link posted by Peter comes in.
Jason | http://blog.configmgrftw.com | @jasonsandys

Similar Messages

Expired updates not being cleaned up

Hi,
I've been trying to clean up old expired updates on my SCCM 2012 SP1 server and for whatever reason it seems that the updates files are never actually getting removed.
At first I tried the instructions at
http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
When I run the script they provide it appears to go thru all the updates but never actually deletes any of them. The script always seems to say found it found an existing folder and then later it says that that it is excluding the same folder because
it is active.
Then I read that SP1 for SCCM 2012 is actually supposed to do the clean up process automatically. But in this case do I need to do anything like expire the updates manually or does SCCM now do that? How can I see what is preventing either
the manual script or the automatic clean up process from actually removing the unneeded files and folders?
And does anything need to be done with superseded updates as well?
Also I've always thought that when you SCCM 2012 to do your updates that you should never go to the WSUS console and do anything but I read
http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/ and he is going the WSUS console and doing a clean up there as well.
Thanks in advance,
Nick

Hi Xin,
In the wsyncmgr.log file I see lots of log entries like this:
Skipped update 2d8121b4-ba5c-4492-ba6e-1c70e9382406 - Update for Windows Vista (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.777+420><thread=4172 (0x104C)>
Skipped update 24d18083-0417-4273-9a5e-1fc3cd37f1d4 - Update for Windows Embedded Standard 7 for x64-based Systems (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.791+420><thread=4172 (0x104C)>
Skipped update 954f2ad2-369e-469e-97a0-3efd0a831111 - Update for Windows 8.1 (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.805+420><thread=4172 (0x104C)>
Skipped update f81d2820-721a-431c-a262-4878a42f0115 - Update for Windows Vista for x64-based Systems (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.822+420><thread=4172 (0x104C)>
Skipped update 7c82171f-025c-46af-849c-63764ba44382 - Update for Windows Server 2008 x64 Edition (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.836+420><thread=4172 (0x104C)>
Skipped update 36c29163-b78a-410f-8bd0-7370b35a24f1 - Update for Windows Server 2012 (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.850+420><thread=4172 (0x104C)>
Skipped update 6146260e-5c34-4483-962d-834250d84c79 - Update for Windows 7 (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.864+420><thread=4172 (0x104C)>
Skipped update e6e7f357-7011-4bfd-8b14-8be61e43fa51 - Update for Windows Server 2003 (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.877+420><thread=4172 (0x104C)>
Skipped update 2ed5e49f-3295-4b89-8a0b-9a38c0027d6d - Update for Windows Server 2008 R2 for Itanium-based Systems (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.890+420><thread=4172 (0x104C)>
Skipped update 62778a2a-11d8-4cb1-9970-9c3f45202d04 - Update for Windows Server 2008 R2 x64 Edition (KB2998527) because it is up to date. $$<SMS_WSUS_SYNC_MANAGER><10-31-2014 01:50:02.905+420><thread=4172 (0x104C)>
And I also see the following entries:
Sync time: 0d00h41m29s $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 01:51:51.388+420><thread=3440 (0xD70)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 02:05:42.535+420><thread=3440 (0xD70)>
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:05:49.050+420><thread=3440 (0xD70)>
Deleting old expired updates... $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:05:49.130+420><thread=3440 (0xD70)>
Deleted 17 expired updates $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:05:57.067+420><thread=3440 (0xD70)>
Deleted 134 expired updates $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:06:06.487+420><thread=3440 (0xD70)>
Deleted 168 expired updates $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:06:07.595+420><thread=3440 (0xD70)>
Deleted 168 expired updates total $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:06:07.651+420><thread=3440 (0xD70)>
Deleted 10 orphaned content folders in package P0100005 (Endpoint Protection Definition Updates) $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:06:07.875+420><thread=3440 (0xD70)>
Deleted 5 orphaned content folders in package P0100007 (Automatic Deployment Rule for Exchange Servers) $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:06:07.953+420><thread=3440 (0xD70)>
Thread terminated by service request. $$<SMS_WSUS_SYNC_MANAGER><10-30-2014 03:06:51.039+420><thread=3440 (0xD70)>
So it seems like it might be skipping updates? And then it says it deleted 168 expired updates for example?
But if I look at the drive where all the update packages are stored it hasn't changed size.

Best Practice for Expired updates cleanup in SCCM 2012 SP1 R2

Hello,
I am looking for assistance in finding a best practice method for dealing with expired updates in SCCM SP1 R2. I have read a blog post: http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
I have been led to believe there may be a better method, or a more up to date best practice process in dealing with expired updates.
On one side I was hoping to keep a software update group intact, to have a history of what was deployed, but also wanting to keep things clean and avoid issues down the road as i used to in 2007 with expired updates.
Any assistance would be greatly appreciated!
Thanks,
Sean

The best idea is still to remove expired updates from software update groups. The process describes in that post is still how it works. That also means that if you don't remove the expired updates from your software update groups the expired updates will
still show...
To automatically remove the expired updates from a software update group, have a look at this script:
http://www.scconfigmgr.com/2014/11/18/remove-expired-and-superseded-updates-from-a-software-update-group-with-powershell/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Best Practice for Retiring Superseded or Expired Updates

If you want to clear out superseded or expired updates, do you delete them from your update package, the deployment package, or both? Or is there another best practice for this?
Thanks,
Bryan

Hi Torsten, im reading this article because im actualy planing to solve some kind of the the same problem.
I create Software Update Groups with monthly patches, and then i will deploy this to certain Client Collections.
If there becomes a single Patch, the Status, "expired", out of the Software Update Group, what would be the effect for the whole Software Update Group wich still have an active deployment?
Thanks for your sugestion.

Expired Updates Removal - Best Practices

http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
I was searching for best practices for removing expired updates from environment and found this useful link.
There are some queries :
1) It actually says to remove all the expired updates in one go without removing them from SUG's first. When the expired updates which are also part of active SUG are removed, wouldn't this trigger a software update rescan request for all clients in the collection
to which these SUG's were targeted to, to rescan the patches required as there was a change in the SUG ?
2) How about deleting the deployments from collections and then removing the expired updates from only those SUG and proceed in this way. Wouldn't this lower the processing ?
3) The expired update not part of any SUG will be removed, just to make sure, if the expired update is part of SUG but not targeted to any collection, will it still be removed ?
4) Once the expired update is removed, what will be the process of its removal from the Distribution Point. What other automated tasks will be triggered for this like updatation of software update packages on DP once there is any change etc? I have been prestaging
software update packages and extracting them on DP's. For any new DP, as the prestage still contains the older updates (expired, which were removed), Will they get extracted on new DP ?
Are all the steps i mentioned above valid in case of superseded updates instead of expired ?

I am not clear of the below Jacob :
If you delete the deployment, all of the policy for those updates will be removed.
But, that removes every single update and not just the ones you removed. A bit more processing goes into removing everything.
What my concern here is, suppose there are 10 SUG's deployed to 40 collections each. lets
say there are 1000 updates.
If i select all the expired updates and just edit their membership, suppose random udpates
are part of all 10 SUG deployments. Removing these will trigger the policy cycle for all the collection clients.
What i was talking about is, if I pick up 1 SUG out of 10 and remove it from 40 collections
first. Once it is done, then go ahead with removing the expired updates from this SUG.
This is what i need some clarification on.

How to undecline an expired update

Hi,
By mistake, I have "declined" a bunch of updates rather than "approving" them.
Is there a way, either
                I can delete them from WSUS database and resync ?   or
               bring them back to Not Approved state ?
Below is the screenshot that display when I select declined udpates.
Any help is appreciated.
-Vissa

By mistake, I have "declined" a bunch of updates rather than "approving" them.
Well.. first... starting your OWN thread for your own unique problem, rather than tacking onto a four -and-a-half year old unrelated thread would have been preferable behavior.
But.... to do what you asked (which is undecline an update):
In the console, "All Updates" view, set the Approval dropdown filter to "Any Except Declined".
Find the updates you're interested in, right click, select Approval and set to "Not Approved".
But, before you go that far, are you familiar with what an EXPIRED update is?
I would suggest you consider reviewing the
WSUS Operations Guide, as well as this overview on Windows
Update Management, if you have further "how to use the console" questions.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Clean Install Vs. Update

Hello everyone,
I always do a clean install of Mac OS X when a new version comes out. I would like to know from everyone's experience if updating to a new OS version without (fresh install) deleting the hard drive will slow down your system.
In other words, Clean Install Vs. Updating which one is better for your system in terms of speed and system errors?
I would like to know, because at every new release I do a complete "Clean" install by deleting my hard drive and starting over.
Any comments would be greatly appreciated.

I had some problems to update my iMac (Mid 2011) from 10.09 to 10.10. The updating process was easy. After it finished, the System had massiv performance problems and stood still. I decided to install it clean and it was a good choice, now the system's back on and very fast. At work I just updated another iMac from 2011 and there were no problems after the process.
I think Apple did a good job with 10.10. I like it.

Expired Updates Question

Hey all my awesome homies!
I have a quick question. Now let's say that I sync'ed my software updates on Patch Tuesday and I deployed them on that day, and then, let's say that on Thursday or Friday, just a couple or few days later after Patch Tuesday, I decide to run a Synchronization
again, and I see that one of the updates that I deployed has been Expired by Microsoft. Does that mean that those clients that are configured for Manual install (set for Available not Required) where the patches are sitting in Software Center where the update
binaries are in the cache will NOT install that particular Expired patch, or it will since the binary has already been downloaded and tossed in the ccmcache on the client prior the update being expired?
Thank you my SCCM friends, I appreciate your help as ALWAYS

About expired updates:
Description:
Expired software updates were previously deployable to client computers, but once a software update is expired, new deployments can no longer be created for the software updates. Expired software updates contained in active deployments continue to be available
to clients.
Operational Concerns:
Replace expired software updates when possible. When software updates become expired, Configuration Manager does not remove the software updates contained within active software update deployments. Configuration Manager continues to assess software update
compliance on expired software updates in deployments, but they are considered “not required” for reporting purposes.
http://technet.microsoft.com/en-us/library/hh848254.aspx

Deploying Expired Update in SCCM 2012 R2

We need to deploy an update to Silverlight to allow one of our web based applications to run correctly. SCCM is currently configured to wait 3 months before expiring a superseded update. Microsoft released an update in Decembers patch release which expired
the update that could of been deployed by SCCM. This latest update was subsequently expired by Microsoft meaning I have no updates available to deploy to the clients. My questions are:
1. If I increase the time period of 3 months to wait before expiring a superseded update, will SCCM rescan all updates and then make expired updates available if they fall within this newly configured time period?
2. If I then revert the setting after deploying the update will it then rescan again and make expire updates again that are older than 3 months?

No. The update you speak of, to my knowledge, was not superseded, it was expired directly by Microsoft. As for updates it may in turn have superseded, no, they will remain expired as there is no unexpire process -- once expired, always expired to my knowledge.
Microsoft simply needs to issue an updated update (that of course is not expired).
Jason | http://blog.configmgrftw.com | @jasonsandys

Lightroom for iphone, 提示:"trial expired, update your subscription or sign out now to sign in with antother ID"

更新最新版的lightroom for iphone
更新完毕进入突然黑屏弹出，然后重新进入就要我输入Adobe账号
登录提示"trial expired, update your subscription or sign out now to sign in with antother ID"
这怎么回事？

https://www.adobe.com/creativecloud.html

BB Bold Apps wiped clean after software update HELP!

I have an app on my Blackberry called BugMe!, where you can create reminder lists, which was wiped totally clean after I updated my Bold last weekend. I had some very important lists and need to know if I can recover these. Please help!

Unfortunately DM only backs up your BB settings, core applications and RIM Add On apps (such as BB Maps, Memo Pad, Password Keeper, etc). If you used BB Swiss Army Knife or BB Master Control Program, then you can recover 3rd party apps. Some applications allow you to backup your settings to the SD card, which is very handy.

Core Audio Components Missing After Clean Install and Update to 10.3.9?

I did a clean install of 10.3.x onto my hard disk and then updated to 10.3.9 through Software Update.
Before this install I'd been running 10.3.9 (my disk crashed -- or so I thought -- hence the re-install of all above). I'd been running a music recording program and taking advantage of Apple's Core Audio AU components (e.g. AUDelay, etc), which should be in /Library/Audio/Plug-ins/Components/ or something like that. Now they are missing entirely.
How do I get them back? Where are they to find?
Thanks!

It was a problem with the 3rd party software -- I hadn't run the installation update to interface with the AU Components -- after the reinstall. Thanks.

Query about expired updates in SCCM 2012

Hi,
We have requirement to include Feature pack updates in SCCM 2012.
For testing purpose, We have modified SUP settings in CAS to include feature packs and run the synchornization. so All feature packs update are synchornized and available(The icon with the green arrow) in SCCM 2012. Since this is for testing, we roll
back the changes in SUP (unchecked Feature packs) and after we run synchornication, Feature pack updates are showing as Expired in SCCM console.
I just want to know if we include Feature packs in SUP and run synshornization again, Will that expired feature pack updates show as normal updates(Green icon) in sccm console?

i have not testes this behavior but i think,it should work as you expected ,the expired feature pack updates will show as normal after you enable and sync is done as the metadata will be overwritten.
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

Software Update Group with Expired Updates

I might be interpreting this incorrectly, but it seems as though a machine is not installing any updates from a particular update group.
One or more of the updates are expired - Would this result in NONE of those updates deploying to the device??

Would this result in NONE of those updates deploying to the device??
No.
Torsten Meringer | http://www.mssccmfaq.de

Lenovo pre-load OS vs. clean install + System Update

Hi all, just wondering what the conventional wisdom is these days: stick with the Lenovo pre-load OS or perform a clean install and then use System Update to add whichever drivers seem worth adding.
I've traditionally performed clean installs on new computers, but I'd be happy to skip the chore if it's not all that beneficial anymore.
Thanks!

Windows 7 - clean install recommendations by Lenovo
My home-forum: http://www.thinkpad-forum.de
Wiki: Deutsches ThinkPad-Wiki English ThinkWiki
My ThinkPad-Collection

Cleaning up expired updates

Similar Messages

Maybe you are looking for