Microsoft Rds 2019

Posted on |



Installing the Remote Desktop Gateway Role (RDGW) on Windows Server 2019 to force RDP over HTTPS (port 443) instead of port 3389.

Installing Remote Desktop Gateway (RDGW) Role on Windows Server 2019

In this example, we had already installed the RD Session Host (RDSH) and RD License Server roles previously on the server. This server is in workgroup mode and not joined to a domain. Steps below are used to install the RDGW role on a single server (installing RDGW also installs IIS) so all three roles (RDSH, RDlic, RDGW) are installed on the same server. If you are already licensing RDS with RDS user licenses, there is no additional cost to installing the RD Gateway Role (other than if you purchase a trusted SSL certificate).

Microsoft Rds Licensing 2019

Microsoft Rds 2019
  1. Go to Server manager, add roles & features, role-based or feature-based installation, select existing server, in Server roles expand Remote Desktop Services and select Remote Desktop Gateway, click through everything else as defaults. It will take about 5 minutes to install. Although it won’t force a reboot, it is typically a good idea to reboot the server after this step.

2. Next go to Server Manager, Remote Desktop Services, Servers, click on server name and right click into properties and to “RD Gateway Manager”. (note: in RDS, Overview, you will see a message about needing to be logged in as domain user to manage servers and collections – to have this functionality you need to be connected to a domain instead of in workgroup mode, we are proceeding with workgroup mode only below).

3. In RD Gateway Manager, expand tree and go to policies. Create a “Connection Authorization Policy” (CAP) for which users can login to the gateway and a “Resource Authorization Policy” (RAP) for what resources can be accessed. For example, we created policies called CAP1 and RAP1 and used defaults for most everything. For CAP1, you probably want to add Remote Desktop Users and Administrators to “user group membership”. For RAP1, under Network Resource, you should change selection to “allow users to connect to any resource” since this is a single server setup. You can modify these policies later to be more specific and restrictive.

Windows Server 2019 RDS Per User CAL Report. On Jan 5, 2021 at 09:23 UTC. Needs Answer Windows Server. Next: Disable File Explorer search bars. Mar 03, 2020 With Server 2008 EOL we've upgraded from three terminal servers in a farm to one terminal server running Windows Server 2019. We have 40 remote desktop users spread across North America We've fed the server more resources to account for the larger user load, there is plenty of cpu and memory to spare, but we still have some users in scattered. Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016. Each user and device that connects to a Remote Desktop Session host needs a client access license (CAL). You use RD Licensing to install, issue, and track RDS CALs. When a user or a device connects to an RD Session Host server, the RD Session Host server. Plan and design your Remote Desktop Services environment.; 2 minutes to read; s; e; H; r; l; In this article. A highly scalable Remote Desktop deployment requires the use of specific patterns and practices. Designing for optimal performance and scale-out is key. Use the scenarios below to help you envision, architect, and continually refine your deployment.

Microsoft offers a wizard to configure the Remote Desktop licensing server role within Windows Server 2019. End-user experience. Microsoft also overhauled the end-user experience in Windows Server 2019 RDS. The Remote Desktop web client utilizes SSO from the browser. RDS 2019 also features GPU virtualization to improve graphics acceleration.

4. For SSL cert (go back to RD Gateway Manager, Properties), create a self-signed cert by going to properties, SSL tab, create self-signed cert, click on “create and import certificate”, change certificate name to the IP address “xxx.xx.xxx.xx” of the server in the certificate name field. Copy the self-signed cert to your local PC because you will need it in order to login through the gateway (all users will need it). If you use a trusted SSL cert from CA then you won’t need to install self-signed cert on each local PC/client like you will with a self signed certificate. Take note of the self-signed certificate expiration date which should be in 6 months – if you decide to continue to use a self-signed certificate, you will need to generate a new cert before the expiration date.

Note: using a self-signed certificate will require you to install the certificate on each client device. It is recommended to use a trusted cert (instead of self-signed cert) where you would need to purchase the SSL cert from a company like GoDaddy and it will be in the name of a URL/domain instead of IP address.

5. At this point, all items in RD Gateway Manager status should be showing as green / green check marks.

6. Go to Services and change the Remote Desktop Gateway Service (service name is TSGateway) to be startup type “automatic” instead of “automatic (delayed)” and make sure it is started/running. This will allow gateway service to start quicker upon a server reboot otherwise you may get a message that the gateway service is unavailable when trying to log in until you wait several minutes for the service to start.

Connecting to RDGW from your local PC

  1. 7Open the Remote Desktop Connection client on your local PC and expand all field by clicking show options.
  2. On the general tab, make sure computer name field is the IP address of the server. You will be entering the IP address on both the General tab and the Advanced tab using the same IP address since the RDSH server and the RDGW server are the same server in this example.
  3. Before connecting, going to the Advanced tab
  4. Click on Settings box under Connect from Anywhere
  5. Select “use these gateway settings”
  6. Enter IP address of the server for Server Name
  7. Uncheck the box to “Bypass RD gateway server for local addresses”
  8. Check the box to use same credentials for RD gateway server and remote computer since same server in this example
  9. Press OK, go back to local resources tab and select what local devices should be redirected (typically printers and clipboard should be redirected, but not local drives under the more button – redirecting local drives uses bandwidth/resources so only do it when needed)
  10. Go to general tab, decide if you want credentials to be allowed to be saved, and save the customized rdp file as a shortcut on your desktop by clicking “save as” and give it a useful name.
  11. When you connect, you may first get a warning message that says “The publisher of this remote connection can’t be identified. Do you want to connect anyway? OR “the identity of the remote computer cannot be verified. Do you want to connect anyway?” You can click the box to “don’t ask me again for connections to this computer” if you don’t want to see this message every time, and continue. This message typically happens because you are using a rdp shortcut on your local desktop that you customized or because you are using a self-signed certificate.
  12. Connect and you will get a message to enter your credentials which will be used for both RDSH and RDGW, select whether to remember credentials or not.
  13. If you try to connect and you get a message “This computer can’t verify the identity of the RD Gateway XXXXX….” and it won’t connect, it is because you are using a self-signed certificate and haven’t put a copy of the certificate in your trusted root certificate authorities on your local PC. So go back on the server and copy the cert from the usersusernamedocumentscertname.cer folder of server to you local PC/desktop, then double click it on your local PC, select “install certificate” and select “Local Machine” store location and select this specific location “Trusted Root Certificate Authorities” (don’t do automatic location). THIS WILL HAVE TO BE DONE ON ALL LOCAL PCs TO CONNECT WHEN USING SELF-SIGNED CERTS.
  14. If you are have trouble logging in, try typing username as servernameusername so WIN-XXXXXXAdministrator or ServerXDan etc.

Turn off port 3389 to internet to force traffic to use port 443/RDGW

  1. Next, turn off the four inbound Windows firewall rules for Remote Desktop for port 3389 FOR PUBLIC PROFILE (Remote Desktop – User Mode (TCP-In) and (UDP-In) and Remote Desktop Services – User Mode (TCP-In) and (UDP-In). Click into the firewall rule, go to the advanced tab, and uncheck the “Public” box so the rule doesn’t apply to the public profile.
  2. RDP Traffic then should go over port 443 from the outside to the server and then 3389 internal to the server. You can test this by trying to login via RDP without Gateway settings.
  3. You can modify/disable other Remote Desktop inbound firewall rules if needed too.

Additional Notes:

See different post on how to purchase and install a SSL certificate from a trusted CA. http://www.riptidehosting.com/blog/purchasing-and-installing-a-trusted-ssl-certificate-to-use-for-rdgw-rdsh/

Remote

Windows Server Remote Desktop Services CAL - Microsoft.com

40 users isn't much, but RDS issues rarely have anything to do with user count. It's about what the users are doing, the apps they run, etc. You can slow down an RDS server with 5 users if they do crazy stuff on there. Or you can run it fine with over 100, if they aren't doing much.
You said only a few are having issues, though? If it's just them... are they in the same location? Seems more likely to be Internet related, if they are at a remote site.
What's slow about it? Is it that moving around and clicking is bad or are the apps running slowly? One is about the RDS server, the other about the connection to it.