Sunday, January 10, 2010

Home /$75FB00 /pre-W2k /QMM /Quest Migration Manager /re-ACL /SamAccountName / Profile Migration Using Quest Migration Manager (QMM)

Profile Migration Using Quest Migration Manager (QMM)

I was doing some computer migrations last week with Quest Migration Manager tool.  After the profile migration (re-ACL), I started noticing some strange profiles names on the workstation.  You can see the details on the following screen shot: 

image

There profiles were started with $ and two digit numbers.  I did some search on Quest knowledge base but I couldn’t find anything.   Anyway, after enough troubleshooting, we identified the root cause of the issue. 

Cause:
After the initial directory synchronization, we migrated all user accounts with an input file to change their SamAccountName in the target Domain.  By default, during the next directory synchronization, the DSA will overwrite these SamAccountName based on source the SamAccountName.  Since we need to keep our new SamAccountName in target domain, we decided to disable the SamAccountName synchronization in the directory sync configuration.   If you create a new user accounts in your source Domain, DSA will create these accounts in target domain.  Since we are filtering the SamAccountName, the DSA cannot use SamAccountName.   So the DSA create these accounts with some random numbers ($65FB00.., $75FB00..).  You need to perform a full migration with your new SamAccountName to resolve these issues.   After the user account migration all these profiles will be updated with the correct user names and you will see the correct SamAccountName and pre-W2K names inside your AD. 

image

SS

Santhosh Sivarajan

Microsoft MVP · Identity & Cybersecurity Architect

Santhosh has 30+ years of hands-on enterprise experience in Identity and Access Management, Microsoft Entra ID, Active Directory, Microsoft 365 and Zero Trust architecture. He is the author of two books on Windows Server and security, and leads consulting, assessments and training at SAG Business Group.

0 comments:

Post a Comment

Popular Posts
Workstation Trust Relationship Issue Issue: You receive the following error message, when you try to login to the domain.  The security database on the server does not have ... ADMT Service Account - Permission and Configuration The ADMT service account needs to have proper permission in source and target domains.  You don’t need to use 2 separate accounts.  You can ... My First Peek into Microsoft Exchange 2010 By Santhosh Sivarajan Before I really dive into Exchange 2010, I thought I would install and play with it first. I took some screen shots and notes during the ins... ObjectSID and Active Directory What is an objectSID in Active Directory? When a new object is created in Active Directory, Domain Controller assigns a unique value used ... AD Group Report - List Group Members in Active Directory–PowerShell Script Updated Script - http://portal.sivarajan.com/2011/10/search-ad-collect-local-admin-group.html Script #1 This script... Add Users to a Group–PowerShell Script Purpose – Add users to a group from an input file – PowerShell V2 Script.  Input file – Input file (Users.csv) contains samAccountName in... User Account Migration and Merging – Part I (ADMT) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM pre-creating user account ... User Account Migration and Merging – Part II (Quest Migration Manager) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM Pre-creating user account in... Delete Stale or Inactive Computer Accounts from Active Directory Here is an easy way to identify and delete inactive or stale computers in an Active Directory environment.  Using the dsquery command you c... Converting PowerShell (PS1) to EXE / Standalone Application As we know, there many applications available to convert a PowerShell file to a standalone executable file.  Based on my experience, PowerSh...