After every upgrade, we have to go to each SW device and put the credentials in for each server.
This is a problem because after the upgrade it tries to create a local user again (which don't have local login) so it starts an HA cycle if we don't quickly catch it or give those local seum users admin access. It seems like a simple thing to have the upgrades ignore the SEUMDomain users configuration file but it doesn't currently happen in our environment.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.