- Overview
- Login Enterprise Virtual Appliance
- Login Enterprise Launcher machine
- Digital Workspace
- Connectivity and permissions
Overview
This article 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 the Architecture overview.
The information in this article is relevant if you have a license to use the appliance.
- For information on the Login Enterprise licensing, see the License.
- For the third-party licenses, see the Third-party Licenses.
- If you need a license file, request one here.
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.
Hypervisor
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) | 6.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 |
The guest OS type in the OVA template is "debian9_64Guest" and the hardware level version is 13. It is to maintain compatibility with ESXi 6.5 and newer. OVA has VM tools installed, so once the VM is deployed from the OVA, the VM tool will automatically change the guest OS type to the highest version supported by the ESXi host.
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 |
100GB |
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.
Certificates
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 in 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 | |
IGEL | |
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.
Windows
- Microsoft .NET Framework 4.8 or higher
- Citrix Receiver / Citrix Workspace
- VMware Horizon Client
Linux
- Curl
- XDOTool
- OpenSSL
- Free RDP
- Citrix Receiver / Citrix Workspace
- VMware Horizon Client
Antivirus and app blocker exclusions
To ensure optimal performance and prevent conflicts, certain files and processes need to be excluded from antivirus scans and app blocking. Add the following exclusions to your antivirus or app blocker to ensure the Login Enterprise runs correctly.
Launcher Machine
- Enterprise Launcher software
- C:\Program Files\Login VSI\Login Enterprise Launcher\LoginEnterprise.Launcher.UI.exe
- Universal Web Connector
- C:\Program Files\Login VSI\Universal Web Connector\UniversalWebConnector.exe
Target VM
- Login Executable
- LoginPI.Logon.exe
- The path will depend on the policy/configuration of the environment
- LoginPI.Logon.exe
- Enterprise engine
- %TEMP%\LoginPI\Engine\LoginPI.Engine.exe
- Login Enterprise EUX Applications
-
%TEMP%\LoginEnterprise\EuxApp
-
AppSpeed.exe
-
CompressionSpeed.exe
-
CpuSpeed.exe
-
DiskSpeed.exe
-
eux2023.zip
-
-
- Login Enterprise EUX work files
-
My Documents\eux2023
-
%LOCALAPPDATA%\eux2023
-
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 Launchers overview and best practices, see the Launchers: overview and best practices.
- To learn about the Login Enterprise Windows Launcher setup, configuration, maintenance, and more, see the Login Enterprise Windows Launcher.
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 |
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.8 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. For more information, see the diagram and the table below:
Source |
Target |
Port Number |
Protocol |
Launcher Machines |
Target Machines |
3389 |
RDP |
Launcher Machines |
Citrix Servers |
80/443 |
HTTP/HTTPS |
Launcher Machines |
Citrix Servers |
1494 |
ICA Sessions |
Launcher Machines |
Horizon Connection Server |
80/443 |
HTTP/HTTPS |
Launcher Machines |
Horizon VDI/Blast |
8443 |
Blast |
Launcher Machines |
Horizon VDI/PCoIP |
4172 |
PCoIP |
Launcher Machines |
Login Enterprise Virtual Appliance |
443 |
Default TCP |
Login Enterprise Virtual Appliance |
Launcher Machines |
443 |
Default TCP |
Login Enterprise Virtual Appliance |
Target Machines |
443 |
Default TCP |
Login Enterprise Virtual Appliance |
AD Server (Optional) |
135, 136, 137, 138, 139, 3268 |
TCP/UDP |
Login Enterprise Virtual Appliance |
AD Server (Optional) |
445 |
TCP |
Launcher Machines |
AD Server (Optional) |
135, 136, 137, 138, 139, 3268 |
TCP/UDP |
Launcher Machines |
AD Server (Optional) |
445 |
TCP |
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
For more information on the Virtual Users, see the Accounts.
If you have questions or need information on specific configuration requirements, feel free to get in touch with us at support@loginvsi.com.