DHCP Server Migration From Windows Server 2012 R2 to Windows Server 2016

With the end of main stream support coming up in a few months, I decided to start upgrading my lab environment to Windows Server 2016. I started with Active Directory and it's related services like DHCP.

In this article we'll migrate the DHCP service from a machine running Windows Server 2012 R2 to one that's running 2016.

The first step of the process would be to install and configure the DHCP server role on the new machine. I'm not going to describe the installation process since it's fairly simple, I will however show you the post installation configuration.

The first screen is the description of the operation, followed by the authorization step:


Here, we have to select the account that is going to be used in order to authorize the server:


On the last step, the server is authorized and the groups used for delegating access are created:


Now that our new DHCP server is ready, we have to migrate the configuration from the old one.

The server dc1 currently has two IPv4 scopes as shown below. The server dc3 is the new DHCP server that does not have any scopes yet.


The "Export-DHCPServer" cmdlet exports the configuration and leases from a server to a file:
Then, we can use the "Import-DHCPServer" to import the configuration from the file:
The options and scopes have been imported on the new server.


The last step is to disable the scopes on the old server:

Now that the scopes are disabled, the clients will not be assigned addresses from the old server.


That's it! Don't forget to remove the file created on the export step!


Popular posts from this blog

Domain Controller Machine Password Reset

Image
On my lab environment, I've configured two Active Directory sites since most enterprises have offices in more that one places. My lab however is not running 24/7 and the domain controllers in the second site are rarely turned on in order to save resources. This leads to issues with the Active Directory replication such as the "The target principal name is incorrect" error when I execute:  repadmin /syncall /AdeP. To remedy the issue, we have to reset the machine password of the domain controller that has been offline. First off, we are going to stop and disable the Kerberos Key Distribution Center (kdc) service on the problematic domain controller, in our case DC4. There may be some tickets in the cache so we should also clear them using klist purge Now it's time to change the machine password of the domain controller using the command netdom resetpwd /s:dc3 /ud:lab\administrator /pd:* Replace the "lab\administrator" with an account on your
Keep reading

Configuring a Certificate on Exchange Receive Connector

Today's article is about configuring Exchange receive connectors with specific certificates. Out of the box, Exchange uses self signed certificates to provide TLS secured mail flow. This will definitely be an issue if you expose the SMTP protocol to client computers since they won't trust the certificate. In this article we are going to configure a certificate that was issued by a third part authority to the Client Frontend receive connector. We'll start with getting the thumbprint of the certificate using the Get-ExchangeCertificate cmdlet: [PS] C:\> Get-ExchangeCertificate Thumbprint                               Subject ----------                               ------- 241B864DC82C664FECBA18B8D54987AAFB65B4C2 CN=*.lab.com, ... D4D210886B34E690191A1F008C78FDD0E7325DD4 CN=Exchange2013A 960171662EB261162F9C8CBE12E0B75D6F06ABB0 CN=Microsoft Exchange Server Auth Certificate 2690324B827A9F2B75D59104F81CAAA57CDD627B CN=WMSvc-Exchange2013A [PS]
Keep reading

Running Multiple NGINX Ingress Controllers in AKS

Image
In some of the previous articles of this blog, we went through the process of installing NGINX as the Ingress Controller in AKS clusters. Either for applications that should be available directly from the public internet, or for applications that should only be accessed from networks considered internal. In the majority of the cases, however, and given that an AKS cluster is an environment that is designed to host multiple applications and provide economy at scale, additional ingress controllers may be required. In this post, we're going to go through the process of deploying an additional NGINX ingress controller that is going to be used for internal applications. The below diagram depicts the desired outcome: The Angular application is published via the public NGINX through the Azure Load Balancer that has been assigned a public IP. The .NET app is published by a different set of NGINX pods that are deployed in a different namespace and their ingress controller service is connect
Keep reading