Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Enterprise Operations Console (EOC) > 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 MindTouch on Jun 23, 2016

Views: 6 Votes: 0 Revisions: 11


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
19:26, 22 Jun 2016