PSM RDP Proxy with Windows 11

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PSM RDP Proxy with Windows 11

L4 Transporter

Hi community,

does someone encountered the issue that the PSM RDP Proxy does not prompt for password if in the RDP file the parameter username:s:userx is defined?

If the username parameter is empty, it works as designed.

 

Interesting though that with username defined, it work on Windows 10, issue is only on Windows 11.

 

Any idea?

5 REPLIES 5

L0 Member

Yes, I have this issue as well. I assume it is a change with the underlying version of RDP. I just leave it undefined on my computer now and in my Autohotkey-based GUI for this, I get the OS version and set or unset this setting based on that.

L0 Member

The root cause is the Windows 11 upgrade from version 21H2 to 22H2. I'm opening a Sev B case with Microsoft. But since CyberArk supports a customized RDP file they need to do some serious research on this.

L1 Bithead

since we upgraded to W11 23h2, this issue is solved on my side.

with W11 22h2, we used mobaxterm rdp session (and test other rdp manager) and it's works too, only the native RDP executable is broken.

Does it still work for you fine?

I have customer that is on W11 23h2 but we get ""Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator Code: 0x907".

 

Tried the CyberArk solution with adding permissions to PSMConnect on the MSLicensing registry but without any change -> https://community.cyberark.com/s/article/Issues-with-Remote-Desktop-on-End-user-Machine-after-Windows11-Update

 

Randomly it fails with above mentioned MS error, but only on the LB VIP address. If we go directly using the specific PSM it works fine.

Can it be related to the signature algorithm? The Root CA is using sha1, the LB cert is on sha256.

Does it still work for you fine?

I have customer that is on W11 23h2 but we get ""Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator Code: 0x907".

 

Tried the CyberArk solution with adding permissions to PSMConnect on the MSLicensing registry but without any change -> https://community.cyberark.com/s/article/Issues-with-Remote-Desktop-on-End-user-Machine-after-Windows11-Update

 

Randomly it fails with above mentioned MS error, but only on the LB VIP address. If we go directly using the specific PSM it works fine.

Can it be related to the signature algorithm? The Root CA is using sha1, the LB cert is on sha256.

  • 1069 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!