We use AD discovery so that SCCM can find computers without the client and install it. The problem though, is that we also have about 4,000 PC's which are scrapped, stolen, lost, or otherwise not in use. So SCCM is not an accurate reflection of our current estate. Q1) I am not confident that the site maintenance tasks can get round this problem – can they? If we were to use WSUS to push the client, then anything that was added to AD would get the WSUS policy and WSUS would push out the client (I presume, because I have not tried using WSUS for this). 2) Is this a recommended setup - is WSUS a reliable way to deploy the client?

Hi, 1) Maintenance tasks alone will not give you a precise overview. You also need to build a Client Health solution, I would start by having a look at the R2 client health feature. 2) Yes, wsus is a very reliable source when it comes to installing the client. You could also use a GPO to do the installation.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

1) Maintenance tasks alone will not give you a precise overview. You also need to build a Client Health solution, I would start by having a look at the R2 client health feature. 2) Yes, wsus is a very reliable source when it comes to installing the client. You could also use a GPO to do the installation. Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products Thanks for the advice Kent, a few follow up questions if I may.... I have got the client health script from http://myitforum.com/cs2/blogs/cstauffer/archive/2009/12/18/sccm-sp2-health-check-startup-script-1-7.aspx - Is that what you are referring to? Because if it is I cannot find any documentation as to what it actually does. If that script is not what you are referring to then what is the R2 Client Health Feature!? I have enabled the client installation through WSUS, i can see that it has copied the current client version to the software update point. I can also see from the WindowsUpdate.log that the client has installed on a particular machines that for some reason the standard Client Installation method failed with, which is great. However - Is there any reporting in WSUS that shows the number of installs with dates and times so I know its working on other machines? I gather I dont need to approve the client like a typical patch?

I have also just noticed this in the WSUS log "Forced install timer expired for deadline install". Does this mean that machines with be forced to reboot in cases where an update is required (there are a few machines in the Client Deployment Success Report with an asterisk.