- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
PCloud + PSM + RDP Proxy + Windows 11 22H2 and newer Workstations
PCloud Component Versions 14.6 and 14.7
Known Issue: https://community.cyberark.com/s/article/KI00019661
Related Error: https://community.cyberark.com/s/article/Error-The-remote-session-was-disconnected-because-license-s...
PSM RDP connections fail with the following error:
This issue occurs because the Remote Desktop Connection client (mstsc.exe) on Windows 11 22H2 and newer requires elevated privileges to create the necessary license store in the registry (specifically under HKEY_CURRENT_USER\Software\Microsoft\MSLicensing) when it's not already present. This store is a local repository used to manage Client Access Licenses (CALs) for RDP sessions. If the license store hasn't been created when the PSM-RDP connection is launched from the PVWA, the connection attempt fails with the "remote desktop needs to be run with elevated privileges" error (often accompanied by details about license store creation failing due to access denied).
According to https://windowsforum.com/threads/fixing-windows-11-remote-desktop-issues-after-24h2-update.352977/ a group policy change is required.
(Note: Some users have found that simply disabling Continuous Network Detect might suffice. Feel free to experiment with which configuration works best for your environment.)
gpupdate /force
Running mstsc.exe as Administrator once (even to any arbitrary remote host) creates the required registry entries with the necessary permissions. After that, non-elevated launches, like those triggered by PSM-RDP, can successfully access and use the existing store without encountering the error. Thank Microsoft for this added "feature."
Idira recommends the registry permissions be adjusted on HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing. Ensure that the current user, Administrators, and "All Application Packages" have Full Control.
On the DC, create or edit a GPO and ensure the GPO is linked to the OU containing the domain-joined workstations.
MACHINE\Software\Microsoft\MSLicensing
Next, apply the GPO a limited group of computers or a test group for initial rollout.
If that works, then roll out the GPO org wide.
KB5051987 causes Windows 11 RDP Session to get Stuck at Login:
1.3.9 Connect-Time and Continuous Network Characteristics Detection:
1.3.1.1 RDP Connection Sequence
1. Optional Connect-Time Auto-Detection: During the Optional Connect-Time Auto-Detection phase, the goal is to determine characteristics of the network, such as the round-trip latency time and the bandwidth of the link between the server and client. This is accomplished by exchanging a collection of PDUs (specified in section 2.2.14) over a predetermined period of time with enough data to ensure that the results are statistically relevant.
These links and documentation from Microsoft show the workaround setting has to do with RDP connection quality, not security; thus, no vulnerability is created by applying the suggested policies.