SCCM unable to install 3 updates out of 547 on select machines

[SamL]

We have a single server site setup with SCCM 2012 SP1 5.0.7804.1000.

 

We have 3 updates that fail to download/install to 10 Win7 x86 workstations. The rest of the computers have successfully installed these patches.

The patches are:

• kb2719857
• kb2732059
• kb2741355

I have confirmed that these patches are in the DP and the download URL from the logs successfully resolves to the DP.

These patches have installed perfectly on 72 machines but fail on 10 of the total 82.

 

Here are the symptoms:

1. Client computers show Downloading (0% complete) in software center.
2. You can successfully install these updates manually from windows updates.
3. SCCM shows "Failed to install update(s)" with an error description of "Item not found"

 

I have troubleshot this for two days and at this point I feel like I'm missing something obvious. Does anybody know why these 3 patches refuse to install on 10 computers but install perfectly on 72? Please help!

Let me know what logs you wish to see.

[Peter33]

Try to repair BITS on the Clients (stop BITS Service, delete C:\ProgramData\Microsoft\Network\Downloader, start BITS Service). If that doesn't help uninstall the SCCM Client, reboot and then push the Client again.

[SamL]

Peter33, thank you for the suggestions! The BITS fix didn't work but it showed new symptoms. Instead of downloading 0%, it fails immediately. I uninstalled the client from the workstation and pushed the install from the SCCM console and now its failing to communicate properly with our SCCM server. What's odd is I can push a new install from the SCCM console, but after its done the console says its offline.

 

This is what the client shows now.

 

[Peter33]

Did the machine policy cycle work correctly? There should be no visible deployments in the software center if the client can't communicate with the server.

Is your Client Firewall possibly blocking the communication?

 

If everything fails you can still try to repair WMI too on your client. Uninstall the client again, reboot, stop the winmgmt service, delete c:\Windows\system32\wbem\repository, start winmgmt, install the client again.

[SamL]

Did the machine policy cycle work correctly? There should be no visible deployments in the software center if the client can't communicate with the server.

Is your Client Firewall possibly blocking the communication?

 

If everything fails you can still try to repair WMI too on your client. Uninstall the client again, reboot, stop the winmgmt service, delete c:\Windows\system32\wbem\repository, start winmgmt, install the client again.

 

Thank you again Peter33 for your help.

 

I ran through this process to repair WMI. http://windowsxp.mvps.org/repairwmi.htm

You are correct, it cant communicate with the server and it can't see the deployments to its collection. The Configuration Manager Properties tabs are showing up now after the WMI fix but its still having a hard time communicating to the SCCM server.

 

I verified this is not a problem with SCCM on the server side because a freshly imaged Win7 x86 installed these problem updates and can see its deployments.

 

In the LocationServices.log its showing "Client is not assigned to a site. Cannot get portal info." I'm confused. The site code in the configuration manager properties is correct. Ideas?

Also showing:

<![LOG[unable to get SMS_MPInformationEx.MP="Unicron.DOMAIN.COM" of [unicron.DOMAIN.COM] from WMI due to error 0x80041002]LOG]!><time="11:17:51.971+300" date="07-03-2013" component="LocationServices"

[Peter33]

Hi Sam,

 

since the repository repair didn't work your WMI itself seems to be broken.

First thing would be to find out what your 10 Clients have in common. Like a package a or application that is only deployed to them. Maybe some snapshot Installation with unwanted registry keys, which are messing up the WMI on the Clients. It's hard to believe that the Clients randomly break without any reason.

 

You can also try to install WMF3.0, if not already installed, to see if it will fix anything.

 

The final solution would be of course the reimaging. But without knowing the source of the problem, it's more like a woraround than a solution.

[SamL]

Hi Sam,

 

since the repository repair didn't work your WMI itself seems to be broken.

First thing would be to find out what your 10 Clients have in common. Like a package a or application that is only deployed to them. Maybe some snapshot Installation with unwanted registry keys, which are messing up the WMI on the Clients. It's hard to believe that the Clients randomly break without any reason.

 

You can also try to install WMF3.0, if not already installed, to see if it will fix anything.

 

The final solution would be of course the reimaging. But without knowing the source of the problem, it's more like a woraround than a solution.

 

 

Peter33, thank you again.

The WMF download doesn't like the computer. Maybe because its Win7 Enterprise?

 

The fact that Software center is failing to install properly after communication to the SCCM server has been confirmed makes me believe you are correct. There is a WMI problem.

 

The only question that remains unanswered is, why can we manually install these updates? The answer will have to remain unknown because its far more time consuming to continue troubleshooting then to simply hop onto each of the 10 computers manually. Besides, we are replacing most of the computers this fall.

 

Thank you for your help Peter33!

[Peter33]

Hi Sam,

 

yer welcome.

WMF3 requires to have .NET4 installed. Otherwise it will fail to install. Rather use .NET4.5 though because it will replace also the infamous .NET4 Client Profile. Only one Version now in 4.5 (except the SDK Version of course).

The Manual install probably works because it doesn't use any WMI calls, like the scripted SCCM Installation.