2012 R2 Datacenter DHCP Authorization Issues
I upgraded a 2008 R2 Datacenter server functioning as a domain controller and DHCP server. I upgraded to 2012 R2 Datacenter. I made it a replica domain controller with DNS and made it a Global Catalogue server and then installed the DHCP server role. I backed up the DHCP database on the 2008 server, copied the file to the new 2012 server and I believe I successfully imported the dhcp database file. I have done this many times. All the scope settings, reservations, lease, etc. showed.
I went to authorize the new server and it says it’s authorized under manage authorized servers but will not issue IP addresses.
When I select IPv4 or Scope within the console, it says the server needs to be authorized.
I have installed and uninstalled everything several times but end up with the same result = no ips being issued.
Suggestions please ????
I went to authorize the new server and it says it’s authorized under manage authorized servers but will not issue IP addresses.
When I select IPv4 or Scope within the console, it says the server needs to be authorized.
I have installed and uninstalled everything several times but end up with the same result = no ips being issued.
Suggestions please ????
ASKER
I was doing all the management on the the DHCP management console on the 2012 box until I reverted back to the 2008 server. When I changed to the 2012 R 2 I turned off DHCP service on the 2008. I uninstalled DHCP on it.
I have started and restarted the DHCP server service dozens of times
I have started and restarted the DHCP server service dozens of times
Yeah I've seen this before.
When you export your existing reservations from 2003/2008 you normally have to jetpack the database.
Your better option, export your entire scope and leases on the 2012 box, delete the all the scopes on 2012 and re-import. That tends to fix it.
Thanks
Alex
When you export your existing reservations from 2003/2008 you normally have to jetpack the database.
Your better option, export your entire scope and leases on the 2012 box, delete the all the scopes on 2012 and re-import. That tends to fix it.
Thanks
Alex
ASKER
Thanks for responding. I have been there and done that. I have also done Metadata clean ups after each install, uninstall and reinstall of the roles
Metadata cleanup isn't the issue
So you've taken your 2012 box, exported all your scopes, deleted the scopes and reimported all on 2012?
So you've taken your 2012 box, exported all your scopes, deleted the scopes and reimported all on 2012?
ASKER
No sir, sorry if I confused you. I have taken one of the two 2012 R 2 servers I upgraded and reverted it back to 2008 R 2 to see if I could get it to work. Neither the 2008 R2 or 2012 R 2 DHCP servers will authorize. When I say reverted, I backed up the 2012 and copied the db file back to the 2008 and re-imported it into the 2008 server.
This is getting complicated, I need the following in simple answers
Thanks
Alex
- What is the current OS you're dealing with?
- When you took the 2012 backup and imported it into 2008, did you do an export again on 2008 and re-import it?
- When you say they won't authorize, they are authorized in AD but you can't get the scope to launch? Correct?
Thanks
Alex
ASKER
What is the current OS you're dealing with?
Ans
I am dealing with two different servers. Both were upgraded from 2008 R 2 to 2012 R2. I still have access to the old 2008 and the new 2012 servers.
When you took the 2012 backup and imported it into 2008, did you do an export again on 2008 and re-import it?
No I reinstalled the server role and imported the back up
When you say they won't authorize, they are authorized in AD but you can't get the scope to launch? Correct?
No, the scope is there but no IP addresses are issuing. I looked at Display Statistics to determine this as well as communication from clients not getting IPs
Ans
I am dealing with two different servers. Both were upgraded from 2008 R 2 to 2012 R2. I still have access to the old 2008 and the new 2012 servers.
When you took the 2012 backup and imported it into 2008, did you do an export again on 2008 and re-import it?
No I reinstalled the server role and imported the back up
When you say they won't authorize, they are authorized in AD but you can't get the scope to launch? Correct?
No, the scope is there but no IP addresses are issuing. I looked at Display Statistics to determine this as well as communication from clients not getting IPs
Right,
So, you have a 2008 box, with your 2012 export that has been imported in and that's not working as expected and dishing out IPs.
Run an export on the 2008 box, delete all your scopes and then import it again, do not use the 2012 export on the 2008 box, use a fresh export from 2008 to 2008.
Regards,
Alex
So, you have a 2008 box, with your 2012 export that has been imported in and that's not working as expected and dishing out IPs.
Run an export on the 2008 box, delete all your scopes and then import it again, do not use the 2012 export on the 2008 box, use a fresh export from 2008 to 2008.
Regards,
Alex
Has the IP of the DHCP server changed? Remember you're authorising the IP, not the server.
ASKER
No, It has not changed. I authorize by using the IP.
ASKER
Alex, I will try your possible solution, thank you
To be honest, I had to move from 2003 to 2012, when you export the database using either the gui or Netsh DHCP, the database inevitably screws up, you're actually meant to jetpack the database and then import it. However the easier option is to migrate, export the database a second time from the new machine and then reimport it.
Then it dishes out IP addresses as expected.
Then it dishes out IP addresses as expected.
ASKER
Thanks again sir
It's late where I am so I will try in the AM
Again, thanks
It's late where I am so I will try in the AM
Again, thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Alex, it is done and thank you for your help and follow through sir
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes sir & thanks again !
Excellent, i'm really pleased, have a great day :-)
P.S Migrating DHCP sucks, it always has done and I suspect it always will do, this is a sure fire way to get around compatibility issues between the versions of DHCP databases and the actual server. ;-)
Anything else let us know
P.S Migrating DHCP sucks, it always has done and I suspect it always will do, this is a sure fire way to get around compatibility issues between the versions of DHCP databases and the actual server. ;-)
Anything else let us know
ASKER
Thanks sir
I left a grateful comment for your work with me
Will do and take care
I left a grateful comment for your work with me
Will do and take care
Is the DHCP server service running? Did you shut dow the DHCP server service and disable it on the 2008 server?