Skip to main content

Part 2:- Building VDI using Remote Desktop Services (RDS)


Task 1: Install Remote Desktop Virtualization Host role

On the RDSVH, install Hyper V roles and Remote Desktop Virtualization Host. You need to install RD Virtualization Host role for each Hyper V server that's hosting Personal or Virtual Desktop Pool

1. Log on to RDSVH with administrative right.
2. Open Administrative Tools. Click Start > Administrative tools > Server Manager
3. Right click Roles and select Add Roles
4. On the Before You Begin page, Click Next
5. On the Select Server Roles page, select Hyper V roles and Remote Desktop Service and then click Next
6. On the Remote Desktop Service page, click Next
7. On the Select Role Services page, select Remote Desktop Virtualization Host and click Next
8. On the Confirm Installation selection page, Click Install
9. Restart the system when asked.

Task 2: Install Remote Desktop Session Host (Redirector) role

1. Right click RDSRedirect VM and select Connect
2. Log on with administrative right
3. Open Administrative Tools. Click Start > Administrative tools > Server Manager
4. Right click Roles and select Add Roles
5. On the Before You Begin page, Click Next
6. On the Select Server Roles page, select Remote Desktop Service and then click Next
7. On the Remote Desktop Service page, click Next
8. On the Select Role Services page, select Remote Desktop Session Host and click Next


9. On the Uninstall and Reinstall Applications for Compatibility page, Click Next
Note that the purpose of installing the RD Session Host role service for this solution is for it to act as a Redirector and not for RemoteApp publishing.

10. On the Specify Authentication Method For Remote Desktop Session Host page, select "Require Network Level Authentication" and click Next. Your client must be running minimum Windows XP SP3 (with some configuration that you need to perform) or later in order to support Network Level Authentication. I'm talking about your offsite computer (that's what i mean).


11. On the Specifying License Mode, select Configure Later and Click Next. You can run RDS for 120 days before activating the license. Remember to get the license before the expire date.



12. On the Select User Groups Allowed Access to this RD Session Server, click Add button and Enter VDIGroup.

13. Click Check name and click Ok button.



14. Click Next15. On Configure Client experience, leave default value and click Next
16. Review the confirmation page and Click Install button
17. Click Close button and select Yes to restart the system.

Task 3: Install Remote Desktop Connection Broker role

1. Right click RDSBroker VM and select Connect
2. Log on with administrative right
3. Open Administrative Tools. Click Start > Administrative tools > Server Manager
4. Right click Roles and select Add Roles
5. On the Before You Begin page, Click Next
6. On the Select Server Roles page, select Remote Desktop Service and then click Next
7. On the Remote Desktop Service page, click Next
8. On the Select Role Services page, select Remote Desktop Connection Broker and click Next
9. Review Confirm Installation selection and click Install button. The installation process will begin.
10. Click Close button

Task 4: Install Remote Desktop Web Access & Remote Desktop Gateway role

1. Right click RDSGatewayWeb VM and select Connect
2. Log on with administrative right
3. Open Administrative Tools. Click Start > Administrative tools > Server Manager
4. Right click Roles and select Add Roles
5. On the Before You Begin page, Click Next
6. On the Select Server Roles page, select Remote Desktop Service and then click Next
7. On the Remote Desktop Service page, click Next
8. On the Select Role Services page, select Remote Desktop Web Access and Remote Desktop Gateway
9. Click Add Required Role Service button


10. Click Next11. On the Choose a Server Authentication Certificate for SSL Encryption page, select Create a self-signed certificate for SSL encryption, and then click Next.
It is recommended to get a 3rd party certificate/External Certificate.



12.On the Create Authorization Policies for RD Gateway page, select Now, and then click Next.



13. On the Select User Groups That Can Connect Through RD Gateway page, click Add. In the Select Groups dialog box, specify VDIGroup, and then click OK to close the Select Groups dialog box. Click Next.



14. On the Create an RD CAP for RD Gateway page, enter the name VDI-RD_CAP_01 for the Remote Desktop connection authorization policy (RD CAP), select Password, and then click Next.


15. On the Create an RD RAP for RD Gateway page, enter the name VDI-RD_RAP_01 for the Remote Desktop resource authorization policy (RD RAP), and then select Allow users to connect to any computer on the network. Click Next.
Note: You can limit user to connect computer on the network. If you would like, you can create a VDI computer group and put the computer pool into this group.



16. On the Network Policy and Access Services page (which appears if this role service is not already installed), review the summary information, and then click Next.

17. On the Select Role Services page, verify that Network Policy Server is selected, and then click Next.
18. On the Web Server (IIS) page, click Next
19. On the Select Role Service, accept the default setting and click Next
20. On the Confirm Installation Selection Page, click Install button. The installation process will begin.
The default URL is https://RDSGatewayWeb/RdWeb . Use this url for accessing the VDI.


21. On the Installation Results page, review the results and click Close

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...