Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Archive > 2017December15 - Deletes > Using group accounts with EOC for accessing NPM servers

Using group accounts with EOC for accessing NPM servers

Created by Interspire Import, last modified by Jessica Solis on Dec 15, 2017

Views: 17 Votes: 0 Revisions: 12


This document covers the requirements for accounts accessing Orion servers with EOC.




All EOC versions and all Orion versions



Users MUST use Windows AD accounts for logging into EOC. If the user prefers to use Windows AD credentials for managing the NPM server, the user can set up a non-password account, but only when the Set Account is the same as the Account being edited in EOC. This works with no issues for individual AD accounts in Orion - however it might not work with AD groups.


You can use accounts without passwords for groups as well. If this does not work, make sure the EOC account and AD group are the same group as used in Orion. Also note that using AD accounts without passwords will restrict users from viewing reports and acknowledging alerts, events, syslogs and importing maps in Network Atlas when no NTLM Authentication is used.

Last modified