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

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

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