Login PI Requirements

From Login VSI Documentation
Jump to: navigation, search

Main components of Login PI:

  • Login PI Server
  • Login PI Launcher Machine
  • Target Environment

Note: We previously stated that we support Windows Server 2008 R2 for the Login PI Server. This is no longer the case, as we only support 2008 R2 with Login PI v1.5. All future releases will require Windows Server 2012 or higher. Other PI components (launcher, engine) should run on Windows Server 2008 R2. However, in future we will only support the platforms that Microsoft currently provides mainstream support for.

Active Directory

Within the Active Directory you will need to create the test users and organizational units. The test users will get the Login PI logon script applied. Login PI creates the test users, organizational units and logon script via our PowerShell script generator. The creation of the users, organizational units and logon script can also be manually performed.

Browser Compatibility

The Login PI Dashboard performs best in Google Chrome but also functions in both Internet Explorer and Mozilla Firefox.

Database Compatibility

Login PI works in combination with Microsoft SQL Server (we recommend using version 2012 onward). When installing the application for the first time, the system will ask for User credentials that must have Database Admin rights. This can be either a Local Windows/Domain Authenticated user or an MS SQL Server security user. The installation and configuration of Login PI will use these credentials once to create the database and authorize the Login PI computer object to read/write/modify the Login PI Database. If you are using a Local Windows/Domain Authenticated user account to initialize the database, please make sure the interactive logon permission is enabled in the Windows OS settings on the Login PI Server. If this goes against company policy, then please use an SQL user account when initializing the database.

Important: The Database Administrator must create this user before installation, which can either have Windows or MS SQL Server security, but must have administration rights. If you try to initially install Login PI with a non-Admin user you will receive an error message.

Note: Please be aware that the Microsoft SQL Express database has a size limit of 10GB, which Login PI will consume with data in approximately six months.

Login PI Server

The Login PI Server handles all the data input/output. On the Login PI Server you install the server components. After installing these components, you must connect the Login PI Server to a SQL database. This database can be hosted on the same server. It is also possible to use an instance on a separate machine.

Hardware

  • 2(v)CPUs
  • 4GB RAM
  • Depending on the amount of data collected, the Login PI Server needs at least 1GB of free space

Software

  • Fully updated Windows Server machine (especially KB2999226 and KB2919355 for 2012 R2)
  • Microsoft Windows Server 2012, 2012 R2 and 2016
  • Microsoft .NET Framework 4.5.2
  • Microsoft SQL 2008, 2012, 2014, or 2016 Express, Standard, or Enterprise
  • Valid Login PI license file

Connections

  • Connectivity between the Login PI Launcher Machine and the target environment over a dedicated port (Default is port 8080)
  • To create the SQL database and SQL login, we require a user account that contains both dbcreator and securityadmin server-level-roles
    • We also use this user account to inject the computer account with the db_owner database-level role into the system, required to maintain the SQL database itself

Login PI Launcher Machine

The Login PI Launcher Machine is used to initiate sessions to the target environment. It can be installed on the Login PI Server.

Software

  • Windows 7 and upwards (64-bit)
  • Windows Server 2012 and upwards
  • Microsoft .NET Framework 4.5.2
  • Lock screen turned off
  • Screensaver turned off
  • When testing Citrix XenApp/XenDesktop, the Citrix Receiver is required
    • Note: Latency metrics data capture is only supported by XenApp/XenDesktop 7.x and higher
  • When testing VMware Horizon, the Horizon Client is required
  • To capture latency metrics when testing Microsoft RDP, RDP version 8.0 or higher is required
    • Note: Windows 7 does not support the capture of latency metrics with the RDP protocol

Hardware

  • 2(v)CPUs
  • 4GB RAM
  • 1GB free space

Note: If you are utilizing only one virtual user, then the minimum requirements for a Login PI Launcher = 1(v)CPU / 1GB RAM.

Connections

The Login PI Launcher Machine has to have access to the target environment and connectivity to the Login PI Server over a dedicated port (default = 8080).

Target Environment

The target environment is the environment you want to test.

Software

  • Windows-based operating system
  • Microsoft .NET Framework 3.5

Connections

The test user(s) must be able to:

  • Log on to the target environment
  • Run the logon script
  • Have connectivity to the Login PI Server over a dedicated port (Default is port 8080)
  • Access the %temp% folder