Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, December 17, 2013 3:14 PM | 1 vote
Trying to setup DHCP failover between two 2012 R2 servers. Each time I try, I get Error 20010. I saw a hotfix for 2012 KB2756872, but that would not even install. Any ideas. It was migrated from a 2003 server using netsh
MCITP Exchange 2010 | MCTS Exchange 2007 | MCITP Lync Server 2010 | MCTS Windows 2008 | MCSE 2003
All replies (14)
Wednesday, December 18, 2013 3:18 AM âś…Answered | 4 votes
Hi,
The blogger encountered the same problem with yours and provided a solution, hope this helps with your problem:
http://blog.rolpdog.com/2012/11/dhcp-failover-breaks-with-custom-options.html
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Tuesday, December 17, 2013 3:22 PM
Tuesday, February 11, 2014 1:18 PM
Hi,
I've got the same Problem for some of my scopes (Error 20010 The specified Option does not exist). 21 scopes did just fine, but 2 scopes show Error 20010. The scopes are DHCP only and the Options in those scopes do exist in other scopes that I set up for Failover as well. I've tried for 2 days now, but nothing worked so far.
I tried the following (all starting with a new 2nd DHCP)
1) Importing the config from the 1st DHCP, then deleting all scopes on the 2nd before configuring Failover, as suggested in the blog Daniel mentioned.
2) Importing only the Server Settings and Options before configuring Failover.
3) Deleting all scope options on source scope before configuring failover
Is there any way to get to the core of the error message and identify the options that prevent the configuration of failover?
Both Servers are virtual 2012 R2 DCs (Hyper-V) of the same Domain on the same site and in the same subnet.
Wednesday, July 30, 2014 9:02 PM
I am having the same problem- went through and manually created the server options, also deleted them and ran a report of those options from my would-be-master DHCP server. Still get the "option doesn't exist" error. Couldn't they have a log somewhere PLEASE so I can find what this option is? wasted hours on this so far. I did do an import of a W2003 DHCP database when I migrated the new "DHCP Server1" a while back- I have a feeling there is some hidden or corrupted option in there it isn't reading correctly. Or perhaps the database i migrated is still in some 2003 format and needs tables to be updated to 2012 R2-proper?
Let's go Microsoft- give us a way to get more diagnostics on this!!!!
Tuesday, September 9, 2014 9:31 AM | 1 vote
I think I finally found a workaround to this problem:
First, I checked that all custom Options were present on the 2nd Server.
Then I deactivated these options on the source DHCP. Now the configuring failover process worked just fine.
As a last step I reactivated the options on both servers.
Friday, October 17, 2014 5:42 PM
Pls i really need help here... i have set up windows server 2012r2, install DHCP, DNS, ADCS, ADDS and REMOTE ACCESS.
I have also set up the REMOTE ACCESS with VPN using DOMAIN NAME pointing to PUBLIC IP given by MY ISP in my domain service host. EG (xyz.biz to 187.234.76.167).. I HAVE forward PORT on my mikrotic router to ports 80: and 443: .. pointing to the internal static IP of the server.. i have no error on the remote access configuration page ... but i cant access my server when i tried using ... (REMOTE.XYZ.BIZ) on another system ... and also i get error connecting thru vpn .. HELP HELP I WANT TO CRY...
Friday, October 17, 2014 5:43 PM
Pls i really need help here... i have set up windows server 2012r2, install DHCP, DNS, ADCS, ADDS and REMOTE ACCESS.
I have also set up the REMOTE ACCESS with VPN using DOMAIN NAME pointing to PUBLIC IP given by MY ISP in my domain service host. EG (xyz.biz to 187.234.76.167).. I HAVE forward PORT on my mikrotic router to ports 80: and 443: .. pointing to the internal static IP of the server.. i have no error on the remote access configuration page ... but i cant access my server when i tried using ... (REMOTE.XYZ.BIZ) on another system ... and also i get error connecting thru vpn .. HELP HELP I WANT TO CRY...
Saturday, January 24, 2015 4:03 PM
Pls i really need help here... i have set up windows server 2012r2, install DHCP, DNS, ADCS, ADDS and REMOTE ACCESS.
I have also set up the REMOTE ACCESS with VPN using DOMAIN NAME pointing to PUBLIC IP given by MY ISP in my domain service host. EG (xyz.biz to 187.234.76.167).. I HAVE forward PORT on my mikrotic router to ports 80: and 443: .. pointing to the internal static IP of the server.. i have no error on the remote access configuration page ... but i cant access my server when i tried using ... (REMOTE.XYZ.BIZ) on another system ... and also i get error connecting thru vpn .. HELP HELP I WANT TO CRY...
If you look at the Scope Options section on the scope you are trying to configure for the failover you will notice that there have been some custom Scope Option values configured. The custom option fields must be created on the destination failover server to eliminate this error. You can recreate the custom scope options by following the below instructions.
Open DHCP.
In the console tree, click the applicable DHCP server.
On the Action menu, click Set Predefined Options.
In Predefined Options and Values, click Add.
In Option Type, type the required information to define the new option, and then click OK.
After you create the custom option fields, go to the scope on the source failover server and right-click and select Replicate Scope.
Hope this helps.
Monday, February 16, 2015 10:51 AM | 1 vote
I confirm this answer:
When configuring Failover, you need to endure that all custom options created on your local server are also manually recreated on remote server, even if not used. Otherwise you'll get error 20010.
Tuesday, May 19, 2015 1:54 AM | 3 votes
I know I'm late to the party but I'd like to offer some insight, since everyone here has been SO SO helpful to me. Yes you have to make sure that ALL of your custom settings from the primary DHCP server are also mirrored on the other server. Those customizations could be vast and many. The more customizations you try to replicate, the more prone to human error you will be.
The easier way is to wait until after hours, when no one needs DHCP. Backup the DHCP settings from the primary server by right-clicking the server name under the DHCP console, and select backup.
Copy the backed up folder to the secondary server. Restore from that backup. Then DELETE all of the scopes, on this secondary server. (Remember for failover to work, the secondary server cannot have the same scopes. you don't want the scopes, you just want an error-proof way of copying the custom options over.) Then you can continue creating the failover relationship. It worked for me just now. :)
Monday, January 11, 2016 1:49 PM
I know I'm late to the party but I'd like to offer some insight, since everyone here has been SO SO helpful to me. Yes you have to make sure that ALL of your custom settings from the primary DHCP server are also mirrored on the other server. Those customizations could be vast and many. The more customizations you try to replicate, the more prone to human error you will be.
The easier way is to wait until after hours, when no one needs DHCP. Backup the DHCP settings from the primary server by right-clicking the server name under the DHCP console, and select backup.
Copy the backed up folder to the secondary server. Restore from that backup. Then DELETE all of the scopes, on this secondary server. (Remember for failover to work, the secondary server cannot have the same scopes. you don't want the scopes, you just want an error-proof way of copying the custom options over.) Then you can continue creating the failover relationship. It worked for me just now. :)
That's work for me, with migration DHCP from 2003 to 2012.
Thank you!
Wednesday, June 29, 2016 10:27 AM
I have the same problem and wish I could kick the programmer ita who put this error message.
WTH doesn't the error include the name of the specified option?
I can easily clone a dhcp server manually by:
SET myNetworkDrive=\...
netsh dhcp server \127.0.0.1 dump > %myNetworkDrive%\dhcpDump_source.txt
and then on the destination
netsh exec %myNetworkDrive%\dhcpDump_source.txt
So why can't DHCP failover do it?
Wednesday, May 31, 2017 4:19 PM
The problema are the options in the scope. Just delete the options and failover creation will success.
After that recreate the option in the both DHCP Servers manualy.
Regards.
Wednesday, December 13, 2017 6:27 PM | 1 vote
This is correct, we just had this issue this morning, we created some scopes option for telephony. Which stopped the sync. We just added the options to the scope, and everything synced up.