This week Microsoft rolled out a BIG hotfix (90 hotfixes) rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1. To better understand all the goodness it gives you check out the AskPFEPlat blog or go to the source of one of the guys who helped put it together, my fellow PFE Jeff Stokes. It is being distributed as an enterprise hotfix and so I think it likely that a lot of you folks running SCCM to manage your enterprise might want to roll out this hotfix. One big advantage that comes to mind is including it in your OSD image capture to cut down on patch install time for future deployments. The trick is that “out of the box” you can’t deploy this. It does not sync to WSUS and your SCCM software update point (SUP) automatically. There are some simple steps you can take to get it there, however.
3-14-13 update - Added links to AskPFEPlat and Jeff Stokes' blogs along with warning about using WSUS admin console
3-14-13 update #2 - added clarity about fix classification
Nice write up, thanks.
Thanks. This makes things easy :)
Did you verified if Offline Servicing is working as well for this update? Using Offline Servicing I receive the following message - Not applying this update binary, it is not supported - while other updates injected successfully. Is this because the update comes with 2 binaries? Using DISM I can insert KB2775511 with success to my wim images.
Ronny - I did not try offline servicing with this. See the criteria on blogs.technet.com/.../3418243.aspx. With all this KB contains I suspect that it is not CBS based. You probably have to include it in a build and capture.
A little bit more searching and I found it on the Ribon bar ;)
I just added this to my Windows 7 SP1 WIM via SCCM 2012 SP1 scheduled updates and it said it was successful. Looks like it works with offline servicing.
Pete - Good to know. Thanks for sharing that with everyone..., it saves me some time trying to setup the test myself. :-)
For those of you still using sccm 2007, importing via SCUP works.
Michael, we have to deploy this as a regular SCCM Deployment, not via SUP. Problem is, we don't see anything showing up on ARP, or on the computer, to tell if it is deploying--how do you inventory for the existence of this hotfix rollup?
We are deploying using this commandline: wusa.exe <filename>.msu /quiet /norestart , where filename = AMD64-all-windows6.1-kb2775511-v2-x64_ec18cc10e27faf443c17e7a8073c9eba773eb13e.msu
It should be in ARP - would expect to find something in CBS.log about it at that point...
Now that 2775511 has been updated to state that after installation you must install 2732673, is there a recommended deployment strategy for SCCM customers? I'm keen to deploy the hotfix rollup in our environment but according to this: blogs.msdn.com/.../roll-up-update-kb-2775511-reports-with-smb-2-0-data-truncation.aspx 2732673 will not be added to the Update Catalogue. It would be much nicer to be able to deliver both hotfixes in a single package as otherwise there will be a delay before 2732673 can be installed.
Stewart - That is a very good observation and question. At this time, I have no great answer to go with it. You could kick a patch install process followed by the new KB but all in one task sequence to minimize the delay between the two, but that's not a good scenario for many folks. You may just have to push out 2732673 as a SWDist on a collection setup to minimize the delta window between the two as much as possible.
That was the best solution I could come up with too. I was hoping there was a more elegant way of doing it but that approach will have to do. Thanks for your response.
KB2775511 is available in SUP, but KB2732673 is not. Now that KB2775511 is published, is KB2732673 still needed?