Skip to main content

Building VDI using Remote Desktop Services (RDS)


In the Virtual desktop deployment, it is not necessary to put the VM as FQDN. From here you can different between Personal Virtual Desktop and Virtual Desktop Pool.


For customer who cannot upgrade the schema to Windows server 2008, then this is the only option to select. I have tested this deployment when running on Active Directory schame is on Windows Server 2003.


Dynamic Virtual Desktop is not a 1 to 1 mapping. If you have 100 users and only 50 users which is actively use the VDI, you can create 70 Virtual Machine in the pool. (just my estimation to include 20 Virtual Machine as a buffer). User will access to any virtual machine which is available on the pool. The entire virtual machine is install with the same program and same setting. Besides that, any changes make by the user will be lost after their log off. In this deployment, i recommend that you deploy roaming profile and folder redirection to overcome this issue.


When using this deployment, you will need to use differencing disk for the client VM. In essence, you need to have a base image which contain the client operating system and standard application which we called it as "master image". Then for the VM, create a differencing disk and map to the master image. Follow the instruction on Part 3:- http://www.ms4u.info/2010/04/part-3-building-vdi-using-remote.html to prepare the client VM for VDI. Once you have done that, create a snapshot and name it as "RDV_Rollback". Remove unncessary name give by the snapshot. The system will automatically revert to initial state once the user is logoff.
Now let look into the configuration on the RD Connection Broker for Virtual Desktop Pool.

1. Click on Create Virtual desktop Pool on the Action pane.






2. Review the Welcome to Create Virtual Desktop Pool wizard and click Next button.

3. On select Virtual Machine, use CTRL to select multiple virtual machine. In case environment, select VDI02-Win7 and VDI03-Win7. (Ignore the FQDN, Dynamic deployment do not need to rename the VM as FQDN as i mentioned previously)





4. Click Next button
5. On set Pool properties, Enter
a) Display name:- Windows 7 client pool
b) Pool ID: - VDIWin7.





6. Click Next button

7. Review the result and click Finish.

That will do. At this moment, you have successful configure static and dynamic 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...

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