whats needed to set up remote desktop connection on windows server 2012 r2
Microsoft Remote Desktop Services [RDS] allows users to access centralized applications and workstations in the data eye remotely. Microsoft RDS is the new expanded and renamed Microsoft Concluding Services. In this mail I volition document the implementation of RDS in my dwelling lab using an 'all-in-1' configuration.
vBoring Blog Serial:
- Setup Remote Desktop Services in Windows Server 2012 R2
- Setup RD Licensing Office on Windows Server 2012 R2
- Setup RD Gateway Role on Windows Server 2012 R2
Server Roles in RDS:
There are three core roles to setup a RDS environment and are as follows:
- Remote Desktop Session Host [RDSH]: Applications are installed and published from the Session Host servers.
- Remote Desktop Connection Broker [RDCB]: This role handles user sessions by load balancing among the RD Session Host servers. Also allows disconnected users to reconnect to their existing sessions without starting a new one.
- Remote Desktop Spider web Access [RDWA]: This role provides a spider web portal to access the RDS environment. Besides allows Windows seven & 8 desktops to connect using the RemoteApp and Desktop Connexion.
The follows roles are non required only add together boosted abilities to RDS:
- Remote Desktop Gateway [RDG]: This role enables remote users to utilise the Remote Desktop Protocol (RDP) over HTTPS. It is placed on the border of your network and acts as the entry point to your RDS environment externally.
- Remote Desktop Virtualization Host [RDVH]: This allows RDS integration with a Hyper-V hypervisor to manage virtual desktops
- Licensing: RDS comes with a 120 solar day trial catamenia. When the trial period ends RDS will no longer accept connections. The RDS License role handles the licensing for RDS.
For additional reading about the roles for RDS bank check out the Microsoft RDS Overview
Installing RDS Roles:
When setting up RDS you have the option of running the three core roles run on a single server or split each part onto its own server. If you are setting RDS up for a lab or a small surroundings then a all-in-one setup would relieve y'all hardware resource. If your environment is large you will want to separate these roles to spread the resources beyond multiple servers. No matter which setup yous selection they both can scale outward depending on user growth.
For my documentation I went with a single server called a Quick Start setup. To start open Server Director then click Manager -> Add together Roles and Features
Click Next
Alter the selection to Remote Desktop Services Installation then click Next
In my environment I will have the 3 core RDS roles running on a single VM (all-in-1 con. If you have a large number of users you will run through the Standard deployment where the three core services run on split up servers.
If you lot choice a Quick Start setup you can add boosted servers to each role to allow expansion. Either pick will let you lot to grow with your environment!
We are setting up application publishing. Change selection to Session-based desktop deployment and click Next
Since we did the Quick Start choice the Connexion Banker, Web Access and Session Host roles will be installed on the unmarried server. Click Next
Check the box labeled Restart the destination server automatically if required then click Deploy
Here is what the progress window looks similar. In my install it rebooted after the Remote Desktop Services role just did non for Session Collection and RemoteApp.
In one case finished click Close. Remote Desktop Servicesis now installed!
Publishing Applications:-
A drove is a logical grouping of RDSH servers that application tin can be published from. Note: Each RDSH server can only participate in a single collection
If you went through the Quick Setup of RDS it will create a drove called "QuickCollection" that contains the applications Wordpad, MS Pigment, and Computer.
To add applications to the drove, click Tasks -> Publish RemoteApp Programs
Information technology volition scan your RDSH for installed applications and display them in a list. I accept the vSphere Customer installed, select your application then click Next
Confirm your awarding selection(south) and click Publish
Click Close to complete the publish process
RemoteApp Global Permissions:
By default the QuickSessionCollection gives all Domain Users access to Remote App programs. To change this click Tasks -> Edit Properties
Click User Groups. If yous wanted to add or remove users ClickAddand search.
If you want to remove Domain Users you must first add a user or grouping kickoff earlier you can remove it.(There has to exist at to the lowest degree ane in User Groups)
Once you accept a second user or group you lot can at present remove Domain Users.
Think this is at the Collections level. Past default all RemoteApp programs inherit these permissions.
RemoteApp Program Permissions:
If you lot want to change the inherent permissions of a RemoteApp, select the application -> right click and click Edit Properties
Click User Assignment -> then change the option to Only specified users and groups. You lot tin at present Add and Remove the permissions inherit from the collection. In my instance I wanted simply my VMware Admins AD grouping to take permission to the vSphere Client. Click Apply and Ok to save you lot changes.
Accessing RemoteApp Programs via the Spider web Access:
To access your newly deployed RDS environment enter the following address of your RDWeb Access into your browser. Allow the add-on to run if prompted.
https://FQDN-or-IP-Address-of-RDWA-server/RDweb
In one case logged in you will see applications that you take admission to. If you went through the Quick Setup of RDS it volition accept created a "Collection" that contains Estimator, MS Paint and Wordpad. Click on a application to launch it. If you get a certificate error click Continue.
The application should launch! If you go to Assist -> Well-nigh you volition come across Server 2012 instead of the local OS. The application is being ran on the RDSH server and are simply viewing it via RDS.
Continue reading – Role two: Setup RD Licensing Part on Windows Server 2012 R2
Source: https://www.virtuallyboring.com/setup-remote-desktop-services-in-windows-server-2012-r2/
0 Response to "whats needed to set up remote desktop connection on windows server 2012 r2"
Postar um comentário