Thanks for sharing ... very helpful.
Thanks Rafael Damásio, but article is not completed.
Tonight will be ready.
If you are doing a revision later of the powershell pictures, you are using "ls" to list all files. Ls is an alias to Get-ChildObject. Ls is used in *nix operating systems, to less confuse people new to powershell i would suggest you use the full cmdlet or short form. Get-ChildObject / CGI. otherwise a great article.
Thanks for the wonderful article and the nitty gritty details for each step. If I may say, while this is certainly one way to get the DHCP migration done, it seems like an awful lot of work/configuration compared to simply exporting the database from the original server to a text file, then import it on the new machine and call it a day. It literally took me about ten minutes.
You of course will have to shuffle some DC IP addresses around (so the DHCP service will function on the network, using the original server's IP address), but that's relatively painless.
I just did the DHCP migration from a 2003 to 2008R2 box last night. Moving the IP addresses was key because we had the following items configured in our environment:
1) scope options for time service that referenced one 2K3 DC that was replaced by a 2k8r2 DC.
2) scope options for DNS resolution that referenced the old 2k3 DC IP addresses.
3) All static member servers in that building/server room were already configured with the original 2k3 DC IP.
I had been using this method for years when switching out DCs with the DHCP role enabled...2k3 to 2k3.
Hope that helps and thanks again for this article.
Worked like a charm. Thanks a ton
This procedure is too long and sticky
This link can do same thing very simple