SCCM Command-Line Properties

Several command-line properties are used to control the installation. Before you start the deployment, you will need to know two things:

◆ What command-line properties are you going to use?

◆ How are you going to provision the command-line properties?

The installation process will always run ccmsetup.exe and client.msi; both of these processes can be controlled using command lines. Any needed prerequisites will be installed and controlled by ccmsetup.exe. When you specify command-line properties, you should do so

like this:

CCMSetup.exe [CCMsetup properties] [client.msi setup properties]

For an updated list of command-line properties, you should look at the TechNet article at this URL:

http://technet.microsoft.com/en-us/library/gg699356.aspx

The following are ccmsetup.exe command-line properties:

/source The /source switch is used to identify the location of the client.msi installer file. You can specify the switch multiple times to provide additional source file locations to provide for redundancy. Usage: ccmsetup.exe /source:folderpath.

/MP The /MP switch is used to specify the management point that will be used as a source location. As with the /source switch, you can specify multiple management points by including the switch multiple times. The setting is not used to control the management point that will be used during the site assignment process. Usage: ccmsetup.exe /MP:Server.

/retry:<minutes> The /retry switch is used to retry values used to determine how often a client will try to download the installation files. The client will attempt to download the files until it reaches the values specified in downloadtimeout. Usage: ccmsetup.exe /retry:30.

/downloadtimeout:<minutes> The /downloadtimeout switch controls the number of minutes the ccmsetup process attempts to download the needed client installation files. By default the ccmsetup process will try downloading files for one day. Usage: ccmsetup / download timeout:120.

/noservice The /noservice switch is used to specify that the logged-in user’s account is the service account for the installation of the client. For this switch to work, the user account will need to have rights to install software; otherwise the installation will fail. Usage: ccmsetup / noservice.

/Service The /Service switch is used to install the client software using the security context of the local system account. For this to work, Active Directory has to be in use within your network, and the computer’s Active Directory account must have access to the installation directory where the client installation files are stored. Usage: ccmsetup /Service.

/Logon The /Logon switch is used to determine if a Configuration Manager client exists on the system. If a Configuration Manager 2012 client is already installed, the installation process will stop. Usage: ccmsetup.exe /Logon.

/forcereboot The /forcereboot switch is used to determine if the ccmsetup process needs to perform a restart of the computer in order to finish the installation. Usage: ccmsetup.exe /forcereboot.

/BITSPriority:<Priority> The /BITSPriority switch controls the bits download priority when downloading the client installation files. You can specify these values:

◆ Foreground

◆ High

◆ Normal

◆ Low

Usage: ccmsetup.exe /BITSPriority:Foreground.

/Uninstall The /Uninstall switch is used to silently uninstall the Configuration Manager client. Usage: ccmsetup.exe /Uninstall.

/UsePKICert The /UsePKICert switch is used to specify that the client will use a PKI certificate that uses client authentication for communication. If no certificate can be found, the client will use a self-signed certificate and communicate using HTTP. Usage: ccmsetup.exe /UsePKICert.

/NoCRLCheck The /NoCRLCheck switch is used to specify that the client will not check the certificate revocation list before establishing HTTPS communication. This example will enable HTTPS communication and not check for any revocation lists. Usage: ccmsetup.exe /UsePKICert /NoCRLcheck.

/config:<configuration file> The /config switch is used to specify the name of a userdefined configuration file. The configuration file replaces the default mobileclient.tcf file. It is a very good idea to modify an existing mobileclient.tcf file whenever you want to create a custom configuration file. That way you ensure that the syntax used in the file is correct. Usage: ccmsetup.exe /config:C:\Windows\ccmsetup\mysettings.txt.

The following are Client.msi command-line properties:

Patch This property allows you to apply client patches during the installation. At the time of writing, there are no Configuration Manager 2012 client patches. Usage: patch=\\Server\ Share\clientpatch.msp.

CCMALWAYSINF This property with a value of 1 allows you to determine that the client will always be Internet-based, thus never connecting to the intranet. Usage: CCMALWAYSINF=1.

CCMCERTISSUERS This property specifies the list of certificate issuers trusted by the Configuration Manager site. Notice that the list is case-sensitive. Usage:  CCMCERTISSUERS= ="CN=CM Root CA; OU=SRV; O=CM, Inc; C=US".

CCMCERTSEL This property allows you to control the certificate selection criteria used when the client has more than one certificate to choose from. When specifying the criteria you can search for the exact subject name (type subject: prior to the SN) or a partial match in the subject name (type subjectstr: prior to part of the subject name, object identifier, or distinguished name). Usage: CCMCERTSEL="subject:Server1.CM2012.COM".

CCMCERTSTORE This property allows you to specify an alternative certificate store. You

should use the command line only if the certificate is not found in the default store. Usage: CCMCERTSTORE="CM2012CERT".

CCMFIRSTCERT With this property configured to 1 the client will automatically select the

certificate with longest validity period. Usage: CCMFIRSTCERT=1.

CCMHOSTNAME This property is used to specify the management point for Internet-based managed clients. Usage: CCMHOSTNAME="MPServer.CM2012.COM".

SMSPUBLICROOTKEY This property allows you to specify the trusted root key if, for some reason, it cannot be retrieved from Active Directory. You can open the mobileclient.tcf

file and copy the trusted root key. Usage: SMSPUBLICROOTKEY=  02000000A40000525341310

0080000010001008186332BF592B793C8B7F7C01FB32CB811465DEB71095C4442DE45661CE- 25031FE2B6F8D9C1C71C6C0BB335C3B5747035E028C43C35E4F8DF1E0CB8B42289A8B-

9F9A3143964817DCC50F0D5DB9A879705AD0F4063F4F30242472A933FE8B452BEE608147D9ECED79CA9422D5441894D152C54B0ABB920741BA0B5582482EA1

231FAB0BD67AAAB-

82DEC50BDCE7D91FCCFB2C3F6C03C8C67C31B5F083A98860389E8D2FD93C4C5BAE-

6124A4977EA76B5A89AE2917687782783E003C5F215C767782C0F79A1C1E1F4D14E8B693-

25C8CC33C574BE774CEA9579AD765A864DB0FBBBBB854D4390473E72014111EFDFC11DDDF46EF7B1F03EF1D60A3ABDAA52E8868A0.

SMSROOTKEYPATH This property allows you to reinstall the trusted root key from a file. Usage: SMSROOTKEYPATH="D:\NewRootKey\Rootkey.txt". often used when you move clients from one Configuration Manager site hierarchy to another. Usage: RESETKEYINFORMATION=TRUE.

CCMAdmins This property allows you to configure which admin accounts are for the client. If there is more than one account, separate the accounts with a semicolon. Usage: CCMAdmins= account1;account2;....

CCMAllowSilentReboot After the installation is complete, if a reboot is required, this property will cause the machine to reboot without saving any user changes. It needs to be specified only if the silent reboot is to be used. A value of 1 forces the reboot if required. Usage: CCMAllowSilentReboot.

CCMDebugLogging This property enables or disables debug logging. A value of 1 enables logging; a value of 0 disables logging. Usage: CCMDebugLogging=0 | 1.

CCMEnableLogging This property turns logging on or off. If this property is not included,

then logging is disabled. Usage: CCMEnableLogging=True.

CCMInstallDir This is the directory where the client software will be installed. Usage:

CCMInstallDir=C:\ConfigMgr.

CCMLogLevel This property is used to control the amount of logging activity. A value of 0 is verbose logging. A level of 1 logs all information, warning, and error conditions. A level of 2 logs warning and error conditions. A value of 3 logs error conditions only. When included, you must also use CCMEnableLogging. Usage: CCMLogLevel=0 | 1 | 2 | 3.

CCMLogMaxHistory This property controls the total number of previous log files within the Logs directory. When included, you must also use CCMEnableLogging. Usage: CCMLogMax History=NumberOfLogFilesToKeep.

CCMLogMaxSize This property controls the maximum log file size. When included, you must also use CCMEnableLogging. Usage: CCMLogMaxSize=LogSizeBytes.

DisableCacheOpt When this property is included in the text box, it disables the Cache configuration setting within the Systems Management properties in Control Panel. Users will not be able to manipulate the settings—only administrators will be allowed to. Usage: DisableCacheOpt=True.

DisableSiteOpt When this property is included in the text box, it disables the Site Code configuration setting within the Systems Management properties in Control Panel. Users will not be able to manipulate the settings—only administrators will be allowed to. Usage: DisableSiteOpt=True.

SMSCacheDir This property controls the directory where the cache is created. Usage: SMSCacheDir=directorypath.

SMSCacheFlags This property can be used to control how much space the cache can occupy and the location where the cache will be stored. When used in conjunction with the SMSCacheDir property, you have control over where the cache is stored. The flags are as  follows:

SMSCacheFlags=PercentDiskSpace Used to control the size of the cache by allocating the total cache size as a percentage of the disk size. Cannot be used with PercentFreeDiskSpace.

SMSCacheFlags=PercentFreeDiskSpace Used to control the size of the cache file by allocating the total cache size as a percentage of the free space on the disk. Cannot be used with PercentDiskSpace.

SMSCacheFlags=MaxDrive Used to place the cache on the largest drive in the system. Cannot be used with MaxDriveSpace.

SMSCacheFlags=MaxDriveSpace Used to place the cache on the drive with the most free space. Cannot be used with MaxDrive.

SMSCacheFlags=NTFSOnly Used to control the placement of the cache drive on volumes

formatted with NTFS.

SMSCacheFlags=Compress Used to compress the files within the cache.

SMSCacheFlags=FailIfNoSpace Used to stop installation of the client if there is not enough space on the drive for the cache.

SMSCacheSize This property controls the amount of space in megabytes that the cache will consume or in percentage if used in combination with PERCENTDISKPACE or PERCENTFREE DISKSPACE. Usage: SMSCacheSize=CacheSizeInMB.

SMSConfigSource This property controls where the configuration source files are stored. Usage: SMSConfigSource=R | P | M | U.

SMSDIRECTORYLOOKUP This property controls whether WINS lookup is allowed when the client is trying to locate the management point and the site code. Usage: SMSDIRECTORYLOOKUP=NOWINS.

CCMHTTPPort This is the HTTP port used by the client to communicate with the site systems. Usage: CCMHTTPPort=80.

CCMHTTPSPort This is the HTTPS port used by the client to communicate with the site systems. Usage: CCMHTTPSPort=443.

SMSMP This property is used to configure the initial management point that the client communicates with. Usage: SMSMP=Server1.CM2012.COM.

FSP This property specifies that a fallback status point is used. Usage: FSP=Server1 .CM2012.COM.

DNSSUFIX This property specifies the DNS domain of the management point. With this option clients will search DNS for the .srv record that includes the DNS suffix of the management point. Usage: DNSSUFFIX=CM2012.COM.

SMSSiteCode This property controls the site code that is assigned to the client. Usage: SMSSiteCode=Auto | SiteCode.

CCMEVALINTERVAL This property controls how often in minutes the client evaluation process runs. By default the process is configured to run once a day. Usage: CCMEVALINTERVAL=1440.

CCMEVALHOUR This property controls when the client evaluation process runs (by the hour).

By default the process is configured to run at midnight. Usage: CCMEVALHOUR=14.

For example, suppose you wanted to push the client to systems, using the following options:

◆ Install the cache in the \Cache directory on the largest drive.

◆ Enable verbose logging.

◆ Keep five log files.

◆ Automatically discover the site code.

Your entry within the Property text box would look like this:

SMSSITECODE=AUTO SMSCACHEDIR=CACHE SMSCACHEFLAGS=MAXDRIVE

SMSENABLELOGGING=TRUE

CCMLOGLEVEL=0 CCMLOGMAXHISTORY =5

Provisioning Command Lines

You can provision command lines in three different ways:

◆ Manually type the command lines during the installation.

◆ Publish them to Active Directory.

◆ Configure a Group Policy with the ConfigMgrInstallation.adm template.

If the AD schema is extended, you can type the command lines in the Installation Properties for the client push installation method. All properties you enter here will be published to Active Directory and used by any client that can access Active Directory during the installation. Notice that this applies only if you start the installation using ccmsetup.exe with no other command lines.

For those scenarios where clients cannot access the information in Active Directory, you can provision the command lines using a Group Policy with the ConfigMgrInstallation .adm template. The template is found on the Configuration Manager 2012 installation media in .SMSSetup\TOOLS\ConfigMgrADMTemplates.