We use CCMSETUP.EXE in a logon script , I thought this was odd enough to share with everyone. We use CCMSETUP.EXE in a logon script at my current engagement, I thought this was odd enough to share with everyone. The script would call \\Servername\share\CCMSETUP.EXE SMSSLP=Servername /MP:Servername /logon FSP=Servername SMSSITECODE=XXX Issue: The issue was that even though we had the /logon in the script, CCMSETUP would ignore it and reinstall the client, we tested it three times to actual client systems in the field. The fix was to move the /logon part as follows: \\Servername\share\CCMSETUP.EXE SMSSLP=Servername /logon /MP:Servername FSP=Servername SMSSITECODE=XXX Nothing states that this should be the case but sure enough, the /logon gets ignored if not near the front. David Baur

Could you share the ccmsetup.log in both scenarios? This will help to see how the parameters are taken in both cases.Thanks,Minh.Minh

This looks to be as it is "by design". The Documentation on this is in the SCCM Help -Search on "How to Install Configuration Manager Clients Manually". The problems was that the Logon script was calling the following, which fails to honor /LOGONFailed Command Line:ccmsetup.exe SMSSLP=servername /MP:servername /LOGON /retry:1 FSP=servername SMSSITECODE=xxx DNSSUFFIX=MYDOMAIN.ORG SMSDIRECTORYLOOKUP=WINSPROMISCUOUS CCMLOGLEVEL=0The problem is that CCMSETUP.EXE allows both native command line options, as well as the MSIEXEC Command lines to be tagged onto it, the rule is that the MSIEXEC commands must come after all the Native Command line options. So in the Above example, SMSSLP= is an MSIEXEC command, and therefore it cancelled out all the rest of the commands after it and reinstalled the client. 1. The RULE is to use the following commands first (in any order though):/source:<path>/mp:servername/retry:<minutes>/noservice/uninstall/logon/forcereboot/BITSPriority:<Priority>/downloadtimeout:<Minutes>/native: [<native mode option>]/config:<configuration file> 2. Thenafter you have added the above syntax, then you can use the below commands, but they must be after all the commands listed above:CCMALWAYSINFCCMCERTSELCCMCERTSTORECCMFIRSTCERTCCMHOSTNAMECCMHTTPPORTCCMHTTPSPORTSMSPUBLICROOTKEYSMSSIGNCERTSMSROOTKEYPATHRESETKEYINFORMATIONCCMDEBUGLOGGINGCCMENABLELOGGINGCCMLOGLEVELCCMLOGMAXHISTORYCCMLOGMAXSIZECCMALLOWSILENTREBOOTDISABLESITEOPTDISABLECACHEOPTSMSCACHEDIRSMSCACHEFLAGSSMSCACHESIZESMSCONFIGSOURCESMSDIRECTORYLOOKUPSMSMPSMSSITECODESMSSLPCCMINSTALLDIRCCMADMINSFSPDNSSUFFIXA Correct Command line looks like this:ccmsetup.exe /MP:servername /LOGON /retry:1 SMSSLP=servername FSP=servername SMSSITECODE=xxx DNSSUFFIX=MyDomain.ORG SMSDIRECTORYLOOKUP=WINSPROMISCUOUS CCMLOGLEVEL=0 David Baur

I know this issue is resolved but I have a quick question. If the /logon switch is used and the client is already installed is the installation completely halted or will it continue to check and apply the remaining configuration details? The reason I ask is we recently merged with another company and went through a major migration into a new domain for the entire company. After moving PCs to the new domain we noticed that even after assigning the new site code they still have certificate issues. To make a really long story short we found that uninstalling the client and re-installing from the new SCCM server worked best. If this would simply ignore the installation portion but force new "AssignedSiteCode" and "Internet MP Hostname", that would solve a lot of problems. Does anyone know if that happens? For example if I find a client that does not have a site code or management point assigned and I run this, will it skip the client install but set the rest of the configurations and assignments? Ramon Rodgers, MCP, APlus Network Support Specialist

Moving a client between hierarchies requires changes of the TRK (trusted root key): http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspxTorsten Meringer | http://www.mssccmfaq.de

Thank you David. In some cases this is exactly what we do. And as I said, in others we were uninstalling the client completely, manually. But you didn't answer the question. What happens to the rest of the process if you run the command with the /logon switch and the client is already installed? I don't want to keep re-installing the client manually and it would even be nice to script it to always run. But if I don;t add /logon, won't it reinstall the client? So for an example I have a PC that is already connected to a different hierarchy and has a site assignment. I move the PC to a new domain in a site boundary of the new SCCM server, and I script THIS: \\<server>\client\ccmsetup.exe RESETKEYINFORMATION = TRUE \\<server>\client\ccmsetup.exe /logon /source:\\<servver>\client /mp:<server> /service /native SMSSITECODE=<CODE> CCMHOSTNAME=<INTERNET MP HOST> Since the client is already installed, what happens?Ramon Rodgers, MCP, APlus Network Support Specialist