Documentation forWeb Performance Monitor

Manage SEUM-User accounts in WPM

As described in the WPM Getting Started Guide, when a WPM Player simulates end user activities by playing back recorded transactions, it uses individual WPM worker processes to perform transaction steps and collect data during playback. Each worker process requires its own SEUM-User account because different processes handle different transaction steps at different times.

In addition to an overview about SEUM-User accounts work, topics in this section include:

By default, the WPM Player on the Orion server includes 2 SEUM-User accounts and WPM Players deployed to remote systems include 7 accounts. You can add up to 15 SEUM-User accounts, if necessary. The recommended limit is 12, based on aspects of the host system such as CPU and RAM.

You can also adjust SEUM-User accounts to make environmental changes, such as adding proxy settings or adjusting permissions. For example, adjust SEUM-User accounts to mimic the authentication users require to access your web application so you can simulate customer traffic. For example, if a step accesses a secured file, the SEUM-User account used for the step requires rights to the file.

Note the following details about SEUM-User accounts:

Here are some additional tips:

  • When using Group Policy Objects (GPOs) in an environment, adjust Local Security Policies to grant permission to Allow log on locally for all SEUM-User accounts on the local system. Otherwise, changes in the user configuration on the local computer will be overwritten with every GPO update.
  • When a GPO is applied, it can block WPM services from using SEUM-User accounts for certain tasks, such as creating WPM worker processes. Pay attention to which GPO is used and modify it for WPM, as necessary.
  • If adding SEUM-Users to the local Administrators group still doesn’t help, set up domain users for playback instead local users.

    The original name for WPM was Synthetic End User Monitor (SEUM), a term that is still used in some directory names and system messages.

Configure SEUM-User account permissions

To perform a transaction step, each WPM worker process requires its own SEUM-User account with the necessary permissions. If playback fails due to permission issues, make sure that all SEUM-User accounts belong to the local Administrators group on the host system.

To set permissions for SEUM-User accounts:

  1. Select Computer Management setting from the system menu, or open Run from the Start button and type: compmgmt.msc
  2. Double-click Local Users and Groups, and double-click Users.
  3. Right-click on SEUM-User-1 and click Properties.
  4. Select the Member Of tab.
  5. Click Add, and enter the local Administrator's group name for this user. To find all available groups, click Advanced > Find now, and then select the Administrators group and click OK.
  6. Press OK twice.
  7. Repeat steps 3—6 for each SEUM-User, and then click OK.
  8. Restart the SolarWinds WPM Playback Player Service and SolarWinds WPM Playback Player Proxy services in the Orion Service Manager.

Add SEUM-User accounts

The number of SEUM-User accounts must equal the number of WPM worker processes used by WPM Player services, and that value can vary for each remote system that hosts WPM. This is required because each worker process handles different transactions at different times.

WPM supports up to 15 SEUM-User accounts, but a limit of 12 is recommended.

SolarWinds recommends backing up WPM Player configuration (*.config) files before proceeding.

To add a SEUM-User account:

  1. Use the Orion Service Manager to stop the SolarWinds WPM Playback Player service.
  2. Go to C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player (or wherever the WPM Player is installed).
  3. Create a backup copy of the SolarWinds.SEUM.Agent.Service.exe.config file.
  4. Open the following file in a text editor: SolarWinds.SEUM.Agent.Service.exe.config
  5. Search for numWorkerProcesses in the </configSection> and edit the value.
  6. Save your changes and start the SolarWinds WPM Playback Player service.
  7. Select Computer Management from the system menu, or open Run from the Start menu and type: compmgmt.msc.
  8. In the Computer Management window, navigate to Local Users and Groups > Users to display the number of SEUM-Users and confirm your changes.
  9. Make sure all SEUM-User accounts belong to the local Administrator group.

  10. Repeat these steps for each WPM Player if you have multiple Transaction Locations.

Set passwords for SEUM-User accounts

To specify a password for a SEUM-User account:

  1. Locate the AgentSettings.dat file in the default directory, c:\Program Files (x86)\SolarWinds\SEUM\Data.
  2. Rename the file from AgentSettings.dat to AgentSettings.bak.
  3. After creating a backup copy, delete the original AgentSettings.dat file.
  4. Go to c:\Program Files (x86)\SolarWinds\Orion\SEUM\Player and create a backup copy of the SolarWinds.SEUM.Agent.Service.exe.config file.
  5. Open the SolarWinds.SEUM.Agent.Service.exe.config file in a text editor.
  6. Locate the workerUserPasswordOverride attribute in the <agentConfiguration> tag.
  7. For example, <agentConfiguration workerUserPasswordOverride="Your_Password"/>

  8. Use the Orion Service Manager to restart the WPM Player services.