SCCM reinstall issues with clients
After a reinstall and renaming of a machine, clients will show up in SCCM but not show the client installed or the GUID. In my logs, TESADPW004-11 is the client, RIVER42 is the (only) site server, and RSD is the (only) site code 1. The client IS installed 2. SMS Agent Host is running (automatically) 3. Old records of the same computer have been deleted 4. There are NO duplicate GUIDs (GUID pulled from the local machine and compared to All Systems collection in SCCM) 5.Client is assigned to the proper server GetCurrentManagementPointEx ClientLocation 6/14/2011 7:57:50 AM 1712 (0x06B0) Current Management Point is RIVER42.RSD.K12.PA.US with version 6487 and capabilities: <Capabilities SchemaVersion="1.0"> </Capabilities>. ClientLocation 6/14/2011 7:57:50 AM 1712 (0x06B0) 6. Client sees the MP (is there a problem that it does not see the site code in GP? Should I set something there too?) LSRefreshSiteCode LocationServices 6/14/2011 7:11:36 AM 2972 (0x0B9C) LSGetGPSiteCode LocationServices 6/14/2011 7:11:36 AM 2972 (0x0B9C) LSGetGPSiteCode: Failed to Get Site Code from Group Policy Reg key [Software\Microsoft\SMS\Mobile Client] (80070002) LocationServices 6/14/2011 7:11:36 AM 2972 (0x0B9C) ProcessPendingSiteAssignment LocationServices 6/14/2011 7:11:36 AM 2972 (0x0B9C) LSGetAutoAssignFlagFromWMI LocationServices 6/14/2011 7:11:36 AM 2972 (0x0B9C) Executing Task LSRefreshLocationsTask LocationServices 6/14/2011 7:11:36 AM 2972 (0x0B9C) LSSendLocationRequests LocationServices 6/14/2011 7:11:36 AM 2972 (0x0B9C) LSGetHomeMPFromWMI LocationServices 6/14/2011 7:17:36 AM 3344 (0x0D10) LSGetHomeMPFromWMI LocationServices 6/14/2011 7:23:09 AM 2200 (0x0898) LSGetSiteCodeFromWMI LocationServices 6/14/2011 7:23:09 AM 1840 (0x0730) LSGetSiteCodeFromWMI : Site code returned from WMI is <RSD> LocationServices 6/14/2011 7:23:09 AM 1840 (0x0730) LS Verifying message LocationServices 6/14/2011 7:23:09 AM 1840 (0x0730) LSGetHomeMPFromWMI LocationServices 6/14/2011 7:57:50 AM 1712 (0x06B0) 7. Client is registered (I think) RegTask - registration has timed out or must be cancelled. Setting timeout event. ClientIDManagerStartup 6/13/2011 2:09:57 PM 2396 (0x095C) RegTask - Executing registration task synchronously. ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) Reg Task: Client is registered, exiting. ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) Entering CCCMIDStartup::ExecuteInternal ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) Read SMBIOS (encoded): 3200550041003000330033003100370039004800 ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) Evaluated SMBIOS (encoded): 3200550041003000330033003100370039004800 ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) No SMBIOS Changed ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) SMBIOS unchanged ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) SID unchanged ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) HWID unchanged ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) Computed HardwareID=2:CC133A4D5B87C301FA69893138024FF8600C4F64 Win32_SystemEnclosure.SerialNumber=2UA033179H Win32_SystemEnclosure.SMBIOSAssetTag=2UA033179H Win32_BaseBoard.SerialNumber=2UA033179H Win32_BIOS.SerialNumber=2UA033179H Win32_NetworkAdapterConfiguration.MACAddress=00:23:24:12:FB:DD ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) Persisted hardware IDs in CCM_ClientIdentificationInformation=@: HardwareID1=2:CC133A4D5B87C301FA69893138024FF8600C4F64 HardwareID2=FBBA0600010000F8 ClientIDManagerStartup 6/13/2011 2:11:34 PM 2328 (0x0918) 8. Client can communicate with the MP BEGIN ExecuteSystemTasks('PowerChangedEx') CcmExec 6/14/2011 7:57:14 AM 2216 (0x08A8) Invoking system task 'PwrMgmtPowerChangedEx' via ICcmSystemTask2 interface. CcmExec 6/14/2011 7:57:14 AM 3572 (0x0DF4) END ExecuteSystemTasks('PowerChangedEx') CcmExec 6/14/2011 7:57:14 AM 2216 (0x08A8) Raising event: instance of CCM_CcmHttp_Status { ClientID = "GUID:8ad8952c-0ccc-45a1-8f5a-ad81170aab5e"; DateTime = "20110614115750.229000+000"; HostName = "RIVER42.RSD.K12.PA.US"; HRESULT = "0x00000000"; ProcessID = 1684; StatusCode = 0; ThreadID = 2456; }; CcmExec 6/14/2011 7:57:50 AM 2456 (0x0998) OutgoingMessage(Queue='mp_mp_hinvendpoint', ID={DD643336-6870-4B2B-BC4E-E18C63EFE737}): Delivered successfully to host 'RIVER42.RSD.K12.PA.US'. CcmExec 6/14/2011 7:57:50 AM 2456 (0x0998) Timer task started CcmExec 6/14/2011 8:00:43 AM 1376 (0x0560) Timer task finshed CcmExec 6/14/2011 8:00:45 AM 1376 (0x0560) Cached CCM (user, session) is: (,-1). CCMEXEC 6/14/2011 8:01:35 AM 1376 (0x0560) No logged on cached user during monitor task, trying to select. CCMEXEC 6/14/2011 8:01:35 AM 1376 (0x0560) ::SelectSession - Couldn't locate an active session. CCMEXEC 6/14/2011 8:01:35 AM 1376 (0x0560) 9. Everything looks fine in ccm.log on the server ======>Begin Processing request: "31PDHHWW", machine name: "TESADPW004-11" SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:08 AM 12328 (0x3028) ---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:08 AM 12328 (0x3028) ---> Attempting to connect to administrative share '\\TESADPW004-11.RSD.K12.PA.US\admin$' using account 'RSD.K12.PA.US\SMSadmin' SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:08 AM 12328 (0x3028) Waiting for change in directory "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:13 AM 4636 (0x121C) Received request: "B9R149C7" for machine name: "RHSFLPW-007" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:13 AM 4636 (0x121C) Stored request "B9R149C7", machine name "RHSFLPW-007", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:13 AM 4636 (0x121C) ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account RSD.K12.PA.US\SMSadmin (00000005) SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account RSD.K12.PA.US\SMSadmin (00000569) SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> Attempting to connect to administrative share '\\TESADPW004-11.RSD.K12.PA.US\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> Connected to administrative share on machine TESADPW004-11.RSD.K12.PA.US SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> Attempting to make IPC connection to share <\\TESADPW004-11.RSD.K12.PA.US\IPC$> SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> Searching for SMSClientInstall.* under '\\TESADPW004-11.RSD.K12.PA.US\admin$\' SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> System OS version string "6.1.7600" converted to 6.10 SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> Mobile client on the target machine has the same version, and 'forced' flag is not turned on. Not processing this CCR SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> Deleting SMS Client Install Lock File '\\TESADPW004-11.RSD.K12.PA.US\admin$\SMSClientInstall.RSD' SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) ---> Completed request "31PDHHWW", machine name "TESADPW004-11". SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) Deleted request "31PDHHWW", machine name "TESADPW004-11" SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) <======End request: "31PDHHWW", machine name: "TESADPW004-11". SMS_CLIENT_CONFIG_MANAGER 6/14/2011 6:00:15 AM 12328 (0x3028) And yet I still see this: http://imageshack.us/photo/my-images/32/ughr.jpg/ I assigned a reinstall task sequence to the old computer, it did its thing, but I forgot to assign a new name in the task sequence, so it came up with a MININT-blahblahblah name. I renamed the computer, then deleted the MININT in SCCM. Where am I going wrong here? Edit: This is interesting. MP_DDR.log shows no record of TESADPW004-11, but it does show its old name of MININT-07302A4 Full report from client MININT-O73O2A4, action description = Discovery MP_DdrEndpoint 6/13/2011 10:57:07 AM 8476 (0x211C) Ddr Task: Translate report attachment to file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box\DPOLMJJG.DDR" returned 0 MP_DdrEndpoint 6/13/2011 10:57:07 AM 8476 (0x211C) Mp Message Handler: copying attachment to C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box\DdrAttachmentO7TQIH43.xml MP_DdrEndpoint 6/13/2011 10:58:17 AM 9424 (0x24D0) Inv-Ddr Task: processing xml file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box\DdrAttachmentO7TQIH43.xml" MP_DdrEndpoint 6/13/2011 10:58:17 AM 8120 (0x1FB8) Full report from client MININT-O73O2A4, action description = Discovery MP_DdrEndpoint 6/13/2011 10:58:17 AM 8120 (0x1FB8) Ddr Task: Translate report attachment to file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box\1IOJAHFD.DDR" returned 0 MP_DdrEndpoint 6/13/2011 10:58:17 AM 8120 (0x1FB8) Mp Message Handler: copying attachment to C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box\DdrAttachmentPC3UQ6SZ.xml MP_DdrEndpoint 6/13/2011 11:11:18 AM 4300 (0x10CC) Inv-Ddr Task: processing xml file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box\DdrAttachmentPC3UQ6SZ.xml" MP_DdrEndpoint 6/13/2011 11:11:18 AM 9880 (0x2698)
June 14th, 2011 3:10pm

Hi, Please check the factors in the following blog: Troubleshooting issues where clients are not reporting Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |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.
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2011 12:43pm

It would appear that the issue is related to duplicate GUIDs or something of the sort. When I renamed the computer, deleted the old name, re-ran AD system discovery, then generated new GUID (scripted DelCert using ConfigMgrTools) it worked. Without running that tool, the client was installed, but it would still do the same as my above problem. So then the question is, why do these computer not pull new GUIDs automatically, even when there is no existing conflicting record?
June 20th, 2011 6:18pm

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

Other recent topics Other recent topics