Migrate IP Configuration to Windows Server 2012

Applies To: Windows Server 2012

Migration of IP configuration data is a necessity for the migration of some server roles to Windows Server 2012, including DHCP Server, Domain Name System (DNS) Server, and Active Directory Domain Services (AD DS). This guide describes how to migrate core IPv4 and IPv6 configuration settings and data.

Supported operating systems

The following table indicates the Windows Server operating systems that are supported by Windows Server Migration Tools.

The versions of operating systems shown in the preceding table are the oldest combinations of operating systems and service packs that are supported. Newer service packs, if available, are supported.

Foundation, Standard, Enterprise, and Datacenter editions of Windows Server are supported as either source or destination servers.

Migrations between physical operating systems and virtual operating systems are supported.

Windows Server Migration Tools does not support migration from a source server to a destination server that is running an operating system in a different system UI language (that is, the installed language) than the source server. For example, you cannot use Windows Server Migration Tools to migrate roles, operating system settings, data, or shares from a computer that is running Windows Server 2008 in the French system UI language to a computer that is running Windows Server® 2012 in the German system UI language.

Both x86- and x64-based migrations are supported for Windows Server 2003, Windows Server 2008 R2 and Windows Server 2012. All editions of Windows Server 2008 R2, and Windows Server 2012 are x64-based.

Roles that are running on Server Core installations of Windows Server 2008 cannot be migrated, because there is no .NET Framework available on Server Core installations of Windows Server 2008.

Supported scenarios and features

Windows Server Migration Tools supports migration of the following frequently used IP configuration settings and data. Settings are migrated in the order in which they are listed in the Windows interface. For example, DNS server settings are migrated in the order in which they are used.

Manually-configured IP settings for all enabled network adapters (also known as network interface cards, or NICs) that are connected to the network

• IPv4 addresses

• IPv4 subnet mask

• IPv4 DHCP status

• IPv4 default gateway addresses (but not gateway metrics)

• IPv4 interface metric

• IPv4 Windows Internet Name Service (WINS) server settings

  • WINS server addresses

  • NetBIOS setting (Default, Enable NetBIOS over TCP/IP, or Disable NetBIOS over TCP/IP)

• IPv6 addresses and corresponding subnet prefix lengths

  Note

  Migration of IPv6 subnet prefix lengths is supported only on destination servers that are running Windows Server 2008, Windows Server 2008 R2 or Windows Server® 2012. If an IPv6 address is imported from a Windows Server 2003 migration store, the subnet prefix length is set to the default value of 64 on the destination server.

• IPv6 router discovery setting

• IPv6 Managed address configuration flag, and Other stateful configuration flag

  Note

  These settings are supported only on Windows Server 2008, Windows Server 2008 R2 and Windows Server® 2012. Windows Server 2003 does not support DHCPv6-based IPv6 address configuration. If Router Discovery is enabled on the source server, you must ensure that the Advertising setting is the same on both source and destination servers to make sure that Managed address configuration and Other stateful configuration values are configured the same on both source and destination servers. For example, if Managed address configuration is configured automatically on the source server, then the value for the Advertising setting must be the same on both source and destination servers for Managed address configuration to be configured automatically on the destination server. Managed address configuration and Other stateful configuration settings are not imported to the destination server if they are configured as Automatic. In other words, they are not imported if the Router Discovery setting is enabled, yet the Advertising setting is disabled.

• IPv6 default gateway addresses (but not gateway metrics)

• IPv6 interface metric

  Note

  IPv6 interface metric is supported only on Windows Server 2008, Windows Server 2008 R2 and Windows Server® 2012. If this setting is manually configured on Windows Server 2003 or Windows Server 2003 R2, it will not be migrated. For more information about how to migrate this setting manually from Windows Server 2003 or Windows Server 2003 R2, see IP Configuration: Appendix.

• DNS settings

  • IPv4 DNS server addresses

  • IPv6 DNS server addresses

  • DNS suffix for this connection

  • Register this connection’s addresses in DNS

  • Use this connection’s DNS suffix in DNS registration

For global (Windows-based) IP configuration

• • For resolution of unqualified names:

    • Append primary and connection-specific DNS suffixes

    • Append parent suffixes of the primary DNS suffixes

    • Append these DNS suffixes and the list of DNS suffixes (also known as the DNS search list)

• Enable LMHOSTS lookup (but not LMHOSTS file)

• IPv6 DisabledComponents property

  Note

  This setting is supported only on Windows Server 2008, Windows Server 2008 R2 and Windows Server® 2012. If this setting is configured in Windows Server 2003 or Windows Server 2003 R2, it will not be migrated.

Scenarios and features that are not supported

Group Policy settings or other autoconfigured settings related to IP configuration are not supported.

If the source server uses additional settings for advanced IP configuration that are not in the previous list, define a custom migration procedure based on the configuration of your organization’s network environment.

For more information about IP configuration settings that are not supported, see IP Configuration: Appendix.

See Also

IP Configuration: Prepare to Migrate
IP Configuration: Migrate IP Configuration Data
IP Configuration: Post-migration Tasks
IP Configuration: Appendix