DHCP Quick Migration

If you have a newer domain you can setup failover to the new DHCP and then remove the failover dependency after or you can do a quick file copy if you can have a quick down window. I am a fan of the following process for efficiency:

First I would recommend lowering your TTL on DHCP to 30 min to an hour

Open command prompt as an administrator from the server you are exporting DHCP from:

netsh dhcp server export C:\source\dhcp.dat all



Copy the dhcp.dat to the C:\source\ on the new DHCP server

Run the following command from command prompt as an administrator:

netsh dhcp server import C:\source\dhcp.dat all



Confirm settings imported and revise scopes as necessary

Disable old DHCP server (disable service to avoid auto start later)

Enable/Authorize new DHCP server and scope and test

Note: Dont forget to point any DHCP helpers or other network appliances as necessary to the new DHCP server.


Another migration method is to run the following: 

From current DHCP Server export to c:\source (named DC01 below)

 Export-DHCPServer -File c:\source\dhcp.xml -Leases -Force -ComputerName DC01 -Verbose

Copy the file from c:\source to the new DHCP server and import from C:\source (named DCNEW below)

Import-DHCPServer -File c:\source\dhcp.xml -BackupPath c:\source -Leases -ScopeOverwrite -Force -ComputerName DCNEW -Verbose

Credit:

https://appuals.com/how-to-migrate-dhcp-from-windows-server-2008-r2-to-windows-server-2016/




Comments

Post a Comment

Popular posts from this blog

Office 365 Deployment Tool Office Download fails “Could not Install”

Image
Problem: you run the setup.exe /download download.xml and fails immediately with “Couldn’t install” You make sure all the settings are correct (see other blogs) and find nothing wrong Solution: Change drives and run it as an administrator again. For example above i am in the F:\OfficeDeploy directory which is the same directory I have the download.xml directing the download to. If i Change to the c: and run the same command again it works The Office Data folder was created and updated as shown below:
Read more

FRS to DFSR Post Cleanup “File Replication NtFrs Stopped”

Image
After successfully migrating from FRS to DFSR you get the File Replication NtFrs service is Stopped error on the local servers AD DS Services list. In the Event logs you may see Event id 13575 13577. You can confirm your migration completed by opening a cmd prompt as administrator and typing in: dfsrmig /getmigrationstate After your migration to DFSR is completed and you have given your servers ample time to propagate this service is no longer required. Since it is set to “Automatic”, as shown below” it shows in logs as a false positive error. Edit the File Replication Service and change it to “Disabled”, as shown below: Once it is listed as “Disabled” it will no longer show in the Console as an “error” Note : it may take some time to clear from the active view
Read more

Domain Migration SubinACL /Migratetodomain How To:

Caution : DO NOT run this on Domain Controller C:\ and only run on roaming profiles folders, or my docs shares day of migration to avoid ownership change issues. Confirm Domain trust is in place and users and groups have been migrated Test ping of olddomain.org from new domain Test ping of newdomain.org from olddomain Add newdomain.org domain controller host records to olddomain.org including reverse DNS records Confirm the user running the app is a domain admin in BOTH domains Download SubinACL here: http://www.microsoft.com/en-us/download/details.aspx?id=23510 /Migratetodomain- command will add the permissions of the new user to the old files and folders for example if jimbob@olddomain.org was migrated to the new domain jimbob@newdomain.org and you run the command below any file or folder in that path that has jimbob@olddomain.org will add Jimbob@newdomain.org with the exact same permissions. This is a safer way to migrate by keeping the old and new permissions intact while a
Read more