Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.

 

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: 10 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
23:13, 22 Jun 2016

Tags

Classifications

Public