I've setup the Client push method, and it has worked for most of my computers. However, I have a couple of machines that it is not working on. Below is the ccm.log entry for the latest manual push to one of these clients. Anyone have an idea what I should be looking at? Received request: "BERYETGC" for machine name: "HQFILE1" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:19 AM 2744 (0x0AB8) Stored request "BERYETGC", machine name "HQFILE1", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:19 AM 2744 (0x0AB8) ----- Started a new CCR processing thread. Thread ID is 0x6b8. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:21 AM 2744 (0x0AB8) Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:21 AM 2744 (0x0AB8) Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:21 AM 2744 (0x0AB8) Waiting for change in directory "d:\Program Files (x86)\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:21 AM 2744 (0x0AB8) ======>Begin Processing request: "BERYETGC", machine name: "HQFILE1" SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:21 AM 1720 (0x06B8) ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:21 AM 1720 (0x06B8) ---> Attempting to connect to administrative share '\\HQFILE1.DOMAIN\admin$' using account 'DOMAIN\account' SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:21 AM 1720 (0x06B8) ---> The 'best-shot' account has now succeeded 1 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) ---> Connected to administrative share on machine HQFILE1.DOMAIN using account 'DOMAIN\account' SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) ---> Attempting to make IPC connection to share <\\HQFILE1.DOMAIN\IPC$> SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) ---> Searching for SMSClientInstall.* under '\\HQFILE1.DOMAIN\admin$\' SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) CWmi::GetFirstObjectFromQuery(): ExecQuery() failed. - 0x80070005 SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) ---> Unable to get Win32_OperatingSystem object from WMI on remote machine "HQFILE1", error = 0x80070005. SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) ---> Deleting SMS Client Install Lock File '\\HQFILE1.DOMAIN\admin$\SMSClientInstall.SAC' SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) Retry request id for "BERYETGC" set to "HQFILE1_DOMAIN" SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) Stored request "HQFILE1_DOMAIN", machine name "HQFILE1", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8) <======End request: "HQFILE1_DOMAIN", machine name: "HQFILE1". SMS_CLIENT_CONFIG_MANAGER 11/30/2010 8:23:22 AM 1720 (0x06B8)

WMI or firewall issue problably. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Well, the Windows firewall was on, so I turned that off, and rebooted the box, and I'm still getting the 0x80070005 error. What I don't understand is that this box was created at the same time all the others were, that worked... How can I troubleshoot WMI? I know next to nothing about it.

You need to make sure that the client push account (or the site server computer account), can access \HQFILE1.DOMAIN\admin$ If not then you will not be able to initiate a client push. As John replied it can be firewall settings or corrupt WMI.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Logged into the SCCM box as the same account being used, I can go to Run, type \\hqfile1\admin$ and the window opens up. The account is a domain admin account, so I can't figure out what the issue is there. As I mentioned, the Windows firewall on HQFile1 is now completely turned off, to remove that factor. Also as mentioned, how can I figure out if WMI is corrupt? And the corruption would be on the HQFile1 box, right?

Yes, that would be WMI on the HQFile1 box. Can you install the client manually by running ccmsetup.exe on the box?Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Yes, moving the Client directory over to HQFile1, and running ccmsetup worked. It is now showing as Yes, under Client in the console. What does that tell me, though? WMI messed up?

Hi, The WMI connection also should be possible from the SCCM server to the client with the account used for Client push installation (You can use WbemTest and try connecting to \\<Clientname>\root\cimv2 and make sure you are able to remotely connect to client WMI)Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.