Documentation forWeb Performance Monitor

Manage SEUM-User accounts in WPM

As described in the How WPM works, 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.

This section also explains how to:

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, customize a SEUM-User account to mimic the authentication a typical user requires to access a web application so you can simulate customer traffic. For a transaction with a step that accesses a secured file, you can adjust a SEUM-User account to provide rights to access the file.

Note the following details about SEUM-User accounts:

Here are some additional tips:

  • If using Group Policy Objects (GPOs), 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 are overwritten with every GPO update.
  • GPOs 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 you cannot add SEUM-Users to the local Administrators group, set up domain users for playback instead of local users.

    The original name for WPM was Synthetic End User Monitor (SEUM), a term that remains 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. Log into the system that hosts the WPM Player.
  2. Open the Computer Management tool from the Windows Start menu.
  3. Double-click Local Users and Groups, and then double-click Users.
  4. Right-click SEUM-User-1, and then click Properties.
  5. Switch to the Member Of tab, and then click Add.
  6. Type 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.
  7. Press OK twice.
  8. Repeat steps 3—6 for each SEUM-User, and then click OK.
  9. 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 the SolarWinds WPM Player Playback service, a value that can vary for each remote system that hosts WPM. This enables WPM to run worker processes that play different transaction steps at different times.

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

(Recommended) Back up WPM Player configuration (*.config) files before proceeding.

To add a SEUM-User account:

  1. Log into the system that hosts the WPM Player.
  2. Use the Orion Service Manager to stop the SolarWinds WPM Playback Player service.
  3. Navigate to the following default folder: C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player
  4. Create a backup copy of the SolarWinds.SEUM.Agent.Service.exe.config file.
  5. In a text editor:
    1. Open SolarWinds.SEUM.Agent.Service.exe.config
    2. Search for numWorkerProcesses in the </configSection> and edit the value.
    3. Save changes.
  6. Start the SolarWinds WPM Playback Player service.
  7. Open the Computer Management tool from the Windows Start menu.
  8. Double-click Local Users and Groups > Users, and then confirm the number of SEUM-Users.
  9. Make sure all SEUM-User accounts belong to the local Administrator group.

  10. Repeat these steps for each WPM Player that hosts multiple transaction locations.

Set passwords for SEUM-User accounts

In WPM 2020.2.5 and earlier, changing passwords for SEUM-User accounts on remote systems often resulted in the loss of SEUM-User configuration data. The deprecated process involved several steps, including:

  • Remove SEUM-User accounts in the Computer Management tool,
  • Delete C:\Users\SEUM-Users-* folders,
  • Disable the WPM Player service,
  • Restart the remote server,
  • Add workerUserPasswordOverride to SolarWinds.SEUM.Agent.Service.exe.config, and
  • Enable the WPM Player service.

To set passwords for SEUM-User accounts in WPM 2020.2.6 and later:

  1. Log into the remote system that hosts the WPM Player.
  2. Navigate to c:\Program Files (x86)\SolarWinds\SEUM\Data.
  3. Rename the AgentSettings.dat file to AgentSettings.bak to create a backup.
  4. Delete the original AgentSettings.dat file.
  5. Navigate to c:\Program Files (x86)\SolarWinds\Orion\SEUM\Player.
  6. Rename SolarWinds.SEUM.Agent.Service.exe.config to SolarWinds.SEUM.Agent.Service.exe.bak.
  7. In a text editor:
    1. Open the original SolarWinds.SEUM.Agent.Service.exe.config file and locate the <agentConfiguration> section.
    2. Edit the workerUserPasswordOverride attribute to add a password, as shown in this example:
      <agentConfiguration workerUserPasswordOverride="Your_Password"/>
    3. Save your changes.
  8. Use the Orion Service Manager to restart WPM Player services.

The value for the workerUserPasswordOverride attribute is stored in cleartext format. When finished setting passwords, SolarWinds recommends removing the password value from SolarWinds.SEUM.Agent.Service.exe.config.