What are the requirements for using Domain Migration Administrator when migrating with SID History? (NETIQKB4365)

  • 7704365
  • 02-Feb-2007
  • 08-Oct-2007


What are the requirements for using Domain Migration Administrator when migrating with SID History?

What conditions must be met to successfully migrate with SID History?

Domain Migration Administrator 6.x

Domain Migration Administrator 7.x

In order for a migration with SID History to be successful, the following conditions must be met:
  • The target domain must be running Microsoft Windows 2000 or Microsoft Windows 2003  in Native Mode.
    • Note: SID History is not available in mixed mode domains.
  • Domain Migration Administrator (DMA) must be installed on a Microsoft Windows 2000  domain controller, Microsoft Windows 2003 server or Microsoft Windows XP machine in the target domain.
  • To migrate SID History to a Microsoft Windows 2000  domain:
    •  The logged on user must be a member of the target domain'sDomain Admins group.
  • To migrate SID History to a Microsoft Windows 2003  domain:
    • The logged on user must be delegated full control to the target Organizational Unit (OU).
    • The logged on user must be granted the Migrate SID History permission to the domain object. To do this:
      1. Open Active Directory Users and Computers.
      2. Right click the domain name.
      3. Select Properties.
      4. Select the Security tab. (This may require enabling Advanced Featured in the Active Directory Users and Computers MMC.)
      5. Add the migration account to the Security tab.
      6. Scroll down through the permissions and select Allow for the Migrate SID History permission.
    • If using DMA 7.2 or higher, the logged on account does NOT have to be a member of Domain Admins when migrating SID History to Microsoft Windows 2003.
      • Note: Support for this additional permission was first added in DMA 7.2. To migrate SID history in prior versions of DMA, the logged on account must be a Domain Admin in the target domain, even when migrating to Microsoft Windows 2003.
  • Source domain may be running:
    • Microsoft Windows NT 4.0 (Service Pack 4 or later)
    • Microsoft Windows 2000 (Mixed or Native)
    • Microsoft Windows 2003
  • For Microsoft Windows NT 4.0 source domains: The source domain's primary domain controller (PDC) must be available.
  • The source domain must not be in the same forest as the destination domain (by definition, a Microsoft Windows NT 4.0 domain is not in the same forest).
  • The source object must be of one of the following types:
    • User
    • Security enabled Group, including:
      • Global group
      • Local group
      • Shared Local Groups (Local Groups created on the PDC and shared with the Backup Domain Controllers (BDCs) in a Microsoft Windows NT 4.0  domain
      • Domain Local Group
      • Universal Group
  • The source object may not have a built-in SID (e.g. Administrators, Users, and Power Users Local Groups). As built-in SIDs are identical in every domain, adding them to SID History would achieve very little.
  • The SID of the source object must not already exist in the target forest, either as a primary account SID or in the SID History of an account.
  • For Microsoft Windows NT 4.0  source domains: Modify the registry on the source PDC, adding the DWORDvalue TcpipClientSupport to: HKLM\SYSTEM\CurrentControlSet\Control\LSA. This value must be set to 1 to enable the Security Accounts Manager (SAM) operations required for cloning to take place over remote procedure call (RPC). DMA will prompt you to allow it to set this registry key when you first enable the option for a migration wi.
    th SID History. You do not need to set this registry key under normal circumstances. The source PDC must be rebooted after this key is set and DMA will also do this automatically.
  • Create a trust so that the source domain trusts the target domain.
  • The user account logged on to the DMA console machine must have administrator privileges in the source domain.
    • To do this, add the Domain Admins group from the target domain to the Administrators  group in the source domain.
  • A local group must be created in the source domain called srcDomainName$$$, where srcDomainName is the name of the source domain. DMA will prompt you to allow it to create this group when you first enable the option for a migration with SID History. 
    • Example: If the domain is called Redmond, the group would be called Redmond$$$.
  • Auditing of success and failure of account management operations must be enabled in both the source and target domains. DMA will prompt you to allow it to create this group when you first enable the option for a migration with SID History.
  • The Global Catalog server must be available in the target domain.

This information can also be obtained from Chapter 2 of the DMA User Guide.

Additional Information

Formerly known as NETIQKB4365