WMI Issues preventing client installs on MANY systems - Help!
We have many systems at our company's two main office not installing the SCCM client due to WMI issues on the local client. Well, I think its WMI issues. However the computer works perfectly fine to the user with no issues. All systems are Win XP w/ SP3. Firewall on all system are turned off via GPO. The domain administrator account is specified for client push installation. From the SCCM central site, I can connect to the systems ADMIN$ share with no issues. In the ccmSetup folder, there are no SCCM client install files or logs. Below is a snippet I'm seeing on almost every client that fails to install: ======>Begin Processing request: "Dont-Floor-XP9_onto_COM", machine name: "Dont-Floor-XP9" SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:27 AM 3044 (0x0BE4) ---> Trying the account stored in the CCR (index = 0x1) SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:27 AM 3044 (0x0BE4) ---> Attempting to connect to administrative share '\\Dont-Floor-XP9.Octn.com\admin$' using account 'Octn\administrator' SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:27 AM 3044 (0x0BE4) ---> Connected to administrative share on machine Dont-Floor-XP9.Octn.com using account 'Octn\administrator' SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:28 AM 3044 (0x0BE4) ---> Attempting to make IPC connection to share <\\Dont-Floor-XP9.Octn.com\IPC$> SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:28 AM 3044 (0x0BE4) ---> Searching for SMSClientInstall.* under '\\Dont-Floor-XP9.Octn.com\admin$\' SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:28 AM 3044 (0x0BE4) ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account Octn\sccmsoftinst (00000035) SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:28 AM 5096 (0x13E8) ---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account Octn\sccmsoftinst (00000035) SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:29 AM 5096 (0x13E8) ---> The device 192.168.189.46 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:29 AM 5096 (0x13E8) ---> Trying the account stored in the CCR (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:29 AM 5096 (0x13E8) ---> Attempting to connect to administrative share '\\temoseri-lsu-10.Octn.com\admin$' using account 'Octn\sccmsoftinst' SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:29 AM 5096 (0x13E8) CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:29 AM 3044 (0x0BE4) ---> Unable to connect to WMI on remote machine "Dont-Floor-XP9", error = 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:29 AM 3044 (0x0BE4) ---> Deleting SMS Client Install Lock File '\\Dont-Floor-XP9.Octn.com\admin$\SMSClientInstall.BOS' SMS_CLIENT_CONFIG_MANAGER 2/20/2011 5:12:29 AM 3044 (0x0BE4) I think the key here is ---> Unable to connect to WMI on remote machine "Dont-Floor-XP9", error = 0x800706ba This error means unable to connect RPC service. Not sure if its a WMI issue or RPC issue? We had similar issues with SMS, but didn't believe it was so widespread which it really is. Any thoughts onto whats going on?
February 20th, 2011 8:50am

Also note if you are installing the client using client push on remote system you must open the random RPC ports on any firewall between the client and the server. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
Free Windows Admin Tool Kit Click here and download it now
March 11th, 2011 11:03am

Also note if you are installing the client using client push on remote system you must open the random RPC ports on any firewall between the client and the server. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/| I thought it was just UDP and TCP Port 135 that was needed?
March 11th, 2011 3:36pm

Also Dynamic RPC is needed. If there is a firewall between the client and server such like TMG. Make sure RPC filtering is setup right. Dennis de Roo
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2012 9:36am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics