Hello,
I apologize for posting this in 2 different forum areas (Migration and Infrastructure). I'm hoping to get a little feedback and appreciate any suggestions. We have a Windows2003 domain (Windows2003 R2 (32bit) Domain Controllers). We will be migrating our domain to Windows2008 this summer and i'm building a baseline. We do need to keep the same ip address for 2 of our domain controllers. One domain controller has DHCP along with 4 of the 5 FSMO roles. I will be transferring these roles to another DC after preparing the AD forest and schema for Windows2008. This will just leave DHCP (we have numerous scopes/reservations). I have read through this article: http://msmvps.com/blogs/acefekay/archive/2010/10/09/remove-an-old-dc-and-introduce-a-new-dc-with-the-same-name-and-ip-address.aspx
- I will use this article as a guideline, but I do have some questions relating to DHCP migration. First of all, I will be using the migration method for DHCP and not the import/export function (from what I read, when going from 32bit to 64bit there are good chances of errors and all scopes/reservations not copying over). I see that the import/export function is noted nicely here, but I need more info on the DHCP migration process using the migration tools.
(Question)
- Would I do the migration process while the source (Windows2003 DC) is a domain controller and the destination server (Windows2008 Member server) a member server before demoting/decommissioning the 2003DC and then promote the Windows2008 server (with DHCP migrated) and at this point I would assign the same ip address as the source?
(OR) - Does the Windows2008 need to be a DC during this migration process? The concerns I have would be what DHCP user groups (admin groups, etc) get migrated over when the server is a member server versus a domain controller.
Thanks in advance,
Bob