We have many systems at our companys two main office not insalling 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 isues. All systems are Win XP w/ SP3. Firewall on all system are turned off via GPO. The domain administrator account is specifed for client push installation. 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?