Thursday, November 29, 2012 7:22 PM
I'm currently deploying RDS services in a testlab.
It's running on Windows 2008 R2 SP1.
I've 1 DC which is also Web Acces, connection broker and license server.
Next to that I also have 2 Remote Desktop Session Hosts.
I've used a self signed certificate which I've generated on the IIS of the DC.
This Certificate has been used to sign the published apps.
The certificate has been added to the user's trusted publisher certificate store as well as to the computers trusted publishers store.
Still I get the following message when launching an application:
Can anyone tell me how to get rid of this popup / warning?
Where should I add the certificate?
Next to that I've also published an RDP file to each of my RD SH servers.
When I launch the RDP connection, I get an authentication request:
How should I get this to single sign on?
Any help is greatly appreciated!
- Edited by Filip Theyssens Thursday, November 29, 2012 7:23 PM
Thursday, November 29, 2012 8:10 PM
To question 1 I think you need to select an SSL Certificate for https of the Default Web Site.
Friday, November 30, 2012 6:38 AM
Thanks for your reply!
I created a selfsigned SSL certificate on the IIS which I've added to the default webite, so your suggestion is already in place :-)
Wednesday, December 05, 2012 2:02 AMModerator
In Windows 2008 R2, with correct certificates issued, you can make the warning not showing up again.
For more detailed information, please refer to the following blog. Hope it helps.
“Unknown Publisher”? Where did this dialog box come from?
Introducing Web Single Sign-On for RemoteApp and Desktop Connections
TechNet Community Support
- Marked As Answer by Aiden_CaoMicrosoft Contingent Staff, Moderator Friday, December 07, 2012 4:12 AM
Friday, December 07, 2012 12:52 PM
I will give this a try and update this topic!
Friday, December 07, 2012 1:13 PM
That blog post looks familiar!
The first dialog is going to come up regardless of the certificate you use. The only way to hide it is to check the box that says "Don't ask me again...." or deploy policies using the SHA1 thumbprint of the certificate (the blog talks about that policy).
The second dialog is obviously a credentials dialog, which you must implement either single sign on using credentials delegation or web single sign on. Web SSO works if your clients are at least RDC 7.
Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging