Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Network Performance Monitor (NPM) > NPM login issue after Active Directory migration

NPM login issue after Active Directory migration

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 43 Votes: 1 Revisions: 8

Issue:

Unable to login to NPM after the Active Directory (AD) was migrated from one controller to another.

Cause:

After the AD migration, new system identifiers (SID) were created and also the SID history gets migrated to the new controller. NPM fails to process such accounts with more SIDs.

Workaround:

Delete the SID history for all the groups/accounts in AD Controller.

Note: In rare cases, when the suggested workaround do not work, you may need to re-add users to AD - Refer to Microsoft site for  detailed steps.
Last modified

Tags

Classifications

Public