You are an Enterprise administrator for TestKing.com. The corporate network of the company consists of 200 Windows Server 2008 servers. The company has recently decided to open a new branch office and moved 75 Windows Server 2008 servers from the existing office to the new network segment.

Which of the following options would you choose to change the TCP/IP addresses on the 75 servers that have been moved to the new branch office by using the minimum amount of administrative effort?

A.
Use ServerManagerCMD tool and run it on the administrator’s client computer.

B.
Use the Netsh tool and run it on the administrator’s client computer.

C.
Use Remote Desktop to connect to each server to make the changes.

D.
Visit each server to make the changes.

E.
None of the above

Explanation:
To change the TCP/IP addresses on the 75 servers that have been moved to the new branch office by using the minimum amount of administrative effort, you need to run the Netsh tool from an administrator’s client computer.

You can use NETSH to make dynamic IP address changes from a static IP address to DHCP simply by importing a file. NETSH can also bring in the entire Layer-3 configuration (TCP/IP Address, DNS settings, WINS settings, IP aliases, etc.). This can be handy when you’re working on networks without DHCP and have a mobile computer that connects to multiple networks, some of which have DHCP. NETSH shortcuts will far exceed the capabilities of using Windows Automatic Public IP Addressing.

Reference: 10 things you should know about the NETSH tool / #4: Using NETSH to dynamically change TCP/IP addresses