Create the RDS VDI Service via Hyper-V Cluster

Assumption

You already configured you lab environment with AD, DNS, DHCP, Hypver-V Failover Cluster via Shared Disk and so on.
You can use the additional AD member server or AD Server for RDS controller role server (Broker, RD Web and Session Tunnel)
- At this example, we use iSCSI server as the RDS controller server.
We have two node Hyper-V cluster servers already configured to work.
RDS requires the TS license.

Preparation

Log into the node that will become RDS Controller node. Use Administrator right account (At this time, Domain Administrator account so that we can avoid any trouble.)
Open Server Manager and move to “All Servers”.
Here you have to add all servers relating to the RD Service
- RDS Broker, RD Web and Hyper-V Cluster node, Hyper-V member nodes are to be added.

Install RDS Service – All one step

Log into the RDS Controller node as its Administrator right account (At this time, we use AD server hence Administrator account of domain is required)
Go to Server manager, Manage -> Add Roles and Features.
Next -> “Remote Desktop Service Installation”.
Standard Deployment
Use “Virtual machine-based desktop deployment”.
Next
RD Connection Broker server select > Add Node you want to make broker.
RD Web Server > Add Node you want to make an RD web server.
RD Virtual Session host > Add Hyper-V member node.
Select “Restart” option and “Deploy” RDS services.

*Your Hyper-V member node will be automatically rebooted by this process.
Confirm all get succeeded. and close.
Notice that the “Remote Desktop Services” appears in Server Manager tree.
You will need to manage all RDS service operation from here.
You need to install RDS license (TS License) into License Server which is basically AD Server.

Install License server

Move to Overview in Remote Desktop Services.
Click “RD Licensing”
Select the one and Next. (At this time we use the iSCSI Server/RDS Session broker server for this role)
Confirm and Add.
Confirm the installation gets succeeded.

*You must configure the license and license server later.

Install RD Gateway Server

Click “RD Gateway” from Overview structure.
Select the one and Next. (At this time we use the iSCSI Server/RDS Session broker server for this role)
Specify the external access public node name of the RD GW service. SSL certificate can be re-created later with other name if needed.
Confirm and Add to proceed.
Confirm the installation gets succeeded. Continue the configuration via “Configure certificate”
Configure deployment opens and Certificates section appears.
You need to select the configuration service item one by one and create Certificates.
*Note : this is the Self-signed Certificate which has some de-merit. Later if you get the formal Certificate opportunity, install it.

*From 2nd item, select this certificate from “Select existing certificate” and assign.
Confirm all Certificates got added. And close.
Now all gets ready.

Testing the RD Web

Configure RDS for VDI deployment

On RDS server, on Server Manager , go to Remote Desktop Services | Overview.
From DEPLOYMENT OVERVIEW, “TASK” -> “Edit Deployment Properties”
At RD Licensing, Select “Per User”. Apply.
on Active Directory, Specify the OU where “Workstations” computer object is to be placed.
At this example AD, we use “OU=Workstations,OU=Computers,OU=Resources,DC=spartan,DC=intersoftkk,DC=com”.
*You will see the alert. So “Apply” will fix the problem. To do it. you must run this operation via Domain Admin/Enterprise Admin users.

If properly applying the setting.
OK to close the properties window.