We are in the first stages of rolling out 64-bit Windows 7 machines across our estate. A few test machines went out to users and were discovered to not be communicating with SCCM properly - Run Advertised Programs was empty and didn't show our company name, and they showed as 'client: no' in the console. The cause of this was found to be a Restart Machine step in the task sequence which restarted into the WinPE environment rather than in the newly installed OS, leaving the client in provisioning mode. I've now fixed this and new machines built with the task manager are working fine. However, some of the computers out there with the wrong setup are refusing to talk to SCCM properly. For some of the machines, doing the following fixed the problem: - - delete machine from SCCM - run full system discovery - update collection membership - right click Install Client, Always Install - confirm installation in ccmsetup logfile - right-click and ran Hardware Inventory and Machine Policy Retrieval tasks using Right Click tools (I know this isn't officially supported, but am providing the information so you've got the whole picture) - update collection membership This set some of the computers to showing as 'Client Yes, Approved Yes, Assigned Yes' in the console. However, for the rest of them, no amount of deleting, rediscovering and reinstalling the client makes a difference, and they appear as 'client no, approved n/a, assigned yes'. We are running R3 and the site is in Mixed Mode. The server is Windows Server 2008, sp2. ClientLocation.log on an affected machine shows that it is communicating with the server and locationservices.log shows the correct site code. The inventoryagent.log shows a lot of messages such as the following: Collection: Class "Win32_ServerComponent" does not exist out. InventoryAgent 10/07/2012 17:12:25 7952 (0x1F10) Failed to get IWbemService Ptr for \\localhost\root\Microsoft\appvirt\client Namespace: 8004100E Inventory: 16 Collection Task(s) failed. I think these are probably normal in a 64-bit system but am including them in case they're useful info. I've looked at this webpage, which was how I found the problem with the restart step: http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspx I'm concerned by the fact that the affected machines don't appear to have the HKLM\SOFTWARE\Wow6432Node registry key on them. I'm starting to think we might need to rebuild the affected machines, but since I got it working ok on some of them, am hoping there's another way out - the users are heavy duty developers and rebuilding their machines would cause them serious inconvenience. Is anyone able to help me out with this and suggest other things I could try? I'm worried this is indicative of a deeper problem and would like to get it resolved now before we start the rollout proper. Do let me know if there's any additional info I should include. Many thanks! M

Try stopping the WMI Service on the PC's. Navigate to C:\Windows\System32\wbem and delete or rename the Repository folder. Start the WMI service backup and wait. This kind of gives WMI a kick in the guts, and resets everything. CCMSetup should launch a repair process and everything should be good to go. Are all of the clients showing an assigned site code in the SCCM Console? Cheers.

I would look at WMIDiag. http://www.microsoft.com/en-us/download/details.aspx?id=7684, it will review your WMI and give you some suggestions. http://www.enhansoft.com/

Many thanks for this! I have now resolved my issue but I will definitely use this in the future. Thanks M

Hi, I seem to be having a similar issue, again this is only on a few Windows 7 64bit systems, strangely enough I am running on 64bit and had no issues with the installing the client to my system, nor do we have any issues with installing on to server 2008 R2. I have tried your suggestion Missred with running the regsrv32, but this has not resolved it. I have a feeling that it is something that has come down to WIndows 7 64bit systems as it is only those now that are having the issue with installing the client. I tried the suggestion from Adrian " PC's. Navigate to C:\Windows\System32\wbem and delete or rename the Repository folder. Start the WMI service backup and wait." but to no avail. I have also run the WMIDiag as suggested, only thing is I am not too sure what I am looking for, it does mention "Error: WMIDiag detected issues that could prevent WMI to work properly!" Any other suggestions, as I mentioned this issue now only seems to be impacting on newly created Windows 7 64Bit systems. Thanks for any suggestion, I am hoping to get this resolved as we have several Windows 7 systems that we need to ensure is running 64bit to utilise greater memory resources rather than restricting to 32Bit. cheers Pg