Architectural overview

Login Enterprise components

Login Enterprise consists of two components specific to our deployment and a "Target". For the environment overview, see the following illustration:

Frame 247.png

Virtual Appliance

This is where the binaries for the management of Login Enterprise exist. This is self-sustaining. Console or SSH access for original configuration and maintenance. 

Once an IP address and hostname have been assigned, you can access the management console from a browser of your choice. Login VSI recommends Google Chrome.


This is where the ICA, RDP, or Horizon client software runs. The protocol will stream from your target environment to this endpoint. This is representative of your real user's endpoint. 

This launcher can be deployed within your data center to understand user experience without the influence of an unstable internet connection.

This launcher can also be deployed remotely, and based on its physical location will help assist administrators in understanding the influence of network connectivity on those real users connecting to your published application or desktop deployment.

To learn about the Login Enterprise Windows Launcher setup, configuration, maintenance, and more, see the Login Enterprise Windows Launcher


This is not a component specific to Login VSI.  However, we utilize this as a generic term to describe some of the following scenarios as illustrated below: 


  • Virtual machine or Instance - This will help you to understand your maximum user experience on an individual VM basis.
  • Host - This will help you to understand the maximum user experience for an individual physical piece of hardware. There could be several VMs running on a single host.
  • Node - This will help you to understand the maximum user experience for a group of hosts.
  • Cluster - This will help you to understand the maximum number of users capable of being supported on multiple nodes.


  • Resource Group - This profile can run against a specific resource group within a Microsoft RDSH, Citrix, or Horizon deployment.
  • Thin Client / IGEL / Linux - End user telemetry data can be captured based on a variety of endpoints you have deployed throughout your environment.
  • Physical - You can configure a profile to run against a physical desktop or laptop. If you are running a workload profile against this, and a virtual desktop you have a single point of comparison.  This has been historically used for comparing fat clients and thin clients and providing a uniform experience across endpoints.
  • Personas - Workflows can be configured to run against your target environment specific to the type of profiles of your employees. For example, Accountant, Call Center Employee, Branch Associate, or Trader.

Additional resources