Policy CSP - ADMX_Smartcard
Tip
This CSP contains ADMX-backed policies which require a special SyncML format to enable or disable. You must specify the data type in the SyncML as <Format>chr</Format>. For details, see Understanding ADMX-backed policies.
The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.
AllowCertificatesWithNoEKU
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/AllowCertificatesWithNoEKU
This policy setting lets you allow certificates without an Extended Key Usage (EKU) set to be used for logon.
In versions of Windows prior to Windows Vista, smart card certificates that are used for logon require an extended key usage (EKU) extension with a smart card logon object identifier. This policy setting can be used to modify that restriction.
If you enable this policy setting, certificates with the following attributes can also be used to log on with a smart card:
Certificates with no EKU
Certificates with an All Purpose EKU
Certificates with a Client Authentication EKU.
If you disable or don't configure this policy setting, only certificates that contain the smart card logon object identifier can be used to log on with a smart card.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | AllowCertificatesWithNoEKU |
| Friendly Name | Allow certificates with no extended key usage certificate attribute |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | AllowCertificatesWithNoEKU |
| ADMX File Name | Smartcard.admx |
AllowIntegratedUnblock
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/AllowIntegratedUnblock
This policy setting lets you determine whether the integrated unblock feature will be available in the logon User Interface (UI).
In order to use the integrated unblock feature your smart card must support this feature. Please check with your hardware manufacturer to see if your smart card supports this feature.
If you enable this policy setting, the integrated unblock feature will be available.
If you disable or don't configure this policy setting then the integrated unblock feature won't be available.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | AllowIntegratedUnblock |
| Friendly Name | Allow Integrated Unblock screen to be displayed at the time of logon |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | AllowIntegratedUnblock |
| ADMX File Name | Smartcard.admx |
AllowSignatureOnlyKeys
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/AllowSignatureOnlyKeys
This policy setting lets you allow signature key-based certificates to be enumerated and available for logon.
If you enable this policy setting then any certificates available on the smart card with a signature only key will be listed on the logon screen.
If you disable or don't configure this policy setting, any available smart card signature key-based certificates won't be listed on the logon screen.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | AllowSignatureOnlyKeys |
| Friendly Name | Allow signature keys valid for Logon |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | AllowSignatureOnlyKeys |
| ADMX File Name | Smartcard.admx |
AllowTimeInvalidCertificates
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/AllowTimeInvalidCertificates
This policy setting permits those certificates to be displayed for logon that are either expired or not yet valid.
Under previous versions of Microsoft Windows, certificates were required to contain a valid time and not be expired. The certificate must still be accepted by the domain controller in order to be used. This setting only controls the displaying of the certificate on the client machine.
If you enable this policy setting certificates will be listed on the logon screen regardless of whether they've an invalid time or their time validity has expired.
If you disable or don't configure this policy setting, certificates which are expired or not yet valid won't be listed on the logon screen.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | AllowTimeInvalidCertificates |
| Friendly Name | Allow time invalid certificates |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | AllowTimeInvalidCertificates |
| ADMX File Name | Smartcard.admx |
CertPropEnabledString
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/CertPropEnabledString
This policy setting allows you to manage the certificate propagation that occurs when a smart card is inserted.
If you enable or don't configure this policy setting then certificate propagation will occur when you insert your smart card.
If you disable this policy setting, certificate propagation won't occur and the certificates won't be made available to applications such as Outlook.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | CertPropEnabledString |
| Friendly Name | Turn on certificate propagation from smart card |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\CertProp |
| Registry Value Name | CertPropEnabled |
| ADMX File Name | Smartcard.admx |
CertPropRootCleanupString
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/CertPropRootCleanupString
This policy setting allows you to manage the clean up behavior of root certificates.
If you enable this policy setting then root certificate cleanup will occur according to the option selected.
If you disable or don't configure this setting then root certificate clean up will occur on log off.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | CertPropRootCleanupString |
| Friendly Name | Configure root certificate clean up |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\CertProp |
| ADMX File Name | Smartcard.admx |
CertPropRootEnabledString
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/CertPropRootEnabledString
This policy setting allows you to manage the root certificate propagation that occurs when a smart card is inserted.
- If you enable or don't configure this policy setting then root certificate propagation will occur when you insert your smart card.
Note
For this policy setting to work the following policy setting must also be enabled: Turn on certificate propagation from smart card.
- If you disable this policy setting then root certificates won't be propagated from the smart card.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | CertPropRootEnabledString |
| Friendly Name | Turn on root certificate propagation from smart card |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\CertProp |
| Registry Value Name | EnableRootCertificatePropagation |
| ADMX File Name | Smartcard.admx |
DisallowPlaintextPin
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/DisallowPlaintextPin
This policy setting prevents plaintext PINs from being returned by Credential Manager.
If you enable this policy setting, Credential Manager doesn't return a plaintext PIN.
If you disable or don't configure this policy setting, plaintext PINs can be returned by Credential Manager.
Note
Enabling this policy setting could prevent certain smart cards from working on Windows. Please consult your smart card manufacturer to find out whether you'll be affected by this policy setting.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | DisallowPlaintextPin |
| Friendly Name | Prevent plaintext PINs from being returned by Credential Manager |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | DisallowPlaintextPin |
| ADMX File Name | Smartcard.admx |
EnumerateECCCerts
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/EnumerateECCCerts
This policy setting allows you to control whether elliptic curve cryptography (ECC) certificates on a smart card can be used to log on to a domain.
If you enable this policy setting, ECC certificates on a smart card can be used to log on to a domain.
If you disable or don't configure this policy setting, ECC certificates on a smart card can't be used to log on to a domain.
Note
This policy setting only affects a user's ability to log on to a domain. ECC certificates on a smart card that are used for other applications, such as document signing, aren't affected by this policy setting.
Note
If you use an ECDSA key to log on, you must also have an associated ECDH key to permit logons when you aren't connected to the network.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | EnumerateECCCerts |
| Friendly Name | Allow ECC certificates to be used for logon and authentication |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | EnumerateECCCerts |
| ADMX File Name | Smartcard.admx |
FilterDuplicateCerts
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/FilterDuplicateCerts
This policy setting lets you configure if all your valid logon certificates are displayed.
During the certificate renewal period, a user can have multiple valid logon certificates issued from the same certificate template. This can cause confusion as to which certificate to select for logon. The common case for this behavior is when a certificate is renewed and the old one hasn't yet expired. Two certificates are determined to be the same if they're issued from the same template with the same major version and they're for the same user (determined by their UPN).
If there are two or more of the "same" certificate on a smart card and this policy is enabled then the certificate that's used for logon on Windows 2000, Windows XP, and Windows 2003 Server will be shown, otherwise the certificate with the expiration time furthest in the future will be shown.
Note
This setting will be applied after the following policy: "Allow time invalid certificates".
If you enable or don't configure this policy setting, filtering will take place.
If you disable this policy setting, no filtering will take place.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | FilterDuplicateCerts |
| Friendly Name | Filter duplicate logon certificates |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | FilterDuplicateCerts |
| ADMX File Name | Smartcard.admx |
ForceReadingAllCertificates
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/ForceReadingAllCertificates
This policy setting allows you to manage the reading of all certificates from the smart card for logon.
During logon Windows will by default only read the default certificate from the smart card unless it supports retrieval of all certificates in a single call. This setting forces Windows to read all the certificates from the card. This can introduce a significant performance decrease in certain situations. Please contact your smart card vendor to determine if your smart card and associated CSP supports the required behavior.
If you enable this setting, then Windows will attempt to read all certificates from the smart card regardless of the feature set of the CSP.
If you disable or don't configure this setting, Windows will only attempt to read the default certificate from those cards that don't support retrieval of all certificates in a single call. Certificates other than the default won't be available for logon.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | ForceReadingAllCertificates |
| Friendly Name | Force the reading of all certificates from the smart card |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | ForceReadingAllCertificates |
| ADMX File Name | Smartcard.admx |
IntegratedUnblockPromptString
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/IntegratedUnblockPromptString
This policy setting allows you to manage the displayed message when a smart card is blocked.
- If you enable this policy setting, the specified message will be displayed to the user when the smart card is blocked.
Note
The following policy setting must be enabled - Allow Integrated Unblock screen to be displayed at the time of logon.
- If you disable or don't configure this policy setting, the default message will be displayed to the user when the smart card is blocked, if the integrated unblock feature is enabled.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | IntegratedUnblockPromptString |
| Friendly Name | Display string when smart card is blocked |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| ADMX File Name | Smartcard.admx |
ReverseSubject
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/ReverseSubject
This policy setting lets you reverse the subject name from how it's stored in the certificate when displaying it during logon.
By default the user principal name (UPN) is displayed in addition to the common name to help users distinguish one certificate from another. For example, if the certificate subject was CN=User1, OU=Users, DN=example, DN=com and had an UPN of user1@example.com then "User1" will be displayed along with "user1@example.com". If the UPN isn't present then the entire subject name will be displayed. This setting controls the appearance of that subject name and might need to be adjusted per organization.
If you enable this policy setting or don't configure this setting, then the subject name will be reversed.
If you disable , the subject name will be displayed as it appears in the certificate.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | ReverseSubject |
| Friendly Name | Reverse the subject name stored in a certificate when displaying |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | ReverseSubject |
| ADMX File Name | Smartcard.admx |
SCPnPEnabled
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/SCPnPEnabled
This policy setting allows you to control whether Smart Card Plug and Play is enabled.
If you enable or don't configure this policy setting, Smart Card Plug and Play will be enabled and the system will attempt to install a Smart Card device driver when a card is inserted in a Smart Card Reader for the first time.
If you disable this policy setting, Smart Card Plug and Play will be disabled and a device driver won't be installed when a card is inserted in a Smart Card Reader.
Note
This policy setting is applied only for smart cards that have passed the Windows Hardware Quality Labs (WHQL) testing process.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | SCPnPEnabled |
| Friendly Name | Turn on Smart Card Plug and Play service |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\ScPnP |
| Registry Value Name | EnableScPnP |
| ADMX File Name | Smartcard.admx |
SCPnPNotification
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/SCPnPNotification
This policy setting allows you to control whether a confirmation message is displayed when a smart card device driver is installed.
If you enable or don't configure this policy setting, a confirmation message will be displayed when a smart card device driver is installed.
If you disable this policy setting, a confirmation message won't be displayed when a smart card device driver is installed.
Note
This policy setting is applied only for smart cards that have passed the Windows Hardware Quality Labs (WHQL) testing process.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | SCPnPNotification |
| Friendly Name | Notify user of successful smart card driver installation |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\ScPnP |
| Registry Value Name | ScPnPNotification |
| ADMX File Name | Smartcard.admx |
X509HintsNeeded
| Scope | Editions | Applicable OS |
|---|---|---|
| ✅ Device ❌ User |
✅ Pro ✅ Enterprise ✅ Education ✅ Windows SE ✅ IoT Enterprise / IoT Enterprise LTSC |
✅ Windows 10, version 2004 [10.0.19041.1202] and later ✅ Windows 10, version 2009 [10.0.19042.1202] and later ✅ Windows 10, version 21H1 [10.0.19043.1202] and later ✅ Windows 11, version 21H2 [10.0.22000] and later |
./Device/Vendor/MSFT/Policy/Config/ADMX_Smartcard/X509HintsNeeded
This policy setting lets you determine whether an optional field will be displayed during logon and elevation that allows a user to enter his or her user name or user name and domain, thereby associating a certificate with that user.
If you enable this policy setting then an optional field that allows a user to enter their user name or user name and domain will be displayed.
If you disable or don't configure this policy setting, an optional field that allows users to enter their user name or user name and domain won't be displayed.
Description framework properties:
| Property name | Property value |
|---|---|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
Tip
This is an ADMX-backed policy and requires SyncML format for configuration. For an example of SyncML format, refer to Enabling a policy.
ADMX mapping:
| Name | Value |
|---|---|
| Name | X509HintsNeeded |
| Friendly Name | Allow user name hint |
| Location | Computer Configuration |
| Path | Windows Components > Smart Card |
| Registry Key Name | SOFTWARE\Policies\Microsoft\Windows\SmartCardCredentialProvider |
| Registry Value Name | X509HintsNeeded |
| ADMX File Name | Smartcard.admx |
Related articles
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for