RD 2016 Session Host Server

[Badaz52]

Hi all,

 

We have recently upgraded our entire network to Windows 10 and as a result thought we would change the RDS to Server 2016 so that it all matches functionally and visually.

 

As it is for staff access we just want a remote session directly to the session host server the trouble is that externally we are only advertising the servers alias and not its fqdn. This means that when users click on the staff access collection rdp from rdweb it tells them they are going to be connecting to the internal fqdn and this is incorrect. On Server 2008 R2 I could just go into remoteapp manager>remote app deployment settings and change the server name that clients will use when connecting to the rd session host server.

 

Does anyone know how I can change this on Server 2016? Microsoft have made some pretty big changes since 2008 R2 and I have no idea where to look.

 

Many thanks,

[cpjitservices]

Will this help ?

 

Change published FQDN for Server 2012 R2 RDS Deployment - Name Mismatch - MSV Consultancy Blog

[Badaz52]

Will this help ?

 

Change published FQDN for Server 2012 R2 RDS Deployment - Name Mismatch - MSV Consultancy Blog

 

That worked and fixed the first part so thank you, it now pops up and says would you like to connect to the alias but on the next screen it asks to reauthenticate to the local fqdn. On server 2008 R2 I had a pass through authentication on this part but again I have no idea how to accomplish this on RDS 2016.

[cpjitservices]

That worked and fixed the first part so thank you, it now pops up and says would you like to connect to the alias but on the next screen it asks to reauthenticate to the local fqdn. On server 2008 R2 I had a pass through authentication on this part but again I have no idea how to accomplish this on RDS 2016.

 

I'm not entirely sure how you would go about the next part - it'll be in powershell no doubt.

[Badaz52]

Im struggling to find anything, its really frustrating to me its like Microsoft have just ruined RDS. On 2008 R2 this would have been working with about half a days work. Now it has taken me 2 days and I'm still no closer to getting it polished.

 

The prompt asking you to connect is set to the alias which is good, I click connect and I get another box asking me to authenticate for the RDS session only its connecting to the fqdn not the alias and I don't even want it to come up I want it to pass the session credentials that were used to login to RDWeb through to the remote desktop session. In 2008 R2 you could just configure the rdp file with custom lines.

[cpjitservices]

Can you rebuild the whole thing and start again ?

[gshaw]

Im struggling to find anything, its really frustrating to me its like Microsoft have just ruined RDS. On 2008 R2 this would have been working with about half a days work. Now it has taken me 2 days and I'm still no closer to getting it polished.

 

The prompt asking you to connect is set to the alias which is good, I click connect and I get another box asking me to authenticate for the RDS session only its connecting to the fqdn not the alias and I don't even want it to come up I want it to pass the session credentials that were used to login to RDWeb through to the remote desktop session. In 2008 R2 you could just configure the rdp file with custom lines.

 

You can make changes to the RDP files via Powershell on 2016 The Microsoft Platform: Adding custom RDP properties in Windows Server 2012 RDS/VDI environments

 

What are the certificate name FQDNs set to in Server Manager?

 

I much prefer the 2016 setup to any previous RDS deployment, have been rather impressed by it after finding the older versions clunky.

[Badaz52]

You can make changes to the RDP files via Powershell on 2016 The Microsoft Platform: Adding custom RDP properties in Windows Server 2012 RDS/VDI environments

 

What are the certificate name FQDNs set to in Server Manager?

 

I much prefer the 2016 setup to any previous RDS deployment, have been rather impressed by it after finding the older versions clunky.

 

Yes, maybe I'm being a little harsh. Fortunately I had two RDS servers to configure. I have just configured the second one and it worked perfectly so I was thinking maybe when I edited the js files so that it wouldn't need a domain entering on the RDWeb login I messed something up. Turns out I did but it was weird it would allow logins on Windows 10 clients but on Windows 7 it needed the domain putting in, not sure how I managed that! anyway I have copied the js files from the new server that I didn't make a mistake on and have copied them to the first one and now everything is working perfectly!