Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.
Use mstsc.exe /remoteGuard for the current signed-in-session experience; RDCMan 3.23 does not document a setting that makes an empty credential profile behave equivalently.
mstsc.exe /v:<target-fqdn> /remoteGuard
Remote Credential Guard uses the signed-in credentials through Kerberos and does not permit NTLM fallback. Microsoft documents mstsc.exe /remoteGuard as the per-session method when Remote Credential Guard is not enforced by client policy.^1^
What the RDCMan prompt means
RDCMan 3.23 documents:
- Explicit username, password, and domain fields under Logon Credentials
- Inherited logon settings
- Credential profiles and credential stores
- Smart-card authentication through Redirect smart cards
It does not document an option that tells an empty credential profile to use the current Windows session for Remote Credential Guard SSO.^2^
Therefore, the available documentation cannot establish whether the RDCMan 3.23 prompt is an intentional limitation or a regression. It does establish that entering the Windows Hello PIN into Remote Computer Credentials is not an equivalent workaround: cloud Kerberos trust cannot be used as a supplied credential for RDP/VDI. It can support RDP through either a certificate enrolled into the Windows Hello for Business container or Remote Credential Guard SSO.^3^
No server-side change is indicated
Because the same account and target already connect through mstsc with the signed-in session, avoid changing server policy or the DisableRestrictedAdmin registry value merely to address RDCMan’s preconnection prompt. Those changes require administrative access and configure Remote Credential Guard prerequisites; they do not provide a documented RDCMan option for suppressing its credential dialog.
If another target also fails with mstsc.exe /remoteGuard, then verify these prerequisites:
- Connect using the target’s FQDN so Kerberos can be used.
- Confirm the client can reach a domain controller; Remote Credential Guard blocks NTLM fallback.
- On the remote host, enable:
Computer Configuration → Administrative Templates → System → Credentials Delegation → Remote host allows delegation of nonexportable credentials. - Confirm the user belongs to Remote Desktop Users or otherwise has RDP access.^1^
These checks are unnecessary for the target that already succeeds through mstsc /remoteGuard.
Requesting the RDCMan behavior
This should be submitted as an RDCMan product issue or feature request because only RDCMan can change how an empty credential configuration is handled before the RDP connection begins. No dedicated public RDCMan issue tracker or product-feedback URL is identified in the published RDCMan documentation. Use either:
- A Microsoft Learn Q&A question tagged Sysinternals—the current report can serve this purpose.
- A Microsoft Support case if an organization needs the behavior classified formally as a regression or limitation and routed to the product team.
Include:
- RDCMan version
3.23and Windows build - Entra join and WHfB cloud Kerberos trust state
- Exact RDCMan setting: Security Settings → Remote Credential Guard
- Confirmation that username/password are empty and not inherited from a parent or credential profile
- Target type and FQDN
- Whether RD Gateway or Connection Broker is involved
- Successful comparison command:
mstsc.exe /v:<same-target-fqdn> /remoteGuard
- The exact prompt text and confirmation that it appears before any network connection attempt
The requested behavior is consistent with Remote Credential Guard’s documented SSO model, but RDCMan’s current public documentation does not confirm that RDCMan 3.23 implements that no-credential path.^1^
References