Getting Started with VMware Virtual Desktops

Over the last few months I’ve received more and more requests and questions regarding virtual desktops, or more specifically, VMware’s VDI solution.

I just went through a fresh installation in the lab to ensure all of the steps were as recent as they are going to be, so let’s get started.

To test out the solution I recommend leveraging an existing VMware VI3 infrastructure, thus requiring no additional hardware.

Requirements:

• Physical/Virtual server to serve as the Connection Broker

• Virtual Machine template for the desired operating system

Installing the “VMware Desktop Manager (VDM) Broker.“

The VDM Broker acts as the traffic cop in your virtual desktop infrastructure. It handles the requests of incoming connections and associates them with an appropriate virtual machine.

• Download the VDM software and start the installation on a Windows Server 2003 VM.

• There are three installation types: Standard, Replica and Security Server.

Standard – Stand alone instance or first broker in the farm. This will be the selection for our testing purposes.

Replica – An additional broker that is added to an existing farm to manage client load. Shares the same directory info as other brokers in the farm.

Security Server – Just the necessary components to serve up a portal to external clients. This is the choice for your front end server exposed in the DMZ.

• The rest of the installation is straightforward.

• Once installation completes, point your browser to https://vdm_broker/admin

• Using an account with admin rights on the VDM server, login to the management portal.

• Under, “Access and Security Settings” click EDIT to add a legitimate license key.

• Under, “Virtual Center Servers” add an appropriate Virtual Center for your environment.

• Under, “VDM Servers” you should see your new server and it should be enabled.

Preparing the Virtual Machine Template

• Build an XP/Vista virtual machine in the usual template manner including appropriate patches and VMware Tools.

• Verify that RDP is enabled for the VM.

• Start the VDM Agent installation.

• Ensure that, “VDM Authentication for GINA,” “USB Redirection,” and “Enable the Remote Capability on this computer” are all enabled.

• Also ensure that the VM is able to resolve the hostname of the VDM Broker.

• Shut down the guest and mark it as a template.

Preparing the Virtual Machine Customization File

• If it doesn’t already exist, create a VM Customization template for your virtual desktops.

• Using the above template, right click and select, “Deploy VM from this template.”

• When prompted, select, “Customize this guest.” That will launch the Customization Wizard.

• Ensure that the VM automatically joins the domain, automatically configures its network (preferably via DHCP) and configures any other applicable settings. I also prefer to use the display name as the hostname.

Building a Pool of Virtual Desktops for Connections

• Point your browser back to https://vdm-broker/admin and login.

• Click the, “INVENTORY” button in the upper left.

• Ensure that, “DESKTOPS” is chosen to the right.

• Click, “ADD” to create a pool.

• Select the appropriate, “Desktop Type.” For this test, we will select, “Desktop Pool Non-Persistent.”

The options are:

Individual Desktop – VMs for the desktop are brought in directly from Virtual Center and manually assigned to users by the admin.

Desktop Pool PERSISTENT – VMs in this desktop are automatically created and assigned by the VDM Broker. Once assigned, each user keeps the same VM for every subsequent connection.

Desktop Pool NON-PERSISTENT – VMs in this desktop are automatically created and assigned by the VDM Broker. The assignment happens on a per session basis.

• In the next screen, set an appropriate, “Desktop ID” and add a brief description. I left, “Desktop Display Name” empty.

• In the next screen, ensure that the following settings are applied:

Desktop state = Enabled.
Provisioning = Enabled.
Pool size =
Prefix for VM Names =
VM power policy = Powered off when not in use (why not? I wouldn’t want idle VMs just sitting there unless I had an issue where VMs could not be powered on quick enough for user demand.)
Automatic logoff after disconnect = After 10 minutes (seems fair).
Allow multiple sessions per user = Enabled (so we can properly test).

• Select the appropriate Virtual Center server.

• Select the proper template.

• Select the appropriate VM Folder location.

• Select the appropriate cluster.

• Select the appropriate resource pool.

• Select the appropriate datastore(s).

• Select the appropriate customization template.

• Click Finish.

• Be patient. If you fire up the VI Client and point it to Virtual Center you will see your new virtual desktop virtual machines being built. While the VMs are being deployed it’s a great time to setup the access to the new virtual desktops.

• Select the new pool you’ve created under, “Desktops” and select, “Entitlement.” Add the appropriate groups (in this case I just used local Administrators).

• Once provisioned they will be customized. You can check this status in the VDM Admin portal under, “Virtual Machines.” Once they say, “Ready,” it’s show time.

Connecting to your brand new virtual desktop

• From a client workstation, point your browser to http: (Note the lack of the /admin).

• Once logged in it may prompt to install several Active-X controls for the VDM Client. That’s a good sign.

• Next we should see our beloved virtual desktop that we created earlier. Click, “Connect” and prepare to be impressed.

• In this case, my fresh XP desktop is loaded. I then fired up IE and pointed to my second favorite website (behind www.F1-Live.com).

Coming in the coming weeks, “Battle of the Brokers.” Some of the most popular VDI Brokers will be thrown to the wolves and tested in the lab for a battle royale. Results coming soon!

Cheers!

- Jason Langone

• Read More?
• Can you digg it?
• Isn't this del.icio.us?
• Seed the newsvine?

Commenting is closed for this article.