In RD Gateway Manager, expand tree and go to policies. (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).ģ. Next go to Server Manager, Remote Desktop Services, Servers, click on server name and right click into properties and to “RD Gateway Manager”. Although it won’t force a reboot, it is typically a good idea to reboot the server after this step.Ģ.
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.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). 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. This server is in workgroup mode and not joined to a domain. In this example, we had already installed the RD Session Host (RDSH) and RD License Server roles previously on the server. Installing Remote Desktop Gateway (RDGW) Role on Windows Server 2019 Installing the Remote Desktop Gateway Role (RDGW) on Windows Server 2019 to force RDP over HTTPS (port 443) instead of port 3389.
0 kommentar(er)
