Hi All, My Client Deployment Success Report is showing that clients are installed on the machines. But, collections are not reflecting that. Is that normal or clients are not able to communicate their status to the SCCM server? please guide.

The collection membership has to be updated (manually or by waiting until it's updated in the periodic cycle) and the console refreshed first before you will see any changes. Have you already done that? It might also be possible that a firewall is preventing the client from reaching the MP.Torsten Meringer | http://www.mssccmfaq.de

Please provide more details. What is the status of client in the console? It shows client is NOT installed ? Or assigned to wrong site code? Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

@Torsten: I have already updated the collections manually and refreshed as well several times. How can I verify that clients are not able to contact the SCCM Server/MP? @Anoop: Client is listed as NO. And they are not assigned to the wrong site. They are assigned to the correct site. I have collections in place where I have one for clients installed and one for clients not installed for different parent collections. But, even in the All Systems collection, the status is still NO.

I would also like to add that the clients are on WAN and they have just been installed an agent last night.

Checkout locationservices.log to find out the client is able to communicate with MP or not. And also check the below blog post http://blogs.technet.com/b/configurationmgr/archive/2009/08/10/troubleshooting-issues-where-clients-are-not-reporting.aspxAnoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Great Article you shared Anoop. I just sat with the network guy and saw the firewall logs and saw that clients are making connection to SCCM Site Server over port 80. Does this mean they are contacting the MP?

The clients do communicate with the MP using that port, see: http://technet.microsoft.com/en-us/library/bb632618.aspx Just initiate a "discovery data cycle" or "hardware inventory cycle" on a client and see if it makes it to the MP (mp_hinv.log).Torsten Meringer | http://www.mssccmfaq.de

Witih which client dear. Just tried with SCCM Client Action Tools and it fails to trigger it. Any other tool recommendation.

No tool at all. It's the default ConfigMgr control panel applet. Also make sure that no firewall is blocking traffic (as indicated in other posts). Torsten Meringer | http://www.mssccmfaq.de

Running that on all clients provides this. Attempt to ping: Success Connect to WMI Namespace \ROOT\CIMV2: Success Verify existence of SMS Agent Host service: Success Connect to WMI Namespace \ROOT\CCM: Success Invoke Client Action: ERROR! Not found It seems everything is in order, but yet it fails in the action. any clues.

Just initiate those actions on the client directly using the control panel applet as I already mentioned. Just RDP into it.Torsten Meringer | http://www.mssccmfaq.de

Torsten, there are too many machines around 100 and users are logged on and working. Should I decrease the HINV SINV time on the agent? OR any other way around.

You still don't know the root cause for those issues, so no need to do it on hundreds of machines. You even don't know if your firewall is blocking traffic from the clients to the MP. So just initiate heartbeat and HINV on one machine and see if they make it to the MP.Torsten Meringer | http://www.mssccmfaq.de

Firewall at the moment is not blocking anything. And I have the Policly refresh in most machines now. Still no change in the collections. Any other suggestion or log file to look upon?

Sure ... I already mentioned the logfile on the MP above ...Torsten Meringer | http://www.mssccmfaq.de

The log file so far only shows clients that are already reporting YES. The clients which are shown in the report as installed and NO in teh collection are still not appearing in teh log file. Any other file where I can make sure that at least the clients tried to contact the MP.

LocationServices.log and ClientLocation.log. ccmexec.log might also be helpful.Torsten Meringer | http://www.mssccmfaq.de

Following are the contents of the logs ClientLocation.log =========== Getting Assigned Site Autodiscover Site Getting Assigned Site Getting Assigned Site Getting Assigned Site LocationServices.log ============= Assigning to site 'AB1' LocationServices LSVerifySiteVersion : Verifying Site Version for <AB1> LSGetSiteVersionFromAD : Failed to retrieve version for the site 'AB1' (0x80004005) Attempting to retrieve SLPs from AD Failed to resolve 'SMS_SLP' to IP address from WINS LSGetSLP : Failed to resolve SLP from WINS, is it published LSGetSiteVersionFromSLP : Unable to get the list of SLPs LSVerifySiteVersion: Failed to get Site Version from AD and SLP Won't send a client assignment fallback status point message because the last assignment error matches this one. Won't send client assignment fallback status point message because last assignment message was sent too recently. Processing pending site assignment. (These lines keep on repeating) It seems the clients are not getting the site name assigned?

Or is it not able to query Active Directory for the MP?

The total number of log files in such clients is very low i.e. 15 and 18 whereas in the same location there is a client installed who is shown as INSTALLED in the collection as well as report has around 67 log files? could it be the case of client not properly installing?

The client is neither able to retrieve site information from AD nor WINS/SLP, that's why it cannot be assigned to a site. That's also the reason why there are less logfiles compared to a working one. See http://blogs.technet.com/b/configurationmgr/archive/2009/05/19/troubleshooting-common-problems-with-site-assignment.aspxTorsten Meringer | http://www.mssccmfaq.de

I am going through the document. Could it be possible because I have defined subnets individually as well along with the only active directory site boundary. it is a single server solution.

on a single server overlappign boundaries should not be a problem?

Overlapping boundaries are not supported and cause issues (especially when talking about an overlap between sites)Torsten Meringer | http://www.mssccmfaq.de

It is a single server solution. There is only one active directory site. So, I have that active directory site as boundary and also individual subnets that comprise of all sites. Should not be a problem? or It can be?

It finally resolved. Actually, the clients were not allowed to make queries to Global Catalogue server so added 3268 to the firewall rule and clients started reporting their status and site assignment went smooth. I hope this helps someone.