Editing RDP Web Access (section)

== Configuring the services to talk ==

Firstly I would suggest you ensure all the VMs have been rebooted. When logging in ensure you use a domain admin account for the next steps

Firstly start by clicking manage in the server manager and select Create Server Group

[[File:rdsguide15.PNG|400px]]

Within this window add your RDS boxes and license server

[[File:rdsguide16.PNG|400px]]

Click on your server group and then select Add Roles and Features

[[File:rdsguide17.PNG|400px]]

This time ensure you have selected Remote Desktop Services Installation

[[File:rdsguide18.PNG|400px]]

Select standard deployment

[[File:rdsguide19.PNG|400px]]

On this following screen select Session-Based desktop deployment and select next on the screen after

[[File:rdsguide20.PNG|400px]] [[File:rdsguide21.PNG|400px]]


In the next screen select your session broker. '''If in the 2 VM scenario this should be your gateway server'''


[[File:rdsguide22.PNG|400px]]

In the next step as above if in a two VM scenario select your gateway server. If you didnt do it previously select install RD Web Access Role '''Image is for illustrative purposes'''

[[File:rdsguide23.PNG|400px]]

Finally select the confirmation screen and allow the restarts


[[File:rdsguide24.PNG|400px]][[File:rdsguide24.PNG|400px]][[File:rdsguide26.PNG|400px]][[File:rdsguide27.PNG|400px]]

Once this completes on the server you configured your group select the following option

[[File:rdsguide28.PNG|400px]]

If you have done things correctly you should now see the following screen, Press the RD Gateway + icon


[[File:rdsguide29.PNG|400px]]

In here select your RDS gateway server

[[File:rdsguide30.PNG|400px]]

'''You may get this error if you havent rebooted'''

[[File:rdsguide31.PNG|400px]]

In the FQDN type in your full domain name and if you have a split zone this will be the same internally. If you want to get access outside of course you will need to use your external domain name


[[File:rdsguide32.PNG|400px]]

Confirm the next two screen

[[File:rdsguide33.PNG|400px]][[File:rdsguide34.PNG|400px]]

Do the same for the License server

[[File:rdsguide35.PNG|400px]][[File:rdsguide36.PNG|400px]]

If you have done everything right you will now get the screen below

[[File:rdsguide37.PNG|400px]]

From the left bar select Collections

[[File:rdsguide38.PNG|400px]]

Once the menu is open select tasks and then create session collection

[[File:rdsguide39.PNG|400px]]

Select next to the following screen and appropriately name your RDS collection 

[[File:rdsguide40.PNG|400px]][[File:rdsguide41.PNG|400px]]

Select your session host you create earlier 

[[File:rdsguide42.PNG|400px]]

Apply a relevant group of people who you want to have access

[[File:rdsguide43.PNG|400px]]

If you have a file server you can create a profile disk

[[File:rdsguide44.PNG|400px]]

Select create to finish your collection 

[[File:rdsguide45.PNG|400px]]

If require select your RDS group, tasks and then Publish RemoteApp

[[File:rdsguide46.PNG]][[File:rdsguide47.PNG|400px]]

Assume you have already install the apps you want to access tick these to publish them 

[[File:rdsguide48.PNG|400px]]

Confirm your selections

[[File:rdsguide49.PNG|400px]][[File:rdsguide50.PNG|400px]]