Login Enterprise - Requirements


This guide outlines the requirements for a successful implementation of the Login Enterprise virtual appliance. To learn how the different components of the Login Enterprise interact with each other, see Architecture overview.

The information in this guide is relevant if you have a license to use the appliance.

Login Enterprise virtual appliance

The Login Enterprise virtual appliance is delivered as a fully configured virtual machine. This virtual machine is provided as an OVA or VHD(X) file.


A hypervisor, also known as a virtual machine monitor (VMM), is a software or hardware component that allows multiple operating systems to run on a single physical machine. It facilitates the creation and management of virtual machines, which are isolated instances of an operating system running on a host system.

For optimal performance, Login Enterprise is compatible with the following hypervisors:

Hypervisor Versions File
VMware vSphere Hypervisor (ESXI) 5.5 to 7.0 OVA file
Microsoft SCVMM (Hyper-V) Server 2012 and greater VHDX file
Citrix Hypervisor 8.2 OVA file
Microsoft Azure - VHD file

Login Enterprise VMWare and Citrix OVA specify virtual hardware version 13. Systems compatible with that should support the appliance.

To learn more about the installation of the Login Enterprise, see Getting started.

Hardware requirements

For the Login Enterprise appliance to perform its functions accurately, you need to configure the correct hardware requirements.

To eliminate external performance influences, we recommend NOT configuring the appliance on a heavily used hypervisor.

Configuration CPU Memory Disk
Recommended 4(v)CPU 8GB RAM


With the recommended configuration, Login Enterprise supports a maximum of 2000 concurrent Load test users. For Continuous tests, Login Enterprise supports a maximum of 250 concurrent users, which also requires an External Database.

For more information on the test scalability, see Login Enterprise scalability tests.

External SQL database (optional)

By default, Login Enterprise is delivered using an internal database. However, starting from Login Enterprise 4.3, you have an option to add an external SQL database.

We recommend using the External Database option when you plan to run tests with more than 75 Concurrent Continuous Test users, or more than 1000 concurrent Load test users.

For information on the external database requirements and configurations, see External SQL Database.


Deploying a certificate is a common practice for enhancing the security and trustworthiness of a product. By default, Login Enterprise is deployed using a self-signed certificate. A best practice is to employ your own certificate. To learn how to manage your certificates for Login Enterprise, see Managing Certificates.

Login Enterprise Launcher machine

The Login Enterprise Launcher machine is used to initiate sessions to the target environment. The machine must be a separate virtual or physical machine.

A Launcher has a maximum capacity of 30 concurrent sessions. If you use custom connectors, the maximum capacity may vary. Additionally, the launcher needs to run in an interactive session to ensure that the appropriate client software can be executed, and graphic content from the protocol is displayed.

For more information on connectors and connection configurations, see Connectors and Connection Configurations.

Operating systems

To run the Launcher software, Login Enterprise is compatible with the following Launcher operating systems:

OS Vendor Versions

Windows 10 and greater

Windows Server 2016 and greater




Debian Debian 10
Ubuntu Ubuntu 20.04 LTS
Fedora Fedora 33

Software requirements

To ensure a Launcher is working accurately, the Launcher needs to have certain software available on it. To connect to the Test platform, all Launchers need a respective vendor-specific connector.


  • Microsoft .NET Framework 4.6.1 or higher
  • Citrix Receiver / Citrix Workspace
  • VMware Horizon Client


  • Curl
  • XDOTool
  • OpenSSL
  • Free RDP
  • Citrix Receiver / Citrix Workspace
  • VMware Horizon Client

Hardware requirements

For optimal functionality of Launchers, you need to configure the minimum hardware requirements. The following specifications represent the minimum requirements applicable to machines running Windows, Linux, and Azure environments:

Configuration CPU Memory Disk
Minimum 2(v)CPU 4GB RAM 1GB free space

For information on best practices for launcher configurations, see Login Enterprise Launcher Best Practices.

Digital Workspace

The Digital Workspace is a virtual or physical machine that you need to have if you want to perform a Test.

Operating systems

To run the target environment software, Login Enterprise is compatible with the following operating systems:

OS Vendor Versions

Windows 10 and greater

Windows Server 2016 and greater

Software requirements

To ensure the target environment is working accurately, you need to have certain software available on the platform.

  • Microsoft .NET Framework 4.6.1 or higher

Connectivity and permissions

For all the Login Enterprise components to work accurately, there are a few additional requirements. They are as follows:

HTTPS configuration (port 443)

The Login Enterprise appliance must be reachable by the Login Enterprise Launcher and the Digital Workspace via HTTPS traffic, i.e. port 443. 

Active Directory (AD) authentication

To use your organization’s active directory credentials (UPN) to authenticate and access the appliance, you need to configure AD Authentication. To learn more about Active Directory Authentication, see Configuring Active Directory Authentication.

Launcher connectivity

The Launcher must have HTTPS (port 443) access to the Login Enterprise appliance. Additionally, it requires access to the connection broker of your vendor when connecting to a remote machine. That is, if you choose a Citrix Virtual Apps and Desktops deployment, the Launcher must be able to reach the StoreFront server.

Virtual users

The virtual users that you’ve configured for Login Enterprise must be able to:

  • Log in to the Digital Workspace
  • Run the logon script 
  • Connect to the Login Enterprise appliance through the 443 (HTTPS) port
  • Have full access to the users %temp% directory
  • Be able to initiate and have the required licenses for the applications to be tested through automation, including Office 365 licenses

In certain scenarios, you might need to implement specific exclusions for successful automation. For more information, see Antivirus and App Blocker exclusions.

If you have questions or need information on specific configuration requirements, feel free to get in touch with us at support@loginvsi.com.