In my CM environment i have 900 clients. About 40 of them show the client as not being installed. When i run psexec on these clients i find that the client is installed and the adverts i am sending to these pcs are working. I installed a CM environment early this year to replace my SMS environment. Not thinking it would be an issue. Most of these client i figured might still be using the SMS client so what i did with a group of 20 is the following. On the console disable system discovery and client push to give me time to clean the 20 clients. On each client i removed the smscfg.ini file and ran ccmsetup \uninstall. After all 20 had that action performed i reenabled discovery and client push i left the server for a couple of hours to let it work. When i came back to the console all of the 20 were still in the same state. The client appears to be working but the server does not acknowledge it. The properties of the clients dont show mp_clientregistration or heartbeat which im sure has something to do with. * ClientLocation.log shows the proper MP assignment * LocationServices.log shows that client found the default MP * ClientIDManagerStartup.log shotly after the client was installed this shows up : RegTask: Client is not registered. Sending registration request... .......... then RegTask: Client is registered. Exiting. * Ccmexec.log show the following instance of CCM_CcmHttp_Status { ClientID = "GUID:49B13AA8-D642-48D6-8F37-61C7411CBA18"; DateTime = "20101001131702.071000+000"; HostName = "SERVERFQDN"; HRESULT = "0x00000000"; ProcessID = 452; StatusCode = 0; ThreadID = 2588; }; Not sure what else to look at. Other forums lead me to other logs but i cant find the point of failure.

dont show mp_clientregistration or heartbeat Yes, that is likely it. Look at the clientidmanagerstartup.log on those machines; if they are showing an error, work on that. If that's is clean (looks like any other normal healthy client), then look at inventoryagent.log. There are 3 basic things reported in inventoryagent.log, heartbeat ( ends in 00001} ) Hardware (ends in 0002}, and Software (ends in 0003} ) The one you care about is the 0001}. Check a broken computer vs. a normal computer, what happens after the 0001} action happens. I've had a few wonky clients where the only thing that wouldn't finish properly was heartbeat. The fix was to repair WMI in those cases. (I used Roger Zander Client Center, his WMIRepair)Standardize. Simplify. Automate.

All of the logs mentioned are similar if not the same as that of known working clients. The inventoryagent.log looks no different in that of the 'broken' client and that of a working one. I believe I found line you were refering too : Inventory: Opening store for action {00000000-0000-0000-0000-000000000001} ... Again compared to a working and non working client both appear to be the same. Will try the WMI repair anyway on a couple and see if it helps. Not sure how long it will take to see if it had an effect or not. I still cant find any issue on the client logs that i look at so i dont know where the issue is? Still trying to figure out why the heartbeat is not being detected. Thanks for the tips to start

Edit, oops: I think I have the ones wrong. Inventory: Opening store for action {00000000-0000-0000-0000-000000000001} that's Hinv, not heartbeat 003} is heartbeat. The parts to look at is comparing the next 10-15 lines or so; a healthy vs a non-healthy. I've seen non-healthy only return say... 3 or 4 "select whatever from". But a healthy one has 8-10 lines or so (I forget, I'd have to have a log in front of me to give the exact count). Standardize. Simplify. Automate.

i did notice that the other one was for hardware inventory too. Thanks for the correction. Does not look like WMI repair worked anyway on the clients i tried it on. I compared the 03} sections of the good and bad clients and they are almost identical except for file names and reported entries created ( difference of 1 ) They both say they were successfully sent to the MP Is there something in the CM server logs i should be looking for?

Do you have anything different for me to be looking at?

Sherry, I am still having this issue. Do you have anything that you can add to your troubleshooting?