Requirements

Note: If you require a license file please request one here: Click here!

This document will outline the requirements and their respective supported versions of Login Enterprise. Login Enterprise consists of a number of components that we are going to highlight:

• Login Enterprise Virtual Appliance
• Login Enterprise Launcher Machine
• Target Environment

Login Enterprise Virtual Appliance

The Login Enterprise virtual appliance is delivered as an fully configured virtual machine. This virtual machine is now delivered as a OVA or VHD(X) file. The appliance has pre-configured resource needs. The specifications are:

• Hypervisor
  • VMware ESXi 5.5, 6.0, 6.5, 6.7, 7.0 (using OVA file)
  • Microsoft Hyper-V - Server 2012 R2 and higher (using VHDX file)
  • Citrix XenServer 7.6 (using OVA file)
  • Microsoft Azure (Using the VHD file)
• Processor:
  • Minimum: 2 vCPU
  • High Load Setup: 4 vCPU (4.3.x and up)*
• Memory:
  • Minimum: 4GB RAM
  • High Load Setup: 8GB RAM (4.3.x and up)*
• Storage: The appliance comes with a preconfigured 100GB Hard disk
• Network: Make sure DNS records are updated with Virtual Appliance IP and Hostname and that reverse lookups are configured
  • Communication between the Login Enterprise Virtual Appliance, Launcher Machine and the Target Environment are over the following ports: 443 (HTTPS)
  • For online updating the virtual appliance make sure you are able to connect to our amazon s3 storage.
• External SQL Database The Login Enterprise Virtual Appliance comes pre-configured with its own database. Optionally, it is possible to setup Login PI  Enterprise with an external SQL Database.  Refer to the SQL Server configuration article for more information.
  • We support SQL Server  SQL Server 2016 or higher
  • We require a DB to be created on the database server and the account should be DBO.
  • We require a SQL account not an AD account

Note: We do not support external SQL Databases when using Windows Server 2012R2. Read more.

High Load Setup

With the release of Login Enterprise 4.3.x (and higher) the maximum supported concurrent sessions of 500 has been improved to 2000. However these results have been reached in our lab using the following setup.

Appliance Configuration:

• 4vCPU
• 8GB Ram
• 100GB Storage

Each different use case has its own limitations, deviating from this configuration can result in unwanted load / behavior of the Login Enterprise Appliance:

Note: Make sure the appliance is not configured on a heavily used hypervisor to eliminate external performance influences.

Load Testing Scalability

Load test setup:

• Max 2000 users
• Login Window 50 minutes
• Test duration 4 hours
• 10 Apps with 3 Measurements per app
• 60 seconds between each app start

Continuous Testing Scalability

Continuous Testing test setup:

• Max 250 concurrent sessions
• Max 1 session per 2 seconds
• Max 500 Launchers
• 10 Apps with 3 Measurements per app
• 60 seconds between each app start

Note: With a high number of sessions in Continuous Testing it’s advised to use an external DB and configure data retention to make sure the amount of data doesn’t become to large.

Browser Compatibility

To connect to the Login Enterprise Web Interface to configure tests and review the collected data we require a browser. The list below highlights the browser versions that we support

• Google Chrome
• Mozilla Firefox
• Microsoft Edge (Also the Chromium version)

Active Directory

Within the Active Directory you will need to create the virtual user accounts. The virtual users will need to have the Login Enterprise logon script applied.

Login Enterprise Launcher Machine

The Login Enterprise Launcher Machine is used to initiate sessions to the target environment. It cannot be installed on the Login Enterprise Virtual Appliance.

Software

• Windows 7 and greater (32/64-Bit)

NOTE: If running the launcher on a Windows 7 machine the console version of the launcher must be used. The console version of the launcher is located in the install directory (e.g., C:\Program Files\Login VSI\Login PI 3 Launcher\LoginPI.Launcher.Console.exe)

• Windows server 2012R2 or greater
• Microsoft .NET Framework 4.6.1
• Lock screen turned off
• Screensaver turned off
• When testing Citrix XenApp/XenDesktop, the Citrix Receiver is required
• When testing VMware Horizon, the Horizon Client is required

Hardware

• Processor: 2 vCPU
• Memory: 4GB RAM
• Storage: 1GB free space

Load Testing

Note: Load testing allows 30 sessions per launcher.

Note: Login Enterprise 4.0.x Launcher versions are no longer supported when using Login Enterprise 4.3.x version and higher.

Target Environment

The target environment is the environment you want to test, this can be a VDI Session, XenApp deployment or a normal desktop device. 

Software

• Windows 7 and greater (32-bit and 64-Bit)
• Windows server 2008 R2 or greater (64-bit)
• Microsoft .NET Framework 4.6.1

Permissions and connections

The test user(s) must be able to:

• Log on to the target environment
• Run the logon script
• Connect to the Login Enterprise Appliance on the following ports: 443 (HTTPS)
• Full access to the users %temp% directory
• Be able to start required applications for automation
• More information about file / AV exclusions here

For the automation we support a number of web browsers highlighted below:

• Google Chrome browser
  • Login Enterprise 4.1 and up - Chrome 79 and 80
  • Login Enterprise 4.2 and up - Chrome 81 and 83 Beta
  • Login Enterprise 4.3 and up - Chrome 84 to 86
• Microsoft Edge
  • Login Enterprise 4.2 and up - Edge 83
  • Login Enterprise 4.3 and up - Edge 84 to 86

Remoting Protocol Latency Requirements

Protocols Supported

• Citrix ICA
• VMware Horizon View (Blast Extreme, PCoIP and RDP)
• Microsoft RDP
  • NOTE: Microsoft Hyper-V VDI deployments are not supported 
  • NOTE: Latency metrics for Windows 7 require additional configuration when using RDP. RDP 8.0 is a minimum requirement. See the following link for additional details.

  • Windows Server 2008 R2 and up is supported.

    NOTE: Latency metrics are not supported for Windows Server 2008 R2 using RDP protocol. This applies to Microsoft RDS and VMware Horizon View with RDP. This is because not all RDP 8.0 features are available for this operating system. 

    From Microsoft's website:

    Are the RemoteFX and RDP 8.0 enhancements available for Windows Server 2008 R2 Remote Desktop Session Host? No, the RemoteFX and RDP 8.0 enhancements are not available for Windows Server 2008 R2 Session Host. However, a Windows Server 2008 R2 computer acting as a client access device will still get the Remote Desktop Connection 8.0 client and thereby get the benefits listed in the ‘client access devices’ section earlier.

    Source:                 https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/Remote-Desktop-Protocol-8-0-Update-for-Windows-7-SP1-Enabling-a/ba-p/247534

     

If you are considering evaluation of Login Enterprise, you may want to review the Login Enterprise Readiness Checklist.