Right now, i am having 3 types of client agent issues. I summarize it as below. Need you guys opinion... :) Client=No, SiteCode=secondary site code and Assigned=Yes - This one, eventhough i cant physically check, i know that this machine DOES NOT have the SCCM agent. This is because, when i want to see the machine resource explorer, it is empty and also, when I double click on the machine object, it displays blank. Therefore, SCCM agent need to be installed. For me, The only way for me is to manually install the agent using .bat or .vb script.... (correct me if im wrong) Duplicate client machine object. One with Client=No, SiteCode=secondary site code and Assigned=Yes and another entry is the correct entry with Client=Yes, SiteCode=primary site code and Assigned=Yes - Im not sure about this one. I can see in console that there are 2 duplicate entry for the same machine object. This are not obsolete object. One is with Client=No and SiteCode=secondary site and another one is the complete entry. However, i am able to advertised to this machine and when i physically checked, there is an SCCM agent installed. If I create a collection and do the query to include only SystemResource.Active=1 and SystemResource.Client=1 object, the machine will not be included. So I assume it is because it has a duplicate object where the incorrect entry overite the correct machine entry. Based on you guys experience, how can the machine object become like this? Is it because it have a duplicate GUID? I assume that it is safe for me to just delete the Client=No and SiteCode=secondary site code entry... Client=No, SiteCode=primary site and Assigned=Yes - For this one, i know that the machine has an agent, eventhough i am unable to physically check it. Reason is because im able to see all the hardware/software inventory of the system through the resource explorer in SCCM console. But the only thing i dont know is why does the Client column display as NO? I was thinking maybe it is because the machine has not connected to the network for a long time. Then once we connect and run the machine policy or update the collection membership, the CLIENT column will change to YES... (correct me if im wrong)

1. This machine was discovered and is found in the boundary of the Secondary. You can also install the client if you use the Right click Install Client method, or you can install the client by checking the box to install discovered resources. 2. Same as #1. It was discovery and then the client was installed. Maintenance task should clear this up, you can delete the other record, no harm. 3. check to see if the client is registered correctly. check the logs. Refresh the All Systems collection and then look to see if the machine is correct. http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Thanks, Matthew. One more questions, Some of my machines have CLIENT=NO and SiteCode=secondary site code. Then i see that a few has agent installed, but it's like not complete. When i see the actions tab, it has only 2 entries which is Machine Policy and User Policy Retreival as below image. Does this means that the agent is corrupted?

this machine hasn't fully registered with the site. Check the ClientIDStarutpManager log for clues. Could be port blocks or any number of issues.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com