Hi, Whats the best way to approach troubleshooting Clients that have stopped communicating with their MPs? Its a large environment. In our SCCM Collections we can see NULL clients and Client=No etc, but alot of these can be valid due to machines no longer in use, rebuilt with new names, machine record in AD but not yet installed\built (not connected to AD etc for over 30 days). Is there a way to grab only the valid machines that have an issue with their clients so that we can troubleshoot or reinstall the client etc..? This would save time wasted investigating machines that turn out to be no longer required. Thanks

You could install the client status reporting tool that comes with R2.

For SCCM clients troubleshooting,you can refer this http://wmug.co.uk/blogs/eskonr/archive/2010/11/16/smssccm_2D00_clients_2D00_installation_2D00_troubleshooting_2D00_check_2D00_list.aspx For the computers which had issues in talking to Manegement Point in getting polycies,May be you can create collection based on its inventory which have not been reported to site server for X days (not the computers which doesnt report their DDR info)? select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System where ResourceId in (select SMS_R_System.ResourceID from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceId where DATEDIFF(dd,SMS_G_System_WORKSTATION_STATUS.LastHardwareScan,GetDate()) > 25) or else ,you can create report for the computers based on the discovery methods where the discovery agent time is old. http://eskonr.wordpress.com/2010/11/25/report-for-computers-where-the-discovery-agent-time-is-older-than-30-days/ Check out this thread for the computers which are Active http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/b08ea1ac-6e97-43ce-a8ca-bd5b632473df //Eswar Koneti @ http://eskonr.wordpress.com/

Hi, On top of the correct answers from Torsten and Eswar you should also look for a more proactive solution like a client startup script that automatically fixes errors. There is a very good and documentet example here - http://blogs.catapultsystems.com/jsandys/archive/2010/11/02/script-update.aspxKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund