About Client Installation Properties in Configuration Manager
Updated: August 14, 2015
Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1
Use the System Center 2012 Configuration Manager CCMSetup.exe command to manually install the System Center 2012 Configuration Manager client software on computers in your enterprise.
The CCMSetup program downloads all the necessary files to complete the client installation from a specified management point or from a specified source location. These files might include the following:
The Windows Installer package Client.msi that installs the System Center 2012 Configuration Manager client software.
Microsoft Background Intelligent Transfer Service (BITS) installation files, if required.
Windows Installer installation files, if required.
Updates and fixes for the System Center 2012 Configuration Manager client, if required.
Note
In System Center 2012 Configuration Manager, you cannot run the Client.msi file directly.
CCMSetup.exe provides several command-line properties to customize the installation behavior. Additionally, you can also specify properties to modify the behavior of Client.msi at the CCMSetup.exe command line.
Important
You must specify all required CCMSetup properties before you specify properties for Client.msi.
CCMSetup.exe and its supporting files are located on the System Center 2012 Configuration Manager site server in the Client folder of the System Center 2012 Configuration Manager installation folder. This folder is shared to the network as <Site Server Name>\SMS_<Site Code>\Client.
At the command prompt, the CCMSetup.exe command uses the following format:
CCMSetup.exe [Ccmsetup properties] [client.msi setup properties]
For example, CCMSetup.exe /mp:SMSMP01 /logon SMSSITECODE=S01 FSP=SMSFSP01 performs the following actions:
Specifies the management point named SMSMP01 to request a list of distribution points to download the client installation source files.
Specifies that installation should stop if a version of the System Center 2012 Configuration Manager or Configuration Manager 2007 client already exists on the computer.
Instructs client.msi to assign the client to the site code S01.
Instructs client.msi to use the fallback status point named SMSFP01.
Note
If a property contains spaces, surround it by quotation marks ("").
Note
Auto upgrade of clients can fail when the installation parameters for CCMSetup run with double quotes around them. Double quotes can be caused by the following:
-
Running CCMSetup and specifying a parameter that is published to Active Directory for the site the client is being assigned to. (Each parameter from AD receives a set of quotes, and CCMSetup adds an additional set of quotes).
-
Running CCMSetup and using quotes when specifying a parameter. (CCMsetup adds an additional set of quotes).
The properties described in the following table are available to modify the installation behavior of CCMSetup.exe.
Important
If you have extended the Active Directory schema for System Center 2012 Configuration Manager, many client installation properties are published in Active Directory Domain Services and read automatically by the System Center 2012 Configuration Manager client. For a list of the client installation properties published in Active Directory Domain Services, see About Client Installation Properties Published to Active Directory Domain Services in Configuration Manager.
CCMSetup.exe Command-Line Properties
Property |
More information |
|---|---|
/? |
Opens the CCMSetup dialog box showing command-line properties for ccmsetup.exe. Example: ccmsetup.exe /? |
/source:<Path> |
Specifies the location from which to download installation files. You can use a local or UNC installation path. Files are downloaded by using the server message block (SMB) protocol. Note You can use the /source property multiple times at the command line to specify alternative locations from which to download installation files. Important To use the /source command-line property, the Windows user account that is used for client installation must have Read permissions to the installation location. Example: ccmsetup.exe /source:"\\computer\folder" |
/mp:<Computer> |
Specifies a source management point for computers to connect to so that they can find the nearest distribution point to download the client installation files. If there are no distribution points or computers cannot download the files from the distribution points after 4 hours, clients download the files from the specified management point. Computers download the files over an HTTP or HTTPS connection, depending on the site system role configuration for client connections. The download uses BITS throttling, if BITS throttling is configured. If all distribution points and management points are configured for HTTPS client connections only, you must verify that the client computer has a valid public key infrastructure (PKI) client certificate. Note You can use the /mp command-line property to specify multiple management points so that if the computer fails to connect to the first one, the next is tried, and so on. When you specify multiple management points, separate the values by using semicolons. Important This property is used only to specify an initial management point for computers to find the closes source to download the client installation files. It does not specify the management point to which the client will become assigned after installation. You can specify any System Center 2012 Configuration Manager management point in any site to provide computers with a list of distribution points from which they can download the client installation files. Example for when you use the computer name: ccmsetup.exe /mp:SMSMP01 Example for when you use the FQDN: ccmsetup.exe /mp:smsmp01.contoso.com Tip If the client connects to a management point by using HTTPS, typically, you must specify the FQDN for this option rather than the computer name. The value that you specify must be included in the management point’s PKI certificate Subject or Subject Alternative Name. Although Configuration Manager supports a computer name only in this PKI certificate for connections on the intranet, as a security best practice, an FQDN is recommended. |
/retry:<Minutes> |
Specifies the retry interval if CCMSetup.exe fails to download installation files. The default value is 10 minutes. CCMSetup continues to retry until it reaches the limit specified in the downloadtimeout installation property. Example: ccmsetup.exe /retry:20 |
/noservice |
Prevents CCMSetup from running as a service. When CCMSetup runs as a service, it runs in the context of the Local System account of the computer, which might not have sufficient rights to access network resources that are required for the installation process. When you specify the /noservice option, CCMSetup.exe runs in the context of the user account that you use to start the installation process. Additionally, if you are use a script to run CCMSetup.exe with the /service property, CCMSetup.exe exits after the service starts and might not report installation details correctly because the CCMSetup service performs the client installation. If this command-line property is not specified, by default, /service will be used. Example: ccmsetup.exe /noservice |
/service |
Specifies that CCMSetup should run as a service that uses the local system account. Example: ccmsetup.exe /service |
/uninstall |
Specifies that the System Center 2012 Configuration Manager client software should be uninstalled. For more information, see How to Manage Clients in Configuration Manager. Example: ccmsetup.exe /uninstall |
/logon |
Specifies that the client installation should stop if any version of the System Center 2012 Configuration Manager or the Configuration Manager client is already installed. Example: ccmsetup.exe /logon |
/forcereboot |
Specifies that CCMSetup should force the client computer to restart if this is necessary to complete the client installation. If this option is not specified, CCMSetup exits when a restart is necessary, and then continues after the next manual restart. Example: CCMSetup.exe /forcereboot |
/BITSPriority:<Priority> |
Specifies the download priority when client installation files are downloaded over an HTTP connection. Possible values are as follows:
The default value is NORMAL. Example: ccmsetup.exe /BITSPriority:HIGH |
/downloadtimeout:<Minutes> |
Specifies the length of time in minutes that CCMSetup attempts to download the client installation files before it gives up. The default value is 1440 minutes (1 day). Example: ccmsetup.exe /downloadtimeout:100 |
/UsePKICert |
When specified, the client uses a PKI certificate that includes client authentication, if one is available. If a valid certificate cannot be found, the client falls back to using an HTTP connection and a self-signed certificate. When this option is not specified, the client uses a self-signed certificate and all communications to site systems are over HTTP. Note There are some scenarios where you do not have to specify this property when you are installing a client to use a PKI client certificate. These scenarios include installing a client by using client push and software update point–based client installation. However, you must specify this property whenever you manually install a client and use the /mp property to specify a management point that is configured to accept only HTTPS client connections. You also must specify this property when you install a client for Internet-only communication, by using the CCMALWAYSINF=1 property (together with the properties for the Internet-based management point and the site code). For more information about Internet-based client management, see Planning for Internet-Based Client Management. Example: CCMSetup.exe /UsePKICert |
/NoCRLCheck |
Specifies that a client should not check the certificate revocation list (CRL) when it communicates over HTTPS by using a PKI certificate. When this option is not specified, the client checks the CRL before establishing an HTTPS connection by using PKI certificates. For more information about client CRL checking, see Planning for PKI Certificate Revocation. Example: CCMSetup.exe /UsePKICert /NoCRLCheck |
/config:<configuration file> |
Specifies the name of a text file containing client installation properties. Unless you also specify the /noservice CCMSetup property, this file must be located in the CCMSetup folder, which is <%Windir%>\Ccmsetup for 32-bit and 64-bit operating systems. If you specify the /noservice property, this file must be located in the same folder from which you run CCMSetup.exe. Example: CCMSetup.exe /config:<Configuration File Name.txt> Use the mobileclienttemplate.tcf file in the <Configuration Manager directory>\bin\<platform> folder on the site server computer to provide the correct format of the file. This file also contains information in comment form about the sections and how they are used. Specify the client installation properties in the [Client Install] section, after the following text: Install=INSTALL=ALL. Example [Client Install] section entry: Install=INSTALL=ALL SMSSITECODE=ABC SMSCACHESIZE=100 |
/skipprereq:<filename> |
Specifies that CCMSetup.exe must not install the specified prerequisite program when the Configuration Manager client is installed. Examples: CCMSetup.exe /skipprereq:silverlight.exe or CCMSetup.exe /skipprereq:dotnetfx40_client_x86_x64.exe;Silverlight.exe Note This property supports entering multiple values. Use the semicolon character (;) to separate each value. |
/forceinstall |
For System Center 2012 Configuration Manager SP1 and later: Specify that any existing client will be uninstalled and then a new client will be installed. |
/ExcludeFeatures:<feature> |
Specifies that CCMSetup.exe will not install the specified feature when the Configuration Manager client is installed. Example: CCMSetup.exe /ExcludeFeatures:ClientUI will not install the Software Center on the client. Note For this release, ClientUI is the only value supported with the /ExcludeFeatures property. |
Client.msi Properties
The properties described in the following table can modify the installation behavior of client.msi. If you use the client push installation method, you can also specify the properties in the Client tab of the Client Push Installation Properties dialog box.
Property |
More information |
|---|---|
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 CCMLOGMAXSIZE), 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:
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:
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:
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 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 you also specify the Internet-based management point (CCMHOSTNAME). In this scenario, 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 a DNS domain for clients to locate management points that are published in DNS. When a management point is located, it informs the client about other management points in the hierarchy. This means that the management point that is located by using DNS publishing does not have to be from the client’s site, but can be any management point in the hierarchy. Note You do not have to specify this property if the client is in the same domain as a published management point. In this scenario, the client’s domain is automatically used to search DNS for management points. For more information about DNS publishing as a service location method for Configuration Manager clients, see Service Location and how clients determine their assigned 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. Example: CCMSetup.exe NOTIFYONLY=TRUE For more information, see How to Configure Client Status in Configuration Manager. |
Supported Attribute Values for the PKI Certificate Selection Criteria
Configuration Manager supports the following attribute values for the PKI certificate selection criteria:
OID attribute |
Distinguished Name attribute |
Attribute definition |
|---|---|---|
0.9.2342.19200300.100.1.25 |
DC |
Domain component |
1.2.840.113549.1.9.1 |
E or E-mail |
Email address |
2.5.4.3 |
CN |
Common name |
2.5.4.4 |
SN |
Subject name |
2.5.4.5 |
SERIALNUMBER |
Serial number |
2.5.4.6 |
C |
Country code |
2.5.4.7 |
L |
Locality |
2.5.4.8 |
S or ST |
State or province name |
2.5.4.9 |
STREET |
Street address |
2.5.4.10 |
O |
Organization name |
2.5.4.11 |
OU |
Organizational unit |
2.5.4.12 |
T or Title |
Title |
2.5.4.42 |
G or GN or GivenName |
Given name |
2.5.4.43 |
I or Initials |
Initials |
2.5.29.17 |
(no value) |
Subject Alternative Name |