My guess is that the original environment was set up with RD Single Sign-On so all of the AD goodness and the person that set it up used a long term self-issued certificate to sign the .RDP apps/files.
Otherwise, users would be prompted for the publishing certificate every 12 months which is a PITA then the SHA would need to be updated in Group Policy.
There are two prompts because there’s a RD Gateway involved?
Philip Elder MCTS
Senior Technical Architect
Microsoft High Availability MVP
MPECS Inc.
E-mail: Phili...@mpecsinc.ca
Phone: +1 (780) 458-2028
Web: www.mpecsinc.com
Blog: blog.mpecsinc.com
Twitter: Twitter.com/MPECSInc
Teams: Phili...@MPECSInc.Cloud
Please note: Although we may sometimes respond to email, text and phone calls instantly at all hours of the day, our regular business hours are 8:00 AM - 5:00 PM, Monday thru Friday.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/ntsysadmin/CAHBr%2B%2BhbzYxOjaYuRq%2BTVprQ6uMsC8hM9FOQjhy9THto2c%3DGPA%40mail.gmail.com.
I would consider checking that all of the certificates have been assigned in the Manage Certificates at from the Connection Broker, specifically for “RD Connection Broker – Publishing”:
Server Manager | Remote Desktop Services | Overview | Tasks | Edit Deployment Properties | Certificates
-Aakash Shah
From: ntsys...@googlegroups.com <ntsys...@googlegroups.com>
On Behalf Of Mike Leone
Sent: Thursday, September 11, 2025 10:13 AM
To: NTSysAdmin <ntsys...@googlegroups.com>
Subject: [ntsysadmin] RDS Published App question
I'm drawing a blank on this. I set up an RDS environment, and am testing it, by trying to run notepad as a published app. I go to the web URL (https://<my-host>/rdweb). I get prompted to log in with Ad cred. I do so. I see my published app. I click on it. ANd I get "cpub-notepad-PHA-TESTIG_Pu-CmsRdsh.rdp could harm your device. Do you want to keep it anyway?".
--
My guess is that the original environment was set up with RD Single Sign-On so all of the AD goodness and the person that set it up used a long term self-issued certificate to sign the .RDP apps/files.
Otherwise, users would be prompted for the publishing certificate every 12 months which is a PITA then the SHA would need to be updated in Group Policy.
There are two prompts because there’s a RD Gateway involved?
I would consider checking that all of the certificates have been assigned in the Manage Certificates at from the Connection Broker, specifically for “RD Connection Broker – Publishing”:
To view this discussion visit https://groups.google.com/d/msgid/ntsysadmin/DM4P221MB1568BD9F0BDC815D4F94D0AAF209A%40DM4P221MB1568.NAMP221.PROD.OUTLOOK.COM.