Obviously the preferred client installation method is either via an automatic client push or manually pushing out the client using the SCCM Administration Console:
However, this method sometimes doesn’t work either because of permissions issues or WMI corruption. Of course, you want to fix the underlying problem that is causing a manual client push not to work.
For those of you interested in an alternative way to install the client, you can use the excellent PSEXEC.EXE command-line tool from Mark Russinovich Sysinternals Suite:
PSEXEC.EXE command window with server names blurred.
psexec.exe \\RemoteComputer -s -d \\SCCMServer\SMS_SiteCode\Client\ccmsetup.exe /logon SMSSITECODE=ABC /MP:MPServer.domain.local CCMHOSTNAME=cm.domain.com
In the above example, PSEXEC.EXE initiates a remote connection to “\\RemoteComputer” using the System Account (/S) and then passes the command and terminates immediately (/D).
For a list of PSEXEC.EXE switches go to http://technet.microsoft.com/en-us/sysinternals/bb897553.
For a list of CCMSETUP.EXE switches go to http://technet.microsoft.com/en-us/library/gg699356.aspx.