Skip to main content

6.Building VDI using Remote Desktop Services (RDS)


To deploy personal virtual desktop or most of the time we called as "static virtual desktop deployment", you need to has
a) Active Directory Schema upgraded to Windows Server 2008.
b) Client virtual machine running Windows XP or Windows 7 need to use FQDN in Hyper V Manager snap-in.

Static Virtual Desktop is a 1 to 1 mapping. If you have 100 users, then you need to create 100 Virtual machine. User will access to their own unique virtual machine and have greater control. Besides that, changes on the Virtual machine will maintain in the Virtual Machine. This concept is similar as their own desktop environment.

Task 1: Personal Virtual Desktop Configuration.
1. Click on Configure virtual desktops on the top right of the Action pane.






2. Review before you begin page and click Next
3. Verify RDSVH is listed on Specify an RD Virtualization Host Server and click next. For my case, my RDSVH computer name is "LAINB.ms4u.info)





4.Verify RDSRedirect is listed on Configure Redirection Settings and click Next.




5. Click Next on RD Web Access Server.




6. Click Apply button.



7.Review the summary page and make sure Assign personal virtual machine is tick and click Finish button.



8.On the Assign Personal Virtual Desktop page, click Select user.
9. Enter Vdiuser1, Click Check name and click OK
10. On the virtual machine, select VDI01-Win7 and click Next




11.Review the confirm assignment and click Assign.




12.On the assignment summary page, uncheck assign another virtual machine to another user
13.Click Finish

Stay tuned for Part 7:- Building VDI using Remote Desktop Services (RDS) - Click here . I will cover on how to create Virtual Desktop Pool/ Dynamic VM Deployment.

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...

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...

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...