There are requirements for an activated copy of Microsoft Office, Adobe Reader, Adobe Flash Player, Java and DoroPDF. What are these needed for?

This software is required for the native workloads that come with Login VSI. If you do not want to use any of these programs they can be excluded from the workloads. If there are other applications you wish to use you may include those in the workloads as well.

For more information go to: https://www.loginvsi.com/blog/login-vsi/665-simulating-vdi-users-introduction-to-login-vsi-workloads

 

A Citrix dialog asks for local file access

During a test the Citrix Receiver might show a dialog asking for if an online application can access files on your computer. This dialog might show on the VSI launcher. To prevent this message from showing up please follow the instructions in the Citrix Support article.

 

Launcher status is stuck on 'waiting'

Adding the launcher to the management console by just its hostname instead of its fully qualified domain name, ip address or random name should resolve this issue.

The launcher will report in to the management console by using its hostname. The management console will be unable to determine which launcher is reporting in ready if the launcher was added to the management console using anything other than the hostname.

DDC, Direct Desktop Connector (ConsoleConnector) is not working

This is a known issue and will be resolved in a future release. We've created a solution for the issue. Until the new version is released please download this version: http://upload.loginvsi.com/Support/Nov14/ConsoleConnector_v1.zip of DDC.

• Delete the current files in: VSIshare\_VSI_Binaries\Connectors\ConsoleConnector\*
• Unpack it to: VSIshare\_VSI_Binaries\Connectors\ConsoleConnector\*

A full screen session is opened when using SFConnect

This is a known issue and will be resolved in a future release. Until the new version is released please download this version: http://upload.loginvsi.com/Support/Oct14/SFConnect.zip of SFConnect.

• Unpack it to \\VSIshare\_VSI_Binaries\Connectors\
• Add /display absolute /displayabsolute 800x600 to the command line. Feel free to change the resolution.

This issue has been resolved in Login VSI 4.1.3

Cannot establish a Storefront session through a Storefront site that has trusted domains configured

If your Storefront website has a domain drop down list like the example below then you will need to use the version of Storefront below and add the /domain parameter to the command line.

 

1. Download http://upload.loginvsi.com/support/dec14/sfconnectdomain.zip
2. Replace \\server\vsishare\_VSI_Binaries\Connectors\SFConnect.exe with the version downloaded.
3. You then change the command line in the VSI management console from:
"{VSISHARE}\_VSI_Binaries\Connectors\SFConnect.exe" /url http:\\MyStoreFrontURL\Citrix\Store /user {domain}\{username} /password {password} /resource "MyResource"

To:
"{VSISHARE}\_VSI_Binaries\Connectors\SFConnect.exe" /url http:\\MyStoreFrontURL\Citrix\Store /user {username} /domain {domain} /password {password} /resource "MyResource"

Recommended read: Citrix StoreFront Connection Issue – Trusted Domains Only

My status bar in the sessions changed from green to red

This happens when you enable debugging within the Login VSI Management Console (either only workload debugging or engine debugging apart or together). For more information about these settings please see: http://www.loginvsi.com/documentation/Management_Console_Explained#Workload_2.

Web pages are not loading within Internet Explorer 11

Please make sure that Enhanced Protected Mode is disabled. You can find the Enhanced Protected Mode under Internet Options > Advanced > Security > Enable Enhanced Protected Mode. Make sure this check box is cleared.

Which languages are supported by Login VSI?

Within Login VSI we have implemented support for different languages of Office and Windows.

- English - Japanese - French - Dutch - German - Korean - Chinese (simplified) - Russian - Danish

Could not start the test: An active test is running?

Make sure there is no "!!!_Example.IsActivetest" or ".Preptest" file exists in the root of your VSIshare, if one exists delete it and you will be able to start a new test.

Can not analyze the test results: Error in the test data. VSImax is lower than minimal data point

Make sure you run a test with at least an average interval per user session of 30 seconds.

What are the different types of workloads their respective resource usage?

Workload Name	VSI Version	Apps Open	CPU Usage	Disk Reads	Disk Writes	IOPS	Memory	vCPU
Light	4.0	2	66%	52%	65%	5,2	1GB	1vCPU
Medium	4.0	5-7	99%	93%	97%	7,4	1GB	2vCPU
Heavy	4.0	8-10	124%	89%	94%	7	1GB	2vCPU
Task Worker	4.1	2-7	70%	79%	77%	6	1GB	1vCPU
Office worker	4.1	5-8	82%	90%	101%	8,1	1,5GB	1vCPU
Knowledge	4.1	5-9	100%	100%	100%	8,5	1,5GB	2vCPU
Power worker	4.1	8-12	119%	133%	123%	10,8	2GB	2vCPU+

What are the Login VSI 4.1 Timer Metrics?

These metrics are used in Login VSI 4.1 release and are used in our new workloads that are available from Login VSI version 4.1 and up.

Measurement ID	Measurement Action	Measurement Action Detailed	Measures Related Resource
NSLD	Notepad starts and loads a 1500kb document	Notepad starts and loads a random local 1500kb document file that is copied from the content pool	CPU and I/O
NFO	Measure how long it takes to show the file-open dialog in VSI notepad	VSI-Notepad file open [ctrl+o]	CPU, RAM and I/O
ZHC*	Create a zipfile with high compression	Compress a local random .pst file that is copied from the content pool (5mb)	CPU and I/O
ZLC*	Create a zipfile with low compression	Compress a local random .pst file that is copied from the content pool (5mb)	I/O
CPU	Calculates a large array of random data	Creates a large array of random data that will be used in the I/O timer	CPU

'*'compression is measured with 7zip

Other VSI 4.1 related measurements helping determine environmental issues (resources). Note, *the measurements in the table below are not used for the calculation of VSImax v4.1.

Measurement ID	Measurement Action	Measurement Action Detailed	Measures Related Resource
NFP	Press print open in VSI-Notepad	VSI-Notepad print open [ctrl+p]	CPU
UMEM	The percentage of memory used by the sessions	The average percentage of memory used by the active sessions	RAM
IO	Write the CPU random data file to disk	The file created by the CPU random data file is written to the local disk	I/O

Other VSI related measurements helping determine environmental issues (resources). Note, *the measurements in the table below are not used for the calculation of VSImax v4.1.

Measurement ID	Measurement Action	Measurement Action Detailed	Measures Related Resource
FCTL	File copy text local	Copy a local random text file from local temp directory to home drive	I/O

Other VSI related measurements helping determine environmental issues (resources). Note, *the measurements in the table below are not used for the calculation of VSImax v4.1.

Measurement ID	Measurement Action	Measurement Action Detailed	Measures Related Resource
FCTS	File copy text share	Copy a text document from VSIshare to temp directory	I/O and Network

How long is my test running for?

LoginVSI tests are based on three different requirements: Logon rate, Logoff timer and Logoff session at (loop, segment, timer).

• Logon Rate: This number determines the time it takes for the test users to be able to sign on
• Logoff timer: This number is how long it takes before the users are given -permission- to logoff
• Logoff session at: This parameter determines when the users will be able to sign off

If everything is left to default, then the test will run for a total of 62 minutes.

If increasing the Logon rate, this will push back the time it takes for the users to sign on. As the last user will no longer sign on at the very end of the default workload, it will sign on farther into the first segment. This in turn, will push back the time in where the Logoff timer will count down, and potentially increase the time in which it takes to run a test.

  -Example: Logon rate: 3600 -> The last user now signs on at 1 hour, which is the very beginning of the second segment. Because of the requirement of Logoff at: segment, the test will run for a total of 74 minutes.

If increasing the Logoff timer, this will force all users to run the workload continuously until the requirements are reached. This parameter is most commonly used to create soak testing, as it can easily be changed to cause all users to run for much longer than default.

  -Example: Logoff timer: 3600 -> All of the users will sign on at default times, but now they will all run continuously for 1 hour before they are given permission to logoff. This will force the test to run for 108 minutes.

If changing the Logoff session at, this will change where in the workloads the users can sign off. The loop option forces all users to sign off when they reach the end of a workload, the segment option forces all of the users to sign off at 12 minute intervals, and the timer option forces all users to sign off at 4 minute intervals. Note: Setting the sign off at timer will have the shortest sign off rate, whereas loop will have the longest.

When is my test complete?

It is common to see the LoginVSI dashboard claim that the test is complete and there is "00:00:00" time left before the users logoff, and yet the users are still running in the background. The reason this occurs is because of the logoff timer and the Logoff session at setting. Although the timer has counted down, the Logoff session at setting probably has not been achieved, and thus, the test is still running. It is recommended to keep an eye on your machines and wait for them to completely finish before trying to analyze results.

A detailed explanation of the timers can be found in this section on the duration of Login VSI tests.

Workload is trying to print to .XPS/.OXPS

If you see a window like this during a workload before the machine becoming stuck, this is an issue with printer redirection. Installing the Target Setup by LoginVSI should prevent this from occurring, but if it still occurs, follow one of the options below.

-Vmware View: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003626

-GPO: http://technet.microsoft.com/nl-nl/library/cc731963%28v=ws.10%29.aspx

-Spooling: http://en.kioskea.net/faq/2349-enable-disable-the-print-spooling-service

-Removing: Remove printing from the test.

By adding write access to the user or group the popup will not appear.

Office 2010 does not import an Outlook Profile

This issue is most likely being caused by a preconfigured Outlook profile. Microsoft Office 2010 can be installed with an admin file. This admin file is created by the Office Customization Tool (OCT). One of the features of this tool is that it can preconfigure the Outlook profile. This is a problem because VSI uses its own custom profile. This profile uses local PST files so you do not need an exchange account. OCT stores this setting under one of the following registrykeys:

32-bit systems

HKLM\SOFTWARE\Microsoft\Office\<office version>\User Settings\<random guid>\create\software\microsoft\office\<office version>\outlook\setup

64-bit systems

HKLM\SOFTWARE\WOW6432node\Microsoft\Office\<office version>\User Settings\<random guid>\create\software\microsoft\office\<office version>\outlook\setup

Removing this key (the entire setup key) should resolve this issue. The screenshot below is an example of an office 2010 installation on a 64 bit machine.

 

Adobe Reader crashes on an Internal Error on a Remote Desktop Session host

We've received some reports that Adobe Reader might crash on a Remote Desktop Session host if protected mode is enabled. This issue seems to be resolved when disabling protected mode within Adobe Reader. This can be done by setting a registry key. Create a dword value under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\11.0\FeatureLockDown.

• Path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\11.0\FeatureLockDown
• Value name: bProtectedMode
• Value type: REG_DWORD
• Value data: 0

We've not been able to reproduce the issue nor have we been able to verify the solution.

The server is unwilling to process the request

Running the ADsetup powershell script might result in several error messages stating: The server is unwilling to process the request. We have seen this happen in multiple domain forests. The AD setup is ran in domain1 while it is trying to create users in domain2. This problem can be resolved by adding -server domain2 to all AD related commands and all GPO related commands.

Microsoft Outlook displays "You don't have appropriate permission to perform this operation" when trying to create a new email

We have seen this happen when the "prevent users from adding new content to existing PST files" and/or "Prevent users from adding PSTs to Outlook profiles and/or prevent using sharing-Exclusive PSTs" group policies are set.

Disabling these policies have resolved the issue.