Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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: 1,094 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