Hardware/Software Requirements

This page is dedicated to supply customers with the recommendations and requirements of Login VSI. It is highly recommended to follow these recommendations and requirements to ensure that Login VSI works properly in your environment. If these are not met, it is possible that some functions/features will not work as designed.

You can also reference this guide: Login-VSI-System-Requirements.pdf (loginvsi.com)

Launcher Machine

For every 25 (1000 for DDC) sessions that has been configured a launcher has to be deployed. This can either be a physical machine or virtual machine. For each different connector a different amount of sessions is recommended:

• RDP - 25 sessions per Launcher
• XenApp - 25 sessions per Launcher
• XenDesktop - 25 sessions per Launcher
• VMware Horizon View - 25 sessions per Launcher
• DDC (a protocoll-less connector) - 1000 sessions per Launcher

The machine needs the following minimum specifications:

Hardware

• 2(v)CPUs
• 4GB RAM

Software

• Windows-based OS
• Microsoft .NET Framework 4.5.2
• Microsoft .NET Framework 3.5
• When testing Microsoft RDS, you must also install the Microsoft RDS Client as well, LoginVSI supports RDP version 8.1 and higher
• When testing Citrix XenApp/XenDesktop, the Citrix Receiver must be installed in the default location (Program Files\Citrix\ICA Client)
• When testing VMware Horizon View the Horizon Client must be installed
• Disable Windows Firewall to make sure this does not cause any issues
• Install Adobe Flash Player (latest version) when using Flash re-direction

Connections

• Connection to the VSIshare (SMB/UNC)
• Connection to the Target Environment, make sure you can connect to a VM using the Client used for the environment
• Connection to the AD to make sure the launcher user can actually log in to the launcher machine

VSIshare Dataserver

This is the central point of the VSI infrastructure. It functions by default as a file/web server and is the place where Login VSI is configured and managed. However, you can place the Dataserver function and Webserver on different machines, if required.

Hardware for around 1000 connections

• 2(v)CPUs
• 4GB RAM
• The server needs 20 gigabyte of free space

Software

• Microsoft .NET Framework 4.5.2
• Microsoft .NET Framework 3.5
• Valid Login VSI license file
• Preferably no anti-virus solutions as this impacts performance or at least exclude the VSI_share to avoid anti-virus issues
• Login VSI only supports Windows Server environments, the (fully) supported operating systems are Windows Server 2008 R2, 2012, 2012 R2 and Server 2016 (64-bit versions)
• Access to a target environment; this is the environment that you want to benchmark/load test
• If Internet Explorer 8 or below is used in the target environment, an IIS web server needs to be set up as well
• RDP 8.1 and higher when using the launcher workflow.

Connections

• Connection to the VMs, there must be a UNC/SMB connection to the VMs so they can access the VSIshare
• Connection to the Launchers, there must be a UNC/SMB connection to the Launchers so the Launchers can access the VSIshare
• Connection to the AD to be able to add the Login VSI group to the VSIshare

VSIshare Permissions

To store the results gathered by Login VSI and to store the binaries to run from a single location a file share in the network is needed. Create a dedicated file share with the following permissions when running a default Login VSI installation. Default groups inherited within your domain do not need to be removed as long as they do not conflict with specified settings below.

Share security:

• Group LoginVSI – Modify
• Group Administrators – Modify

NTFS security:

• Group LoginVSI – Modify
• Group Administrators – Modify

Target Environment / VMs

The target environment or VMs need to have the following applications and hardware specifications available:

Hardware

• 2(v)CPUs - Recommendation Only (depending on Workload)
• 1.5GB RAM - Recommendation Only

Software

• A clean and default installation of Windows, either Client or Server, we support:
  • Server 2008 R2 / Server 2012 / Server 2012 R2 / Server 2016 with the latest service pack
  • Windows 7 / 8(.1) / 10 including full support the most recent Annual windows 10 build 1803
• An activated version of Microsoft Office 2007, 2010, 2013 or 2016. If it is office 2010, please make sure that no Outlook profile is configured through OCT.
  • MS Office is required for the out-of-the-box workloads. If you do not use MS Office, it can be excluded from the out-of-the-box workloads through customization, where you can also add any application you want to test.
• Microsoft .NET Framework 3.5
• Preferably no anti-virus solutions as this impacts performance or at least exclude %temp%\VSI to avoid anti-virus issues.
• Adobe Reader. Any recent version will do. The LoginVSI target setup can install this if needed.
  • This application is used as part of the out-of-the-box workloads, but can be excluded using workload customization.
• Adobe Flash player. Any recent version will do. The LoginVSI target setup can install this if needed.
  • This application is used as part of the out-of-the-box workloads, but can be excluded using workload customization.
• Java. Any recent version will do. The LoginVSI target setup can install this if needed.
  • This application is used as part of the out-of-the-box workloads, but can be excluded using workload customization.
• DoroPDF. The LoginVSI target setup can install this if needed OR we can disable PDF printing.
  • This application is used as part of the out-of-the-box workloads, but can be excluded using workload customization.
• Access to an Active Directory. This can either be a shared AD environment or a dedicated AD. We will be creating OUs, user objects, and a security group. We will also create and link a group policy to the OUs that have been created. This step to use the LoginVSI AD setup is optional though we strongly recommend it.
• Install the latest Microsoft hot fixes from Microsoft Update.
• Only install drivers that are truly required. It is not recommended to install management/security software if you do not intend to analyze their specific performance impact.

For SBC Environments only:

• Enable Remote Desktop Services (Terminal Server)

For all VM solutions

• Install client/agent software

Connections

• Connection to the AD to make sure the users can be used to login to the VM.
• Connection to the VSIShare to make sure the VM can run the Logon Script and receive and send the correct files.

Note: Do not forget to perform any additional system tuning recommended by the vendor.

AD Requirements

In the environment we always recommend using AD. There are a few requirements/recommendations to use AD successfully:

• An installed copy of the Login VSI Management Console
• Windows Server 2008 or higher as Active Directory server
• PowerShell 2.0 and higher
• The Active Directory deployment script should be run on the domain controller/member server logged on as Domain Admin
  • Admin rights are required for both account and group creation, GPO import, and for the NetLogon script to be copied into the domain SysVol directory
• Group Policy Management Console has to be installed on the domain controller/member server
• When choosing a password for the Login VSI users make sure it meets the basic requirements of the password complexity set on your domain

Extra Note

Windows Server 2003 is not recommended as Active Directory server. This is because of GPO Registry imports and some GPO rules that we import that are not supported by the Windows Server 2003 Active Directory. We have a separate Windows Server 2003 Active Directory setup but this does not contain all of the GPOs needed.