Description

The Logon Components are crucial to the functionality of Login Enterprise. This part makes sure the software starts as soon as the users logs in. Navigate to the "Accounts" tab in Login Enterprise to download either of these components.

The logon component must run when a Login Enterprise Virtual User logs into the desktop. Therefore, it must be located somewhere that is accessible by the virtual user when it logs on to the system. There are multiple ways to do this. You can either run the component in the user properties for the AD User Object or in the AD Group Policy, or you can run it via UEM tooling, such as RES Workspace Manager or AppSense.

Login Enterprise has two options for starting the virtual user within the Target session.  The preferred option is the Logon Executable.

• Logon Executable
• Logon Script

Logon Executable

IMPORTANT:If you are using Login PI 3.6 or lower please contact support to get access to the logon app. 

IMPORTANT: The Logon Executable does not support server 2008 R2, Windows 7 and older versions of windows.

Once the Logon Executable has been downloaded and extracted you can implement it. All we require is that the LoginPI.Logon.exe is executed with a single command-line parameter, the URL of your Login Enterprise environment. See example below:

.\LoginPI.Logon.exe https://p05-appliance.play.loginvsi.com 

Note the lack of forward slash character after the base URL string.

You can implement this as the logon script command and place the executable on a location that is accessible by all Login Enterprise users. Or you can create your own logon script with this command that is then executed by your preferred setup. 

Desktop Connection

NOTE: If you are using the Desktop Connector for Application or Continuous tests there is one exception on the command-line parameter. Starting from versions 4.4.X The test name needs to be added and the command will look like this:

.\LoginPI.Logon.exe https://p05-appliance.play.loginvsi.com "Test Desktop"

If you are on a version below 4.4.X you will need to add the guid at the end of the command line parameters as shown in the example below:

.\LoginPI.Logon.exe https://p05-appliance.play.loginvsi.com ebdfa18b-772b-4423-8069-5211c7a62688

The GUID at the end of this command is the unique ID of the environment you have configured with the desktop connector. The easiest way of finding out the GUID of the environment is opening the environment configuration page and selecting the environment. In the URL bar of your browser you can see the ID at the end of the URL.

Note: Please be aware that if your company uses Windows 10, there will be a short delay before the logon script starts running. To speed up the process Microsoft has released a fix for this click on this link.

Logon Script

The Logon script is meant to be used in older environments that the Logon Executable does not support. To use the Logon Script, download it and attach it to the user. There are multiple ways to do this. You can either run the component in the user properties for the AD User Object or in the AD Group Policy, or you can run it via UEM tooling, such as RES Workspace Manager or AppSense.

NOTE: The Logon Script uses Power-shell. Your test users must be allowed to run this in power-shell's full language mode. For more information about what is needed for the Logon Script, take a look at the following article https://support.loginvsi.com/hc/en-us/articles/360006168159-Antivirus-and-App-Blocker-exclusions

Desktop Connection

When using Login PI 3.6 or lower the logonscript for the desktop connector can be found in the Configuration of the environment under "Schedule" There is a download button at the right where you can download the Logonscript.