Partager via

AD DS and DNS Server Migration: Appendix A - Migration Data Collection Worksheet

  • Article

Applies To: Windows Server 2008 R2

Migration data collection worksheet

You can use this migration data collection worksheet to collect data about your source server and help ensure that the destination server functions properly after the migration. You can use Windows commands on your source domain controller to identify the settings that are requested in the worksheet.

On the source domain controller, open a Command Prompt window: click Start, click Run, type cmd, and then press ENTER.

Migration data collection worksheet

# Source server essential settings Setting values

1

Server name

At a command prompt, type the following command, and then press ENTER.

ipconfig /all

The host name of a server is the first part of the fully qualified domain name (FQDN). The FQDN is the full computer name, including both the host name and the primary DNS suffix, separated by dots (.). For example, the FQDN of a computer named “host” with a primary DNS suffix of “example.microsoft.com” is “host.example.microsoft.com”.

Computer host name: _____________________________

FQDN: _______________________

2

Operations master roles

Determine what operations master (also known as flexible single master operations or FSMO) roles are hosted on the source server. At a command prompt, type the following command, and then press ENTER.

Netdom query /domain:<domain> fsmo

where <domain> is the name of the domain. Before you begin your migration, determine which operations master roles you will assign to other computers and which roles will go to the destination server.

For more information, see article 324801 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkID=93375).

Check all that apply (√)

  Schema master

  Domain naming master

  Primary domain controller (PDC) emulator master (also known as PDC emulator)

  Relative ID (RID) master (also known as RID pool manager)

  Infrastructure master

3

Server functions

  • Determine whether the source server is a global catalog server or a read-only domain controller (RODC). At the command prompt, type the following two commands, and press ENTER after each command:

    ldifde -s %COMPUTERNAME% -d "" -p base -f DCcfg.txt
    findstr /i "4.1920 GlobalCatalog" DCcfg.txt
  • The commands return exactly one or two lines of text:

    supportedCapabilities: 1.2.840.113556.1.4.1920 indicates that the source server is an RODC.

    isGlobalCatalogReady: TRUE indicates that the source server is a global catalog server.

    isGlobalCatalogReady: FALSE indicates that the source server is not a global catalog server.

If the source server is functioning as either of these two types of domain controllers, the destination server must function in the same way.

Check all that apply (√)

  Global catalog

  RODC

4

Site membership

Determine what site the source server is in. For more information about sites, see Active Directory Sites and Services (https://go.microsoft.com/fwlink/?LinkId=130490).At a command prompt, type the following command, and then press ENTER.

nltest /dsgetsite

Source server site: __________________________

5

Organizational unit

Determine the organizational unit (OU) that the source server is a member of. For more information about OUs, see Organizational units (https://go.microsoft.com/fwlink/?LinkId=130493). At a command prompt, type the following command, and then press ENTER.

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine" | find /i "OU="

Source server OU: __________________________

6

LDAP policy

Perform the following procedure on your source domain controller to determine if it has a Lightweight Directory Access Protocol (LDAP) query policy assigned. If so, make sure that the destination domain controller has the same query policy assigned.

To determine the LDAP query policy on a domain controller

  1. Open Active Directory Sites and Services.

  2. Expand the Sites container.

  3. Expand the site object containing the domain controller.

  4. Expand the Servers container.

  5. Expand the server object that is named for the domain controller.

  6. Right-click the NTDS Settings object and then click Properties.

  7. On the General tab, note the value in the Query Policy box.

If the Query Policy box on the source domain controller is empty, no LDAP query policy changes are required on the destination domain controller.

If the Query Policy box on the source domain controller is not empty, note the value. After the destination domain controller is promoted, perform the preceding procedure on the destination domain controller to make sure that the same query policy is assigned to it.

  

7

DNS information

Record the source TCP/IP settings for DNS. When you record IP information, you must also record DNS client (interface) settings. Look for “DNS servers” information on each interface. Use the following command to create a text file that contains all the necessary information.

IPConfig /All > <filename>.txt

Interface #1

  • IP address: ____________________________

  • Subnet: ____________________________

  • Default gateway: ____________________________

  • DNS servers: ____________________________ (list)

Interface #2:

  • IP address: ____________________________

  • Subnet: ____________________________

  • Default gateway: ____________________________

  • DNS servers: ____________________________ (list)

8

Visually verify that the time, date, and time zone on the source server are synchronized. To view the current settings, type the following commands at a command prompt, pressing ENTER after each command.

time /t
date /t
w32tm /tz

  Time and time zones are synchronized (√)

9

Group Policy

Determine the Group Policy objects (GPOs) that are applied on the source server. For more information about Group Policy, see Windows Server Group Policy (https://go.microsoft.com/fwlink/?LinkID=75191).

Configure policy settings on the source server to be identical to the settings on the destination server. Match the source server policy settings, or determine why you should not match the policy settings on the source server and destination server.

gpresult /scope computer >GPO.txt

If you are running the command on Windows Server 2003, at the command prompt, type the following command, and then press ENTER:

gpresult /scope computer >GPO.txt

If you are running the command on Windows Server 2008 or Windows Server 2008 R2, at the command prompt, type the following command, and then press ENTER.

gpresult /scope computer /r >GPO.txt

Either command prints a text document that contains the GPOs that are applied on the source server.

  

See Also

Concepts

Active Directory Domain Services and DNS Server Migration Guide
AD DS and DNS Server Migration: Preparing to Migrate
AD DS and DNS Server Migration: Migrating the AD DS and DNS Server Roles
AD DS and DNS Server Migration: Verifying the Migration
AD DS and DNS Server Migration: Post-Migration Tasks
AD DS and DNS Server Migration: Appendix B - Migration Verification Worksheet
AD DS and DNS Server Migration: Appendix C - Stand-Alone DNS Migration