Bypass Windows RDP Warning Prompt (RedirectionWarningDialogVersion) for downloaded CyberArk 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

Bypass Windows RDP Warning Prompt (RedirectionWarningDialogVersion) for downloaded CyberArk RDP files

L0 Member

Hello CyberArk Support Team,

 

We are running into an issue regarding the new Windows security behavior that prompts users with a "Caution: Unknown remote connection" ("Vorsicht: Unbekannte Remoteverbindung") dialog box every time they launch a downloaded .rdp file from the CyberArk PVWA.

 

Problem Details:

- Users are forced to manually check checkboxes (like Clipboard, Printers, WebAuthn) and click "Connect" every single time they launch a connection.

 

 

Request / Goal:

We would like guidance or official documentation on implementing a sustainable solution for our environment. Specifically:

1. What is the recommended way to configure automatic RDP file signing (SignRDP) within our CyberArk deployment so Windows recognizes it as a trusted publisher?

2. Are there any known native CyberArk workarounds or recommended Group Policy (GPO) parameters to suppress this specific multi-checkbox redirection dialog for enterprise users without compromising overall endpoint security?

 

Field_Content_versions_oct20__068Vy00001obj93IAA.png

2 REPLIES 2

L7 Applicator

To revert behaviour see

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/understanding-security-warnings#frequently-asked-questions

 

There are registry changes and group policy. Ms doesn't talk about the gpo change there , but I've seen it on

 

https://illinitechs.com/2026/04/24/windows-rdp-warning-after-april-update/

 

 

Pvwa can sign rdp files.

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

 

You may need to add the signer to the trusted roots on desktops via group policy to trust the certificate fully.

 

 

L3 Networker

Sign files with a Server Authentication Certificate from your trusted PKI/Private CA on all of your PVWA's (at least on PAM self-hosted)

Then add the SHA1 Hash/Thumbprint of that signing certificate to your clients as trusted for RDP publishers:

 

GPO ->

  • Path: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client
  • Setting: Specify SHA1 thumbprints of certificates that represent trusted .rdp publishers

 

 

PS: this is a open community where you ask your questions, you better not put in screenshots with customer names/domains if that might be undesirable

 

  • 82 Views
  • 2 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!