Introduction Publishing Individual Virtual Desktop Pools
Version: Horizon View 5.1
With a basic VMware View Connection Server installed, we are now in a position to publish our first desktop. We recommend doing this as a first step so you can ensure that the View Client can connect to the Connection Server, and in turn connect to the Virtual Desktop running the View Agent. Once you are satisfied that the virtual desktop works, we can think about making a template out of it and create a larger pool of virtual desktops. After all, there’s little point in creating a pool of 100 virtual desktops if the source of that pool is broken or doesn’t work properly. All the way back in View 3 it was possible to publish what were called Individual Desktops. These allowed one virtual desktop to be used per user, and ensured that only that user had rights to a particular virtual desktop. This feature is now deprecated, however it is still very easy to create a manual pool that contains only one virtual desktop and assign it to one user – which is essentially the same thing. It is also possible to assign an individual virtual desktop to more than one person. On the surface this might seem an oxymoron. But, if you’re looking for a usage case, you often see one PC being used by different people at different times in factories and production environments. Remember though, that unlike Microsoft Remote Desktop Services or Citrix XenApp Server, only one person at a time can connect to a Windows XP/Vista/7 client desktop. In other words, these clients do not support the concept of “multi-win” where many Windows “sessions” can be spawned from a single kernel.
Publishing an Individual Desktop
2. Open the >Inventory node and click the Pools icon
3. Next click the Add button
4. In the Pool Type page select Manual Pool
5. In the User assignment page, ensure the Dedicated option is enabled, and ensure the option to “Enable automatic assignment” is enabled. Auto assignment means that you are letting View assign the entitled users to a desktop rather than you pre-assigning the users to a desktop
6. Choose the Desktop Source to be vCenter virtual machines
7. Select the vCenter which manages the virtual desktop
8. Next you must specify a unique ID for this virtual desktop together with some friendly information by which the end user will be able to identify the virtual desktop.
The ID must be unique to this instance of Horizon View, and is stored in the Microsoft AD LDS system. It’s important to know that, once set, the ID value cannot be changed, but the friendly information that the user sees can be changed at any time. New back in View 4.5 was the ability to create folders within the View Administration console, with folders you are able to structure your environment with greater ease, to add your desktops to a folder you will need to pre create the folder in the pools view prior to creating your pool, we wish VMware would allow you to create a folder at this stage however it is possible to move a Pool into a folder later in the same Pools view.
9. The next page allows you to control some per-virtual desktop settings that centre around the end user connection. We will be looking at this page in more detail later on. For now we just want to confirm that the system works and that a client can connect to the virtual desktop
10. Next you select the virtual desktop that the end user will be allocated
A list of compatible images that can be used will be generated, from this list you will need to pick the desktop you wish to use.
11. We are now presented with advanced storage options where we can configure host caching for the pool, as this is only a test desktop at this time we are not going to enable host caching.
After clicking Next and Finish, a desktop will be created in VMware View. The next step is making sure that only the right user has access to the desktop – VMware calls this process “Entitlement”. By default, no user has any rights to the virtual desktop until this step is carried out.
12. Select the virtual desktop in the list and click Entitlements
13. In the Entitlements pop-up page, click the Add button
14. Click the Find button and locate the correct user, in our case ViewTest1
Connecting to a desktop with the View Client
Now the virtual desktop is created and entitled, we can use the client to attempt our first connection to the virtual desktop. The screen grabs below show this process from the user’s perspective:
Note: Notice how the dropdown arrow next to the desktop name allows the user to set which protocol they wish to use with View
By creating our first desktop we have been able to prove that not only is our View Connection Server configured properly but also that our template is configured correctly to work with View, we have also started looking at some of the basic pool configuration options. In the next chapter we will delve deeper into the configuration options of desktops pools, including dedicated and floating pools.