Anyone migrated a 2K3 DHCP server to 2K8?

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

We are about to decomission an old server which just happens to be our DHCP server. I intend to migrate the DCHP server to one of our new 2K8 R2 DC's but as I understand it, some people have had issues doing this. (red X's on leases, reservations not coming across etc...)

There is an official MS KB guide in order to do exactly what I'm talking about. I'm going to try migrating it to a test virtual server first though and see what happens.

If anyone has already done this and has the bald patches of hair to proove it, I'd appreciate any tips before I get my hands dirty.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

So long you know: the scope of IP addresses that your server will manage (e.g., 192.168.1.50 to 192.168.1.200), which machines require static IP addresses (i.e., those machines such as servers and routers that will not use DHCP to receive their IP addresses but will be set manually),which network information you want to send out to DHCP clients when they get their IP addresses (e.g the addresses for your default gateway, DNS servers, and WINS servers).

Besides that, it's pretty straight forward.

Edit: also check the duration of the lease (expired or not). ;-)

----------------
Now playing: 12 Stones - Games You Play
via FoxyTunes

 

Yes, I could re-create the DHCP server manually by noting the things you mentioned and setting them up on the new server, but that wasn't the question. Stick to your brain dumps dude.

 

I've recently done such migration (although not to R2 but I doubt it matters).

Had no bigger issues what-so-ever but I had to manually delete old leases on the old server before it went offline.
For some reason when there were leases on the old server the machines on new server were showing as "incorrect ip address" once a while (Even with the old server being offline :/). Set up new server. Delete the leases on the old one. Offline the old server. Test.
That's how I've done it.

By offline I mean DHCP service being offline and not the machine.
Also just noticed you don't want to recreate the dhcp settings but migrate. Apologies for not reading properly

 

I am reluctant to delete the old leases as I have had problems in the past when I have done that, but it sounds like there are potential pit falls using either method. Thanks for the input guys, I'm sure it will all go swimmingly.

 

Update: I tried an import to a WK8 R2 server using the method outlined by MS and got an error during the import (to a test virtual server). So it didn't work.

I have instead setup a new 2K3 R2 virtual server and done the import to that which ... worked perfectly*. I used the method outlined here.

I think I'll leave it running just as a dedicated DHCP server for now. What's that old saying, let sleeping dogs lie ...

*Ok I say perfectly, it didn't want to authorise at first (it said it had, but hadn't actually), so an un-athorise & re-authorise worked in the end. Oh and erm... turning the firewall off helped the clients see the new server, after a bit of head scratching.

 

Hmm it is working nicely now, I suppose it's time to break it.

 

Like you said mate, that's what snapshots are for ...