Answered by:
Unable to connect to WMI on remote machine "COMPUTER", error = 0x80070005.

Question
-
According to the ccm.log on the Primary Site Server I get this error message. There are only a handful of machines in the environment that indicate this error. The SCCM 2012 is being installed on about 98% percent of the machines on the network successfully. Any thoughts?
Unable to connect to WMI on remote machine "COMPUTER", error = 0x80070005.
Here are some things I have already checked.
1) SCCM account does have access to the computer
2) Firewall is turned off on the machine
3) I can connect to the admin$ share on the local machine
Wednesday, November 13, 2013 3:43 PM
Answers
-
WMI is probably screwed up.
0x80070005 = Access Denied
Troubleshoot or rebuild WMI.
http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx
http://support.microsoft.com/kb/875605
http://technet.microsoft.com/en-us/library/cc180763.aspx
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
- Marked as answer by Joyce L Monday, November 25, 2013 10:52 AM
Wednesday, November 13, 2013 5:18 PM
All replies
-
This is quite normal in an environment. Client push will never achieve 100% penetration. You should also use other client installation methods to complete
1. manual
2. PSExec
3. computer startup script
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Wednesday, November 13, 2013 4:04 PM -
I agree with you but WMI errors dont seem to be normal. The Manual process does not work as well.
Wednesday, November 13, 2013 4:08 PM -
Unfortunately WMI errors are very "common" (not normal). If a manual installation is failing examine the ccmsetup.log file on the client.
(By manual, I mean copy the client files to the PC and launch ccmsetup.exe while logged in locally)
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Wednesday, November 13, 2013 4:12 PM -
It does work manually but I was hoping to find a solution to the WMI issues.Wednesday, November 13, 2013 5:11 PM
-
WMI is probably screwed up.
0x80070005 = Access Denied
Troubleshoot or rebuild WMI.
http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx
http://support.microsoft.com/kb/875605
http://technet.microsoft.com/en-us/library/cc180763.aspx
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
- Marked as answer by Joyce L Monday, November 25, 2013 10:52 AM
Wednesday, November 13, 2013 5:18 PM