Login VSI AD Test Accounts

From Login VSI Documentation
Jump to: navigation, search

If you are not allowed to run the automated Login VSI user creation PowerShell scripts within your environment, or do not want to, then it’s also possible to manually create test accounts using the steps outlined below (these steps describe every object normally created by the automated creation process).

During the automated creation process, Login VSI will create the following Organizational Unit (OU) structure, please note that the OU structure is only there to provide you with an overview (it is not required for Login VSI to work).

OU Structure

  • <Select a root OU within your domain>
  • LoginVSI
    • User
      • Launcher
      • Target
    • Computers

Users

The automated AD preparation will create two types of users:

1. So called target users. These users will log on to your target environment (the environment that you want to test). The users have a logon script specified that will start the test once the users log on. This logon script is by default placed in the sysvol folder of your domain ([file://yourdomain/SYSVOL/YourDomain/scripts/V4-VSI_Logon.cmd \\YourDomain\SYSVOL\YourDomain\scripts\V4-VSI_Logon.cmd]) although the script can be placed anywhere. More details on the logon script can be found below.

Note: You can create as many user accounts as you'd like to test with.

2. A single launcher user. This user is used in the launcher workflow. It is a user that will log on to the launcher machines (the machines that initiate the test sessions). Once it logs on, the user logon script will make sure that the launcher agent is started. This user also uses a logon script in the sysvol folder. More details on the logon script can be found below. This is just a single user account.

Create a Group

Every user mentioned above will be a member of a group. This group allows you to easily set permissions or allow access to resources. The group that is created is called LoginVSI. This group is also referenced in the (optional) Target Setup. If you choose to create a group that is not named LoginVSI, then please remember to unmark the checkbox called Add Login VSI group to local RDP group in the Target Setup.

Import and Link GPOs

The automated AD preparation imports and links backups of group policy objects. These are intended to make the implementation easier. The VSI-system object is linked to the Computers OU mentioned above while the VSI-user object is linked to the Target OU mentioned above.

The most important settings made in the GPOs are:

  • Logon Synchronously
    • Allows the VSI script to complete before the users are logged on, preventing timing issues
  • Disable User Account Control (UAC)
    • Makes sure that UAC prompts will not interfere with the actual test runs

The backups can be found in [file://server/VSIshare/_VSI_Binaries/AD Setup/ \\Server\VSIshare\_VSI_Binaries\AD Setup\]

If you want to manually import the pre-built Login VSI GPOs, then please execute the steps below. Please note that the Login VSI Policy objects are split up into User and System settings.

Description

Screenshot

Log on to a machine that is configured as a domain controller and start the “Group Policy Management Console” (GPMC.msc).

2013-11-01 06 48 00-Group Policy Management.png

Browse to the OU containing the Login VSI test computer objects. Right click and select “Create a GPO in this domain, and link it here”.

Comp-create-gpo.png

The system asks to provide a name for the newly created GPO. Use (for example): LoginVSI-System-M.

2013-11-01 06 48 15-New GPO.png

In the GPMC tree browse to the “Group policy objects” container. Right click the newly created GPO and select “Import settings”.

2013-11-01 06 49 26-Import Settings Wizard.png

A wizard will now guide you through the steps required to import the predefined settings. It also asks to create a backup of the policy object. If you just created this object there is no need to backup as its empty. If you are using an existing GPO make sure a backup is created.

2013-11-01 06 49 28-Import Settings Wizard.png

Open the location of your VSIshare and browse to the folder: \\Server\VSIshare\_VSI_Binaries\AD Setup\VSI System\ and click “Next”.

2013-11-01 06 49 59-Browse For Folder.png

Select the “VSI-System-V4” GPO backup and click “Next”

2013-11-01 06 50 10-Import Settings Wizard.png

Complete the steps in the wizard to finish the import process.

2013-11-01 06 50 19-Import Settings Wizard.png

Complete the steps in the wizard to finish the import process.

2013-11-01 06 50 21-Import Settings Wizard.png

Check if the “VSI-System-M” policy object now contains the imported settings.

Imported settings.PNG

Browse to the OU containing the Login VSI test user objects. Right click and select “Create a GPO in this domain, and link it here”.

User-create-gpo.png

The system asks you to provide a name for the newly created GPO. Use (for example): LoginVSI-User-M.

2013-11-01 06 52 56-New GPO.png

In the GPMC tree browse to the “Group policy objects” container. Right click the newly created GPO and select “Import Settings”.

2013-11-01 06 49 26-Import Settings Wizard.png

A wizard will now guide you through the steps required to import the predefined settings. It also asks to create a backup of the policy object. If you just created this object there is no need to backup as its empty. If you are using an existing GPO make sure a backup is created.

2013-11-01 06 49 28-Import Settings Wizard.png

Browse to the location of your VSIshare and browse to the folder: \\Server\VSIshare\_VSI_Binaries\AD Setup\VSI User and click “Next”.

2013-11-01 06 53 14-Browse For Folder.png

Select the “VSI-User-V4” GPO backup and click “Next”.

2013-11-01 06 53 17-Import Settings Wizard.png

Complete the steps in the wizard to finish the import process.

2013-11-01 06 53 19-Import Settings Wizard.png

Complete the steps in the wizard to finish the import process.

2013-11-01 06 53 21-Import Settings Wizard.png

Check if the “VSI-User-M” policy object now contains the imported settings.

Imported settings user.PNG

Create the Logon Scripts

The logon scripts used by the test user and the launcher accounts are, by default, created in the Netlogon folder. These scripts are easy to create as they only contain one line of code:

Description

Screenshot

Log on to a machine that is configured as a domain controller and start Notepad with administrative privileges. These steps will describe how to add the Login VSI Engine to a User logon script that will be executed at the target machines.

2013-11-01 06 54 26-Untitled - Notepad.png

Within Notepad go to File > Open and browse to the Netlogon folder within your domain. Typically found at:

\\Nameofyourdomain.TLD\Netlogon

Make sure to set the File extension filter to “All files *.*”.

2013-11-01 07 00 31-Open.png

Within the Netlogon folder right click to create a new TXT file.

2013-11-01 07 01 03-Open.png

After creation rename this file to: V4-VSI-Logon.cmd and open it for editing.

2013-11-01 07 01 33-Open.png

Add the following line to the file:


CALL \\server\VSIshare\_VSI_Binaries\Target\Logon.cmd


Make sure to replace \\server\VSIshare with the actual path to the VSIshare within your environment!

Save and close the file.

2013-11-01 07 01 11-V4-VSI Logon.cmd - Notepad.png



Description

Screenshot

Log on to a machine that’s configured as a domain controller and start Notepad with administrative privileges. These steps will describe how to add the Login VSI engine to a User logon script that will be executed at the launcher machines.

2013-11-01 06 54 26-Untitled - Notepad.png

Within Notepad go to File > Open and browse to the Netlogon folder within your domain. Typically found at:

\\Nameofyourdomain.TLD\Netlogon

Make sure to set the File extension filter to “All files *.*”.

2013-11-01 07 01 33-Open.png

Within the Netlogon folder right click to create a new Text Document.

2013-11-01 07 01 39-Open.png

After creation rename this file to: V4-VSI-Launcher.cmd. Open the created file to edit.

2013-11-01 07 01 39-Open.png

Add the following line to the file:

CALL "\\server\VSIshare\_VSI_Binaries\Launcher\Agent.exe"

Make sure to replace \\server\VSIshare with the actual path to the VSIshare within your environment.

Save and close the file.

2013-11-01 07 01 42-V4-VSI Launcher.cmd - Notepad.png