Not even sure how to properly frame the question in the title bar. Lol
Trying to decipher the Server 2019 RDS info from the web is confusing me. What I am finding seems to be discussing setting up Virtual Desktops as a Terminal Server replacement. And I can not find a helpful Step by Step either. I believe it is no longer a Web Page, but a RDP file I configure and give to each user?
Currently I have 5 users that use the RWW feature of SBS 2011 to connect to their office computers and work from home. Do you have a guide on setting this up in Server 2019?
Thanks.
D.
In Windows Server 2019 there is no longer an Essentials Experience role and that means we will no longer have RWW as in SBS 2011 or Access Anywhere in Windows Server 2012/2016 Essentials.
We can setup RDS but that requires extra licenses and costs. Many of my customers choose a VPN solution. Once that VPN connection is established you can RDP to any workstation inside your Lan assuming it has been set up to allow such connections. You can setup VPN over SSL on the Windows Server 2019 (there is not yet a guide) or you can use a third party device for this.
I did consider a VPN, but I am not sure I want a user's home computer, that is out of my control, directly on the office network. As I understand it, an RDP session adds a layer of security. I did get the 5 pack of Server 2019 RDS User Cals with the new server.
I'm looking to do something similar after I complete the migration from sbs 2011 to 2019. What did you eventually do?
Dom
Susan Bradley pointed me to:
https://ryanmangansitblog.com/2013/03/27/deploying-remote-desktop-gateway-rds-2012/ Look for rdgateway info.
and Richard Kokoski published a white paper:
https://www.dropbox.com/s/1l6v2bv4sljik4c/HowToSetUp_RDSServer2016_19.pdf?dl=0
One gotcha I ran into was trying to install it on the same server with Exchange. I figured they both use IIS so why not, right? Wrong. They both use port 443, and can not co-exist. Or at least I could not get it to. So I had to fire up a separate Server 2019, put a second router on the network with it's own live IP, and install it there, get a second Cert for Remote.domain.local, and put the server's gateway to the second router. It worked.
Thanks for the info! I did a test-run based upon the info you provided, and it seemed to work out OK.
Enjoy the day,
Your browser doesn't have Flash, Silverlight or HTML5 support.