Hi,
I've a bit of a problem here so would appreciate any help!! I just migrated one of our DHCP servers to a VM and all looked good until I checked the migrated VM's DHCP. The scopes did not migrate over. Is this something that needs to be done manually?
Thanks,
Pedro
http://communities.vmware.com/message/853389
**If you found this information useful, please consider awarding points for
"Correct" or "Helpful"**
You migrated an entire server, or just moved the DHCP database over? If you migrated the server everything should be there.
If not you probably want to read this: http://www.microsoft.com/windows/windows2000/en/advanced/help/sag_DHCP_tro_MovingDatabaseToNewServer...
If you changed the IP of the machine I could see DHCP getting cranky with that.
On the migration I've always found it easier to bring a new machine online and then phase over, though it sounds like it's too late for that...
No, the scope is a integral part of the DHCP, the mac address will be different on the VM, this could cause the scope to deactivate
I migrated a full server over. I had to rollback to the physical box last night due to the issues encountered.
Should I import the DHCP scopes manually next time or should they just migrate into the VM automatically.
Note - I didn't change the IP address or name of the server.
Thanks for your help,
Pedro
DHCP was empty. There was no sign of any scopes which is strage.
Can yo think of any reason why the scopes did not migrate?
what os is on the server and how are you migrating into esx
The OS is Windows 2003 Standard & I'm using VM Converter version 4 for the migration.
stop the dhcp server service before you migrate
I posted the steps on how to do this, all you have to do is stop the DHCP service on the Physical box, then move the database over (its like 4 meg or less...) and copy to the DHCP folder on the VM. That's it.
ALL your scopes, machines, IP reservations everything will be there. It's a snap, just follow the directions I posted.