DHCP / SERVER 2012

I have the following

a remote site with an old domain controller that has been demoted to a member server but it is the dhcp server for the site.

There is a new physical server at the site, server 2012,  and the DHCP service has to be moved to this server.

As an addition to this, there is a DHCP server running in their datacenter that they would like used as a failover, should the local server fail.

Initially my thoughts are that a local and remote dhcp will cause issues and that we should just use the DHCP server in the datacenter?

There are actually two dhcp servers in the datacenter configured in a dhcp failover
cmatchettAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Manjunath SulladConnect With a Mentor Technical ConsultantCommented:
Below link will guide you to how to migrate DHCP server from 2008R2 to 2012.

http://blogs.technet.com/b/teamdhcp/archive/2012/09/11/migrating-existing-dhcp-server-deployment-to-windows-server-2012-dhcp-failover.aspx


Step-by-Step: Configure DHCP for Failover (Windows Server 2012)

http://technet.microsoft.com/en-us/library/hh831385.aspx
0
 
cmatchettAuthor Commented:
what if i just want to take the scopes to an existing server?
0
 
cmatchettAuthor Commented:
hi thanks so far,

I would be sure enough that we could lift and shift the dhcp database from the 2003 server to the 2012.

There are quite a quite a few scopes on this server.  Would another way be to move one scope at a time?

I could have dhcp-server-1 with 12 scopes

on day 1, move scope1 - update the ip helper on the local router
on day 2, move scope2 etc etc

if we move the whole database at once, all the leases are maintained and it wouldn't matter how long the current lease duration was.  at 50% of the lease, the client would broadcast and a different server would respond having the same DHCP lease information?
0
All Courses

From novice to tech pro — start learning today.