Migrate dhcp windows 2003 to 2008

By bankajac , April 9, in Windows. I just got a new server running server enterprise and would like to move or migrate everything to that server. Where do I start? Do I migrate AD first or last? Any good guides or advice?

From now on you will be using both servers for your domain. And exclude first half the scope address from server and exclude second half of the scope address from server. This way you can use both dhcp servers at the same time and when you remove the server the clients will automatically shift to the new server.

Join the server to the domain, doing this first before dcpromo will help identify any connectivity issue or configuration issues with the existing domain before you run into them in the middle of dcpromo.

DCPromo the server. You seem to imply your environment is a single server, but if you have more than one once you have completed all your DCs to DCs migrations consider switching the forest to "Windows Server " mode and migrate to DFS-R replication for sysvol.

You're supposed to use the local admin account, which you can't do once you've promoted your server, unless you use AD Recovery mode. I have one DC. Do I need to run all 3 commands on it? Since I don;t have a forest, I am assuming not the first command but the last two?

Should I run all three anyways? OK, so I did everything but demote the original DC did not remove anything yet. How do I know that everything is working properly? Will that change once I remove those roles from the old DC? Did I do something wrong since the IP addresses have not been updated to the new server? You needed to reduce the DHCP lease from the default 8 days to something like 4 hours at least 8 days before making the switch.

Once the lease time is shortened and they're all on a 4 hour lease, make your change by authorising the new server's DHCP and deauthorising the old one. When I right click I can only unauthorize. What should I do now? Lastly, I have terminal licensing running on the old server and also on a terminal server I wanted to have all the licensing on the new domain controller so I deactivated the open licenses and installed on the new server.

I did the same with the retail licenses but with those I had to contact Microsoft as I could not activate. Did I have this issue because the licenses were open and the retail? Just my curiosity at this point as it all works now. Search In. Share More sharing options Followers 0.

Recommended Posts. Posted April 9, Link to comment Share on other sites More sharing options IrfanL Posted April 9, Crimson Tide Posted April 9, Extend the AD schema for using adprep from the CD.

Move this file to the new Windows Server server 4. Here are descriptions of both processes. Then, you'll import those settings into the server that's running Windows Server You should be prepared to spend about minutes performing the procedure, assuming that you already have Windows Server installed and configured ahead of time.

After disabling the service, stop the currently running DHCP service; either click the Stop button shown in Figure A or issue the net stop dhcpserver command from the command line. After disabling and stopping the running DHCP service, all that remains to be done on the legacy Windows server is to export the DHCP database information so that it can be transferred to the Windows Server computer. You can do this using the Registry Editor regedt Save the appropriate key to another location, such as a networked drive that is accessible to both the Windows Server and the server running Windows Server If you have not done so, you can do this from the Server Manager available on the Start menu.

To do so, from a command prompt, issue the command net stop dhcpserver. First, import the registry key that you previously exported. On the server that's running Windows Server , double-click the registry file that you exported earlier.