Universal Fix for Broken clients, which can be deployed through sccm or can be run on the machines individually

Question

Hi Friends,
Often the service desk gets laptops from employees on which the client is broken or not getting policy updates
The Deskside team tries few steps 
Reinstall the client using the cmd line 
Run the "OSprovision" utility to add the machine back to domain 
Run the "OSD Collection Utility " to Add the machine to a collection
However the sucess rate is less, i believe due to few reasons like, the OS image is old, missing pre requisites etc
so firstly i would like to know what all it takes to make the Client healthy, what all need to be checked to make sure it meets the pre requisites
Work around to fix the client, by remoting into the computer
Eventually i wish to build a Task Sequence which can be deployed to a collection, which will check the following
Does the computer meets the Pre requisites, if not it will install/reinstall the missing/corrupt pre requisites
installs/reinstalls the client ( wish to know how to execute the command line via task sequence, also if there is any other procedure to do the same )
runs the web based utility "osprovision" to add the machine if it has fallen out of domain
Adds the machine to appropriate collection utility
checks to make sure that the client is working fine after install/reinstall and is getting updates
Most importantly it should skip all the above steps if the client is already healthy
I am a new bee to the sccm, however i understand the concept, Please bear with me and help me step by step to complete this task, 
also your idea's are most welcome for any updates/changes 
Regards
Tanoj
OSLM ENGINEER - SCCM 2007 & 2012

Answer 1

If there was a magic bullet to keeping clients healthy, then keeping clients healthy would not be an issue.
However, ConfigMgr 2012 does have a a built-in client health tool called ccmeval -- this is run using a scheduled task on client systems every day and does a very good job of keeping clients healthy.
Using a task sequence or anything directly deployed by ConfigMgr won't work because its a catch-22: how is the ConfigMgr agent supposed to run a deployment if it or a dependent component is not healthy.
Other things to keep clients healthy:
- Don't give users local admin privileges.
- Beat users that hard shutdown or reboot systems (this is IMO the number 1 cause of client health issues)
- Get rid of XP
- Use client startup script that supplements ccmeval
Jason | http://blog.configmgrftw.com