Troubleshooting issues where clients are not reporting. Sometimes the most challenging part of the Configuration Manager 2. SMS 2. 00. 3 deployment phase can be ensuring that the client successfully reports to the site server. We occasionally see these issues here in support, typically either as cases for clients not reporting after the client installation, or maybe where its noticed that the client count is decreasing from the collection. Collections not being refreshed in ConfigMgr 2012. System Center Configuration Manager Toolkit Package. Collections not being refreshed in ConfigMgr 2012 R24. Im curious if SCCM can sync with AD to create Collections based off of our computer OUs, then import those computers into the properly named Collections. In our collections, when changing the name of a machine, the old machine is still staying in the collection, saying that the client agent is installed. Sccm Collections Not Updating Properly DefinitionWhen we look at the SMSSCCM console collection, there is an entry for the client status that indicates either Yes or No. Assuming everything is installed and configured properly, a client installed on a system should automatically report as Yes, but sometimes that does not turn out to be the case. The reason could be that the client has not yet reported to the SCCMSMS server, or it was reporting previously but has now stopped. Do not install WSUS. Install SCCM 2012 Use this guide. Configuration Manager Assets and Compliance Device Collections Create. In sccm 2012 my device collectionall system is not updating properly. When a new computer added to the AD. Sccm also update the same. But if i manually delete any. In our collections, when changing the name of a machine, the old machine is still staying in the collection, saying that the client agent is installed AND. SCCM. Collections OS Deployment. SCCM Configmgr 2012 Troubleshoot Client software update issues. Responses to SCCM Configmgr 2012 Troubleshoot Client. I have few issues regarding SCCM. My collections are not updating. SCCM Clients are Installed but Status is. Clients Service is running properly. Sccm dynamic collection not updating. UseIncUpdforthiCol1.jpg' alt='Default Client Not Properly Installed' title='Default Client Not Properly Installed' />Managing the client in the collection is a continuous task and for a healthy environment the client should be continuously reporting to the SMSSCCM server. There are various reasons why a client may not be able to report to even if the SMSSCCM agent is installed on a machine. A few of these reasons are discussed below The first thing to check is whether the client is on the network, and if its not on the network, does the system even exist  Its possible that represents a stale record from AD. Systems NOT on the network  If the system is not actually on the network, check if it is shutdown, and if so if its been shutdown for long time. If yes then first restart the system and then initiate the discovery cycle from the control panel agent properties action TAB. Stale Entries  When you use AD discovery, the DDRs are created for the computers that reside in the AD container that we have requested to be queried by the discovery process. If that container has the stale records for the resources, then client records may be created for systems that dont actually exist, thus they will never report. There is a Maintenance task that will clear the inactive records but if the discovery process runs again and the AD container still has these entries then they will simply show up again. Resolution For the stale records you need to make sure that the AD container is cleared of these stale records and scavenging is done for the computers container in AD regularly. Once this is done you can either make use of the maintenance task or you can create a collection for the NON SMS CLIENTS and then do a delete special to the collection so that the entries will be removed permanently from the SMSSCCM database. Then a discovery can be run which will bring back only the active systems in the collection. Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process Client location services identify the site code and the MP it is supposed to connect to. The client connects to the Management Point and downloads the policies. Once the policies are downloaded it sends the heartbeat record to the server. Once the server receives this heartbeat record these are converted in to DDR and processed. This will set the client flag to 1 which will make the client status display as Yes in the console. On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to No. So only if this process is completed and it continues to happen will the client remain reporting to the server. This is why I said earlier that client management is a continuous task. There can be a variety of reasons why this process might fail, and Ive outlined a couple of them below The Boundaries of the Agent are not specified in the site server. If the client is not assigned in the console or the client is unable to discover the site code, make sure that the AD site or the IP subnet is added in the boundary list. The server will only allow those clients within its boundary to download the polices, so if you have not specified the boundaries the client will not be authorized and the policies will not get downloaded. For boundary issues you can use this as a reference http blogs. For the case of overlapping boundaries see http blogs. In the client if you check the location services. C WindowsSystem. CCMLogs, you can get the information of the site assigned to it as well as the MP it is reporting to. If it is not able to report properly, you need to make sure that the agent can communicate over the network to the site server successfully. Unable to get the site code. If the client is not able to get the site code, you need to check first the boundaries as above, and also verify that the site information is published in the AD. You can check the last part of the sitecomp. MP, SLP etc successfully published or updated. If you are unable to see that and you get access denied errors, make sure that the computer account has readwrite permission to the system container in AD. Make sure the permission is flowing to the objects within and the objects below. If you are not publishing the information in AD then you need to make sure that the SLP is configured and working. For more information you can check Post installation phase in the link http support. The client itself is not installed in the Agent. You can take a look at this article http support. There is a name resolution issue in the Client. Make sure that the client is able to communicate to the SMSSCCM server using the FQDN as well as the Net. BIOS name. Use Nslookup or ping to check the name resolution. If you cant ping the server using the FQDN then you will have problems. The client is behind a firewall. If clients are behind a firewall, it may be restricting it from contacting the SMS site server. Check if the necessary ports are opened. You can check http support. There are systems in the collection that have multiple GUIDs. If you suspect your clients may have multiple GUIDs refer to https technet. MP not working as a result of which the policies are not getting downloaded. You first need to check to see whether the MP is working. For that you will need to check the mpcontol. How To Edit Rpt File. Log location SMSlogs in SMS and program filesMicrosoft Configuration Managerlogs in SCCM. If it is showing a 2. OK status code then that means the MP is working. For information on troubleshooting the MP you can use the Troubleshooting management point issues section at http support. If the MP is working fine and the client is unable to contact and download polices, you will have an error on download in the policyagent. Log location C WindowsSystem. CCMLogs. Before checking this though, check if the locationservices. MP information. If it doesnt then check the resolution mentioned in the topic under Site Code and Boundaries above. If it does have the correct MP information, make sure that the BITS service is started on the client. You can try the following URLs to verify that this is working smsmp. Client is unable to download policy. You may also have issues downloading policies if the client agent has WMI corruption. If you suspect this to be the cause of your issue, if it is a XP client then follow these steps 1. Uninstall the SMSSCCM client agent. Use the ccmclean all Available in the SMS tool kit command for SMS and cmsetup uninstall for SCCM. Troubleshoot or rebuild WMI. SCCM Clients are Installed but Status is NO in Client attribute. I am using SCCM 2. Windows Server 2. I have few issues regarding SCCM. My collections are not updating correctly from Active Directory OU. I have made a New Collection with Resource Class System Resource where System Resource System OU Name and I have selected the OU value which SCCM get from AD. But only few clients are updated from Active Directory OU. I have installed SCCm clients on all machines and i can get inventoryRemote Tools etc from these machines but the clients Status is NO in Collection.