How to fix the SMS
client GUID issue
1.If the client status unknown in the SMS console after
installing the SMS client (make sure that CCM setup.log shows the succeeded
message)
2.Use the psexec tool to login to the machine locally
Usage of the tool
Psexec \\IPadress of the machine (space) cmd
Make sure that open client
id manager startup.log in the client system to observer the changes
Patch of the client id manager startup.log would be
c:\windows\system32\ccm\logs\
Below are the commands you should execute in the PSEXEC tool
a)
net stop ccmexec
b)
del "%windir%\Smscfg.ini"
c)
net start ccmexec
now open “client id
manager startup.log “ in client system and observe the message
Once you identify that you fixed the client guid , open the
sql and check the system status after few minits .
Use below query to
check the same.
SELECT Name0 AS
[Machine Name], User_Name0 AS [User Name],AD_site_name0 as [AD site code]
,creation_date0 as [AD discoverd date],
CASE Active0 WHEN '0' THEN 'InActive' WHEN '1' THEN 'Active' ELSE
'Unknown' END AS [Active Client],
CASE Client0 WHEN '0' THEN 'No' WHEN '1' THEN 'Yes' ELSE 'Unknown' END
AS [Client Status],
CASE obsolete0 WHEN '0' THEN 'No' WHEN '1' THEN 'Yes' ELSE 'Unknown' END
AS [Obsolete Client], DATEDIFF(D,V_GS_WORKSTATION_STATUS.LASTHWSCAN,GETDATE())
AS [HW SCAN DIFFERENCE]
FROM
v_R_System LEFT JOIN
V_GS_WORKSTATION_STATUS ON V_R_SYSTEM.RESOURCEID =
V_GS_WORKSTATION_STATUS.RESOURCEID
WHERE (Name0 IN (
'Systemanem'))
