Migrate Windows DHCP server

A few weeks ago at work, I was tasked with the project of decommissioning one of our older Windows Server 2008 machines and upgrading it to Windows 2012. I was initially a little worried, seeing as this server ran a lot of key roles, such as DHCP, DNS, was a Domain Controller, and also acted as a print server as well as a few other services. As I was migrating the DHCP role, I wondered if there was a simple way of exporting all of the settings, such as DHCP scope and reserved IP addresses. Turns out there was, and it went off without a hitch!

Here’s how I did it:

Log on to the old/existing DHCP server.

Click Start, click Run, type cmd in the Open box, right-click, and then “Run as Administrator”.

On the Action menu, click Backup.

Type netsh dhcp server export C:\Users\\Desktop\dhcp.txt all, and then press ENTER.

Install the DHCP role on the new (2012) DHCP server using Server Manager.

Copy the exported DHCP text file to the desktop of the new DHCP server.

Verify that the DHCP service is installed and started on the new DHCP server.

Click Start, click Run, type cmd in the Open box, right-click, and then “Run as Administrator”.

Type netsh dhcp server import C:\Users\\Desktop\dhcp.txt all, and then press ENTER

Open DHCP console on the new server.

In the console tree, right-click DHCP.

Select “Authorize”.
If your old DHCP server is in the same network/subnet as the new DHCP server, you’ll notice that the old DHCP server has been de-authorized automatically. This is to prevent two DHCP servers from handing out conflicting addresses.

Check to make sure that your new DHCP has all of the same settings, options, scopes, and reservations set as the current one. If done correctly, everything should have been brought over. I was pretty impressed as to how well this worked and just how seamless it truly was.

Set AD Attributes

You can also view and set these values with PowerShell, provided you have the ActiveDirectory module installed.


Get-ADUser <username> -Properties extensionattribute1

Set-ADUser <username> -Add @{“extensionattribute1″=”Your Value Here”}

Set-ADUser <username> -Clear extensionattribute1

Stubborn Belly Fat

Let’s Get Rid of Belly Fat, Shall We?

Stubborn Belly Fat? Drink a protein shake (100-130 calories and 20-25g protein) 10 minutes before every meal. It curbs your hunger so you won’t eat as much and gives you a metabolic advantage from the higher protein intake.

Stubborn Belly Fat? Do a short, quick, powerful metabolic density workout 4 days/week, at least. If I feel like challenging myself I’ll do 7x/week for a full month. Each workout should be short (15 minutes or less) and can be tacked on to the end of your normal strength workouts.

Stubborn Belly Fat? Caffeine is a potent thermogenic and naturally increases your metabolic rate. So, coffee!

Stubborn Belly Fat? Meditate 60 seconds/day. That’s it. Just 60 seconds. It doesn’t magically burn fat but it does, I think, reduce stress and help you be more mindful. And, truth is, most people rarely take a full 60 seconds to actively focus on themselves and their mindset every day. Try it — I think it’ll help.

Adding a USB backup drive to SBS backup

Add a new disk to the backup schedule by running the wbadmin command from an elevated command prompt.

Run the following command from an elevated command prompt to determine the Disk Identifier of the new disk:
wbadmin get disks
Based on the output, locate the disk that will be added to the scheduled backup. Make a note of the Disk Identifier. The output will resemble the following:

Disk name: xxxxxxxxxxx
Disk number: x
Disk identifier: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
Total space: xxx.xx GB
Used space : xxx.xx GB

Run the following command to add the new disk to the Scheduled backup. Use the Disk Identifier from the previous step as the “AddTarget” parameter.

WBADMIN ENABLE BACKUP -addtarget:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

When you receive the following prompt, type Y for Yes.
“Do you want to enable scheduled backups with the above settings?”