Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > Why local administrator accounts are recommended for WPM playback

Why local administrator accounts are recommended for WPM playback

Table of contents

Updated November 7, 2018


This article describes why SEUM-User accounts used for WPM playback should have local administrator permissions. 


  • All WPM versions


As described in the Web Performance Monitor Administrator Guide, the WPM Player uses various 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.

By default, WPM includes seven SEUM-User accounts that you can adjust to make environmental changes, such as adding proxy settings or adjusting permissions. You can add up to 15 SEUM-User accounts to improve processing if you have a large quantity of transactions and transaction locations in an environment. To learn more, see Manage SEUM-User accounts.

Synthetic End User Monitor (SEUM) was the original product name for WPM.

SolarWinds recommends granting local admin privileges to SEUM-User accounts to avoid WPM playback  issues, including:

  • WPM Playback Player Service cannot start WPM Worker process under any SEUM-User account and returns error 0x509.
  • WPM Playback Player Service cannot play transactions that require interactive sessions via Remote Desktop Protocol (RDP) connections. Even if the account is a member of local Remote Desktop Users group, the first user account for the WPM Player (usually SEUM-User-1) is blocked from running the WPM RDPClient process if it doesn't have local admin rights.
  • Custom proxy configuration settings for specific transactions may not work.
  • Other minor errors may appear in WPM Player or Workers logs.

These environment-based issues can also occur for domain accounts that WPM uses for playback; most relate to the lack of permissions for operating system resources required by the Internet Explorer browser, an RDP connection, or another process running for a service for another SEUM-User account. To learn more, see Use domain accounts in Web Performance Monitor.

SolarWinds recommends adding SEUM-Users and/or domain accounts to a local admin group to avoid transaction playback issues and inconsistent results from WPM, but this practice is not required. Depending on your organizational policies, you may need to balance the ability of WPM to run processes for WPM playback with the security of your environment.

For security purposes, your organization should internally review and assess to what extent local admin rights are provided for SEUM-User accounts.

To resolve playback issues related to permission for required resources, add all SEUM-User accounts to the local Administrators group on the Player server. See Set permissions for SEUM-User accounts.

Here are some additional tips:

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

Upon request, SolarWinds Support can provide a list of register keys for which the WPM Recorder and WPM Player need read/write access during recording or playback.

WPM leverages Internet Explorer, which also requires access to specific register keys. However, please note that SolarWinds does not provide direct support for third-party products. Refer to Microsoft documentation to learn about identifying Internet Explorer registry keys.

Additional troubleshooting resources include:


Last modified