Thursday 11 August 2011

LoginVSI - Basic Overview and installation notes

I have been testing Login consultants VDI benchmarking tool LoginVSI today.
This product allows the benchmarking of a VDI environment to ensure it will scale as you expect.
It will ultimately allow you to answer the question of how many guests you can deliver on your hypervisor
and see if the bottleneck is CPU/Memory/IO

The product itself consists of 2 main installs :
Launcher - This component will launch the virtual desktops. A single launcher can handle around 50-80 desktops. You can pool the launchers to ensure a larger test.
Guest Tools - These are tools that you need to install within the Guest VM desktops. These will be used to carry out automated tests within that VM. You will basically create one good VM image with these tools then clone this image to the number of desktops that you wish to test.

Lab Environment
In addition to the LoginVSI components you will obviously need a working VDI environment consisting of things like :
Hypervisor  (Vmware , XenServer, Hyper-V)
Connection Broker
Web interface
Connection Client (ICA, RDP , PCOIP etc..)
AD  (LoginVSI will create its own OU for placing test users and computers)
Network File Share (for storing all the output logs)

Installation Overview
The installation of this product is very far from an smooth process. A number of pre-reqs and seperate installers are required to get the installation working. Here i give a some brief notes on how i got the install working.


ADSETUP - This will ask how many user accounts you wish to create, and the syntax of test User IDs                            
                     and password.
                      This will then create an OU in AD with the relevant containers and add the newly created                
                       user IDs into this container.

FileShare -    Create a network file share for storing the output logs from tests. The test user account created
                        above will require modify access to this area to be able to create output logs.


Guest VM - The XPS printer driver needs to be removed their is a tool to perform this
                   Add the provided GPO to remove the xendesktop splash-screen
                   Ensure that test user account are members of the remote desktop users group
                   Set the VM pagefile size to fixed and 2x physical RAM
                   Move the machine account into the LoginVSI OU
                  Disable Internet Explorer ESC (server 2003 and 2008 only)
                   Run the loginVSI installer. This will install some products like adobe, flash, java and kidkeylock


Launcher - The installer will ask you to specify the file share location
                  Install the separate anaylser product to be able to view the output files
                  Install 3rd party .net Add ins from start menu (this is for the anaylser)
                  Ensure
 
                  Next the launcher will need to be configured with the required parameters.
                  RDP connections work out of the box , but no ICA launcher is included. For this
                  a custom scripting technique and Python third party code is required (see seperate section)

Citrix ICA launcher
This launch process is not supported by Citrix , but did however work in our Lab environment.

Install Python v2.6 onto the launcher machines
Install windows for Python extensions
Copy wi.py script to c:\python26
Rename wi.py to WILauncher.py
Copy PAM3 files into C:\Pythin26\lib\site-packages

Then in the launcher configuration menu choose "custom command line with CSV"

The following syntax is required to use the Python Citrix Launcher

c:\python26\python.exe "c:\python26\WILauncher.py" "http://DDC/Citrix/desktopweb" "%CSV_User%" "Password!" "Domainname" "XDgroup" "20"

Then on the next line provide the path to the CSV file. The CSV file needs to only list the user ID fields.

XenDesktop Policies
In order to ensure smooth automated testing policys should be set to prevent users recieved any popups. Best practice for this would be to disable client device mappings like drives and USB devices. It is also good practice to remove the XenDesktop splash screen to improve performance.








No comments:

Post a Comment