- Windows Server 2019 Essentials Remote Desktop Cal
- Windows Server 2019 Essentials Remote Desktop Download
- Windows Server 2019 Essentials Remote Desktop Windows 10
- Windows Server 2019 Essentials Remote Desktop Services
Preface:
Remote Desktop Services is a robust role in the windows role group. RDS is used to remote into the central RDS server or any member server or the user’s desktop computer through the RDS server using the Remote Desktop web services either on the internal network or through the internet.
This article discusses the access of the servers and desktops accessed over the internet using RD Gateway using the https port. The Servers and desktops on the on-premises can be accessed without the need RDP port 3389 opened on the firewall. Where the RDP port 3389 is the hacking target for hackers over the internet. As the https port used for the access of remote desktop, the port is usually used for most of the businesses to access the webserver hosted internally.
To install Windows Server Essentials Experience on Windows Server 2019, all that needs to be done is for you to copy its required files and registry entries from Windows Server 2016 over to Windows Server 2019, add its prerequisite server roles and features, create its required services, and then complete its setup process by running the Configure Windows Server Essentials wizard. Download Visual Studio Community, Professional, and Enterprise. Try Visual Studio IDE, Code or Mac for free today.
The Remote Desktop Services will be cost-effective when the number of users or devices accessing applications with an excessive amount of licenses needed. Also, this role is most useful where the client computers installed on the company network or home is not the latest, and the application demands such as hardware or operating systems.
We are going to delve deep into this installation and configuration on an active directory domain network with network policy server (NPS) security. We are using a public CA certificate in this demonstration and hostname assigned on the public DNS.
The following points discussed in this article. Following this article, one can install and configure Remote Desktop Services on a Windows Server 2019 and publish the RDP app to access a server or a desktop as per need on the remote desktop web app portal.
- Add Remote Desktop Services Role
- Add Server to RD Licenses and RD gateway
- Install public CA certificate to each role of RDS
- Configure RD Licenses
- Configure Remote App Collection
- Publish and Configure Remote App
- Access RD Web and Remote App
To begin with, the demonstration, let’s add the Remote desktop Roles group on the server manager and going forward to configure each component.
Add Remote Desktop Services Role
There are two Windows Server 2019 servers used on this demonstration where the first server is installed as a domain controller, and the RDS server has been joined to the domain of the domain controller, which we have added in the first place.
On the planned RDS installation server called remote, we are going to install the RDS role by launching the server manager dashboard and by clicking the “Add roles and features” link.
The instruction of wizard will show up on the screen, and if you don’t want to see this page on adding roles and features anymore, just check the skip this page checkbox and continue by clicking next.
X force for mac download. The RDS Installation can be installed through Role-based or feature-based installation. Still, it requires a lot of effort as there are a number of components to be selected and configured after installation. To make life easier, Microsoft has consolidated all the component installation in one group. That installation method can be used by clicking the Remote Desktop Services installation option at the select installation type.
On the deployment type, select Quick Start so that all components will be installed by itself, and the Quick App Collection will be added to the Remote Desktop Services deployment. Select Quick Start and click Next.
In this article, we are going to look into Session-based desktop deployment, so select session-based desktop deployment and click Next.
On the Server Selection page, select the local server where we have planned for RDS deployment and click next.
On the confirmation page, check the checkbox “Restart the destination server automatically if required” and click deploy to start the RDS deployment.
When the Deploy tab is clicked, the RDS Role installation will start installing roles, and the progress can be monitored on the popup.
The server will be restarted in the middle of the installation. When the server restarted and logged in as the same administrator account, the installation will continue, and the progress will show succeeded on the RDS roles deployment completion.
Once the Remote Desktop Services role has been added, the very next step is to configure it. On the server manager, you would find a Remote Desktop Service deployment setup on the left side navigator. Click on that, and additional configuration of this service will be available.
Add Server to RD Licenses and RD gateway
The icons in green or not configured with a deployment server, here the RD licensing and RD Gateway, are in green, and we are going to configure them in the coming up steps. Click RD Licensing, and the configuration window will show up.
On the RD Licensing deployment windows select the server which in our case the local server and selects the server and click on the arrow next to it to deploy RD Licensing server and click Next.
Once the RD licensing server added, the result indicates succeeded next to the progress bar. Click close to close out the RD License server deployment wizard.
As we have already planned, this RDS server is accessed through the internet also, so our very next move is the deploy RD Gateway. Click the RD Gateway icon on the deployment overview area, which is in green, which means it has not been deployed yet. The RD Gateway deployment wizard will open, and we can deploy it with adding the server.
We are adding the local server as an RD Gateway server to the Remote Desktop Services by clicking the arrow in the middle of the selection, and once the server added, click next to configure SSL certificate name.
In this demonstration, I have already created a hostname under my public domain mrigotechno.club called remote, but you need to give a name that is relevant to your RDS gateway hostname and certificate pertinent to be purchased and installed on the internet information Server (IIS). Once the Certificate Name typed, click Next.
On the confirmation, click add to add RD Gateway server to the deployment. Click Add.
On the Results page, the progress indicator will show succeeded and click Configure Certificate to install the certificate.
Install public CA certificate to each role of RDS
On each role services on the Manage Certificate, we need to configure the certificate, there are four roles, and we need to configure the certificate for them. I have installed the third-party CA certificate on Internet information server and export it as a pfx file format while exporting I have secured the certificate with a password. Please have your third party certificate in pfx format file and the password of the pfx file handy as we are going to apply the certificate from the topmost role and apply one by one till the fourth role.
Select the first role and select an existing certificate to apply the certificate dialogue window.
On the Choose a different Certificate, click browse and select the pfx certificate file and type the password of the certificate and check “Allow the certificate to be added to the trusted root certification authorities certificate store on the destination computer.” Click OK to go back to manage the certificate window.
On the state of the certificate configuration for the role, you would see Ready to Apply on state column, click apply and wait to change for the level to Trusted and status to OK and the state to Success.
Do the same steps to apply the certificate to the next three roles, and you would see the State changes to Success as in the below screen capture. Click OK to complete the certificate Configure.
Configure RD Licenses
The Next step is to Edit Deployment properties, on the deployment overview click tasks, and select edit deployment propertied to start the wizard.
As we have already completed Certificate configuration, we have only edit that we need to do RD Licensing. On the RD Licensing under Configure the deployment, select the RDS Licensing mode as per your requirement in the example. I have chosen Per user, but choose the one which is relevant to your environment and click OK.
Configure Remote App Collection
On the left side navigation on the Remote Desktop Services Setup, you would see Quick Session Collection, where the App publisher available to published App, which we would access through RD Web Access. On the Properties area, click properties and select edit properties.
We are going to edit only one option in these properties that we are going to add the User groups to associate to this collection. I have already created a security group called RDS_Users and added some test users to it. I’m adding that group here to associate with the collection., click OK and back to the main window.
Publish and Configure Remote App
In this demonstration we are going to see how to access a member server or a user desktop from the RD web access from the internet, without opening RDP port 3389, the same steps will apply to add a user’s desktop. But make sure the member server or user desktop is enabled Remote Desktop on the system property of the computer. So I got a server on the network that can be configured to access from RD Web, we are going to configure Remote Desktop App by publishing the RDP app to the Quick Collection Apps.
On the Remote App Programs area, click tasks on the screen below and click “Publish RemoteApp Programs.”
You will be presented with selecting the RemoteApp programs list and choose the App you want to publish. In this case, the Remote Desktop Connection. Select “Remote Desktop connection” and click Next.
On the confirmation page, click publish.
On the completion page, you would see published status message click close to go back to the main window.
On the Remote Desktop Connection RemoteApp that we just published right-click and select edit properties to configure the properties of the App.
On the General page, type a name that is appropriate for the RDP Connection Computer. In this case, it a server called server1, so I type the name server1 on the name box.
The next page is parameters, on the parameters page, click “Always use the following command paraments” radio button and type the IP address of the server or desktop to which the RDP connection to be established. In this case the private IP4 address of server1 is 192.168.24.190. The correct parameter value is /v:192.168.24.190. Replace the IP address with the one of the servers or Desktop IP address on your network.
The next item is User Assignment, add the user account to which users need to find this Remote App program that has to be visible on the RD Web Access login. Click add and choose the relevant user or group.
On the next page, leave the file type association with default setting and click OK.
Access RD Web and Remote App
We have completed all RDS configuration and moving on to the RD Web portal to login to the portal and access the apps assigned to the use. The URL for the RD Web is https://remote.mrigotechno.club/rdweb
Replace the remote.migotechno.club with the one you have configured for your environment.
Type the username and password with the domainuser format and password of the user and click Sign In.
The portal will show the web resources, the Remote desktop connection app that we have configured with the name server1 is available for us to access from the RD Web access login. Click Server1 and follow the login screen.
Click connect on the notification popup.
On the security login dialogue, type the user name and password of the user and click OK.
The RDP connection is remote into the server1 computer, as shown below.
The RDP access is successful to the IP address 192.168.24.190, and this concludes our demonstration.
Conclusion
In this article, we have discussed and gone through the demonstration of deploying Remote Access Services on Windows Server 2019 elaborately. You can follow the same step and deploy Remote Desktop Services on your lab or production environment.
I have demonstrated other roles of Windows Server 2019 in Get An Admin article. You may have some questions or feedback to share with me, please click the comments below and share your thoughts. I am so happy to answer your questions.
Windows Server 2019 Essentials Remote Desktop Cal
There are two primary editions of Windows Server 2019: Standard and Datacenter, based on the size of the organization as well as virtualization and data center requirements (see features comparison). Both editions' licensing models include both Cores + Client Access Licenses (CALs). All physical cores on the server must be licensed, subject to a minimum of 8 core licenses per physical processor and a minimum of 16 core licenses per server. CALs are required for every user or device accessing a server. See the Product Terms for details. Core licenses are sold in packs of two (2Lic Core) and in packs of sixteen (16Lic Core). At the same time, there are legal requirements:
A minimum of 8 core licenses is required for each physical processor (2Lic Core - 4 licenses).
A minimum of 16 core licenses is required for each server. (2Lic Core - 8 licenses or 16Lic Core - 1 license).
If you need to install more than 13 virtual instances of Windows Server on the server, then it is economically feasible to purchase the Datacenter edition. The number of required Datacenter licenses will be the same as for Standard edition with the number of virtual Windows Server = 0.
CALs or CALs + RDS (Remote Desktop Services) CALs are required to access instances of Windows Server. The number of servers used does not matter. The current version of the client access license permits the use of the functionality of servers of previous versions.
The use of previous versions of Standard and Enterprise is allowed. Keys and distributions for current and previous versions are provided on the Microsoft VLSC website. Before purchasing licenses, carefully read the Windows Server 2019 Licensing Datasheet.
Talk to a real human. Get pricing, ask questions, or get advice for your migration.
Calculate the required number of 2-core Windows Server licenses :
| Processors in the server | |
| Cores in each processor | |
| Physical instances of Windows Server on the server | |
| Virtual instances of Windows Server on the server | |
| The required number of 2-core licenses for the server (Cores: 1, Copies: 1) | 8 |
Server licenses
Windows Server 2019 Standard
For proper server licensing, you must purchase the required number of licenses (2-core and / or 16-core).
The required number of Standard licenses provides the right to use 1 physical and 2 virtual instances of Windows Server on the licensed server. For every two additional virtual instances, you must additionally purchase the required number of Standard licenses for the server.
| 2 core licenses (minimum purchase - 8 licenses per server) | |||
| 9EM-00653 | Microsoft Windows Server 2019 Standard - License - 2 cores - Open License - Single Language | N/A | |
| 16 core license (minimum purchase - 1 licenses per server) | |||
| 9EM-00652 | Microsoft Windows Server 2019 Standard - License - 16 cores - Open License - Single Language | N/A | |
Windows Server 2019 Datacenter
For proper server licensing, you must purchase the required number of licenses (2-core and / or 16-core).
The required number of Datacenter licenses grants the right to use 1 physical and any number of virtual instances of Windows Server on the licensed server.
| 2 core license (minimum purchase - 8 licenses per server) | |||
| 9EA-01045 | Microsoft Windows Server 2019 Datacenter - License - 2 cores - Microsoft Qualified - Open License - Single Language | N/A | |
| 16 core license (minimum purchase - 1 licenses per server) | |||
| 9EA-01044 | Microsoft Windows Server 2019 Datacenter - License - 16 cores - Microsoft Qualified - Open License - Single Language | N/A | |
Windows Server 2019 Essentials
Windows Server Essentials offers a flexible, affordable, and easy-to-use server solution for small businesses with up to 25 users and 50 devices. An ideal first server, Windows Server Essentials can also be used as the primary server in a multi-server environment for small businesses.
Windows Server Essentials licensed in PER-SERVER model and doesn't require Client Access Licenses (CALs). You can use 1 physical and 1 virtual instance of Windows Server Essentials on the physical hardware. If Virtual instance is used for production purposes then Physical instance can only be used for virtualization purposes and nothing else.
| License for one server | |||
| G3S-01259 | Microsoft Windows Server 2019 Essentials - License - 1 server - Open License - Single Language | N/A | |
Windows Server 2019 Essentials Remote Desktop Download
Client licenses
Device CAL
Windows Server 2019 Device CAL license grants the right to use the server functionality from one device to any number of users. To calculate the required number of User CALs, you need to calculate the number of users on the network using the server functionality.
| Client access license for one device | |||
| R18-05767 | Microsoft Windows Server 2019 - License - 1 device CAL - Open License - Single Language | N/A | |
User CAL
Windows Server 2019 User CAL license grants the right to use the server functionality to one user using any number of devices. To calculate the required number of User CALs, you need to calculate the number of users on the network using the server functionality.
| Client access license for one user | |||
| R18-05768 | Microsoft Windows Server 2019 - License - 1 user CAL - Open License - Single Language | N/A | |
Device CAL RDS
Windows Server 2019 Device CAL Remote Desktop Services (RDS) is purchased in addition to the Device CAL license to obtain the right to use terminal access to the server from one device to any number of users. To calculate the required number of Device CAL RDS licenses, you need to calculate the number of devices on the network that users use terminal access to the server.
| Remote Desktop Services Client Access License for one device | |||
| 6VC-03747 | Microsoft Windows Remote Desktop Services 2019 - License - 1 device CAL - Open License - Win - Single Language | N/A | |
User CAL RDS
Windows Server 2019 Essentials Remote Desktop Windows 10
Windows Server 2019 User CAL Remote Desktop Services (RDS) license is purchased in addition to the User CAL license to obtain the right to use terminal access to the server to one user using any number of devices. To calculate the required number of User CAL RDS licenses, you need to count the number of users on the network that use terminal access to the server.
| Remote Desktop Services Client Access License for one user | |||
| 6VC-03748 | Microsoft Windows Remote Desktop Services 2019 - License - 1 user CAL - Open License - Win - Single Language | N/A | |
Windows Server 2019 Essentials Remote Desktop Services