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
Store

EOC - non domain accounts

EOC forces you to set up accounts from a windows domain. Is there a way to create non-domain accounts? Our operations center team would like a non-domain account that's shared to access Orion and EOC. Orion I can do and works. They would like to be able to use their local domain accounts to log in their machines and use a generic account to access EOC. Otherwise I'd have to create an EOC account for every person which is a nightmare to manage with turnover, etc.

If not now...can we see this in a next release?

Find more posts tagged with

Accepted answers

All comments

derhally

Hi Bryan,

You are definitely not the first person to ask for built in accounts.

For the time being, are local windows user accounts that are not part of the domain an option?

If they are not, then can you please give us reasons why. This would help the PMs to understand the need for built in accounts for EOC.

Thanks.

BryanBecker

This is not a local user on the server itself...everyone has a domain account...I just do not want to have to create individual accounts for them. I would create a local EOC account, like you can do in Orion now, that they all can use.

So no....local windows account on the server is not an option. I just want to see the same functionality in EOC that Orion has with creating these accounts.

TGhosh

Agreed. I've been holding off on deploying EOC until the security model is changed from domain only. My EOC server lives in a datacenter where I can not join to my corporate domain.

derhally

Bryan,

Maybe I'm misunderstanding your request. You just don't want to use window accounts at all regardless if they are local or AD accounts because of security reasons or from a account management perspective?

Would supporting Groups in EOC help with managing access to the EOC server?

TGhosh,

Accounts do not have to domain accounts, you can create and use local windows users.

davidmaltby

I'm really not understanding how local Windows accounts, won't provide you with what you need. Maybe you don't realize that if you use a local account of the EOC box, that remote boxes logging into the EOC website, can still authenticate with that local Windows account. When they try to access the EOC web console, they will get prompted with a Windows Authentication dialog. Here, althought they are on a remote machine, they can type in the credentials for the EOC local Windows account.

Therefore, you can create a local Windows account on the EOC box that has super restricted priviledge on that box, but can be used to log into EOC from computers in other domains, or even across the Internet (if you choose to expose it).

If after this explaination, this still isn't an option, can you explain what advantage there is in using Orion authentication accounts instead of local Windows accounts in EOC?

Thanks,

David

BryanBecker

It would be best probably to have a quick call to explain this. Please PM me to set up a call to discuss. Thanks.

bunny

Hello, was this ever resolved? I'm looking to do the same thing on EOC and it seems like you can set up a Windows account.

Thanks

derhally

I'm not aware of what was the resolution to the previous poster, but you are able to use local windows accounts with EOC. using domain accounts is not a requirement.

FormerMember

I'd like to revive this topic. One reason that non-AD, local EOC user accounts would be advantageous, is in a NOC environment where we use large displays and Digital Media Players to display HTML content on the large NOC screens. These devices do not have the ability to authenticate to AD (which is why we chose them for public viewing). I would love to be able to display the EOC home page on a large NOC screen, using local EOC accounts (including automatic login, like we do for NPM). Making EOC just like NPM (AD or Local accounts) would be a great help.

dkeyser

I'd like to revive this topic as well since I believe having EOC only accounts much like NPM would be beneficial for use this software in such a way as to give users who are not a part of the domain and will never be granted local access to this or any other server to still utilize this system. We would potentially like users to monitor their nodes across many different deployments of Orion in one location for total visibility. These users would be external to our own company so they will never have a domain account created for them. They are using NPM currently but they would have to jump from deployment to deployment to keep track of all their assigned assets and it truly is a hassle. I get that most of the information can be sent via email but sometimes clients just like to see what's going on. Some will be letting others handle the issue and just want to see the total health of their departments.

Has this been posted as a feature request before? I'll +1 if so.

jchambley

It would be handy to have this ability. To create a test user easily to test new roles before assigning to someone. To have to remote into the server, then go into EOC to make the changes then back into the server to disable the account seems a bit much considering the functionality exists in NPM.