<div>
Does it matter if my 2003 server is x86 and the 2008 is x64?
</div>


<div>
I would usually move the DHCP database; just to avoid the possibility of IP's being re-used.<br />
So this will aide the seamless migration.<br />
<br />
The link provided in the first post is a good reference.<br />
But essentially, yes, just unauthorize the old DHCP server and authorize the new DHCP server.<br />
<br />
Monitor the DHCP logs to check if any IP's have been issued or requested.<br />
<a href="http://technet.microsoft.com/en-us/library/dd183591(v=ws.10).aspx" rel="ugc">http://technet.microsoft.com/en-us/library/dd183591(v=ws.10).aspx</a>
</div>


<div>
Use both servers for DHCP:<br />
<br />
Use the same scope, but split the address pool between the two servers.. This gives you an out if a DHCP server dies.
</div>


<div>
<div class="content wysiwyg-content">
I am planning on moving DHCP services from a 2003 DC to a 2008 DC. I already created the new scope on the 2008 R2 server. There are no reservations configured on the old DHCP server. Can I just stop the DHCP Server service on the 2003 server and start and activate the scope on the new DHCP server? Is it necessary to do a backup/restore of the DHCP database? I would like this to be seamless and not have to do a release/renew on the PC's.
</div>
</div>


I am planning on moving DHCP services from a 2003 DC to a 2008 DC. I already created the new scope on the 2008 R2 server. There are no reservations configured on the old DHCP server. Can I just stop the DHCP Server service on the 2003 server and start and activate the scope on the new DHCP server? Is it necessary to do a backup/restore of the DHCP database? I would like this to be seamless and not have to do a release/renew on the PC's.

Does it matter if my 2003 server is x86 and the 2008 is x64?

I would usually move the DHCP database; just to avoid the possibility of IP&#39;s being re-used.
So this will aide the seamless migration.

The link provided in the first post is a good reference.
But essentially, yes, just unauthorize the old DHCP server and authorize the new DHCP server.

Monitor the DHCP logs to check if any IP&#39;s have been issued or requested.
http://technet.microsoft.com/en-us/library/dd183591(v=ws.10).aspx

Use both servers for DHCP:

Use the same scope, but split the address pool between the two servers.. This gives you an out if a DHCP server dies.

Moving DHCP from 2003 Server to 2008 R2

I am planning on moving DHCP services from a 2003 DC to a 2008 DC. I already created the new scope on the 2008 R2 server. There are no reservations configured on the old DHCP server. Can I just stop the DHCP Server service on the 2003 server and start and activate the scope on the new DHCP server? Is it necessary to do a backup/restore of the DHCP database? I would like this to be seamless and not have to do a release/renew on the PC&#39;s.

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).