- Windows Remote Desktop Server Setup
- Unlimited Remote Desktop Connections Windows Server 2019 Free
- Remote Desktop Connection Windows Download
Use Windows Server 2019 for your Remote Desktop infrastructure (the Web Access, Gateway, Connection Broker, and license server). Windows Server 2019 is backward-compatible with these components, which means a Windows Server 2016 or Windows Server 2012 R2 RD Session Host can connect to a 2019 RD Connection Broker, but not the other way around. Installing Remote Desktop Services (RDS) on Windows Server 2019 appears to take many steps, but in reality is quite easy. In this article, we dive into how to install these services in a domain environment that requires two servers. For VMs created using the Classic deployment model, verify that another Azure VM that is in the same cloud service or virtual network can make Remote Desktop connections to your Azure VM. Read more detailed RDP troubleshooting concepts and steps.
-->Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016
Use the following steps to create the virtual machines in the tenant's environment that will be used to run the Windows Server 2016 roles, services, and features required for a desktop hosting deployment.
For this example of a basic deployment, the minimum of 3 virtual machines will be created. One virtual machine will host the Remote Desktop (RD) Connection Broker and License Server role services and a file share for the deployment. A second virtual machine will host the RD Gateway and Web Access role services. A third virtual machine host the RD Session Host role service. For very small deployments, you can reduce VM costs by using AAD App Proxy to eliminate all public endpoints from the deployment and combining all the role services onto a single VM. For larger deployments, you can install the various role services on individual virtual machines to allow better scaling.
This section outlines the steps necessary to deploy virtual machines for each role based on Windows Server images in the Microsoft Azure Marketplace. If you need to create virtual machines from a custom image, which requires PowerShell, check out Create a Windows VM with Resource Manager and PowerShell. Then return here to attach Azure data disks for the file share and enter an external URL for your deployment.
- Create Windows virtual machines to host the RD Connection Broker, RD License Server, and File server.For our purpose, we used the following naming conventions:
- RD Connection Broker, License Server, and File Server:
- VM: Contoso-Cb1
- Availability set: CbAvSet
- RD Web Access and RD Gateway Server:
- VM: Contoso-WebGw1
- Availability set: WebGwAvSet
- RD Session Host:
- VM: Contoso-Sh1
- Availability set: ShAvSet
Each VM uses the same resource group. - Create and attach an Azure data disk for the user profile disk (UPD) share:
- In the Azure portal click Browse > Resource groups, click the resource group for the deployment, and then click the VM created for the RD Connection Broker (for example, Contoso-Cb1).
- Click Settings > Disks > Attach new.
- Accept the defaults for name and type.
- Enter a size (in GB) that is large enough to hold network shares for the tenant's environment, including user profile disks and certificates. You can approximate 5 GB per user you plan to have
- Accept the defaults for location and host caching, and then click OK.
- Create an external load balancer to access the deployment externally:
- In the Azure portal click Browse > Load balancers, and then click Add.
- Enter a Name, select Public as the Type of load balancer, and select the appropriate Subscription, Resource Group, and Location.
- Select Choose a public IP address, Create new, enter a name, and select Ok.
- Select Create to create the load balancer.
- Configure the external load balancer for your deployment
- In the Azure portal click Browse > Resource groups, click the resource group for the deployment, and then click the load balancer you created for the deployment.
- Add a backend pool for the load balancer to send traffic to:
- Select Backend pool and Add.
- Enter a Name and select + Add a virtual machine.
- Select Availability set and WebGwAvSet.
- Select Virtual machines, Contoso-WebGw1, Select, OK, and OK.
- Add a probe so the load balancer knows what machines are active:
- Select Probes and Add.
- Enter a Name (like HTTPS), select TCP, enter Port 443, and select OK.
- Enter load balancing rules to balance the incoming traffic:
- Select Load balancing rules and Add
- Enter a Name (like HTTPS), select TCP, and 443 for both the Port and the Backend port.
- For a Windows 10 and Windows Server 2016 Deployment, leave Session persistence as None, otherwise select Client IP.
- Select OK to accept the HTTPS rule.
- Create a new rule by selecting Add.
- Enter a Name (like UDP), select UDP, and 3391 for both the port and the **Backend port.
- For a Windows 10 and Windows Server 2016 deployment, leave Session persistence as None, otherwise select Client IP.
- Select OK to accept the UDP rule.
- Enter an inbound NAT rule to directly connect to Contoso-WebGw1
- Select Inbound NAT rules and Add.
- Enter a Name (like RDP-Contoso-WebGw1), select Customm for the service, TCP for the protocol, and enter 14000 for the Port.
- Select Choose a virtual machine and Contoso-WebGw1.
- Select Custom for the port mapping, enter 3389 for the Target port, and select OK.
- Enter an external URL/DNS name for your deployment to access it externally:
- In the Azure portal, click Browse > Resource groups, click the resource group for the deployment, and then click the public IP address you created for RD Web Access and RD Gateway.
- Click Configuration, enter a DNS name label (like contoso), and then click Save. This DNS name label (contoso.westus.cloudapp.azure.com) is the DNS name that you'll use to connect to your RD Web Access and RD Gateway server.
Usually, RDP server providers give you a single remote desktop connection by default. You won’t have multiple RDP connections, even when you buy admin RDP, which if you log in to the same RDP with a different device, the first session will be lost! But how can we enable multiple concurrent remote desktops? This article will first discover how to activate two RDP sessions and then multiple RDP sessions.
Windows server’s Remote Desktop feature has to be enabled; if it is not and you have not remote access to the server, to do this, use the below link:
Enable Multiple RDP Connections
To have multiple RDP connections, we have to do some configurations. First, we should disable the remote desktop user’s restriction to a single remote user and the second one is to change the limit number of connections.
Windows Remote Desktop Server Setup
Steps To Activate Multiple RDP Connections
- Login to your RDP server.
- Press Windows Logo Key (also known as Windows Key) and R key simultaneously to open the Run page.
- Type gpedit.msc and press OK to open Local Group Policy Editor.
- Go to the following path:
Computer Configuration -> Administrative Templates -> windows Component -> Remote Desktop Services -> remote desktop session host -> connections
- We need to edit two files here, Edit the Restrict Remote Desktop Services users to a single Remote Desktop Services Session, put the status on Disabled, and then press OK.
Also, edit the Limit number of connections and put the status on Enabled, Increase the RD Maximum Connection allowed to 2.
Note: If you set it more than 2, it won’t make any difference because you can make two concurrent sessions in this case! - It’s done; now you should able to have multiple RDP connections at the same time.
Create New Remote Desktop Users
To administrate RDP sessions, it is better to create separate users. However, you can connect multiple times to RDP with a single user at the same time!
Steps To Create Users
- Open the Computer Management. (Type compmgmt.msc in the Run and press Enter)
- Go to
Computer Management(Local) -> Local User and Groups -> Users
, Right-click on Users and select New User…
Note: Also, you should add new users to the Remote Desktop Users Group! - Fill the fields and create as many users as you want(Here you only need 2 users)!
All is set now! try to connect RDP with two different devices and different users.
Let’s take a look at Task Manager to check online users and run on their sessions.
Let’s take a look at Task Manager to check online users and run on their sessions.
Allow More Than 2 Remote Sessions
To allow more remote users on your Windows server, you need to install the RDS(Remote Desktop Services) and purchase a RDS License, but It will give you 120 days free trial for this feature when you install(without license). Here we will install RDS without ADDC (active directory domain controller).
Steps To Install RDS
- Open Server Manager.
- In Dashboard, select Add roles and features.
- Choose Role-based or feature-based installation in the Installation Type step, and click Next.
- Choose to select a server from the server pool in the Server Selection step and go ahead.
- Tick the Remote Desktop Service check-box in the Server Roles step and click Next.
- Go ahead Features step by default options.
- Tick the Remote Desktop Connection Broker and Remote Desktop Session Host check-boxes, and click Next.Note: Maybe it will ask you to install some pre-required role services or features, which you should accept.Note: If you want to use the RDS deployment beyond the 120-day trial period, you’ll need to install the Remote Desktop Licensing role too.
- In the last step, tick the “Restart the destination server automatically if required” and press Install.Note: It will take a while to be installed completely, and the server may need a few reboots.
That’s it; now you should increase the RD Maximum Connection allowed in the Limit number of connections file (For example 99) and set both files status’ which we described how you could do above already. (Step 2-7 in “Enable Multiple RDP Connections” section)
Conclusion
To have multiple RDP connections, we should disable the single-user remote desktop mode and change the remote connection limit. In this situation, you can have 2 RDP sessions simultaneously for free, but if you wish to have more, you should install the RDS role through the server. This tool is open just for 120 days, and after this period, you will have to buy an RDS license to be able to use it.
Unlimited Remote Desktop Connections Windows Server 2019 Free
I wish you’ve enjoyed this post and found it useful, Feel free to leave a comment.
Remote Desktop Connection Windows Download
Let us know if you liked the post. That’s the only way we can improve