I am having very hard time getting a simple CM client install script to work via GPO start up script. For the purpose of trouble shooting I have stripped out all logic from my script and simply have the install command remaining. I've used just about every combination of switches that I could come up with including /mp, /source, and /noservice. I've verified that domain/domain computers has access to the share. The scrip is running, it appears that ccmsetup.exe starts to run, but then just kind of stops with the line "Ccmsetup is not registered in the Run key". Does anyone have any idea what may be going on here?Also though it is not specified in the sample provided below, I do have an FSP set up, have specified the FSP on some of my testing, and basically revieved the exact same results as below.We have been using a very similar script for many years to install the SMS client, this one just does not seem to want to work.Thanks.neilp<-------SCRIPT--------------------------------------------------------Set wshShell = WScript.CreateObject("WSCript.shell")wshShell.exec("\\SERVERNAME\CLIENT\ccmsetup.exe /service SMSSITECODE=XXX")--------------------------------------------------------------------------><-------CCMSetup.log---------------------------------------------Version: 4.0.6221.1000 ccmsetup 9/3/2008 10:48:37 AM 1372 (0x055C)Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 9/3/2008 10:48:37 AM 1372 (0x055C)Command line: \\SERVERNAME\Client\ccmsetup.exe /service SMSSITECODE=XXX ccmsetup 9/3/2008 10:48:37 AM 1372 (0x055C)Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 9/3/2008 10:48:37 AM 1372 (0x055C)A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 9/3/2008 10:48:37 AM 1372 (0x055C)Ccmsetup is not registered in the Run key ccmsetup 9/3/2008 10:48:37 AM 1372 (0x055C)----------------------------------------------------------------------->

If you are using GPO, why not install using the approved and supported GPO deployment method? http://technet.microsoft.com/en-us/library/bb633010.aspx I can't help with scripts, I am not a script person. However there are plenty of others out there who are and can help. But my question still stands :-)

p.MsoNormal, li.MsoNormal, div.MsoNormal {margin-top:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in;line-height:115%;font-size:11.0pt;font-family:'Calibri','sans-serif';} .MsoChpDefault {;} .MsoPapDefault {margin-bottom:10.0pt;line-height:115%;} @page Section1 {size:8.5in 11.0in;margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {page:Section1;} Thanks for the Reply Wally - I had really hoped to use some logic contained in the script to either install the client or not. I've already deployed the CM client to all existing machines via and SMS deployment. Now I'm looking for a solution to get the client installed on all new machines. I am not an AD guy and may have this incorrect, but I for some reason have been under the impression that installation via GPO will not perform any logic to check for a previous installation. I had thought about incorporating the /logon switch however see that a deployment via GPO can accept no additional arguments. Thanks again for the reply Wally and pleas correct me if I am wrong on any of these accounts. I am definitely not bent on using a script I simply do not want to redeploy the client to all machines that currently have it. neilp

My limited understanding of Group Policy is that when it runs again the client checks to see if the product is installed. In this case, the Group Policy should detect that it is already installed. I'll see if I can get a clarification on that from our end, but that's my understanding of how it works.

I've just done some testing and it does apear that once the Group Policy is put into place to install the cleint this will install over any previously instalations.

I checked with someone on the client deployment team, and my limited knowledge was close enough to be considered correct. When the client checks GP assignments, it will identify that the product is already installed, and not reinstall. So this sounds like a cleaner way to deploy, if you are deploying all clients from GP.

For Neil's response: I've just done some testing and it does apear that once the Group Policy is put into place to install the cleint this will install over any previously instalations. If they had been deployed through Group Policy, it would not reinstall. But apparently they were not installed via our supported group policy deployment method :-(

Below is what I understand about GPO In GPO client deployment, when the machine is logged on, AD will send the client a list of policies, which asks the machine to complete before the machine can be logged on. That list will have a policy to install a SCCM client (using ccmsetup.msi). If the machine has run the SCCM client installation policy already, the machine will will check that policy as done (without re-running the ccmsetup.msi) and move on to the next policy. The machine always keeps a list of .msi installations that have been installed in its registry keys; therefore, it can determine which policy is new and needed to run and which is old and not needed to execute. As a result, the /logon switch would be redundant to use in a GPO deployment. Hope this helps. Thanks, Minh.

You can try this script SCCM : Check and install SCCM client through logon script http://blogs.microsoft.co.il/blogs/doli/archive/2011/05/16/sccm-check-and-install-client-through-logon-script.aspx