SCCM 2007 R2 Unable to connect to WMI on remote machine error = 0x800706ba
After deploying System Center Configuration Manager (SCCM) 2007 R2, and pushing out some Client Agents to Windows 7 machines on the local LAN. We tried to do some testing of clients on a separate subnet. When trying to use the Client Push install we ran into some issues.
Using SMS Trace, we followed the ccm.log file during the push operation which revealed the following error messages:
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba~ $$<SMS_CLIENT_CONFIG_MANAGER>
---> Unable to connect to WMI on remote machine "WINDOWS-7VVJKST", error = 0x800706ba. $$<SMS_CLIENT_CONFIG_MANAGER>
After some troubleshooting I identified that the SCCM server wasn't correctly resolving the server name. To fix the issue I added the domain name suffix to the network interfaces DNS suffix list. After doing this SCCM correctly resolved the name and deployed the agent.
Some other things to check, with this are any firewalls between SCCM and the client, including windows firewall. File and Print Sharing needs to be enabled, permissions can also cause similar issues. You can test WMI using the wbemtest.exe tool and connect to WMI on the client from the SCCM server.
In the spirit of troubleshooting Client Push Install problems another issue was identified and fixed. When deploying to one particular client we found the following error message in the ccm.log file:
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e~ $$<SMS_CLIENT_CONFIG_MANAGER>
---> Unable to connect to WMI (r) on remote machine "Server1", error = 0x8004100e. $$<SMS_CLIENT_CONFIG_MANAGER>
After reviewing the log, the error number doesn't appear to be specific to the problem we identified on the server which was identified in the event log:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 1013
Date: 13/04/2010
Time: 8:33:45 AM
User: NT AUTHORITY\SYSTEM
Computer: Server1
Description:
Product: Configuration Manager Client -- There is not enough available disk space on C: to complete this operation. Installation requires at least 90MB free disk space.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 32 36 30 39 45 44 46 {2609EDF
0008: 31 2d 33 34 43 34 2d 34 1-34C4-4
0010: 42 30 33 2d 42 36 33 34 B03-B634
0018: 2d 35 35 46 33 42 33 42 -55F3B3B
0020: 43 34 39 33 31 7d C4931}
Which made this an easy one to fix.




