Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM login issue with AD Group members

NPM login issue with AD Group members

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

Views: 2,168 Votes: 0 Revisions: 9

Issue:
NPM Windows Group accounts and AD users that are members of that group receive the error message "Password is not working" when attempting to login.

Resolution:

This may be caused by duplicate SID historical data created when the user account was migrated from one controller to another.

After you delete SID history for all groups/accounts in your AD controller, the user should be able to login.

To remove SID History:

 

1. Identify the servers involved in your AD migration.

2. Install Active Directory Migration Tool somewhere but NOT on a Domain Controller.

3. Create a SID mapping file.

4. Run the ADMT security translation wizard against the old servers using the sid mapping file you just created.

5. With the ACLs 'fixed', purge SID history from users and groups, slowly and gradually. Starting with a small test gropup and go from there.

Also see the following article on how to delete SID history http://support.microsoft.com/kb/295758

Last modified

Tags

Classifications

Public