How to Deploy Phantom Updates with System Center Configuration Manager
Have you ever wanted to deploy an update in Configuration Manager and went hay i don't see that in my list of updates? You probably started looking around checking to ensure your classifications and products were all filled out and noticed all were selected or the ones you required were selected and still nothing to be found.
Well if you have, you have been in the same boat as me until i realized how to fix this problem. Its maybe not as straight forward as you would think but the process is very easy to get these phantom updates synced up in WSUS so you don't have deploy them via software distribution etc.
1) First open up the Windows Server Updates Services Console.
2) Next lets expand Update Services --> Server --> Updates and select import updates from the actions pane on the right.
3) You will be redirected to https://catalog.update.microsoft.com once here install the Activex Control if this is your first time visiting the site.
4) Now lets search for our Phantom Update in this example i am going to use the recently released https://support.microsoft.com/kb/2775511 Update. Once found select "Add All" and View Basket.
5) Next we can simply select Import and the selected updates will be imported directly into WSUS.
6) Open the Configuration Manager Console and Expand Overview --> Software Updates --> All Software Updates and select "Synchronize Software Updates". After a few minutes you can monitor the wsyncmgr.log and verify your updates synced with your SUP.
7) You should now see your Phantom Update in the All Software Updates node in the ConfigMgr Console and can deploy it like any other update.
Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified
in the Terms of Use .
Comments
Anonymous
January 01, 2003
Nash is correct this is a limited release hotfix rollup which is why you wouldn't see this update regardless of how your WSUS is syncing. This is common and occasionally we release these sort of Phantom Updates that don't show up in WSUS.Anonymous
January 01, 2003
DJ - when you 'sync from Microsoft Update' with ConfigMgr, it is using the WSUS instance you configured during your initial setup to do the actual synchronization. The reason you aren't seeing this KB2775511 is that it is not a normal update, it is a 'hotfix rollup' (not to be confused with a 'update rollup'). Hotfixes and hotfix rollups are not published to the WSUS/SUP catalog. I hope that helps! NashAnonymous
January 01, 2003
You would need to Expire the update.Anonymous
January 01, 2003
you need to have the Classification and Product selected of the update you are trying to import. If you are trying to import a hotfix that will not work.Anonymous
March 14, 2013
Quick question, for your Sync Settings, do you sync from Microsoft Update? I do, and i'm guessing that's why I do not see the 2775511 updates in SCCM after running a Sync.Anonymous
March 14, 2013
I did run the import and see the suucessful download in wsyncmgr.log.Anonymous
March 12, 2014
Is there any way to remove an update that was added via this method?Anonymous
May 01, 2014
Hi
I'm about to try this but somehow i can't pull up my WSUS console. it shows this mmc error...
"MMC has detected an error in a snap-in and will unload it"...
-Report this error to MS, and then shut down MMC
-Unload the snap-in and continue running
Please help
ThanksAnonymous
June 04, 2014
The comment has been removedAnonymous
June 04, 2014
Apologies scratch that....I had the product correct..but not the correct classifications (derrr)
Thanks for this article!Anonymous
July 16, 2014
Thanks a lot mate!Anonymous
August 27, 2014
I have a problem to deploy an update imported through Update catalag.
After the synchronization with SCCM was done I’ve added KB2670838 to my deployment package with all others Windows 7 updates.
Now when I push this update deployment package,KB2670838 is stuck on downloading and prevents other updates
to install. In updatehander.log I'm getting message:
Bundle update (9f0ff821-ad6d-45bb-bb67-862147e1b599) is requesting download from child updates for action (INSTALL) UpdatesHandler 2014-08-27 09:25:25 4716 (0x126C)
CCacheManager::CCacheManager UpdatesHandler 2014-08-27 09:25:25 4716 (0x126C)
Any clues?Anonymous
December 24, 2014
I have been reading that there are issues with update 2670838. Is this update still required as its not a normal update from Windows update anymore? If its still required, is anyone experiencing issues with Aero on the desktop or messed up task bar etc?Anonymous
January 19, 2015
I have followed this procedure but can't get the updates in SCCM. Do I need to choose all categories to be able to see them?Anonymous
January 20, 2016
in our case we see the hotfix rollup KB2775511 after we followed the steps in this article but this hotfix rollup adds some issues for which you need additional hotfixes as mentioned in the KB2775511.
They are 2732673, 2728738, 2878378 but categorized as hotfixes in update catalog. Does any one have an idea of how to import these hotfixes into SCCM. I thought hotfixes fall under Critical updates category but looks like they have their own classification which we don't see it on SCCM SUP.