Note: the methods referenced herein are not officially supported. However, they're being provided as-is for convenience. The officially supported method is using the AD setup script (link)

Symptom

There isn't access to the Active Directory environment in order to setup target logon scripts, either manually by Active Directory administrators or by our AD Setup Script. (Target meaning the test users on the test platform which are desired to have testing conducted on.) The target logon script being performed by test users at logon, is so test invocation will be automatic.

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 target logon script. The following example is for if the logon script is at its default path:

CALL "\\{VSIserver host}\{Login VSI share}\_vsi_binaries\target\logon.cmd"

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 target machines
  • 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 "all users" 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

Properties

Applies to

Login VSI 4.x

See also

• How the logon phase works
• Logon script for Login VSI
• Creating the Login VSI AD Setup Script