Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

EOC and adding multiple users

I want to start a discussion to see how many Orion’s EOC admin’s are monitoring and how they are handling adding multiple users.

I currently have two networks with redundant EOC servers on each and each EOC monitoring seven Orion’s. Needless to say adding a user is a pain to say the least. Once I get through the ordeal of looking up a user and get them added to EOC I then have to go back and add the credentials for each Orion server for the user or users. Now multiply that by for each EOC server and you can join me in the rubber cage.

I know EOC is still in its infancy but this really needs to be addressed.

I would like to know, unofficially, from the EOC admin’s how many Orion’s they are monitoring with EOC and how they are dealing with adding their users.

Thanks!

Scott

Find more posts tagged with

Accepted answers

All comments

MarieB

Hi Scott--

Your point is well taken. I'll make sure the product manager gets it.

Thanks,

FormerMember

The plan is to add support for Windows and AD groups.

TGhosh

Denny,

How about offering the option of AD authentication'

or better yet, allow input of records from the "accounts" table in the NPM database.

I'm currently dead in the water with EOC because security policy prevents me from creating local windows accounts on my EOC server. My server also has two domains and my Engineering head will not allow me to join the EOC server to the domain in which all my users exist. I'm stuck....

FormerMember

We'll consider it, but it's a major change, and the combination of not allowing the server to join a domain and being disallowed from creating local windows accounts is one I've only heard from you. If others have this same situation, I'd like to hear it, because that would help us prioritize.

Sonic777

The AD groups would solve my problems, and I would only have to work on dealing with one off special cases where views or menus are customized beyond what would be offered to those groups. The AD setup would work all the way around for EOC and NPM servers that I have.

I want to add that I do have various apps that use AD groups and some are successful while others fail at this solution. To that point, I would like to note that if this is done, please don't take away individual setup features.

Sonic777

The plan is to add support for Windows and AD groups.

I know I added my comments earlier about groups, but I want to add that not only groups for the EOC but when setting up groups of users I can add my regional default user id / password for the NPM pass-through as one group, this way I don't have to go in and edit every single user, only the ones with special requirements.