Configuring Windows Server RDP Smart Card and YubiKey Redirection in Pakistan: FIDO2 WebAuthn, Kerberos PKINIT, and Phishing-Resistant MFA Guide

Complete guide to enabling Smart Card and YubiKey redirection in Windows Remote Desktop (RDP). Configure Group Policy, registry keys, and WebAuthn pass-through for phishing-resistant MFA.

Configuring Windows Server RDP Smart Card and YubiKey Redirection in Pakistan: FIDO2 WebAuthn, Kerberos PKINIT, and Phishing-Resistant MFA Guide
Direct Answer

To enable Smart Card and YubiKey redirection in Windows RDP: Set the Group Policy Do not allow smart card device redirection to Disabled under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection, ensure the Smart Card service (SCardSvr) is set to Automatic on both server and client, and add redirectsmartcards:i:1 and redirectwebauthn:i:1 to your client .rdp file.[1]

This production guide provides the exact server-side Group Policy objects, registry modifications, client configurations, and diagnostic steps required to pass physical security keys and PIV credentials through Remote Desktop.


1. How Smart Card and Security Key Redirection Functions in RDP

When connecting to a remote Windows Server from Pakistan or abroad, legacy password-based authentication exposes administrative credentials to keyloggers and brute-force attacks. Hardware security keys—such as YubiKeys and smart cards—enforce phishing-resistant multi-factor authentication (MFA).[2]

Remote Desktop Protocol (RDP) handles hardware keys through two distinct redirection architectures:

Authentication Protocol Physical Transport Mechanism Primary Use Case Supported Hardware
PC/SC Smart Card Subsystem Virtual Channel SCARD (MS-RDPESC) Windows Smart Card logon, Kerberos PKINIT, PIV certificates, BitLocker unlocking YubiKey PIV, Gemalto, Feitian, CAC/PIV cards
WebAuthn / FIDO2 Pass-Through Virtual Channel Microsoft::Windows::RDS::WebAuthn Browser logins (Google, GitHub, AWS, Microsoft Entra ID), passkeys, FIDO2 U2F YubiKey 5 Series, Google Titan, Windows Hello
RemoteFX USB Redirection Raw USB bus virtualization over TCP Specialized cryptographic tokens lacking standard PC/SC drivers Custom USB dongles, proprietary PKI tokens

The native PC/SC Smart Card and WebAuthn channels operate at a higher protocol layer than raw USB redirection. They tunnel cryptographic APDUs (Application Protocol Data Units) without requiring client USB device ownership, resulting in faster handshakes and lower latency over internet links.[3]


2. Server-Side Group Policy: How to Enable Smart Card Redirection in Windows RDP

By default, hardened Windows Server operating systems disable device pass-through to restrict attack surfaces. You must configure Group Policy on the Remote Desktop Session Host (RDSH) or standalone Windows Server.[1]

Step 1: Open Local Group Policy Editor

Press Win + R, type gpedit.msc, and press Enter.

Step 2: Navigate to Device and Resource Redirection

Browse the policy tree to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection

Configure the following policies:

  1. Do not allow smart card device redirection: Set to Disabled. (In Windows Group Policy, setting this to Disabled permits the redirection).
  2. Do not allow WebAuthn redirection: Set to Disabled. This enables FIDO2 and WebAuthn security key pass-through for web browsers inside the RDP session.[4]
  3. Do not allow supported Plug and Play device redirection: Set to Disabled if using multi-interface security keys.
# Automated PowerShell Configuration for Remote Desktop Host
# Sets registry equivalents directly in Local Machine policy hive

$RegPath = "HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"
If (!(Test-Path $RegPath)) { New-Item -Path $RegPath -Force | Out-Null }

# 0 allows smart card redirection, 1 blocks it
Set-ItemProperty -Path $RegPath -Name "fEnableSmartCard" -Value 1 -Type DWord
Set-ItemProperty -Path $RegPath -Name "fDisableSmartCard" -Value 0 -Type DWord
Set-ItemProperty -Path $RegPath -Name "fDisableWebAuthn" -Value 0 -Type DWord

# Force immediate Group Policy update
gpupdate /force
Pro Tip: Setting fDisableWebAuthn=0 requires Windows Server 2022 or Windows 10/11 version 22H2 or newer on both the host and client. If you connect from an older Windows build, FIDO2 web authentication will fail even if the Smart Card PIV certificate succeeds.

3. Configuring the Smart Card Service Architecture

Both the client machine and the remote Windows Server must run the native Windows Smart Card service (SCardSvr). If this service is stopped, disabled, or crashed, the Remote Desktop client cannot read the cryptographic reader on your physical workstation.[5]

# Verify and configure Smart Card service startup on both Host and Client
Get-Service -Name SCardSvr | Select-Object Name, DisplayName, Status, StartType

# Set startup type to Automatic and start the service
Set-Service -Name SCardSvr -StartupType Automatic
Start-Service -Name SCardSvr

# Verify the Smart Card Device Enumeration Service
Set-Service -Name ScDeviceEnum -StartupType Automatic
Start-Service -Name ScDeviceEnum
Common Pitfall: Do not set SCardSvr to "Manual" on dedicated terminal servers. If an idle session times out, the service can shut down automatically and fail to reinitialize when a user reconnects with their hardware key.

4. Client-Side Setup: Remote Desktop Connection (mstsc.exe) Configuration

Even when the server permits device pass-through, the client connection profile must explicitly instruct mstsc.exe to expose the hardware token.[3]

[Local Workstation: YubiKey / Smart Card Inserted]
                    │
                    ▼
[Local SCardSvr & USB CCID Driver Reads Token]
                    │
                    ▼
[mstsc.exe with redirectsmartcards:i:1] ─── Virtual Channel MS-RDPESC ───> [Remote Windows Server]
                    │                                                             │
                    ▼                                                             ▼
[WebAuthn Pass-Through: redirectwebauthn:i:1] ───────────────────────────> [Remote Browser / LSASS]

Method A: Graphical User Interface (mstsc.exe)

  1. Open Remote Desktop Connection (mstsc.exe).
  2. Click Show Options at the bottom left.
  3. Switch to the Local Resources tab.
  4. Under Local devices and resources, click More….
  5. Check the box for Smart cards or Windows Hello for Business.
  6. Check WebAuthn (Windows Hello or security keys).
  7. Click OK, return to the General tab, and click Save.

Method B: Directly Editing the .rdp Configuration File

Open your .rdp connection file in a text editor and verify that the following directives are set:

redirectsmartcards:i:1
redirectwebauthn:i:1
redirectprinters:i:0
redirectclipboard:i:1
devicestoredirect:s:*

For enterprises running mission-critical database administration, financial terminals, and secure developer environments, zero-trust hardware key authentication requires low-latency, uninterrupted connectivity. Explore our high-performance Dedicated Servers and locally routed Dedicated Servers in Pakistan, equipped with out-of-band IPMI interfaces, enterprise NVMe storage, and round-the-clock technical operations.


5. Step-by-Step Diagnostic Runbook: Why Is My YubiKey or Smart Card Not Recognized in RDP?

If your remote session shows “No smart card found” or web browsers fail to prompt for touch verification, follow this diagnostic checklist.[6]

Diagnostic Checklist

  • Check 1: Local Device Recognition. On your local physical PC, open PowerShell and execute certutil -scinfo. Verify that your smart card reader and certificate are listed.
  • Check 2: Remote Session Reader Visibility. Inside the RDP session, run certutil -scinfo. You should see Reader: Microsoft Multi-Slot Reader or the exact name of your physical reader with a redirected prefix.
  • Check 3: Driver Installation on the Remote Host. YubiKey PIV cards require the Microsoft Usbccid Smartcard Reader (WUDF) or Yubico Minidriver. Verify in Device Manager under Smart card readers.
  • Check 4: Group Policy Override. Confirm that domain-level GPO has not overridden local server settings by running gpresult /h gpreport.html.
:: Run inside the RDP Session to test smart card reader detection
certutil -scinfo

:: Expected healthy output includes:
:: ================= Card 0 ================
:: Provider = Microsoft Base Smart Card Crypto Provider
:: Key Container = {UUID}
:: Card: YubiKey PIV

6. People Also Ask: Frequently Answered Questions

How do I enable Smart Card redirection in Remote Desktop?

Enable the Smart Card service on both client and server, verify that the Group Policy Do not allow smart card device redirection is set to Disabled on the server, and check the Smart cards box under the Local Resources tab in mstsc.exe.[1]

Why is my YubiKey or Smart Card not recognized in RDP?

The most common causes are a stopped SCardSvr service on the remote server, missing redirectsmartcards:i:1 in the client .rdp profile, or Group Policy blocking device pass-through. On newer web services, missing WebAuthn redirection (redirectwebauthn:i:1) prevents FIDO2 keys from triggering.[4]

Which Group Policy settings control Smart Card redirection in Windows Server?

The primary policy is Do not allow smart card device redirection, located at Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection. Secondary policies include Do not allow WebAuthn redirection and Do not allow supported Plug and Play device redirection.[1]

Does RDP Smart Card redirection work across different subnets or WAN connections?

Yes. Because Smart Card and WebAuthn data is transmitted across dedicated RDP virtual channels (MS-RDPESC and Microsoft::Windows::RDS::WebAuthn) within the primary TCP/UDP 3389 stream, redirection functions seamlessly across firewalls, subnets, and WAN routes without opening extra ports.[3]


Secure, Low-Latency Remote Infrastructure

Protect your enterprise workstations and developer workloads with hardware-level security, isolated bare-metal servers, and optimized low-latency routing across Pakistan. Nextgen delivers enterprise-grade dedicated hosting built for high security.

Explore Pakistan Dedicated Servers
Sources & Official References
  1. Microsoft Learn. "Device Redirection Group Policy Settings for Remote Desktop Services." https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-device-redirection
  2. Yubico Documentation. "Using YubiKeys with Remote Desktop Protocol (RDP) and PIV Smart Card Redirection." https://support.yubico.com/hc/en-us/articles/360016649239-YubiKey-Support-over-RDP
  3. Microsoft Open Specifications. "[MS-RDPESC]: Remote Desktop Protocol: Smart Card Virtual Channel Extension." https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpesc/
  4. Microsoft Learn. "WebAuthn Redirection in Remote Desktop Services (Windows Server 2022)." https://learn.microsoft.com/en-us/azure/virtual-desktop/fido2-webauthn-redirection
  5. Microsoft TechNet. "Smart Card Architecture and Troubleshooting (Certutil & SCardSvr)." https://learn.microsoft.com/en-us/windows/security/identity-protection/smart-cards/smart-card-debugging
  6. NIST Special Publication. "SP 800-63B: Digital Identity Guidelines - Authentication and Lifecycle Management." https://pages.nist.gov/800-63-3/sp800-63b.html

Disclaimer: This post is for informational and educational purposes only, accurate to the best of our knowledge at publication. It does not constitute advice. We do not guarantee accuracy or completeness and accept no liability for any decisions or losses resulting from reliance on this content.

Disclaimer: This post is for informational and educational purposes only, accurate to the best of our knowledge at publication. It does not constitute advice. We do not guarantee accuracy or completeness and accept no liability for any decisions or losses resulting from reliance on this content.