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 displays 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 Planning for Internet-Based Client Management.

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

CCMCERTISSUERS

Specifies the certificate issuers list, which is a list of trusted root certification (CA) certificates that the Configuration Manager site trusts.

For more information about the certificate issuers list and how clients use it during the certificate selection process, see Planning for PKI Client Certificate Selection.

This is a case-sensitive match for subject attributes that are in the root CA certificate. Attributes can be separated by a comma (,) or semi-colon (;). Multiple root CA certificates can be specified by using a separator bar. Example:

CCMCERTISSUERS=”CN=Contoso Root CA; OU=Servers; O=Contoso, Ltd; C=US | CN=Litware Corporate Root CA; O=Litware, Inc.”

Tip
Reference the mobileclient.tcf file in the <Configuration Manager directory>\bin\<platform> folder on the site server computer to copy the CertificateIssuers=<string> that is configured for the site.

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 box, 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 box, 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 Planning for the Trusted Root Key.

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 Planning for the Trusted Root Key.

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

RESETKEYINFORMATION

If a System Center 2012 Configuration Manager 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%\CCM\Logs.

Example: CCMSetup.exe CCMENABLELOGGING=TRUE

CCMLOGLEVEL

Specifies the amount of detail to write to System Center 2012 Configuration Manager 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 System Center 2012 Configuration Manager 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 is 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 client cache 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 client cache folder on the client computer, which stores temporary files. By default, the location is %Windir \ccmcache.

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 System Center 2012 Configuration Manager 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 you upgrade an existing client.

SMSCACHESIZE

Specifies the size of the client cache folder in megabyte (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. The lowest value that you can specify is 1 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 program or application will not run.

This setting is ignored when you upgrade an existing client and when the client downloads software updates.

Example: CCMSetup.exe SMSCACHESIZE=100

Note

If you reinstall a client, you cannot use the SMSCACHESIZE or SMSCACHEFLAGS installation properties to set the cache size to be smaller than it was previously. If you try to do this, your value is ignored and the cache size is automatically set to the last size it was previously. For example, if you install the client with the default cache size of 5120 MB, and then reinstall the client with a cache size of 100 MB, the cache folder size on the reinstalled client is set to 5120 MB.

SMSCONFIGSOURCE

Specifies the location and order that the Configuration Manager 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 at the command prompt.
  
  
• M: Check for existing settings when upgrading an older client with the System Center 2012 Configuration Manager client software.
  
  
• U: Upgrade the installed client to a newer version (and use 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 whether the client can use Windows Internet Name Service (WINS) to find a management point that accepts HTTP connections. Clients use this method when they cannot find a management point in Active Directory Domain Services or in DNS.

This property is independent from whether the client uses WINS for name resolution.

You can configure two different modes for this property:

• NOWINS: This is the most secure setting for this property and prevents clients from finding a management point in WINS . When you use this setting, clients must have an alternative method to locate a management point on the intranet, such as Active Directory Domain Services or by using DNS publishing.
  
  
• WINSSECURE: In this mode, a client that uses HTTP communication can use WINS to find a management point. However, the client must have a copy of the trusted root key before it can successfully connect to the management point. For more information, see Planning for the Trusted Root Key.
  
  

If this property is not specified, the default value of WINSSECURE is 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

Specifies an initial management point for the Configuration Manager client to use.

Important
For Configuration Manager with no service pack: If the management point accepts client connections over HTTPS only (does not allow HTTP client connections), you must prefix the management point name with https://

Example: CCMSetup.exe SMSMP=smsmp01.contoso.com

Example: CCMSetup.exe SMSMP=smsmp01.contoso.com

Example: CCMSetup.exe SMSMP=https://smsmp01.contoso.com

SMSSITECODE

Specifies the Configuration Manager site to assign the Configuration Manager client to. This can either be a three-character site code or the word AUTO. If AUTO is specified, or if this property is not specified, the client attempts to determine its Configuration Manager site assignment from Active Directory Domain Services or from a specified management 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 these scenarios, you must directly assign the client to its site.

Example: CCMSetup.exe SMSSITECODE=XZY

CCMINSTALLDIR

Identifies the folder where the Configuration Manager client files are installed. If this property is not set, the client software is installed in the %Windir%\CCM folder. Regardless of where these files are installed, the Ccmcore.dll file is always installed in the %Windir%\System32 folder. In addition, on 64-bit operating systems, a copy of the Ccmcore.dll file is always installed in the %Windir%\SysWOW64 folder to support 32-bit applications that use the 32-bit version of the Configuration Manager client APIs from the Configuration Manager software developer kit (SDK).

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

CCMADMINS

Specifies one or more Windows user accounts or groups to be given access to client settings and policies. This is useful where the System Center 2012 Configuration Manager administrator does not have local administrative credentials on the client computer. You can specify a list of accounts that are 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 client computers.

For more information about the fallback status point, see Determine Whether You Require a Fallback Status Point.

Example: CCMSetup.exe FSP=SMSFP01

DNSSUFFIX

Specifies the DNS domain for clients to use to locate management points in DNS, when Configuration Manager publishes management points to DNS.

For more information about DNS publishing as a service location method for Configuration Manager clients, see Planning for Service Location by Clients.

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

When this property is specified, clients look for a DNS service location resource record (SRV RR) in DNS that includes this DNS suffix of the management point.

Note
By default, DNS publishing is not enabled in Configuration Manager.

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

CCMEVALINTERVAL

Specifies the frequency when the client health evaluation tool (ccmeval.exe) runs. You can specify a value from 1 through 1440 minutes. If you do not specify this property, or specify an incorrect value, the evaluation will run once a day.

CCMEVALHOUR

Specify the hour when the client health evaluation tool (ccmeval.exe) runs. You can specify a value between 0 (midnight) and 23 (11pm). If you do not specify this property, or specify and incorrect value, the evaluation will run at midnight.

IGNOREAPPVVERSIONCHECK

Specifies that the existence of the minimum required version of Microsoft Application Virtualization (App-V) is not checked before the client is installed.

Important
If you install the Configuration Manager client without installing App-V, you cannot deploy virtual applications.

Example: CCMSetup.exe IGNOREAPPVVERSIONCHECK=TRUE

NOTIFYONLY

Specifies that client status will report, but not remediate problems that are found with the Configuration Manager client.

For more information, see How to Configure Client Status in Configuration Manager.