How to install Sprinter for use with Mirroring

Installing Sprinter on Computers for use with Mirroring

Sprinter’s Mirroring feature enables you to run your test on multiple machines simultaneously with different configurations.

A test that is run with Mirroring has a primary machine and secondary machines:

  • Primary machine. The machine on which you manually perform all the user actions in your test.
  • Secondary machines. The machines on which Sprinter replicates your user actions.

You can work with a maximum of five secondary machines in a run with mirroring.

Working with mirroring requires that you have the required number of available HP ALM licenses. The number of licenses you need depends on the number of secondary machines you want to use in your test.

To run a test with Mirroring you configure the secondary machines with the specific configuration whose compatibility you want to test. After you perform each user action on your primary machine, Sprinter replicates that user action on your secondary machines.

You install Sprinter on secondary machines the same way that you install it on your primary machine.

After you install Sprinter on a secondary machine, confirm that the Sprinter Agent icon is displayed in the notification area of the task bar of the secondary machine. If the Sprinter Agent icon is not displayed in the notification area of the task bar, the Sprinter Agent can be launched from the start menu (All Programs > HP Sprinter > Sprinter Agent).

Once Sprinter is installed on a secondary machine and the Agent is running, that machine is available for use in a Mirroring test. You should not run Sprinter on the secondary machine. The Sprinter Agent is configured to run automatically when the machine starts. For details on configuring the Sprinter Agent, see the HP Sprinter User Guide.

‘Capture all images during a test’ in Sprinter settings is greyed out

In Sprinter the option ‘Capture all images during a test’ in Sprinter settings is greyed out.

Note: It is not recommended to enable this setting as uploading images for every step can cause a huge performance penalty. However, if the user chooses to enable this, they can follow the below steps.

In order to check or modify this option, proceed as described below:

1. Log in to the project in ALM/QC

2. Select ‘Tools -> Customize…’ from the menu

3. Select ‘Sprinter’ in the left pane

4. Select the radio button ‘Enable storing all images during a test’

What is the Windows User Account Control (UAC)

The User Account Control (UAC) is a security component that enables users to perform common tasks as non-administrators (called standard users in Windows Vista), and as administrators without having to switch users, log off, or use Run As. User accounts that are members of the local Administrators group run most applications as a standard user. By separating user and administrator functions, UAC helps users move toward using standard user rights by default.

When an administrator logs on to a computer that is running Windows 7 or Windows Vista, the user is assigned two separate access tokens. Access tokens, which contain a user’s group membership and authorization and access control data, are used by the Windows operating system to control what resources and tasks the user can access. The access control model in earlier Windows operating systems did not include any failsafe checks to ensure that users truly wanted to perform a task that required their administrative access token. As a result, malicious software could install on users’ computers without notifying the users. (This is sometimes referred to as a "silent" installation.)

Even more damaging, because the user is an administrator, the malicious software could use the administrator’s access control data to infect core operating system files, and in some instances, become nearly impossible to remove.

The primary difference between a standard user and an administrator is the level of access that the user has over core, protected areas of the computer. Administrators can change the system state, turn off the firewall, configure security policies, install a service or a driver that affects every user on the computer, and install software for the entire computer. Standard users cannot perform these tasks, and they can only install per-user software.

Impact during installation or other tasks

Unlike earlier versions of Windows, when an administrator logs on to a computer running Windows 7 or Windows Vista, the user’s full administrator access token is split into two access tokens: a full administrator access token and a standard user access token. During the logon process, authorization and access control components that identify an administrator are removed, resulting in a standard user access token. The standard user access token is then used to start the desktop, the Explorer.exe process. Because all applications inherit their access control data from the initial launch of the desktop, they all run as a standard user.

After an administrator logs on, the full administrator access token is not invoked until the user attempts to perform an administrative task. When a standard user logs on, only a standard user access token is created. This standard user access token is then used to start the desktop.

That is very important because registering components (products installations, QC/ALM component downloads) as well as other tasks, are not a per-user install, it’s an everyone install, all user profiles access a common mode.

In order to install HP products, for example QuickTest Professional, Service Test, Quality Center, etc or using this installation method user must have administrator rights and disable the UAC.

To temporarily turn off the UAC option, do the following:

  • For Microsoft Windows Vista and Windows Server 2008:

1. Log in as an administrator.

2. From Control Panel, select User Accounts > Change Security Settings, and clear the Use User Account Control (UAC) to help protect your computer check box.

3. Restart the machine, so changes take effect

  • For Microsoft Windows 7 and Windows Server 2008 R2:

1. Log in as an administrator.

2. From the Control Panel, select User Accounts > User Accounts > Change User Account Settings.

3. In the User Account Control Settings window, move the slider to Never notify.

4. Restart the machine, so changes take effect

More information on the User Account Control (UAC) can be found in the following Microsoft document:

http://technet.microsoft.com/en-us/library/cc709691%28WS.10%29.aspx#BKMK_WhatIs

Task impacted by UAC as ON

Most Common

  • Product Installation / Uninstallation
  • Repair or Modify(install/uninstall add-in)
  • Install Patches / Hot-Fixes
  • Every time QC / ALM components must be downloaded.

Others

For client products such as QTP, ST or UFT, there may be other tasks affected, however it is best end-user to check minimum permissions requirements

Internet Explorer, Protected Mode and UAC

When using Internet Explorerto connect and start downloading the client components for Quality Center (QC) / Application Lifecycle Management (ALM) you get the configurations and limitations from Internet Explorer which are different from other applications.

Since the client installation of QC / ALM is not run directly as an isolated application, the UAC is not involved directly, instead of using UAC to restrict write access to securable objects such as processes, files, and registry keys with higher integrity levels we use the Protected Mode feature from Internet Explorer.

When you run the installation from Internet Explorer it is require to disable the Protected Mode or add the URL to the Trusted Sites.

If further information is required on the Protected Mode for Internet Explorer you can check the following link pointing to a Microsoft KB article:

http://msdn.microsoft.com/en-us/library/bb756991.aspx

Sprinter crashes immediately after executing a test in Power Mode

If the name of the logged in user includes spaces, Sprinter fails to close the "SprinterRTE" process at end of a Power Mode test and a violent closing of the process is done (by the "SprinterRTE" process itself) within the first minute after the end of the test execution.

This is due to the fact that "SprinterRTE" process detects that keep-alive messages from "Sprinter" process do not arrive any more raising an error message from the operating system.

Avoid using spaces in the machine user name. If not possible, create a new user not containing spaces in its name to use Sprinter.

Clean uninstall/reinstall Sprinter

Here are the steps for a clean uninstall/reinstall of HP Sprinter:

1. (Sprinter 11.5 and higher) In standalone mode: backup your tests, if such reside under Sprinter’s installation folder.

2. Uninstall Sprinter (Control Panel -> Add Remove Programs/Programs and Features).

3. Go to the install directory of Sprinter.

The default directory is “C:\Program Files\HP\Sprinter“. Note: When working with a 64bits operating system, ensure to locate the above folders under C:\Program Files(x86)\…

4. Delete all the directories under this directory. Note: The above steps can be performed via command line:

rmdir /s /q "C:\Program Files\HP\Sprinter"

IMPORTANT: The following steps relating to HKEY_CURRENT_USER must be performed for each user on a Citrix or Terminal Services environment, and for any user that has run QuickTest Professional)

5. Open the registry editor (Start > Run > type "regedit" > Click "Ok")

6. (If exists) Delete following registry keys (including all the keys and values under it):

Note: When working on a 64bits operating system, the below keys may not exist, instead following key should: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\…

HKEY_CURRENT_USER\Software\Mercury Interactive

HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\

HKEY_CURRENT_USER\Software\Wow6432Node\Hewlett-Packard\Manual Runner

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hewlett-Packard\Manual Runner

7. (If exists) Delete BHOManager.dll in %windir%\system32 folder. For 64bits, is possible to find it under %windir%\SysWOW64 folder

8. (If exists) Delete the following assemblies from the C:\Windows\assembly\ directory:

Mercury.QTP.Agent

Mercury.QTP.CustomServer

Mercury.QTP.WpfAgent

policy.6.5.Mercury.QTP.CustomServer

policy.8.0.Mercury.QTP.Agent

policy.8.0.MngUtils

policy.X.X.Mercury.QTP.WpfAgent (“X” could 9.5 or 10.0. This item may appear repeated, just different version, so delete them all)

9. Delete the following directory and contents under Windows folder (Go to “Start” menu, select “Run”, type “%windir%”, click “Ok”):

C:\Windows\Microsoft.NET\assembly\GAC_32\Mercury.QTP.Agent\

Note: This command may help achieving task: rmdir /s /q %windir%\Microsoft.NET\assembly\GAC_32\Mercury.QTP.Agent

C:\Windows\Microsoft.NET\assembly\GAC_64\Mercury.QTP.Agent\. Note: If 64bits support is enabled

Note: This command may help achieving task: rmdir /s /q %windir%\Microsoft.NET\assembly\GAC_64\Mercury.QTP.Agent

C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Mercury.QTP.WpfAgent

Note: This command may help achieving task: rmdir /s /q %windir%\Microsoft.NET\assembly\GAC_MSIL\Mercury.QTP.WpfAgent

10. Delete/rename the associated application data “Sprinter” directory. (Start -> Run -> type “%appdata%\HP” -> Ok).

Following are command line options:

Delete folder: rmdir /s /q "%appdata%\hp\Sprinter"

Rename/Backup folder: rename "%appdata%\hp\Sprinter” “Sprinter.bak"

11. Reboot the machine (recommended)

12. Install or reinstall Sprinter.