Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Updated January 10, 2017
When logging in as an individual account that has been added to the Orion console under an Active Directory Group, you are unable to set the default status under Manage Nodes.
All NPM versions
When logged in to the console as an individual but your account is part of an AD group, you are in effect logged in under two accounts: the group account and your individual account.
All personal settings - group by, filters, and other settings are stored in the DB in the table WebUserSettings. This table stores the defaults for the account.
As you are part of the group, no settings are saved for your account. Instead, they default to the group settings which are not changed and always default to Vendor which is the predefined setting.
When you log in, you are logged under WIN2008R2TEMP\ADMINACCOUNT - WIN2008R2TEMP\ADMINISTRATORS.
You are working under 2 accounts:
But the related win2008r2temp\Administrators has no setting at all. So when you are logged under an individual account you are working under a GROUP account which has a higher priority on top of individual.
There are several workarounds:
Go to Start > All Programs > Solarwinds Orion > Advanced Features > Database Manager > Add Default Server>
Expand the NPM Database (default )SolarWindsOrion > Select Settings table > Right Click > Query Table and run the default query.
Find the following settings and update: