Hello, I recently upgraded from SMS 2003 to SCCM 2007. It was bumpy but I have it working again. I have a couple dozen clients that showup in the Console with No in the Clientcolumn. The other 200+ clients are okay. I have looked at several of these and they look okay to my non-SMStrained eye. SCCM Client has been installed. Lookingat the client log files, the client appears to be talking to the MP. I am not sure which log to check on the server side. I don't have the schema extended. We are using WINS for discovering the MP's. I have tried to reinstall the client from the Console, and checking the CCMSetup.log, it does reinstall the client. What obvious answer am I missing? Any ideas? Thanks.

Have you tried checking DNS entries for the touble machines, I had similar problems and cleaned alot of them up by clearing up old DNS records

Have you checked to see whether those clients send any DDR to the site server? (ccmexec.log on the client should show this action, for example: "OutgoingMessage(Queue=mp_mp_ddrendpoint', ID={.....}: Delivered successfully to host abc.com")

o Why does my Advanced Client not show as being installed in the All Systems collection, but it is installed? First, verify that the SMS Agent Host service is installed and running. If it is, the Advanced Client really is installed. If it doesnt show up in the All Systems collection, it might be either that the client is not assigned to a site or that the client cannot find the default management point in its assigned site. You can use the Advanced tab of the Systems Management program in Control Panel to verify that the client is assigned to a site. If not, you can configure the site code the client should be assigned to. If it is assigned to a site, view the LocationServices.log on the client (Windows\System32\CCM\Logs) to see if the client was able to retrieve the default management point for the assigned site. It may be that the management point installation failed due to lack of IIS or BITS services being installed prior to the management point role being assigned to the computer. ClientLocation.log to ensure that they are assigned to a site LocationServices.log to verify that they have found the default MP ClientIDManagerStartup.log to verify that they've registered with the site Ccmexec.log to verify that there are no HTTP errorsyou can also check the ccm.log file on the server side. On the server reports check the Run rhereport Computers that may share the same SMS Unique ID Make sure the comptuers you are looking for do not have the same GUID.

Okay, thanks for the help guys. It looks like I have some dupe SMS GUID's. Looking in the ClientIDManagerStartup.log I see this: <![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="09:22:54.509+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="740" file="regtask.cpp:1434"><![LOG[RegTask: Client is registered.]LOG]!><time="09:22:54.899+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="740" file="regtask.cpp:1441"><![LOG[RegTask: Client is registered. Exiting.]LOG]!><time="09:22:54.915+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="740" file="regtask.cpp:1737"><![LOG[Read SMBIOS (encoded): 35004200380047004A0046003100]LOG]!><time="09:22:54.946+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="384" file="smbiosident.cpp:118"><![LOG[Evaluated SMBIOS (encoded): 35004200380047004A0046003100]LOG]!><time="09:22:54.962+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="384" file="smbiosident.cpp:185"><![LOG[No SMBIOS Changed]LOG]!><time="09:22:54.962+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="384" file="smbiosident.cpp:65"><![LOG[SMBIOS unchanged]LOG]!><time="09:22:54.962+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="384" file="ccmid.cpp:919"><![LOG[SID unchanged]LOG]!><time="09:22:54.962+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="384" file="ccmid.cpp:936"><![LOG[HWID unchanged]LOG]!><time="09:22:54.962+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="384" file="ccmid.cpp:952"><![LOG[Client settings prohibit local GUID generation, no smsid will be (re)generated.]LOG]!><time="09:22:54.962+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="1" thread="384" file="ccmid.cpp:1286"><![LOG[Smsid is missing but (re)generation is disabled.]LOG]!><time="09:22:54.962+300" date="03-18-2008" component="ClientIDManagerStartup" context="" type="3" thread="384" file="ccmid.cpp:1306"> Anybody know if resetting GUID's in SCCM 2007 is the same as SMS 2003? Thanks.

If the SMS Agent Host servcie is running, then the client is installed, so no need to look at the Ccm.log. However, if it is an upgrade scenario, then yes, it would be valuable, if using push. Other than that, yes, the other logs are proper to view, plus if all else is good, then Ccmexec.log to see if there any HTTP errors. Usual reasons for this scenario (client installed but not listed as a client in the console) include: * Client not installed (not the case here as the agent is running) * Client not assigned (can validate in ClientLocation.log) * Client can't find the default MP (can validate in LocationServices.log) * Client can't register (can validate in ClientIDManagerStartup.log) * Client can't communicate with the MP (Ccmexec.log) On the site end: * Boundaries not set correctly * AD not extended and no SLP

The last two lines of the log indciate a GUID needs to be created, but can't due to some local setting. I'm not familiar with any settings that might prvevent this. I'll see if I can find anything out on it.

Please post back on this when you can Wally, I have run into the same error, and quite a few machines with duplicate sms GUIDS, need to know a new procedure if deleting the old smsconfig.ini file and restarting the sms agent host will not fix. thx

Hi guys, We are also experiencing the same problem. We have upgraded our SMS2003 clients to SCCM, the client has installed OK, log files look good and the client system appears to be good. However in the SCCM console they are appearing as "Assigned" but client "No". We have tried repairing clients several times with no joy. We managed to get it working by running the SMS tool "ccmdelcert.exe" onthe clients. This worked! The client then changed to "Yes". Is there any right-click tool that can do this for SCCM?? Hope this helps. Samir

Wally, have you found anything on this? I get the same on some machines when deleting the smsconfig.ini and reinstalling client

I had a similar issue. The machine was trying to use a GUID from SMS 2003 and would not register with the SCCM server. I uninstalled the client, deleted the Windows\Smscfg.ini and re-installed the client. All is working on it now.

Surprise Surprise, i have been having this same problem with clients that are actually installed, but display as not installed, and not approved.... I ran the query to verify computers that may be sharing the same SMS Unique ID, and discovered 196 entries...conveniently the same number of clients i ahve in my collection that are displayed as not being installed or approved. There are some replies here that indicate running a sms tool on the client to solve the problem, but is there not a way to initiate this maybe from the SCCM server, to alleviate me from visiting almost 200 machines? Thanks in advance,

My experience-I tried the following and found that machines were continuing to create duplicate GUIDS, so i modified it to run ccmdelcert (instead of tranguid) and delete the smsconfig.ini, then re-push the client to my collection based on non-client systems. We can't initiate a company-wide reboot, or logoff for all users, but as the script gets ran and the cleints are repaired, the issue is getting cleaned up. http://blogs.technet.com/smsandmom/archive/2007/11/07/duplicate-guids-fix-it-with-scripts.aspx My script: Set oWMI = GetObject("winmgmts:\\.\root\cimv2") Set oComputerSystem = oWMI.ExecQuery("Select Name from Win32_ComputerSystem") For Each oInstance in oComputerSystem oName = oInstance.name Next Set WshShell = WScript.CreateObject("WScript.Shell") Set filesys = CreateObject("Scripting.FileSystemObject") Dim arrFileLines() i = 0 Set objFSO = CreateObject("Scripting.FileSystemObject") Set objFile = objFSO.OpenTextFile("\\scriptpro\netlogon\tools\DuplicateGuids.txt", 1) Do Until objFile.AtEndOfStream Redim Preserve arrFileLines(i) arrFileLines(i) = objFile.ReadLine i = i + 1 Loop objFile.Close For l = Ubound(arrFileLines) to LBound(arrFileLines) Step -1 If UCase(arrFileLines(l)) = oName Then If filesys.FileExists("c:\Windows\smscfg.ini") Then filesys.DeleteFile("c:\Windows\smscfg.ini") CreateFlagFolder End If End If Next Sub CreateFlagFolder If filesys.FolderExists("C:\Package\Delcert") Then CreateFlagFile Else If filesys.FolderExists("C:\Package") Then Set folder = filesys.CreateFolder("c:\Package\Delcert") CreateFlagFile else Set folder1 = filesys.CreateFolder("c:\Package") Set folder = filesys.CreateFolder("c:\Package\Delcert") CreateFlagFile End IF End If End Sub Sub CreateFlagFile If NOT (filesys.FileExists("c:\Package\Delcert\TranGuid.txt")) Then WSHShell.Run "\\scriptpro\netlogon\tools\ccmdelcert.exe" Set filetxt = filesys.CreateTextFile("c:\Package\Delcert\TranGuid.txt", True) End If End Sub

Thanks David, I will give this a shot and see how it goes. The only thing i noticed, is that when you run ccmdelcert.exe rather than tranguid.bat, you do not restart the SMS agent service CCMEXEC...is this not necessary? thanks again,

Well i have tried this on a few systems, and some work...some dont. the whole scripting process seems to work, but the clients are not updating to "yes" and "approved" in configmgr. When i check the new SMSCFG.ini file, there is no SMS unique identifier listed? I even try the script again, but to no avail...same results. I am having a hard time figuring out why there is no sms unique identifier in my smscfg.ini. Any suggestions? thanks again

Derek, i can't report 100% success, but this has worked on most of my systems, I found that if all I did was restart the sms service, the client wouldn't actually generatea new GUID, so I re-run the install/push. This has worked.

In my case, this was related to the sms certificates. Although running delcert on an installed client would SOMETMES remove the certificates, often it ran without removing anything. Either way, accessing the certificates for the local machine through the mmc snap in, and manually deleting them, i was able to delete the smsconfig.ini, and restart sms agent host to successfully generate a new, unique GUID, this can be done locally or remotely.

sorry, i was away for a couple few weeks. I also had the same problem where it did not remove the certificate, and a lot of manual intervention was required. Upon returning from holidays, i now noticed that when i click "show counts", I have "Total number of clients in collection:77" and "total number of non-obsolete clients in collection: 76" before i left, ALL these clients use to be in "total number of clients in collection: 153"...what is the difference between these two entries? i cannot seem to find an answer anywhere. Thanks in advance,

I have exactly the same issue with several clients after upgrading from SMS to SCCM. After reading all threads in this post I tried simply running CCMCLEAN.EXE from the old SMS site server and re-installing the SCCM client. It has been working so far. Clients are showing up in the collections with the client installed flag "yes". On a large scale you could runccmclean.exe from a GPO. I didn't see ccmclean on the SCCM install but the SMS one appears to work for the SCCM client just fine. Good luck to all upgrading.

Thanks for the info! My upgrade is kind of wonky...We used to run (prior to my time) sms 2003, but it was decomissioned. The client is still installed on most of our PC's, and from what i have discovered, also a part of our default images. Does the CCMCLEAN.exe have to be run from the old SMS site server?...because it is no longer existent. Thanks!

CCMCLEAN.EXE is available on the SMS 2003 product CD in the SMSSetup\Client\i386 folder. If ound this article about it. http://www.microsoft.com/technet/sms/2003/library/spgsms03/spsms16.mspx If you don't have the SMS 2003 CD or access to the product download you can get ccmclean from the SMS toolkit and that can be found here. http://technet.microsoft.com/en-us/sms/bb676787.aspx Happy cleaning

Configuration Manager does not use CCMClean.exe any longer. That's why we don't have one for Configuration Manager. Now, to remove the Configuration Manager client, you run: ccmsetup.exe /uninstall

I do have the same problem, but in my envirnment ALL clients show up in the management console, but NO client says it is installed. However the push installation of the Client went well on all machines. They are really installed! I begint o get frustrated. Since I am working on the SCCM installation for a week now...

I do have the same problem, but in my envirnment ALL clients show up in the management console, but NO client says it is installed. However the push installation of the Client went well on all machines. They are really installed! I begint o get frustrated. Since I am working on the SCCM installation for a week now...

Have this issue on about 8.3% of my clients (125/1500, mostly servers). Checked all logs. Every one of the 8.3%, I'm able to see where it's assigned to an MP, all actions are available, boundaries are properly assigned, all logs mentioned by Wally are in the clear. I guess I should probably bite the bullet and call PSS. However, as much as Wally seems to know about SCCM, he never seems to be staffing the phones.

ChrisMullins wrote: I guess I should probably bite the bullet and call PSS. However, as much as Wally seems to know about SCCM, he never seems to be staffing the phones. That's okay, they have some really knowledgable guys on the SCCM support team. I have had nothing but positive experience with them. I will however admit that there are a couple I know by name that I prefer to talk to ;-) because they are just good, they are GREAT.

What is the support number for SCCM technical issues?

I too am having the same problems with a small percentage of clients in my environment and was curious to know if anyone resolved this issue fully or received a possible fix for this issue. I have checked the relevant logs and the only one that I see an issue with is the ClientIDManagerStartup log which shows the following: RegTask: Server rejected registration request: 3 RegTask: Initial backoff interval: 1 minutes RegTask: Reset backoff interval: 257 minutes Already refreshed within the last 10 minutes, Sleeping for the next 7 minutes before reattempt. GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSE Computed HardwareID=2:F6B477032583CC7124C7211AEB18AB033F5B62E4 Win32_SystemEnclosure.SerialNumber=<empty> Win32_SystemEnclosure.SMBIOSAssetTag=<empty> Win32_BaseBoard.SerialNumber=None Win32_BIOS.SerialNumber=VMware-50 35 04 f9 2f fa c4 fe-08 ee ad d6 07 45 46 c4 Win32_NetworkAdapterConfiguration.MACAddress=00:50:56:B5:53:76 RegTask: Client is not registered. Sending registration request... This is repeated over and over.

Is anyone else experiencing this issue because I have probably about 125 out of 130 that are not showing up installed but the last line in the ccmsetup.log says installation successfull, deleting the ccmsetup service. I am wondering if i need to reboot the workstations because a handful showed up this morning as installed as opposed to none yesterday.

With all of the log checking going on here, to no avail, I too had an issue with >5000 clients. A pattern I noticed was that about 25% of them installed easily through either manual scripting using GPO, PSExec and also client push, but they still did not show up in the console as "Client-Yes". One item that everyone with an answer seems to have overlooked is...... (drum-roll) CCMDelCert. I struggled with the issue for a week and simply "remembered" CCMDelCert as another tool. After having ran CCMCLEAN before pushing the SCCM Client, I ran CCMDelCert remotely with PSExec and within minutes my clients showed up as "Client-Yes".

I have experienced the exact same issue and used the following procedure to fix it: Using SMS/SCCM Collection Commander and targeting our SMS00001 collection (Because we had 4500 discovered devices but only 244 reflected as clients), I used "Client actions > Inventory Actions > Refresh DataDiscoverRecord(DDR)" and 5 minutes later the stats has already changed to 4500 discovered and 2712 clients