We’ve got VMware View installed, so now what?
The key technology of VMware View is the use of VMware View composer with linked clone. Since users will not have the mechanism to make changes to the OS drive (or even if they change the OS by installing a new app, it will be replaced with a linked clone of master VM during next refresh or recompose operation), the master VM should contain all the necessary components for end-user operation. Programs like Adobe Flash that are typically installed by the end user should be installed in the master VM before deployment. Additionally, the master image should be optimized to reduce as much unnecessary overhead as possible.
1. Create a master VM for Windows 7 with 1.5G RAM, 18G HD (thin provisioned), 32MB Video RAM, and VMXNET3. Use the 500G SATA datastore to store the Microsoft Windows 7 Master VM. During VMware View provisioning, the master VM image is cloned to the replica datastore (which will be SSD drive). It is important to make the OS disk as small as possible to reduce the SSD space consumption and clone time. Avoid any operation that may increase the thin provisioned HD space such as defrag or index operation.
2. After the Microsoft Windows 7 installation, install the VMware Tools and perform a desktop optimization. VMware has a very good Microsoft Windows 7 desktop optimization guide with CMD script that will perform the optimization automatically. (http://www.VMware.com/files/pdf/VMware-View-OptimizationGuideWindows7-EN.pdf) Key optimization steps include:
a) Set the Microsoft Windows performance level to best performance. Computer Properties->Advanced->Performance Settings
b) Fix the paging file size to 75% of RAM
c) Turn off operations that make changes to disks and increase the size of the linked clone, like System Restore, SuperFetch, Defrag, and Microsoft Windows search. Microsoft Windows update and any other update services should be disabled just before shutting down the master VM for provisioning.
3. Install any necessary applications, such as Microsoft Office suite, Adobe Reader, Adobe Flash, Google Chrome, Video Codec, GOM player, printer drivers, and antivirus software. Setup printers for users or use a print server.
4. If Interactive Login-> Do not Require Ctrl-Alt-Del is enabled, single sign on over PCoIP will not work. Disable that policy.
5. Install the VMware View agent. VMware View agent installation may require Microsoft windows update service. Turn on the Microsoft Windows update before the VMware View agent installation. Turn off the Microsoft Windows update after the agent install.
6. After the VMware View agent installation, the Teradici audio device driver redirects analog audio devices and will need to be installed to enable bi-directional audio that is necessary for services like Skype. Download the audio driver from the Teradici support site. (http://techsupport.teradici.com/ics/support/DLRedirect.asp?fileID=15032). After the installation of the Teradici audio device driver, go to control panel->sound and set the Teradici device as the default playback and recording device.
7. Before the master VM can be used, it needs to be activated. Enter the Volume License Key and activate Microsoft Windows. Once Microsoft Windows is activated, two of the registry keys will need to be modified. The first one changes the default activation mechanism for VMware View linked clones from Microsoft Windows Key Management Service (KMS) to Multiple Activation Key (MAK) activation. The second bypasses activation during provisioning.
Set AllowActivateMAKLicense to 1
Set SkipLicenseActivation to 1
8. Release the IP address and shutdown the VM
9. Choose the VM setting to change the swapfile location to host setting that should point to the 500G SATA drive. Otherwise, the VM swapfile will get created in the SSD storage space.
10. Take a snapshot. As the application and Microsoft Windows get updated, take a subsequent snapshot. A snapshot will then be used during VMware View provisioning. However, it is not necessary to keep too many snapshots. Your best bet is to consolidate snapshots from time to time.
a). Installation and configuration of VMware View Manager (Connection Broker)
VMware View Manager (or connection broker) provides VDI administration functions like desktop provisioning and user assignment while providing connection brokering between end user connections to the user’s desktop VM. When a connection request is initiated from an end user device (such as a desktop PC, zero client, or iPad), the VMware View connection broker authenticates the user, and connects the user device to the assigned desktop VM. Depending on the configuration, the display traffic (RDP/PCoIP) can be tunneled through the connection broker.
- Deploy Microsoft Windows 2008 R2 VM with static IP address and join the active directory domain.
- Install the connection broker software. Use Run as administrator option.
- Once the connection broker is installed, run web browser to https://<connectionbroker IP>/admin (the connection broker web GUI is written in Adobe Flex. Use a 32bit web browser)
- Login with domain administrator credential
- Enter your VMware View license key
- In the VMware View Configuration section, select Servers and edit the VMware View connection server settings. Uncheck the Use Secure Tunnel connection to desktop option if a security server is not used.
- Add a vCenter Server to VMware View manager.
Enter the server IP or Fully Qualified Domain Name (FQDN) in the server address. The user should be a domain administrator who can manage the vCenter operation.
You can change the advanced settings and increase the provisioning and power operations, but that should only be necessary for a large scale deployment.
Check Enable VMware View Composer
Add a domain name for VMware View Composer. The domain should be FQDN, such as slhome.local. User name should be in the format of domainusername (ex: slhomesam)
How can we help your agency achieve its mission?
Maximize your IT investments. Learn more about solutions and services from Force 3.