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

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

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