CNG v3 certificates overview - Configuration Manager (2024)

Configuration Manager supports Cryptography: Next Generation (CNG) certificates. Configuration Manager clients can use a PKI client authentication certificate with the private key generated and stored in a CNG Key Storage Provider (KSP). With KSP support, Configuration Manager clients support hardware-based private keys, such as a TPM KSP for PKI client authentication certificates.

Supported scenarios

You can use Cryptography API: Next Generation (CNG) v3 certificate templates for the following scenarios:

• Client registration and communication with an HTTPS management point
• Software distribution and application deployment with an HTTPS distribution point
• OS deployment
• Client messaging SDK (with latest update) and ISV Proxy
• Cloud management gateway (CMG) configuration
• User-targeted available applications in Software Center

Also use CNG v3 certificates for the following HTTPS-enabled server roles:

• Management point
• Distribution point
• Software update point
• State migration point
• Certificate registration point, including the NDES server with the Configuration Manager policy module

Unsupported scenarios

The following scenarios currently aren't supported:

• The following server roles aren't operational when installed in HTTPS mode with a CNG v3 certificate bound to the web site in Internet Information Services (IIS):

  • Enrollment point
  • Enrollment proxy point

To use CNG certificates

To use CNG v3 certificates, your certification authority (CA) needs to provide CNG certificate templates for target machines. Template details vary according to the scenario; however, the following properties are required:

• Compatibility tab

  • Certificate Authority must be Windows Server 2008 or later. (Windows Server 2012 is recommended.)

  • Certificate recipient must be Windows Vista/Server 2008 or later. (Windows 8/Windows Server 2012 is recommended.)

• Cryptography tab

  • Provider Category must be Key Storage Provider. (required)

  • Algorithm name must be RSA. (required)

  • Request must use one of the following providers: must be Microsoft Software Key Storage Provider.

For best results, we recommend building the Subject Name from Active Directory information. Use the DNS Name for Subject name format and include the DNS name in the alternate subject name. Otherwise, you must provide this information when the device enrolls into the certificate profile.