IP Configuration: Appendix

Articolo
08/31/2016

Applies To: Windows Server 2012

This Appendix contains additional information that might help you prepare for a custom IP configuration migration when your migration is not supported according to the list of supported migration scenarios and features in IP Configuration: Prepare to Migrate.

Migrating manually-configured IPv6 interface metrics from Windows Server 2003

If you have manually-configured IPV6 interface metrics on a computer that is running Windows Server 2003, manually migrate the interface metrics to Windows Server® 2012 by using netsh commands.

To obtain index numbers for source and destination network adapters

On source servers that are running either Windows Server 2003 or Windows Server 2003 R2, open a Command Prompt session by clicking Start, clicking Run, typing cmd in the Open box, and then either clicking OK or pressing Enter.
On the destination server, open a Command Prompt session with elevated user rights. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
On both source and destination servers, obtain the index numbers of source and destination network adapters. Type the following in each Command Prompt session, and then press Enter.
```
netsh interface ipv6 show interface
```
Record the numbers in the Index column that correspond to the names of the interfaces that you want to migrate.

To obtain the manually-configured IPv6 metric from the source server

If a Command Prompt window is not already open on the source server, open one as directed in Sstep 1 of To obtain index numbers for source and destination network adapters.
Type the following, in which Index represents the index numbers that you obtained in To obtain index numbers for source and destination network adapters, and then press Enter.
```
netsh interface ipv6 show interface <Index>
```
For example, if your interface has an index number of 11, use the following command.
```
netsh interface ipv6 show interface 11
```
Record the IPv6 metric that you want to migrate to the destination server in the Metric field.

To migrate the manually-configured IPv6 metric to the destination server

If a Command Prompt window is not already open on the destination server, open one as directed in step 1 of To obtain index numbers for source and destination network adapters.
Type the following, in which Index represents the number that you obtained in To obtain index numbers for source and destination network adapters, and Integer represents the number that you obtained in To obtain the manually-configured IPv6 metric from the source server, and then press Enter.
```
netsh interface ipv6 set interface <Index> metric=<Integer>
```
For example, for an interface with an index of 22, use the following command to set the metric to 2.
```
netsh interface ipv6 set interface 22 metric=2
```

Additional resources

Some advanced IPv4 and IPv6 configuration settings for a network adapter are not displayed in the Windows interface. Depending upon the configuration of the destination network, you might need to migrate these settings manually to a destination server.

If you have manually configured nondefault routes for an interface, use the following command to view these settings on the source server. The value for ipvx can be either IP (for IPv4) or IPv6.
```
netsh interface <ipvx> show route
```
To set these settings on the destination server, see netsh help by entering the following command, in which the value for ipvx can be either IPv4 or IPv6.
```
netsh interface <ipvx> add route
```
If you have manually configured general interface settings for a network adapter, use the following netsh command to view these settings on the source server. The value for ipvx can be either IP (for Ipv4) or IPv6.
```
netsh interface <ipvx> show interface <InterfaceIndex>
```
To set these configuration settings on the destination server, view netsh help by entering the following command, in which the value for ipvx can be either IPv4 or IPv6.
```
netsh interface <ipvx> set interface
```

For the complete list of all settings that can be viewed and configured by using the netsh command, see the following articles on the Microsoft Web site.

Additional general TCP/IP configuration parameters are stored in registry keys. For the complete list of general TCP/IP configuration settings that are stored in registry keys, see TCP/IP Configuration Parameters on the Microsoft Web site (https://technet.microsoft.com/library/cc739819.aspx).

For additional information about IP configuration, the following resources are recommended.

Condividi tramite