My site has about 15,000 clients. Of those I have about 500 that don't have the client for different reasons, however of the rest I have any number of unknown systems that actually are not working correctly. This could be anything from WMI issues, BITS turned of or access issues. Is there a way to find out what systems might not be functioning within SCCM? Right now we just want until we have a deployment and see what systems don't accept it and work off those, however that is a reactive method we're rather not wait until we want them to work to find out they don't.

You can install the client status reporting utility that ships with SCCM 2007. Better yet there are some third party tools (not free ones) that would probably help you more. I've always been satisfied if I get at least 95% success on all deployments. Nobody will ever get 100%. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Implement a startup script the will perform the health checks. There is a good example here - http://blogs.catapultsystems.com/jsandys/archive/2010/12/30/updated-configmgr-startup-script.aspx It can be implemented in less than 10 minutes.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Thanks I'll look into both, I wasn't aware of the client status reporting utility and so far that looks like what I need. The script while good too, we don't use GPO's and that would be a big push to get that going.