Login VSI Configuration

From Login VSI Documentation
Jump to: navigation, search

First start of the Login VSI Management Console

When starting Login VSI Management Console for the first time you have to import the license file that is provided by Login VSI. A free trial license can be requested at http://www.loginvsi.com/products/login-vsi/free-trial

Steps

Description

Screenshot

Start the Login VSI Management Console from the VSIshare.

Location:

{VSIshare}\_VSI_ManagementConsole\VSI Management Console.exe

Start the Login VSI Management Console.PNG

At first run the Login VSI license file needs to be imported.

Make sure the VSIshare path points to the VSIshare you just installed

To import the license uncheck the check box “Login VSI License is stored in VSIshare” and click browse.

2013-11-04 01 52 21-Login VSI Analyzer.png

Open the LoginVSI.lic that has been provided by Login VSI. If your license file is in .zip format make sure to unzip it first.

LoginVSI lic.png

Click “Save”.

The LoginVSI.lic will be saved at the following location:

{VSIshare}\_VSI_Configuration\LoginVSI.lic

2013-11-04 01 52 53-Login VSI Analyzer.png

The splash screen will appear with your license information.

Splash screen.png

The Login VSI Management Console will appear with the home screen.

2013-11-01 07 07 46-Login VSI Management Console 4.0.7.162 - Express.png

Microsoft Active Directory preparation

The Active Directory preparation will prepare the Microsoft Active Directory for use with Login VSI. A new OU at a location of choice is created, test users are created and GPO’s are imported and linked.

Please note that the AD preparation tool provided by Login VSI is completely optional but highly recommended! We have an explanation about how to configure the Active Directory manually, this is found here. We recommend that you use the script provided by the AD setup tab of the Login VSI Management Console since this saves a lot of trouble and is a lot faster.

Ensure the domain controller is performing accordingly. Login VSI has a minimal load, but you want to prevent the domain controller or your Microsoft Active Directory becomes a bottleneck.

Setup

Phase 1: Creating a script that can create all required users, groups and policy objects.

Description

Screenshot

Start the Login VSI Management Console and select: 1. Setup AD

2013-11-04 01 47 01-Login VSI Management Console 4.0.7.162 - Express.png

In this screen you can generate a PowerShell script to create the Login VSI Active Directory components. By default the root of the domain is selected. To create the users in a sub OU click browse to select the correct OU.


Note: The script will always create a sub OU named LoginVSI that contains the OU’s Users and Targets.

Ad.PNG

Select the preferred OU and click “Ok”.

Select OU.PNG

Base OU = Location to create the VSI OU

Username = LoginVSI username, the username will contain a number at the end of the username that will be auto incremented starting at 1

Password = Default password for all users

Domain = The domain wherein the AD objects should be created.

VSIshare = Path to the VSIshare created earlier

Number of Users = The total amount of users you want to create

Formatting Length = The amount of leading zeroes in the username for example: 1 results in: LoginVSI1 or 2 results in: LoginVSI01

Launcher username: Username for the launcher machine.

Launcher user password: Default password for the launcher account.

Note: There will be one Launcher user account created.

Ad.PNG

Save to PS1:

Save to PS1 will save the script with reference to the VSIshare. This way you can directly run the script, please make sure you have sufficient privileges to create the objects.

Save to ZIP:

When you are not allowed to write in the Microsoft Active Directory you can use “Save to ZIP” option to save the PowerShell script and GPO settings to a ZIP file. This way you can hand over the pre-configured AD preparation scripts to the person responsible for AD changes.

Ad.PNG

Click Save to PS1 or Save to ZIP.


Select the location to save the VSIADSetup.ps1 or VSIADSetup.zip and click Save.


PS1 or Save to ZIP.PNG
Save to ZIP .PNG

The PowerShell script can be reviewed and edited to add or change specific options.

The GPO files are located on the VSIShare\ _VSI_Binaries\AD Setup

PS1 script.PNG

The VSIADSetup.zip also contains the VSI System and VSI User GPO files.


VSIADSetup.PNG

Phase 2: Running the script that creates the users, groups, ou’s and GPO’s in AD

Description

Screenshot

Logon to a machine that is configured as a domain controller and logon with an account that has sufficient privileges. Start an elevated PowerShell window.


AD AdministratorWindows PowerShell.png

Note: Please make sure the Execution policy is set to unrestricted.

Set-executionpolicy unrestricted

More information can be found at:

http://technet.microsoft.com/en-us/library/ee176961.aspx


2013-11-01 06 43 36-Greenshot.png

Execute the following command:

& “VSIADSetup.ps1”


2013-11-01 06 43 55-Greenshot.png

Execute the script and wait to the script to complete.

The following information will be displayed.

2013-11-01 06 44 12-Greenshot.png

The OU’s, Users and Groups are created.


2013-11-01 06 46 04-Active Directory Users and Computers.png

The Group Policy Objects are added and linked to the Login VSI Target OU and Computer OU.

GPMC.PNG

Manually creating test accounts

If you do not want to or are not allowed to run the automated Login VSI user creation PowerShell scripts within your environment then it’s also possible to manually create test accounts using the steps outlined below. These steps describe every object normally created by the automated preparation.

During the automated creation process Login VSI will create the following OU structure, please note that the OU structure is there to help you keep overview. It is not required for Login VSI to work.

Organizational Unit (OU) structure

  • <Select a root OU within your domain>
  • LoginVSI
    • User
      • Launcher
      • Target
      • Computers

Users

The Automated AD preparation will create 2 types of users.


  1. So called target users. These users will logon to your target environment (the environment that you want to test). The users have a logon script specified that will start the test once the users log on. This logon script is by default placed in the sysvol folder of your domain ([file://yourdomain/SYSVOL/YourDomain/scripts/V4-VSI_Logon.cmd \\YourDomain\SYSVOL\YourDomain\scripts\V4-VSI_Logon.cmd]) although the script can be placed anywhere. More details on the logon script below. Create as many user accounts as you like to test with.


  1. A single launcher user. This user is used in the launcher workflow. It is a user that will logon to the so called launcher machines (the machines that initiate session). Once it logs on the users logon script will make sure that the launcher agent is started. This user also uses a logon script in the sysvol folder. More details on the script below. This is just a single user account.

Create a group

Every user mentioned above will be a member of a group. This group allows you to easily set permissions or allow access to resources. The group that is crated is called LoginVSI. This group is also referenced in the (optional) Target setup. If you choose to create a group that is not named LoginVSI then please remember to uncheck the “Add Login VSI group to local RDP group” checkbox in the Target setup.

Import and link Group Policy objects

The automated AD preparation imports and links backups of group policy objects. These are intended to make the implementation easier. The VSI-system object is linked to the Computers OU mentioned above while the VSI-user object is linked to the Target OU mentioned above.

The most important settings made in the GPO’s are:

  • Logon synchronously. This allows the VSI script to complete before the users are logged on, preventing timing issues.
  • Disable User Account Control (UAC). Disabling UAC makes sure that UAC prompts will not interfere with the actual test runs.

The backups can be found in [file://server/VSIshare/_VSI_Binaries/AD Setup/ \\Server\VSIshare\_VSI_Binaries\AD Setup\]

If you want to manually import the pre-build Login VSI GPO’s please execute the steps below: Please note that the Login VSI Policy objects are split in User and System settings.


Description

Screenshot

Logon to a machine that is configured as a domain controller and start the “Group Policy Management Console” (GPMC.msc)

2013-11-01 06 48 00-Group Policy Management.png

Browse to the OU containing the Login VSI test computer objects. Right click and select “Create a GPO in this domain, and link it here”

Comp-create-gpo.png

The system asks to provide a name for the newly created GPO. Use (for example): LoginVSI-System-M.

2013-11-01 06 48 15-New GPO.png

In the GPMC tree browse to the “Group policy objects” container. Right click the newly created GPO and select “Import settings”

2013-11-01 06 49 26-Import Settings Wizard.png

A wizard will now guide you through the steps required to import the predefined settings. It also asks to create a backup of the policy object. If you just created this object there is no need to backup as its empty. If you are using an existing GPO make sure a backup is created.

2013-11-01 06 49 28-Import Settings Wizard.png

Browse to the location of your VSIshare and browse to the folder: \\Server\VSIshare\_VSI_Binaries\AD Setup\VSI System\ and click “next”

2013-11-01 06 49 59-Browse For Folder.png

Select the “VSI-System-V4” GPO backup and click “Next”

2013-11-01 06 50 10-Import Settings Wizard.png

Complete the steps in the wizard to finish the import process.

2013-11-01 06 50 19-Import Settings Wizard.png

Complete the steps in the wizard to finish the import process.

2013-11-01 06 50 21-Import Settings Wizard.png

Check if the “VSI-System-M” policy object now contains the imported settings.

Imported settings.PNG

Browse to the OU containing the Login VSI test User objects. Right click and select “Create a GPO in this domain, and link it here”.

User-create-gpo.png

The system asks to provide a name for the newly created GPO. Use (for example): LoginVSI-User-M.

2013-11-01 06 52 56-New GPO.png

In the GPMC tree browse to the “Group policy objects” container. Right click the newly created GPO and select “Import Settings”.

2013-11-01 06 49 26-Import Settings Wizard.png

A wizard will now guide you through the steps required to import the predefined settings. It also asks to create a backup of the policy object. If you just created this object there is no need to backup as its empty. If you are using an existing GPO make sure a backup is created.

2013-11-01 06 49 28-Import Settings Wizard.png

Browse to the location of your VSIshare and browse to the folder: \\Server\VSIshare\_VSI_Binaries\AD Setup\VSI User and click “next”.

2013-11-01 06 53 14-Browse For Folder.png

Select the “VSI-User-V4” GPO backup and click “next”.

2013-11-01 06 53 17-Import Settings Wizard.png

Complete the steps in the wizard to finish the import process.

2013-11-01 06 53 19-Import Settings Wizard.png

Complete the steps in the wizard to finish the import process.

2013-11-01 06 53 21-Import Settings Wizard.png

Check if the “VSI-User-M” policy object now contains the imported settings.

Imported settings user.PNG


Create the logon scripts

The logon scripts used by the test user and the launcher accounts are, by default, created in the netlogon folder. These scripts are easy to create as they only contain one line of code:


Description

Screenshot

Logon to a machine that is configured as a domain controller and start “Notepad” with administrative privileges. These steps will describe how to add the Login VSI engine to a User logon script that will be executed at the target machines.

2013-11-01 06 54 26-Untitled - Notepad.png

Within Notepad goto File > Open and browse to the netlogon folder within your domain. Typically found at:

\\Nameofyourdomain.TLD\Netlogon

Make sure to set the File extension filter to “All files *.*”

2013-11-01 07 00 31-Open.png

Within the netlogon folder right click to create a new TXT file

2013-11-01 07 01 03-Open.png

After creation rename this file to: V4-VSI-Logon.CMD and open it for editing.

2013-11-01 07 01 33-Open.png

Add the following line to the file:


CALL \\server\VSIshare\_VSI_Binaries\Target\Logon.cmd


Make sure to replace \\server\VSIshare with the actual path to the VSIshare within your environment!

Save and close the file

2013-11-01 07 01 11-V4-VSI Logon.cmd - Notepad.png



Description

Screenshot

Logon to a machine that’s configured as a domain controller and start “Notepad” with administrative privileges. These steps will describe how to add the Login VSI engine to a User logon script that will be executed at the launcher machines.

2013-11-01 06 54 26-Untitled - Notepad.png

Within Notepad goto File > Open and browse to the netlogon folder within your domain. Typically found at:

\\Nameofyourdomain.TLD\Netlogon

Make sure to set the File extension filter to “All files *.*”

2013-11-01 07 01 33-Open.png

Within the netlogon folder right click to create a new Text Document.

2013-11-01 07 01 39-Open.png

After creation rename this file to: V4-VSI-Launcher.cmd. Open the created file to edit.

2013-11-01 07 01 39-Open.png

Add the following line to the file:

CALL "\\server\VSIshare\_VSI_Binaries\Launcher\Agent.exe"

Make sure to replace \\server\VSIshare with the actual path to the VSIshare within your environment.

Save and close the file.

2013-11-01 07 01 42-V4-VSI Launcher.cmd - Notepad.png

Additional VDI optimization scripts for Windows 7 and 8, provided by Microsoft

- Windows 7 download

Script as told at PFE Blog. This is the PFE VDI Script in form since October 2012 for Windows 7 SP1

It is particularly geared towards stateless VDI. Originally posted here

- Windows 8 download

Script Basics, Fine for 8.0. This script needs tweaks (not yet documented/understood) for 8.1.1

Steps

During the setup all the individual installations will be shown. The process can be seen in the CMD box.

Description

Screenshot

Copy the Login VSI target setup to the target and run the TargetSetup.exe as an administrator with elevated privileges.

2013-11-01 07 04 26-2. Target Setup.png

Select the components that need to be installed. Default = all

2013-11-01 07 04 32-Login VSI Target Setup 4.0.7.162.png

Wait for the setup to finish.

2013-11-01 07 04 47-Login VSI Target Setup 4.0.7.162.png

You can verify if the applications are installed by running Appwiz.cpl or opening the Programs and Features from the control panel.


The listed application are:

Adobe Reader

Doro

Java

2013-11-01 07 07 00-Programs and Features.png

These programs may be installed individually if already on the target machine.

Adding launchers

Launchers are required to initiate the remote connection to the target. Launchers require a Microsoft Windows based OS that contains the remote client that is used (e.g. RDP client, VMware View client, Citrix client etc). We recommend using the launcher workflow to start all launchers or set auto logon to automatically start the Login VSI Launcher Agent.

The requirements and recommendations for the launchers can be found here.

Steps

Description

Screenshot

Start the Login VSI Management Console from the VSIshare and click on 2. Add Launchers

2013-11-01 07 07 46-Login VSI Management Console 4.0.7.162 - Express.png

Click on “add launcher” in the blue bar or “add launchers” down in the right corner.

2013-11-01 07 07 49-Login VSI Management Console 4.0.7.162 - Express.png

Click “Next”.

2013-11-01 07 07 53-Add Launcher Wizard.png

Depending of the total amount of launchers to add you can select Single machine or Batch entry.


Start with “Single entry”.


Click “Next”.

2013-11-01 07 08 02-Add Launcher Wizard.png

Provide the launchers names as IP address, Hostname or FQDN (Fully Qualified Domain Name) of the computer that will be used as the launcher.

Note: The “Name” must be identical with the IP address, Hostname or FQDN (Fully Qualified Domain Name) of the launcher computer.

Provide the “Maximum capacity” of total sessions that can be launched on the launcher. It is not recommended to go above 50 sessions per launcher for RDP, 25 sessions for ICA/HDX and 25 sessions for PCoIP. DDC can initiate 1.000 sessions per launcher.

Mark the checkbox enable to enable the launcher for use.

Click “Next”.

2013-11-01 07 08 20-Add Launcher Wizard.png

Review the information and click on Finish

2013-11-01 07 08 23-Add Launcher Wizard.png

The launcher machine is added and ready for use.

2013-11-01 07 08 26-Login VSI Management Console 4.0.7.162 - Express.png

Optional: To add a batch of launchers please continue the wizard until the “Select method” tab.

Select “Batch entry” and click “Next”

2013-11-01 07 08 41-Add Launcher Wizard.png

Provide the launchers names as IP address, Hostname or FQDN (Fully Qualified Domain Name) of the computer that will be used as the launcher.

Note: The “Name” must be identical to the IP address, Hostname or FQDN (Fully Qualified Domain Name) of the launcher computer.

Provide the “Start number”, default = 1

“Increment” can be configured, default = 1

“Count” will be the total of launchers that will be created.

Provide the “Maximum capacity” of total sessions that can be launched on the launcher. It is not recommended to go above 50 sessions per launcher for RDP, 25 sessions for ICA/HDX and 25 sessions for PCoIP. DDC can initiate 1.000 sessions per launcher.

“Formatting length” is the amount of numbers that will be used after the name.

“Enabled” will enable all launchers.

When every option is configured properly click “next”.

2013-11-01 07 09 07-Add Launcher Wizard.png

The following screen will provide you with an overview of the launchers that will be added. In this view you can modify the name, capacity or disable/enable the launcher.

Click “next” to continue.

2013-11-01 07 09 10-Add Launcher Wizard.png

The review information is shown with all the launchers that will be added.

Click “finish” to add all the launchers.

2013-11-01 07 09 20-Add Launcher Wizard.png

The launchers machines are added and ready for use.

2013-11-01 07 09 22-Login VSI Management Console 4.0.7.162 - Express.png

Data servers setup

To make sure you have the right UNC path to the VSIshare you need to go to Infrastructure > data servers tab and make sure the UNC path(s) is (are) valid i.e. "\\%computername%\VSIShare\.." and *not* "C:\VSIShare\..".

Basic workload settings

The knowledgeworker workload is the default workload in Login VSI.

Steps

Description

Screenshot

Start the Login VSI Management Console located in the VSIshare. In the Home screen on the left side click “workload”.

2013-11-01 07 07 46-Login VSI Management Console 4.0.7.162 - Express.png

In this overview all the workload settings can be configured. The only required setting is the “Office version”.

2013-11-01 07 09 49-Login VSI Management Console 4.0.7.162 - Express.png

The setting “Office version” is required to configure, all other settings are optional. In this quick setup the office version 2013 is used.

Please see chapter 3.9.2 for a detailed overview of all settings.

By leaving the tab the settings will be saved.

2013-11-01 07 10 00-Login VSI Management Console 4.0.7.162 - Express.png

In some environments Operating Systems are not equal to the Microsoft Office versions and Language Packs (MUI). Therefore Login VSI has the option to combine these settings.

The "OS language", "Microsoft Office version" and "Microsoft Office language" setting is required to configure, all other settings are optional.

  • "OS language", is configured for the Operating System Language, in this example, the OS is English.
  • "Microsoft Office version", is configured for the Microsoft Office version, in this example, the Office version is 2007.
  • "Microsoft Office language", is configured for the Microsoft Office Language, in this example, the Office version is Dutch.
  • "Microsoft Office print sequence", is the configured print sequence for Microsoft Office, in this example, ctrl+p.

Note: Office 2010 and 2013 have different print sequences if the Microsoft Office setup is not English (If both OS/Office2013 version is configured in Dutch, I need to configure the following print sequence: bkk).

By leaving the tab the settings will be saved.

Workload-language os&office.png

Creating a scenario

Scenarios are used to control the amount of users Login VSI will logon during one or multiple timeframes. Login VSI can logon users in one single phase with a fixed interval or in multiple phases all with different intervals. The basephase is used to measure the performance of the environment without the user load. This way Login VSI can estimate the normal response times to calculate the baseline that is used in the VSImax results.

How to create a scenario with Login VSI 4.x

How to setup a BasePhase configuration with Login VSI 4.x

Setup

Description

Screenshot

Start the Login VSI Management Console in the VSIshare and Click 4. Configure Scenario

2013-11-01 07 07 46-Login VSI Management Console 4.0.7.162 - Express.png

On this tab you can create a scenario for your test.

2013-11-01 07 10 22-Login VSI Management Console 4.0.7.162 - Express.png

By default the knowledgeworker workload is selected.

Click on sessions and enter the amount of sessions you want to run.

The timeframe is shown in seconds and by default all sessions will be launched in 48 minutes (2880 seconds).

By leaving the tab all settings will be saved automatically

2013-11-01 07 10 25-Login VSI Management Console 4.0.7.162 - Express.png

Connection configuration

The connection setup is where the connection to the target environment is created. This example is for setting up an RDP connection. For other connectors / connections please click here.

Setup

Description

Screenshot

Start the Login VSI Management console from the VSIshare and Click 5. Configure connection.

2013-11-01 07 07 46-Login VSI Management Console 4.0.7.162 - Express.png

Here you can configure the connection command line. In this demo we will configure a RDP connection to a Windows Terminal Server.

Click on start connection wizard.

2013-11-01 07 10 49-Login VSI Management Console 4.0.7.162 - Express.png

Click next.

2013-11-01 07 10 52-Connection Wizard.png

Select the connection type. In this case we will select RDP Connection.

Click next.

2013-11-01 07 10 56-Connection Wizard.png

In this step you have to specify the connection information. To specify the user or session host numbers you can use the {Count} variable. In case a formatting length is used you can specify the length with a {Count/ number}. Example: LoginVSI{Count/3} will generate the username LoginVSI001. Default = LoginVSI{Count}

Specify a RD Session Host.

Enter a username

Enter the password, default = Password!

Domain is optional

2013-11-01 07 11 31-Connection Wizard.png

In this step you can specify the session display settings. Suppress warnings is recommended.


Click next.

2013-11-01 07 11 36-Connection Wizard.png

In this step you can enable resource mappings. Mapping printers is not recommended.


Click next.

2013-11-01 07 11 37-Connection Wizard.png

In this step you can edit the connection experience.


Click next.

2013-11-01 07 11 39-Connection Wizard.png

If required you can configure a remote desktop gateway.


Click next.

2013-11-01 07 11 41-Connection Wizard.png

The final command line is shown.


Click finish.

2013-11-01 07 11 43-Connection Wizard.png

All settings are configured and can be edited.


2013-11-01 07 11 45-Login VSI Management Console 4.0.7.162 - Express.png

Troubleshooting

-LoginVSI downloadable is not extract.

  A: The file is probably corrupted, and the best thing to do is to redownload and try again.

-Server Setup cannot find a location to install.

  A: A file share must be created on the local machine to be able to install the software. If one does not exist, it must be created. 

-Server Setup did not install correctly.

 A: This is usually caused by a corrupted download of the installer. Repeat the steps from above.

-Target Setup has failed on some portions of the installation.

 A: This is usually caused by the environment. Many times, failed installations are caused by permission/policy issues. This is to be installed on the target machines. 

-My license is telling me there is an issue/time expired/etc and will not open up the Management Console.

 A: Please contact your account manager about licensing issues.

If any of these do not help with your installation issue, please contact support at Support@LoginVSI.com