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.
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.
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.
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.
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
It would be best probably to have a quick call to explain this. Please PM me to set up a call to discuss. Thanks.
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
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.
You may be able to use local machine accounts instead of domain accounts but why isn't EOC using the same security model as NPM where you can create a local account within NPM?
We have a generic account setup in NPM for our on call people and I would like to create a generic account in EOC by the same method and not using the local machine account becuase our security policy doesn't allow for local accounts to be created.
Is there anyway round this?
