Symptom

There isn't access to the Active Directory environment in order to setup Login VSI Launcher user logon script, either manually by Active Directory administrators or by our AD Setup Script.

Note setting the Launcher logon script is not necessary, but recommend for ease of use. That is, the launcher logon script can make getting the launchers ready before each test easier, so the Launcher Agent (agent.exe) doesn't have to be manually ran each time off of the VSIserver host.

Cause 

Sometimes Active Directory administrators and internal security policy disallow logon scripts to be configured for users in the AD.

Resolution

There are different ways other than user configuration in the Active Directory that will result in the logon script running.

Only one line is needed to call the Launcher logon script. The following example is for if the logon script is at its default path:

CALL "\\{VSIserver host}\{Login VSI share}\_vsi_binaries\launcher\agent.exe"

This could be used in a batch file. 

Some places where this script or functionality can reside are:

• In the run/runonce registry path on the Launcher host(s)
  • Please see this Microsoft doc for more information
• The script can be called by a Windows policy
  • Please see this Microsoft support article for more information
• The script can be placed in the Startup Windows directory, in the Start Menu
  • A shortcut to get here is opening the Windows Run dialog box and running "shell:common startup" in it
• The logon script can be invoked by a 3rd party profile, workspace, or user experience manager
• Additionally, the Launcher host(s) could have the Windows Auto-logon policy enabled, so when the Launcher host(s) are turned on they automatically connect with the configured user, and the logon script could be ran automatically by one of the aforementioned methods
  • Please reference this Microsoft support article

Note: it could also be convenient spinning-up a Launcher-specific user in AD. Meaning, if internal security allows for this, to create an ad hoc user that is specifically just used to log into Login VSI launcher hosts and run the Launcher Agent app. This can make maintenance and implementation easier.

Properties

Applies to

Login VSI 4.x

See also

• Creating the Login VSI AD Setup Script
• Login VSI Launchers
• Login VSI Launcher