|
TERMSERV/SessionHost1.FQDN
TERMSERV/SessionHost2.FQDN
TERMSERV/SessionHost3.FQDN
TERMSERV/SessionHost1
TERMSERV/SessionHost2
TERMSERV/SessionHost3
TERMSERV/Broker-Gateway-Web.FQDN
TERMSERV/ Broker-Gateway-Web
That’s how that needs to be set up.
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.
From: ntsys...@googlegroups.com <ntsys...@googlegroups.com>
On Behalf Of Mike Leone
Sent: Friday, September 12, 2025 09:28
To: NTSysAdmin <ntsys...@googlegroups.com>
Subject: [ntsysadmin] RDS prompting for credential even tho GPO says not to
I am trying to set up SSO for RDS to make the lives of my users a bit easier. I am following this:
For starters, I am still being prompted as to what to do with the .rdp file:
Then getting prompted to keep it:
And then I am prompted for credentials AGAIN:
So I have "Prompt for credentials on the client computer" to DISABLED in Computer Conifg/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Connection Client.
I've done this:
And listed my sites:
Computer Policy - RemoteDesktop Services Configuration
|
And done this:
Next, you need to enable the Logon options policy under User/Computer Configuration -> Administrative Tools -> Windows Components -> Internet Explorer -> Internet Control Panel -> Security -> Trusted Sites Zone. Select ‘Automatic logon with current username and password’ from the dropdown list.
Did that, and added the servers to the zone.
So what then am I missing? The only aspect I've been able to resolve is to trust the .rdp publisher (by specifying the thumbprints of the cert on the RD Web; that part at least worked).
--
Mike. Leone, <mailto:tur...@mike-leone.com>
PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
Photo Gallery: <http://www.flickr.com/photos/mikeleonephotos>
--
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%2Bg3R2bHX%3D-LqAfXFmWweTx1eprszKaYMVu7jy7Bo8iTAw%40mail.gmail.com.
This is going way out of scope. We’ve done a lot of RD Farms and never have we needed to muck about with this.
SSO involves setting up the GPO(s) for allow the credentials to get flung about between user source, broker/gateway/web, and the intended session host via BGW.
The publishing certificate, so the one use for the top two certificates against the Collection, need the SHA thumbprint set in that same Group Policy Object.
https://vcloudnine.de/single-sign-on-sso-with-remoteapps-on-windows-server-2012-r2/
^^^
These are the two reference sites we used back in the day to set up SSO. Nothing has changed other than our using a 5 or 6 year self-issued for SSO/Publishing to get rid of the annual PITA of updating the GPO SHA thumbprint among other things.
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.
From: ntsys...@googlegroups.com <ntsys...@googlegroups.com> On Behalf Of Mike Leone
Sent: Friday, September 12, 2025 10:12
To: NTSysAdmin <ntsys...@googlegroups.com>
Then getting prompted to keep it:
And then I am prompted for credentials AGAIN:
So I have "Prompt for credentials on the client computer" to DISABLED in Computer Conifg/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Connection Client.
I've done this:
- Enable the policy Allow delegation defaults credential under Computer Configuration -> Administrative Templates -> System -> Credential Delegation
And listed my sites:
Computer Policy - RemoteDesktop Services Configuration
TERMSERV/dctrrds004.wrk.ads.pha.phila.gov
TERMSERV/dc1rds010.wrk.ads.pha.phila.gov
And done this:
Next, you need to enable the Logon options policy under User/Computer Configuration -> Administrative Tools -> Windows Components -> Internet Explorer -> Internet Control Panel -> Security -> Trusted Sites Zone. Select ‘Automatic logon with current username and password’ from the dropdown list.
Did that, and added the servers to the zone.
So what then am I missing? The only aspect I've been able to resolve is to trust the .rdp publisher (by specifying the thumbprints of the cert on the RD Web; that part at least worked).
--
Mike. Leone, <mailto:tur...@mike-leone.com>
PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
Photo Gallery: <http://www.flickr.com/photos/mikeleonephotos>
--
Mike. Leone, <mailto:tur...@mike-leone.com>
PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
Photo Gallery: <http://www.flickr.com/photos/mikeleonephotos>
--
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%2Bj0ZHO-t7_-hVDLXsM%3DD8-cb1%3D17ZFUXF_K0T2BjkrbAg%40mail.gmail.com.
TERMSERV/SessionHost1.FQDN
TERMSERV/SessionHost2.FQDN
TERMSERV/SessionHost3.FQDN
TERMSERV/SessionHost1
TERMSERV/SessionHost2
TERMSERV/SessionHost3
TERMSERV/Broker-Gateway-Web.FQDN
TERMSERV/ Broker-Gateway-Web
That’s how that needs to be set up.
This is going way out of scope. We’ve done a lot of RD Farms and never have we needed to muck about with this.
SSO involves setting up the GPO(s) for allow the credentials to get flung about between user source, broker/gateway/web, and the intended session host via BGW.
The publishing certificate, so the one use for the top two certificates against the Collection, need the SHA thumbprint set in that same Group Policy Object.
https://vcloudnine.de/single-sign-on-sso-with-remoteapps-on-windows-server-2012-r2/
^^^
These are the two reference sites we used back in the day to set up SSO. Nothing has changed other than our using a 5 or 6 year self-issued for SSO/Publishing to get rid of the annual PITA of updating the GPO SHA thumbprint among other things.