I deleted this but was still getting the error. So I opened up mmc.exe added the Certificates snap-in, browsed the computer certificate store and under personal I could see an EXPIRED certificate. Now I had imported a proper certificate (that hadn’t expired) but still found this issue. After having a talk with someone in the office I had found out the Session Host server was hosting some demo web apps that ran using HTTPS. My next issue was when my demo client when to connect it errored out with 0圆07 – An authentication error has occurred.
This should now allow clients to see a connecting to a proper server FQDN instead of something like. Simply go to the directory you have the script in with a PowerShell admin prompt and enter the following Set-RDPublishedName "" A script from the TechNet Gallery called Change published FQDN for Server 2012 or 2012 R2 RDS Deployment works a treat for Server 20 R2. For web access it is simply a matter of having a public DNS record and pointing to your web server but getting it working for the RD Gateway requires some PowerShell. For example we’ll use adatum.internal and. The first thing was getting the FQDN of the RD Gateway / Web Access server set to our external domain (since it is different). The process to setup Remote Desktop Services is much easier in Server 2012 / 2012 R2 thanks to the Add Remove Features Wizard, but there are still some gotcha’s that I encountered and will cover in this blog post. Our goal was to have Remote Web Access and then publish RemoteApps through that so we could give live demos. So I was recently setting up a demo environment in Azure with two servers.
0 kommentar(er)
