CCMALWAYSINF

Set to 1 to specify that the client will always be Internet-based and will never connect to the intranet. The client's connection type will display Always Internet.

This property should be used in conjunction with CCMHOSTNAME, which specifies the FQDN of the Internet-based management point. It should also be used in conjunction with the CCMSetup property /UsePKICert and with the site code.

For more information about Internet-based client management, see Overview of Internet-Based Client Management.

Example: CCMSetup.exe /UsePKICert CCMALWAYSINF=1 CCMHOSTNAME=SERVER3.CONTOSO.COM SMSSITECODE=ABC

CCMCERTSEL

Specifies the certificate selection criteria if the client has more than one certificate that can be used for HTTPS communication (a valid certificate that includes client authentication capability).

You can search for an exact match in the Subject Name or Subject Alternative Name (use Subject:) or a partial match (use SubjectStr:), in the Subject Name or Subject Alternative Name. Examples:

CCMCERTSEL="Subject:computer1.contoso.com" searches for a certificate with an exact match to the computer name "computer1.contoso.com" in either the Subject Name, or the Subject Alternative Name.

CCMCERTSEL="SubjectStr:contoso.com" searches for a certificate that contains "contoso.com" in either the Subject Name, or the Subject Alternative Name.

You can also use Object Identifier (OID) or distinguished name attributes in the Subject Name or Subject Alternative Name attributes, for example:

CCMCERTSEL="SubjectAttr:2.5.4.11 = Computers" searches for the organizational unit attribute expressed as an object identifier, and named Computers.

CCMCERTSEL="SubjectAttr:OU = Computers" searches for the organizational unit attribute expressed as a distinguished name, and named Computers.

Important
If you use the Subject Name field, the matching process for the Subject: selection criteria value is case-sensitive, and the matching process for the SubjectStr: selection criteria value is case-insensitive. If you use the Subject Alternative Name field, the matching process for both the Subject: selection criteria value and the SubjectStr: selection criteria value is case-insensitive.

The complete list of attributes that you can use for certificate selection is listed in Supported Attribute Values for the PKI Certificate Selection Criteria.

If more than one certificate matches the search, and the property CCMFIRSTCERT has been set to 1, the certificate with the longest validity period is selected.

CCMCERTSTORE

Specifies an alternate certificate store name if the client certificate to be used for HTTPS communication is not located in the default certificate store of Personal in the Computer store.

Example: CCMSetup.exe /UsePKICert CCMCERTSTORE="ConfigMgr"

CCMFIRSTCERT

If set to 1, this property specifies that the client should select the PKI certificate with the longest validity period. This setting might be required if you are using Network Access Protection with IPsec enforcement.

Example: CCMSetup.exe /UsePKICert CCMFIRSTCERT=1

CCMHOSTNAME

Specifies the FQDN of the Internet-based management point, if the client is managed over the Internet.

Do not specify this option with the installation property of SMSSITECODE=AUTO. Internet-based clients must be directly assigned to their Internet-based site.

Example: CCMSetup.exe /UsePKICert/ CCMHOSTNAME="SMSMP01.corp.contoso.com"

CCMHTTPPORT

Specifies the port that the client should use when communicating over HTTP to site system servers.

If the port is not specified, the default value of 80 will be used.

Example: CCMSetup.exe CCMHTTPPORT=80

CCMHTTPSPORT

Specifies the port that the client should use when communicating over HTTPS to site system servers. If the port is not specified, the default value of 443 will be used.

Example: CCMSetup.exe /UsePKICert CCMHTTPSPORT=443

SMSPUBLICROOTKEY

Specifies the Configuration Manager trusted root key where it cannot be retrieved from Active Directory Domain Services. This property applies to clients that use HTTP and HTTPS client communication. For more information, see How to Pre-Provision the Trusted Root Key on Clients.

Example: CCMSetup.exe SMSPUBLICROOTKEY=<key>

SMSROOTKEYPATH

Used to reinstall the Configuration Manager trusted root key. Specifies the full path and file name to a file containing the trusted root key. This property applies to clients that use HTTP and HTTPS client communication. For more information, see How to Pre-Provision the Trusted Root Key on Clients.

Example: CCMSetup.exe SMSROOTKEYPATH=<Full path and filename>

RESETKEYINFORMATION

If a Configuration Manager 2012 client has the wrong Configuration Manager trusted root key and cannot contact a trusted management point to receive a valid copy of the new trusted root key, you must manually remove the old trusted root key by using this property. This situation commonly occurs when you move a client from one site hierarchy to another. This property applies to clients that use HTTP and HTTPS client communication.

Example: CCMSetup.exe RESETKEYINFORMATION=TRUE

CCMDEBUGLOGGING

Enables debug logging. Values can be set to 0 (off) or 1 (on). The default value is 0. This causes the client to log low-level information that might be useful for troubleshooting problems. As a best practice, avoid using this property in production sites because excessive logging can occur, which might make it difficult to find relevant information in the log files. CCMENABLELOGGING must be set to TRUE to enable debug logging.

Example: CCMSetup.exe CCMDEBUGLOGGING=1

CCMENABLELOGGING

Enables logging if this property is set to TRUE. By default, logging is enabled. The log files are stored in the Logs folder in the Configuration Manager Client installation folder. By default, this folder is %Windir%\System32\CCM\Logs.

Example: CCMSetup.exe CCMENABLELOGGING=TRUE

CCMLOGLEVEL

Specifies the amount of detail to write to Configuration Manager 2012 log files. Specify an integer ranging from 0 to 3, where 0 is the most verbose logging and 3 logs only errors. The default is 1.

Example: CCMSetup.exe CCMLOGLEVEL=3

CCMLOGMAXHISTORY

When a Configuration Manager 2012 log file reaches 250000 bytes in size (or the value specified by the property CCMMAXLOGSIZE), it is renamed as a backup, and a new log file is created.

This property specifies how many previous versions of the log file to retain. The default value is 1. If the value is set to 0, no old log files are kept.

Example: CCMSetup.exe CCMLOGMAXHISTORY=0

CCMLOGMAXSIZE

Specifies the maximum log file size in bytes. When a log grows to the size that is specified, it is renamed as a history file, and a new file is created. This property must be set to at least 10000 bytes. The default value is 250000 bytes.

Example: CCMSetup.exe CCMLOGMAXSIZE=300000

CCMALLOWSILENTREBOOT

Specifies that the computer will be allowed to restart following the client installation, if this is required.

Important
The computer will restart without warning even if a user is currently logged on.

Example: CCMSetup.exe CCMALLOWSILENTREBOOT

DISABLESITEOPT

If set to TRUE, disables the ability of end users with administrative credentials on the client computer to change the Configuration Manager Client assigned site by using Configuration Manager in Control Panel of the client computer.

Example: CCMSetup.exe DISABLESITEOPT=TRUE

DISABLECACHEOPT

If set to TRUE, disables the ability of end users with administrative credentials on the client computer to change the temporary program download folder settings for the Configuration Manager Client by using Configuration Manager in Control Panel of the client computer.

Example: CCMSetup.exe DISABLECACHEOPT=TRUE

SMSCACHEDIR

Specifies the location of the cache folder on the client computer, which stores temporary files. By default, the location is %Windir%\System32\CCM\Cache.

Example: CCMSetup.exe SMSCACHEDIR="C:\Temp"

This property can be used in conjunction with the SMSCACHEFLAGS property to further control the client cache folder location.

Example: CCMSetup.exe SMSCACHEDIR=Cache SMSCACHEFLAGS=MAXDRIVE installs the client cache folder on the largest available disk drive on the client.

SMSCACHEFLAGS

Configures the Configuration Manager 2012 cache folder, which stores temporary files. You can use SMSCACHEFLAGS properties individually or in combination, separated by semicolons. If this property is not specified, the client cache folder is installed according to the SMSCACHEDIR property, the folder is not compressed, and the SMSCACHESIZE value is used as the size in MB of the folder.

Specifies further installation details for the client cache folder. The following properties can be specified:

• PERCENTDISKSPACE: Specifies the folder size as a percentage of the total disk space. If you specify this property, you must also specify the property SMSCACHESIZE as the percentage value to use.
  
  
• PERCENTFREEDISKSPACE: Specifies the folder size as a percentage of the free disk space. If you specify this property, you must also specify the property SMSCACHESIZE as the percentage value to use. For example, if the disk has 10 MB free and SMSCACHESIZE is specified as 50, the folder size is set to 5 MB. You cannot use this property with the PERCENTDISKSPACE property.
  
  
• MAXDRIVE: Specifies that the folder should be installed on the largest available disk. This value will be ignored if a path has been specified with the SMSCACHEDIR property.
  
  
• MAXDRIVESPACE: Specifies that the folder should be installed on the disk drive that has the most free space. This value will be ignored if a path has been specified with the SMSCACHEDIR property.
  
  
• NTFSONLY: Specifies that the folder can be installed only on disk drives formatted with the NTFS file system. This value will be ignored if a path has been specified with the SMSCACHEDIR property.
  
  
• COMPRESS: Specifies that the folder should be held in a compressed form.
  
  
• FAILIFNOSPACE: Specifies that the client software should be removed if there is insufficient space to install the folder.
  
  

Note
Multiple properties for this property can be specified by separating each with a semicolon.

If this property is not specified, the client cache folder will be created according to the SMSCACHEDIR property, will not be compressed and will be the size specified in the SMSCACHESIZE property.

Example: CCMSetup.exe SMSCACHEFLAGS=NTFSONLY;COMPRESS

Note
This setting is ignored when upgrading an existing client.

SMSCACHESIZE

Specifies the size of the client cache folder in MB or as a percentage when used with the PERCENTDISKSPACE or PERCENTFREEDISKSPACE property. If this property is not set, the folder defaults to a maximum size of 5120 MB.

Note
If a new package that must be downloaded would cause the folder to exceed the maximum size, and if the folder cannot be purged to make sufficient space available, the package download fails, and the advertised program will not run.

This setting is ignored when upgrading an existing client.

Example: CCMSetup.exe SMSCACHESIZE=100

SMSCONFIGSOURCE

Specifies the location and order that the Configuration Manager Client Installer checks for configuration settings. The property is a string containing one or more characters, each defining a specific configuration source. Use the character values R, P, M, and U, alone or in combination, as shown in the following examples:

• R: Check for configuration settings in the registry.
  
  
• P: Check for configuration settings in the installation properties provided on the command line.
  
  
• M: Check for existing settings when upgrading an older client with the Configuration Manager 2012 client software.
  
  
• U: Upgrade the SMS 2003 advanced client or upgrade the Configuration Manager 2012 client to a newer version (using the assigned site code).
  
  

By default, the client installation uses PU to check first the installation properties and then the existing settings.

Example: CCMSetup.exe SMSCONFIGSOURCE=RP

SMSDIRECTORYLOOKUP

Specifies how the client uses Windows Internet Name Service (WINS) for service location.

Service location by using WINS and HTTP client communication includes the management point and server locator point.

Service location by using WINS and HTTPS client communication includes the server locator point only.

If WINS is not used by clients to find a server locator point, it must be directly assigned to clients, for example, by using the SMSSLP Client.msi property.

This property has no impact on whether the client uses WINS for name resolution..

You can configure how WINS is used for service location using one of the following three modes:

• NOWINS: This is the most secure method. In this mode, WINS is not used for service location, and clients must have an alternative method of locating management points and a server locator point (if required).
  
  
• WINSSECURE: In this mode, a client that uses HTTP communication can use WINS for service location but verifies the management point's non-PKI certificate before communicating with it.
  
  To verify the certificate, the client checks its copy of the non-PKI trusted root key in WMI. If the signature on the management point certificate matches the client’s copy of the trusted root key, the certificate is validated, and the client communicates with the management point found through WINS. If the signature on the management point certificate does not match the client’s copy of the trusted root key, the certificate is not valid and the client will not communicate with the management point located with WINS.
  
  
• WINSPROMISCUOUS: In this mode, the client can use WINS for service location, but does not verify the management point's non-PKI certificate before communicating with it. This mode is not secure and is not recommended.
  
  

If this property is not specified, the default value of WINSSECURE will be used.

Example: CCMSetup.exe SMSDIRECTORYLOOKUP=NOWINS

SMSSIGNCERT

Specifies the full path and .cer file name of the exported self-signed certificate on the site server.

This certificate is stored in the SMS certificate store and has the Subject name Site Server and the friendly name Site Server Signing Certificate.

Example: CCMSetup.exe /UsePKICert SMSSIGNCERT=<Full path and file name>

SMSMP

Associates the Configuration Manager 2012 client with the specified management point. You can specify a fully qualified domain name as this property.

Example: CCMSetup.exe SMSMP=SMSMP01

SMSSITECODE

Specifies the Configuration Manager 2012 site to assign the Configuration Manager Client to. This can either be a three-character Configuration Manager 2012 site code or the word AUTO. If AUTO is specified, the Configuration Manager Client attempts to determine its Configuration Manager 2012 site assignment by using Active Directory or a server locator point.

Note
Do not use AUTO if the client finds a management point by using Domain Name System (DNS), or if you are also specifying the Internet-based management point (CCMHOSTNAME). In both of these scenarios, you must directly assign the client to its site.

Example: CCMSetup.exe SMSSITECODE=AUTO

SMSSLP

Specifies the server locator point for site assignment and locating management points for clients that cannot locate this information from Active Directory Domain Services, DNS, or WINS.

Example: CCMSetup.exe SMSSLP=SMSSLP01

CCMINSTALLDIR

Identifies the folder where the Configuration Manager Client files are installed. If this property is not set, then the client software is installed in the %Windir%\System32\CCM folder. Regardless of where the Configuration Manager Client files are installed, the Ccmcore.dll file is always installed in the %Windir%\System32 folder.

Example: CCMSetup.exe CCMINSTALLDIR="C:\Temp"

CCMADMINS

Specifies one or more Windows user accounts or groups to be given access to client settings and policies. This is useful where the Configuration Manager 2012 administrator does not have local administrative credentials on the client computer. You can specify a list of accounts separated by semi-colons.

Example: CCMSetup.exe CCMADMINS="Domain\Account1;Domain\Group1"

FSP

Specifies the fallback status point that receives and processes state messages sent by Configuration Manager 2012 client computers.

For more information about the fallback status point, see About the Fallback Status Point in Configuration Manager 2012.

Example: CCMSetup.exe FSP=SMSFP01

DNSSUFFIX

Specifies the DNS domain to use for locating the default management point in DNS, when DNS publishing is used.

For more information about locating management points in DNS, see Configuration Manager and Service Location.

If this property is specified, SMSSITECODE must not be set to AUTO.

When this property is specified, client assignment looks for a DNS service location resource record (SRV RR) in DNS, which includes this DNS suffix of the management point. For the exact record format, see How to Manually Publish the Default Management Point to DNS.

Note
By default, DNS publishing is not enabled in Configuration Manager 2012. For more information on whether you should use DNS publishing, see Determine If You Need to Publish to DNS.

Example: CCMSetup.exe SMSSITECODE=ABC DNSSUFFIX=contoso.com