Geeky Stuff I Learned Today

This one has been bugging be for quite some time... Sometimes, when you've published an update from SCUP to WSUS as metadata only, it fails to publish the full content later and gives an error of "incorrect file digest". What's going on here? This is where the publisher has created an updated binary for the same release, but not updated the Origin File Digest in the metadata. When SCUP imports a update, it stores a SHA-1 Base64 hash of the file which is held in the SCUP database. When you go to publish "full content", it compares the hash of the downloaded file with that in the database. When the don't match, you get the file digest error. Ultimately, this is a mistake on the part of the vendor, but they're pretty inconsistent at fixing them (Dell being a particular offender). So how do we fix it to get that critical update out? Download the binary directly from the vendor Get the SHA-1 Base64 encoded of the file (I used online...

Massively helpful post here as to why I couldn't import drivers into SCCM from a de-duped drive. Things I'm bound to forget: Error importing drivers into SCCM 2012 SP1 :

Update: See bottom of post for another variation on this. Now here was a real barrel of laughs to track down and fix. The setup: Import the Dell Client catalogs into SCUP 2011 Publish them all to WSUS with automatic (effectively metadata only) Check for updates from a client machine Get Error 0x8024000f in Windows update Upshot of this is that WSUS is broken and by extension, so are software updates via SCCM. The culprit? Circular references in Dell's update catalog. How to fix: Turn on verbose logging for WSUS on a client PC  http://support.micro...723#letmefixit2 Check for updates Open c:\windows\windowsupdate.log Search for the word "cycle" Get the update ID that has the circular reference Find that update in SCUP and expire it (you may want to fix it, but I didn't bother as I don't need the affected updates) Publish the update again Go back to step 2 and keep repeating until Windows Update on the client PC works (I had about 8 wi...

In SCUP 2011, there's the Software Update Cleanup Wizard which will remove from WSUS any updates that are no longer in SCUP. Only one problem: if the update exists in WSUS, but the content isn't in UpdateServicePackages, the clean up fails as it can't verify the signature of the cab file. As the wizard doesn't care about the content of the file, it's quite easy to fool it. Open SCUP.log and find the error Create a folder in UpdateServicePackages that matches the folder of the missing content. e.g. \\WSUS01\UpdateServicesPackages\7d0f53e4-482e-462d-b81b-127941c32091 Find an existing cab file within the UpdateServicePackages folder and copy it into your new folder Rename the copied cab file to the name of the missing cab in the SCUP folder Run the SCUP Cleanup Wizard again Clean up success! Seems like a bug to me as removing the entry from the WSUS database shouldn't really care if the content exists.

Just had a issue where the SCCM 2012 R2 Console on Win 8.1 (x64) would no longer connect to the site server after installing MDT 2013 on my local machine. AdminUI.log complained about performance counters. Fix: c:\windows>cd syswow64 c:\windows\syswow64>lodctr /R c:\windows\syswow64>winmgmt.exe /RESYNCPERF Uninstall SCCM Console Reinstall SCCM Console All working again H/T  http://support.microsoft.com/kb/2554336?wa=wsignin1.0