WPM domain service accounts

bourlis

2 questions for the collective-

# 1 - For WPM domain service accounts, can I use a naming standard as directed by my organization or am I restricted to using the SEUM-User name?

# 2 - It's unclear to me how use the WPM domain service account for playback functionality.  Does this mean the WPM domain service account needs to be used in the WPM recording?  Is there a hidden setting to over-ride the recording username/password? 

My confusion around Q # 2 stems from the 'Use domain accounts as WPM Player service accounts', where it says:

You can use the SolarWinds WPM Domain Accounts Configuration Tool to set up domain accounts as WPM Player service accounts, for example, to support SSO Authentication allowing successful playbacks of WPM transactions that require it. Otherwise, WPM transactions will fail to execute SSO Authentication due to pulling credential details and permissions from local account that usually lack login details to execute SSO Authentication successfully.

The number of domain accounts required depends on how many worker processes the WPM Player service needs, as cited in the numberOfWorkerProcesses entry in the AgentSettings.dat file, located at C:\ProgramData\SolarWInds\SEUM\Data.

My brain tells me that the username/password information supplied in transaction recordings is completely separate the WPM domain service account, but by gut tells me it is somehow related.

bourlis

Update,

The name does not matter when you use WPM Domain Accounts.  

For a point of reference.  I edited AgentSettings.dot | numberofWorkerProcesses to10 on all WPM players.  Next I enabled domain accounts for playbacks and supplied the service account names and passwords, note that their are 10 accounts listed.  Next I made sure all 10 accounts are in the SEUM-User group and in the server admin group.  Next I worked with our security team and our AD team to ensure the domain SEUM service accounts have the required rights and like that... WPM was up and running with domain service accounts.

One important note, this has to be manually pushed out to all WPM players in your environment.  I'm going to submit an enhancement request that this needs to be centrally managed and replicated across all players.