Security warnings when opening Remote Desktop (RDP) files

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

Security warnings when opening Remote Desktop (RDP) files

L3 Networker

Hello All,

While connecting to the servers via CyberArk we are receiving the Security warning (due to the April 2026 Security update from MS). Is there any way to whitelist this warning without making any changes to the registry key as updated by MS in below article.

wanted to check if we can whitelist the "Publisher" which shows as "unknown publisher" while initiating the connection.

 

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/understanding-security-warnings#:~:text=This%20warning%20means%20your%20organization's,Is%20it%20safe

1 accepted solution

Accepted Solutions

L5 Sessionator

Hey @Venkatesh Kulkarni​  We are aware that following the recent Microsoft patch for Remote Desktop Services, some customers are encountering the security warning when launching Remote Desktop connections via RDP files downloaded from the PVWA. This warning occurs because the RDP files generated by the PVWA are unsigned.

 

For Self-Hosted environments the ability to sign the .rdp files using the PVWA server certificate is available from version 14.2 onwards. You can read more about this feature and the underlying issue be accessing the articles below:

 

https://docs.cyberark.com/pam-self-hosted/14.2/en/content/pasimp/sign-rdp-file.htm

https://community.cyberark.com/s/article/PSM-The-publisher-of-this-remote-connection-can-t-be-identified

 

The alternate workaround from Microsoft, is to revert this new security dialog directly at the registry level as mentioned in Microsoft's official documentation:

 

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/understanding-security-warnings#im-an-it-administrator-how-do-i-temporarily-revert-the-new-security-dialog

 

 

View solution in original post

7 REPLIES 7

L7 Applicator

Have a look at this thread from yesterday .

https://community.cyberark.com/s/question/0D7Vy00000JlfETKAZ

L4 Transporter

@Venkatesh Kulkarni​ I resolved this issue by:

 

Applied the following gpo to workstations:

 

User Configuration

└─ Administrative Templates

  └─ Windows Components

   └─ Remote Desktop Services

     └─ Remote Desktop Connection Client

      └─ Specify SHA1/SHA256 thumbprints of certificate used to sign the rdp file (from pvwa).

L5 Sessionator

Hey @Venkatesh Kulkarni​  We are aware that following the recent Microsoft patch for Remote Desktop Services, some customers are encountering the security warning when launching Remote Desktop connections via RDP files downloaded from the PVWA. This warning occurs because the RDP files generated by the PVWA are unsigned.

 

For Self-Hosted environments the ability to sign the .rdp files using the PVWA server certificate is available from version 14.2 onwards. You can read more about this feature and the underlying issue be accessing the articles below:

 

https://docs.cyberark.com/pam-self-hosted/14.2/en/content/pasimp/sign-rdp-file.htm

https://community.cyberark.com/s/article/PSM-The-publisher-of-this-remote-connection-can-t-be-identified

 

The alternate workaround from Microsoft, is to revert this new security dialog directly at the registry level as mentioned in Microsoft's official documentation:

 

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/understanding-security-warnings#im-an-it-administrator-how-do-i-temporarily-revert-the-new-security-dialog

 

 

To clarify, Users will still receive the warning even if the RDP files are signed and the publisher is trusted. Microsoft explains this Understanding security warnings when opening Remote Desktop (RDP) files | Microsoft Learn.

The warning can safely be eliminated by applying the GPO mentioned on the previous comment.

L3 Networker

Hello @Fatjon Nushi​ , @Malcolm Murray​ , @Patrick Booth​ ,

 

thank you for the update.

Could you please let me know if the parameters "CLipboard" "Drives" and "Printer" are checked by default once configured the certificate on the PVWA machine to sign the PSM RDP files. Currently it is not the case, users need to check these parameters to be able to enable the copy paste option.

 

Those will no longer be visible as the warning will disappear. User will be able to map the local drives (if allowed on the platform level) just like they use to do before the KB was applied so no changes are needed there.

L0 Member

Hi All, even after following

https://docs.cyberark.com/pam-self-hosted/14.2/en/content/pasimp/sign-rdp-file.htm

 

and updating GPO value for SHA1/SHA256 thumbprints of certificate used to sign the rdp file (from pvwa).

 

Our issue did not got solved. Is there any other alternative present?

  • 1 accepted solution
  • 270 Views
  • 7 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!