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

Similar Messages

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.

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

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

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 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.

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.

Can we make things more Useful...? not an update question.

Ok well i said its not an update question.. well it kinda is.
today is friday.. the release date of the new iphone 3g.. great.. i love my iphone.. im goin to wait a week or so before i go ahead and buy the new phone for sake of bugs and lil tweaks..
ok so today i dont know what drove me to update my iphone.. and it got totally bricked for 3 hours.. until i finnally got thru using the "clicking" solution... well i understand the server is overwelmed.. and everyone is updatin and the same time.. but there was a prompt askin if i wanted to update and get the latest iphone software and the latest version of itunes... good.. lets all download it.. most of us it will take 3-6 hours for the iphone to update because the whole problem with the overload on apples side...
..BUT...
what if we cant wait that long?
i SYNC'd my iphone before the update.. well everyone does... itunes prompts you to do so.. WHY.. emphasizing on WHY... if we synced the phone to our computer systems.. and a problem like for example is goin forth now with this update... CAN'T we just restore our iphones back to how it was before we even tried updating it?
IT did SAVE to our computers right?
why cant we just double click here, right click right there..
and BOOM..
back for pre 2.0 days.. well until after the storm has passedt..
why cant we have that option in itunes... heck why not?
hey doctors will always have beepers to get in contact with.. so hey the whole life death situation thing means it isnt that that THAT bad.. but hey everyone needs there cell phone and people use cell phones.. this one in particular for business.. so maybe we could have avoided some confrontation to some conference calls and clients.. etc... well regardless.. as easy for the update to have made the iphone in a way "bricked".. i think it should have been easy to restore to pre 2.0 .
windows has that option in its system restore feature...
download something that messes up your system? virus? update that doesnt work well with the OS?.. restore to an earlier date is an option in the control panel..
i think itunes need something like that with the iphone version..
last but not least..
i love my iphone :-D

uppers

Updated question: Both Mac & PC links possible??

I apologize right away for posting a new topic with my updated question. But I realized I didn't phrase it right to get any help.
The question is - is it possible make both Mac links and PC links available on one disk. They would be in separate chapters. (i.e., directing Mac users to this page and Pc to another) Anyone tried this.
thanks.

hi jujubes
I just realised I misled you in my replay to your earlier post due to my poor writing skills
to clarify:
I suggest using Intellidisc to create the links for playback on a PC
you would also use DVD@Access within DVDSP to create the links for Mac playback
the links will work when played back on both mac and PC from this single disc
the Intellidisc website gives all this in a tutorial at:
wwwintellidisc.com

Expired userPassword question

We are migrating from an older directory setup to 5.2 from 2005Q1. We developed a simple tool to allow a user to change their password. This tool binds to the directory as the user to verify the password and then changes the userPassword field with new data. On our current production system a user with an expired password can still change their password. On our new system (JES 2005Q1 with messaging and access manager), a user with an expired password cannot change their password. Is the behavior I see the new default for the directory server? If I can't change it is it best to catch the expired password return code and then bind with a proxy account?
Thanks.

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

Software Update Questions

Hi everybody,
I'm still relatively green in the computer world, so, I'm sure these questions are way to "rookie" for you. Nevertheless; here they are.
Software Update Questions:
1. What is J2SE 5.0 Release 4, version 4.0 (39.3 MB) and, is it necessary to install?
2. What is X11 Update 2006, version 1.1.2 (51.0 MB) and, is it necessary to install?
In case you need to know, I have Mac OS X (10.4.8) with a Verizon FIOS connection.
Thanks,
Wayhun
iMac Mac OS X (10.4.8)

J2SE 5.0 is the latest version of Java. Mac OS X originally ships with Java 1.4 and this gives you the opportunity to upgrade to the latest version.
It's an optional upgrade since there are many changes between Java 1.4 and java 5, so some people might prefer to hold off until they've verified their Java apps work with the new version. For most people, though, it isn't an issue.
X11 (also known as XWindows) is a standard GUI interface for Unix systems. If you're using X11 you'd probably alredy know about it and therefore wouldn't be asking this question. It's not going to cause any problems if you update it, but it won't offer any advantage unless you're running X11-based applications.

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

Acrobat 9.5.2 update questions

Nov. 15, 2012 - As Adobe sends there update notices, I updated yesterday morning and lost all functionality. Couldn't open a PDF, kept getting messages that my license had expired. Called Customer Support and after an hour on the phone, we uninstalled my Acrobat 9.0 Standard (download version) and then reinstalled it from my Adobe Order History online.
Then was told to update with 9.5.1 (not 9.5.2 which was what the upgrade was yesterday). Now, 9.51. will not install because of a message that reads: "The upgrade patch cannot be installed by Windows Installer because the program to be upgraded is missing, or the upgrade patch may update a different version of the program.
This is case no. 183809469 - a few questions regarding the install this morning:
Also, I was instructed to download Acrobat to my desktop (???), then it of course installed in my Programs Folder. Now I have a new 334 mb Adobe folder on my desktop and a new 884 mb folder under Programs, which I believe is new 9.0 program (its dated today). Can I delete the one on the desktop now?
Also have an original 334mb folder for Acrobat 9.0 on my C:/drive. which is from my 2009 install. Can I delete this now?

I hope you did not delete all the download files. If nothing else you should store a copy on a CD or DVD to archive the files. You can then also record the software key in case you need to do future installs. Do not expect for the download to be available in years to come, so you need to have the archive in case you have issues requiring a reinstall.
When the update from the Help menu does not do the job, you can download them from the web site provided. Be aware that most of the updates are not cummulative and you will need to install them in order.

EFI Update Question

Hey all.
I just have a question about the EFI update that i have been promted to install via the update function on my new MBP 2011.
But then when i read witch models that are affected, then my model is not amoung the affected models, so why do i need to install this update...?
Therefor my question is this...! Is there something "sinister" about the hardware, that i dont know about in my MBP 2011 edition, since this update is primarily for older MacBooks. So is it an "old" MacBook in disguise.....or just something everybody has to install...?

The EFI updates are designed to install Apple monitoring software so they can read your hard drive, your browser and record any ripped MP3 files or other copyrighted media you have.
This is the exact intention of why EFI was created by Intel at the behest of the media industry. The UEFI forum is run by the MIAA and RIAA lawyers, the same who now run the US Justice Department
http://www.wired.com/threatlevel/2009/04/obama-taps-fift/
http://www.uefi.org/about/
You have no access to EFI, it does exactly what it pleases, your OS X and programs you install have no control over it or even can tell what it's doing.
If EFI allows you to do something, it's because it is, it has the power to stop you as it sits between your OS and hardware.
Every wonder why you can't boot off certain OS X install disks? It's because of EFI.
Apple sent out a firmware update and disallowed any booting off 10.5 disks, try it!
Not only that, Apple has scrambled the airport wifi signals so you can't use sniffing software on another Mac to determine if EFI is making outbound connections.
Also Apple has turned off the Airports blinking light, or if you like the blinking, it blinks all the time without any regard to if there is a transmission going over it or not.
To add further insult, new wired keyboard from Apple require software installed, firmware in the keyboard can record your keystrokes.
The pieces to a fully secure, fully monitored, computing system is slowly being lowered into place.
In fact the iSight camera can be turned on remotely without the green light appearing for covert surveillance.
Apple has hired NSA expert David Rice to lead it's computer security team, you KNOW the NSA has backdoors
on the Internet
http://www.wired.com/science/discoveries/news/2006/04/70619
in Windows
http://slashdot.org/story/99/09/03/0940241/nsa-backdoor-creates-security-hole-in -windows
Do you really think the Mac has been ignored?
It just works better in EFI that's all.

Expired Updates Question

Similar Messages

Maybe you are looking for