Migrating DHCP Services from 2008 R2 to Windows Server 2012
After all the tools are installed on
the source and destination servers, you can perform the export and
import process. Aside from the export and import process, after the
export is completed on the source server, the source server IP address
must be changed, and the original source server IP address must be
added to the destination server for the import and DHCP operation to be
seamless.
Preparing the Source Windows Server 2008 R2 DHCP Server for Export
After the migration tools are copied to the source Window Server 2008 R2 DHCP server, the migration process can be started.
1. Log on to the source Windows Server 2008 R2 DHCP server and open the DHCP console.
2. Add the local
server to the DHCP server console (if not already present), and then
select and right-click the server and select Add/Remove Bindings. Note
the current IP address of the server because this is used later. Click
Cancel in the window to close it.
3. Right-click the server again, select All Tasks, and then select Stop to stop the DHCP service on that system.
4. Select Start, All
Programs, Administrative Tools, Windows Server Migration Tools, and
then click the Windows Server Migration Tools PowerShell link.
5. When the PowerShell window opens it should default to the C:\MigTools\SMT_ws08R2_amd64 folder. Type ./Servermigration.psc1 and press Enter to open a new PowerShell window. This step may seem redundant, but greatly simplifies the process.
6. In the new PowerShell window type Export-SmigServerSetting -FeatureID DHCP and press Enter.
7. When prompted for the path, enter C:\MigTools\Export and press Enter
8. When prompted for a
password, enter a password with at least six characters and press Enter
to continue. The process creates the export folder and returns the
results into the PowerShell windows, as shown in Figure 1
Figure 1. Exporting the source server DHCP settings.
9. After the export
completes, open the services applet on the source server and set the
DHCP server service to Disabled, then close the services applet.
10. Copy the C:\MigTools\Export folder to the destination Window Server 2012 system.
11. Once the export
has completed and the DHCP server service is disabled, change the IP
address of the source server to something other than the IP address
that was originally bound to the DHCP service.
12. Shut down or reboot the source server as required.
Preparing the Destination Windows Server 2012 DHCP Server for Import
After the export process has completed and
the export data has been copied to the destination server, the original
server can have its IP address changed and can be shut down or
rebooted. After that process has completed, the import process on the
Windows Server 2012 destination server can commence. To perform the
import process, follow these steps:
Note
Running this import procedure overwrites all
DHCP data, so as a best practice do not install the DHCP server service
before this import or use the -Force option when running the import.
1. Log on to the
destination Windows Server 2012 DHCP server and change the network IP
address to the IP address originally bound to the source DHCP server.
2. Reboot the server
to ensure that proper DNS registration is now updated and that all
services are running under the new IP address.
3. Once the server has rebooted, log back in and open the Server Manager.
4. When the Server Manager console opens, click Tools, and then select the Windows Server Migration Tools option.
5. If necessary change to the C:\Windows\System32\ServerMigrationTools folder. Once at the correct path, type ./Servermigration.psc1 and press Enter to open a new PowerShell window
6. In the new PowerShell window, type the command Import-SmigServerSetting -FeatureID DHCP -Force -Verbose
and press Enter. For this example, we are using the -Force option
because the DHCP server service has already been installed, even though
it has not been configured.
7. When prompted for the path, enter C:\MigTools\Export and press Enter to continue.
8.
When prompted for the password, enter the password previously used
during the export process on the source server and press Enter to
continue.
The PowerShell window displays the
current status of the import process and when completed displays the
results and whether a reboot is required, as shown in Figure 2.
Figure 11.8. Importing the DHCP settings to the destination Windows Server 2012 system.
9. If needed, reboot
the server and log on and verify that the original source server IP
address is still bound to this Windows Server 2012 system.
10. Open the Server Manager, click Tools, and then select the Services option.
11. Verify that the DHCP server service is set to automatic startup and if necessary start the service.
12. After the server has rebooted, log back on and open the Server Manager.
13. When the Server Manager console opens, select Tools, and then select the Windows Server Migration Tools option.
14. Open the DHCP
console, and if necessary add the local server to the console.
Right-click the DHCP node in tree pane and select Manage Authorized
Servers. If the original source server is listed, unauthorize it. If
the current destination server is listed with the incorrect IP address,
unauthorize it and close that window.
15. Back in the DHCP
console, right-click the local server in the tree pane and expand the
IPv4 node and verify that the scope has been successfully imported.
16. Right-click the local server in the tree pane and select Authorize as required.
17. Make any necessary modifications to the scope or scope options as required.
18. Right-click the scope beneath the IPv4 node and select Activate as required.
19. Verify that new DHCP clients can obtain a valid IP address lease.
This completes the DHCP migration process from Windows Server 2008 R2 to Windows Server 2012.
Understanding DHCP Client Alternate Network Capability
As an extension of
that protocol, Windows clients and servers can also default to a
fallback static IP address that can be used when a DHCP server is
offline. This can be beneficial to enable complete network connectivity
in the event of a DHCP server outage.
A reasonable application of this
functionality can be remote network systems that rely on DHCP relay
agents that may be less than reliable. On a Windows Server 2012 system,
this functionality can be configured as follows:
1. Log on to a Windows Server 2012 system that is configured with DHCP enabled on the network adapter.
2. On the right side of the taskbar, right-click the Network icon and select Open Network and Sharing Center.
3. When the window opens, in the top-left pane select Change Adapter Settings.
4. In the Network Connections window, right-click the desired network adapter and select Properties.
5. In the Network
Adapter window, scroll down and highlight Internet Protocol Version 4
(TCP/IPv4) and press the Properties button.
6. Click the Alternate Configuration tab and select the User Configured Radio button.
7. Enter the desired IP address information and click OK, as shown in Figure 3.
Figure 3. Configuring a user-configured APIPA address.
8. Click OK twice to save the settings and close the Network Connections window.
This completes the configuration of the DHCP client alternate network configuration.
