We have hundreds of broken Windows 7 clients in our SCCM 2007 r3 environment.   Is there a best practices for fixing them?  Any proven repeatable methods?    Or do you just have to hack your way through it using the client tools and psexec?  

There is no right answer to this, except, try to find out why it I happening in your environment.

As for fix it, yes you will need to "hack" your way through it, however you could try to use one of the start-up scripts to get all the low hanging fruit... Jason Sandy has a good one.  

Hi,

I agree with Garth, there is no "universal" solution, start checking your clients and if you find a pattern of what is broken script it..

Regards,
Jrgen

Thanks for the advice.   Next part of this issue.....   how do we find broken clients?   We know of many but I'll give an example.  We have a collection called "All Windows 7 Workstations"  and in this collection we have over 1,000 machines that have no client, no site,  approved = N/A and assigned = no.   

Now, I know SCCM reads AD each night and many of these can be machines that are no longer in our environment but how do you find the machines that are online but have a broken client?   pinging machines is slow and difficult since we have so many laptop users who travel and are not always online.

There is no simple way to fix this. Personally I would start with AD, find all PCs that have not changed their password in the last 60 days. Then disable those account. 30 days after that, delete those accounts.  Make sure that you clean up DNS at the same time.

IMO if you do just those two things you will bring the 1000 PC down to under 25. If not then you like have major problems. With the remain 25 PC you will need to find them and work out what exactly is going on with each of them.