- Standard Deployment
- Qucik Start
- Domain Name: ARADMIGRATION.local
- Active Directory / DNS Server: W2k12AD.ARADMIGRATION.local
- IP Address of AD / DNS server: 172.16.50.67/16
- Operating System: Windows Server 2012
- RDS Server: ARW2k12RMTAPP.ARADMIGRATION.local
- IP Address of RDS Server: 172.16.50.69/16
- Operating System: Windows 2012 R2
- To start the RDS installation go to “Manage” on top of the Server Manager and select “Add Roles and Features”
- It will start the “Add Roles and Features” Wizard and Click on “Next” as nothing to do with this step
- Select the “Remote Desktop Services installation” option at the next step and Click on “Next”
Here we are going to deploy RDS using “Quick Start” method as we are going to install all these services in to one server. Select the “Quick Start” and Click Next to continue.
At the next step there are two deployment scenarios that you can use:
- Virtual machine-based Desktop deployment: An individual VM is running with a Desktop OS. There is only one user can login to these VMs at a time.
- Session-Based Desktop deployment: An individual session is running inside a single server, there can be multiple user sessions in a server
- Here we are going to use a server with multiple sessions for these users, so the “Deployment Scenario” should be “Session-Based Desktop deployment” , Select the option and Click “Next” to continue.
- At the next step you need to select the server that you are going to use for this from the server pool. In my case I have only one server. Select the server and Click on the small arrow to add the server. Here this wizard will install “RD Connection Broker” , “RD Web Access” and “RD Session Host” services on the same server.
- RD Connection Broker – This Role service helps to reconnect the existing disconnected user session (due to a network failure or disconnected by users ) back to the same user session when the users are trying to re-connect to the RDS. This RD Connection broker role keeps the track of users sessions details in a load balanced RD server farm such as RD Session host server which these users sessions resides, name of the session, user name of the session, session state, session ID. RD Connection Broker uses these information to re-connect the disconnected sessions.
- RD Session Host (RDSH) – RDSH is the server which host all the windows based applications to run during the user’s remote session.
- RD Web Access – Formally known as the Terminal Server Web access which helps to connect to the RemoteApps and Remote Desktops through the web browser.
- At the Next step You can see the “Confirmation” window and you have to select the “Restart the destination server automatically if required” option to deploy the Services. Once you select the option Click on “Deploy” to continue the installation.
- You can see the progress of the Deployment at the next window and server will reboot after the completion of deployment
- Completion of the Deployment will give you an URL to access the RD Web access console to access the RemoteApps and Remote Desktops . In my case the URL is : https://ARW2K12RMTAPP.ARADMIGRATION.local, click on this to open you a web browser to access the Remote Apps and Desktops.
- You can see a small “warning” appear on the web browser and click on the “Continue to this website (not recommended).” option to continue.
Type the “Administrator” username and password to login to RD Web Access and Click on Sign In to continue
- You can see default published Apps on the next page
Click on the any of the Default App to test the Connectivity, I have click on the Calculator and you can see a window similar to this window, click on “Connect” to continue.
You will see a username password prompt and type “Administrator” Username and password to launch the App.
- Application will load on your screen now
- Now we have successfully deployed the RDS and Remote Apps on the server, also we have tested and verified the accessibility. Now we need to customize the applications and we are going to deploy new set of applications on the server for remote access. Go to your server manager and click on the “Remote Desktop Services” as shown in the below
- Now you can see the overview of the RDS Server environment
Go to collection, right click on the “QuickSessionCollection” and select “Remove Collection” to remove the default Apps Collection.
- Click on “Yes” to confirm the Collection Removal
- Click on the “TASKS” and select “Create Session Collection” to create a new application collection
- This will start the “Create Collection Wizard” and click on “Next” as we don’t have anything to do on the “Before you begin” step
- There is a really cool feature at the next step where you can save all your documents and can work as a roaming profile of the RD Session host for a user. You have to provide a shared location to keep user’s VHD files to map when they are connecting to RD Session Host server, You can specify the Maximum Size of the VHD in this step. But here I”m not going to use this option here and I deselect the option and click on “Next” to continue.
- At the next step you can see the Confirmation and Click on “Create” to create the Collection set.
- Let this wizard to complete the creation and succeed the creation , once it complete the creation close the wizard.
- We have successfully created the Collection and now we are going to publish the RemoteApps on this collection. Go to your Collection and click on “TASKS” and select “Publish RemoteApp Programs” to publish Apps for remote access.
This will start the “Publish RemoteApp Programs” wizard and select the Apps that you need to publish for the Remote Access. Click on “Next” to continue.
- Click on “Publish” on the confirmation step
- Close the Wizard after Completion of the Publishing Apps for the Remote Access.
- Now login to your RD Web Access see whether you can access the Apps.