Architectural Overview

Login Enterprise Components

Login Enterprise consist of two components which are specific to our deployment, and a "Target"

Environment Overview

 Illustration 1. Login Enterprise deployment components.  For more detail click here: Link.

Virtual Appliance

This is where the binaries for management of Login Enterprise exist.  This is self sustaining.  Console or SSH access for original configuration and maintenance.  You can download the OVA, VHD or VHDX from: Login Enterprise Download

Once an IP address and host name 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 end point.  This is representative of your real users end point. 

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 upon it's 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.

See our launcher best practices deployment guide from: Login Enterprise Launcher Deployment Guide


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: 

  • Pre-production
    • 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.
  • Production
    • Resource Group - This profile can run against a specific resource group within an Microsoft RDSH, Citrix or Horizon deployment.
    • Thin Client / IGEL / Linux - End user telemetry data can be captured based upon a variety of end points 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 comparsion.  This has been historically used for comparing fat clients and thin clients and provide a uniform experience across end points.
    • 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.