I am getting the following error messages on about 10 out of 50 clients in a recently created site in SCCM: This is from the ClientIDManagerStartup.log: GetSystemEnclosureInfo failed (0x80004002) ComputeHardwareID failed (0x80004002). RegTask: Failed to create registration request body. Error: 0x80004002. The following error message shows up in CCMExec.log: Endpoint'PolicyAgent_PolicyEvaluator' return 0x80070057 from event notification The following error message show up in SMSCLIUI.LOG: WMI Query failed. Error 0x80004002 !!! WARNING - Client is currently unassigned or an error occurred retrieving the assigned site. GetAssignedSite() returned : 0X0 Unable to get CacheInfo. Error: 0X80070005 I have tried all the WMI repair steps I have found while researching the issue as well as uninstalling/reinstalling the client. We have thousands of clients reporting just fine. We brought in a new company into our SCCM enviroment and migrated their computer accounts into our domain. 15 percent of those new clients are having this issue. Please help!

How was the client installed? Are these systems within a boundary?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hi, For this error: RegTask: Failed to create registration request body. Error: 0x80004002. This can occur because of a missing registry key. It isn't related to SCCM but is needed by a function we use. Please do following steps on the problematic client: 1. Open Regedit 2. Goto: HKLM\System\CurrentControlSet\Services\TCPIP\Paramaters 3. Create a Reg_sz called 'Domain' 4. If it's a workgroup machine add a blank space as value. If it's domain machine add the name of domain 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.

Eric, I have the exact error with a couple of clients and they do have the registry key. Could there be something else that is causing the issue? GetSystemEnclosureInfo failed (0x80004002) ComputeHardwareID failed (0x80004002). RegTask: Failed to create registration request body. Error: 0x80004002 Error initializing client registration (0x80040222).

I have tried the following steps on a computer experiencing the same issue that I have not worked on yet. 1. I checked the registry setting (HKLM\System\CurrentControlSet\Services\TCPIP\Paramaters) on one of the clients that is having this issue, and that registry setting is there. 2. I uninstalled the client and deleted the CCMSETUP folder from C:\Windows\System32. 3. I then stopped the WMI service and renamed the C:\Windows\System32\wbem\repository to repository.old. I then rebooted the computer and re-installed the client. Same issue. I posted some screen shots and additional info here: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Systems_Management_Server/Q_26451054.html#a33646626 I really need to get the client functional on these systems!

They are installed with a logon script. Just as the other 800 or so systems in my environment have been. Yes, they are within a boundary.

@jeabou Have the same issue on a machine here. Not sure what the problem is, but it matches what you show on those screen shots. Were you able to find a solution for this issue? If so, what was it?