Dhcp сбой настройки отработки отказа ошибка 20010

• Remove From My Forums

Ответы

• • Помечено в качестве ответа
    Daniel JiSun
    24 декабря 2013 г. 6:42

Все ответы

• http://translate.google.ru/translate?sl=ru&tl=en&js=n&prev=_t&hl=ru&ie=UTF-8&u=http%3A%2F%2Fwww.bazedy.ru%2Fblogs%2Fkabal%2Fmigraciya-dhcp-s-windows-server-2003-r2-na-windows-server-2012-ili-2008

• • Помечено в качестве ответа
    Daniel JiSun
    24 декабря 2013 г. 6:42

• 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.

• 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!!!!

  • Изменено
    Jason Lehr
    31 июля 2014 г. 12:58
    added pertinent info

• 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.

  • Предложено в качестве ответа
    MRanderath
    9 сентября 2014 г. 9:31
  • Изменено
    MRanderath
    9 сентября 2014 г. 9:41

• 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…

• 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…

  • Предложено в качестве ответа
    scshort33
    24 января 2015 г. 15:59
  • Отменено предложение в качестве ответа
    scshort33
    24 января 2015 г. 15:59
  • Предложено в качестве ответа
    scshort33
    24 января 2015 г. 15:59
  • Отменено предложение в качестве ответа
    scshort33
    24 января 2015 г. 15:59

• 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.

  • Предложено в качестве ответа
    _JeB_
    16 февраля 2015 г. 10:49
  • Отменено предложение в качестве ответа
    _JeB_
    16 февраля 2015 г. 10:49

• 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.

  • Изменено
    _JeB_
    16 февраля 2015 г. 10:53
    Confirmed answer
  • Предложено в качестве ответа
    jAkEkInG
    19 декабря 2015 г. 0:30

• 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. 🙂

  • Предложено в качестве ответа
    SMCZ
    11 января 2016 г. 13:48

• 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!

• 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?

  • Изменено
    mandango
    29 июня 2016 г. 10:37

• 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.

  • Предложено в качестве ответа
    Dan Dziubanski
    13 декабря 2017 г. 18:26

• 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.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

• Remove From My Forums

Answers

• • Marked as answer by
    Daniel JiSun
    Tuesday, December 24, 2013 6:42 AM

All replies

• http://translate.google.ru/translate?sl=ru&tl=en&js=n&prev=_t&hl=ru&ie=UTF-8&u=http%3A%2F%2Fwww.bazedy.ru%2Fblogs%2Fkabal%2Fmigraciya-dhcp-s-windows-server-2003-r2-na-windows-server-2012-ili-2008

• • Marked as answer by
    Daniel JiSun
    Tuesday, December 24, 2013 6:42 AM

• 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.

• 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!!!!

  • Edited by
    Jason Lehr
    Thursday, July 31, 2014 12:58 PM
    added pertinent info

• 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.

  • Proposed as answer by
    MRanderath
    Tuesday, September 9, 2014 9:31 AM
  • Edited by
    MRanderath
    Tuesday, September 9, 2014 9:41 AM

• 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…

• 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…

  • Proposed as answer by
    scshort33
    Saturday, January 24, 2015 3:59 PM
  • Unproposed as answer by
    scshort33
    Saturday, January 24, 2015 3:59 PM
  • Proposed as answer by
    scshort33
    Saturday, January 24, 2015 3:59 PM
  • Unproposed as answer by
    scshort33
    Saturday, January 24, 2015 3:59 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.

  • Proposed as answer by
    _JeB_
    Monday, February 16, 2015 10:49 AM
  • Unproposed as answer by
    _JeB_
    Monday, February 16, 2015 10:49 AM

• 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.

  • Edited by
    _JeB_
    Monday, February 16, 2015 10:53 AM
    Confirmed answer
  • Proposed as answer by
    jAkEkInG
    Saturday, December 19, 2015 12:30 AM

• 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. 🙂

  • Proposed as answer by
    SMCZ
    Monday, January 11, 2016 1:48 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!

• 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?

  • Edited by
    mandango
    Wednesday, June 29, 2016 10:37 AM

• 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.

  • Proposed as answer by
    Dan Dziubanski
    Wednesday, December 13, 2017 6:26 PM

• 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.

• Remove From My Forums

Answers

• • Marked as answer by
    Daniel JiSun
    Tuesday, December 24, 2013 6:42 AM

All replies

• http://translate.google.ru/translate?sl=ru&tl=en&js=n&prev=_t&hl=ru&ie=UTF-8&u=http%3A%2F%2Fwww.bazedy.ru%2Fblogs%2Fkabal%2Fmigraciya-dhcp-s-windows-server-2003-r2-na-windows-server-2012-ili-2008

• • Marked as answer by
    Daniel JiSun
    Tuesday, December 24, 2013 6:42 AM

• 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.

• 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!!!!

  • Edited by
    Jason Lehr
    Thursday, July 31, 2014 12:58 PM
    added pertinent info

• 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.

  • Proposed as answer by
    MRanderath
    Tuesday, September 9, 2014 9:31 AM
  • Edited by
    MRanderath
    Tuesday, September 9, 2014 9:41 AM

• 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…

• 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…

  • Proposed as answer by
    scshort33
    Saturday, January 24, 2015 3:59 PM
  • Unproposed as answer by
    scshort33
    Saturday, January 24, 2015 3:59 PM
  • Proposed as answer by
    scshort33
    Saturday, January 24, 2015 3:59 PM
  • Unproposed as answer by
    scshort33
    Saturday, January 24, 2015 3:59 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.

  • Proposed as answer by
    _JeB_
    Monday, February 16, 2015 10:49 AM
  • Unproposed as answer by
    _JeB_
    Monday, February 16, 2015 10:49 AM

• 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.

  • Edited by
    _JeB_
    Monday, February 16, 2015 10:53 AM
    Confirmed answer
  • Proposed as answer by
    jAkEkInG
    Saturday, December 19, 2015 12:30 AM

• 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. 🙂

  • Proposed as answer by
    SMCZ
    Monday, January 11, 2016 1:48 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!

• 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?

  • Edited by
    mandango
    Wednesday, June 29, 2016 10:37 AM

• 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.

  • Proposed as answer by
    Dan Dziubanski
    Wednesday, December 13, 2017 6:26 PM

• 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.

Answers

• Hi mandango,

  Sorry for the later reply.

  I tested it in my lab and without success, option 60 can not be replicated automatically in DHCP failover relationship in any case.

  After some research, I found option 60, 66 and 67 are related with WDS server, and option 60 is highly related with WDS when DHCP role and WDS role on the same server.

  If your scenario is that DHCP1 and WDS on the same machine, and the DHCP has failover relationship with DHCP server2, you are considering that when DHCP1 is down, could DHCP2 work well for WDS services like DHCP1. 

  As far as I’m concerned, DHCP2 can failover for normal DHCP service, but WDS service is hard to say, probably not work.

  Best Regards,

  Anne

  ---

  Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

  • Proposed as answer by

    Friday, July 22, 2016 8:19 AM

  • Marked as answer by
    Anne HeMicrosoft contingent staff
    Friday, August 5, 2016 2:54 AM

Answers

• Hi mandango,

  Sorry for the later reply.

  I tested it in my lab and without success, option 60 can not be replicated automatically in DHCP failover relationship in any case.

  After some research, I found option 60, 66 and 67 are related with WDS server, and option 60 is highly related with WDS when DHCP role and WDS role on the same server.

  If your scenario is that DHCP1 and WDS on the same machine, and the DHCP has failover relationship with DHCP server2, you are considering that when DHCP1 is down, could DHCP2 work well for WDS services like DHCP1. 

  As far as I’m concerned, DHCP2 can failover for normal DHCP service, but WDS service is hard to say, probably not work.

  Best Regards,

  Anne

  ---

  Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

  • Proposed as answer by

    Friday, July 22, 2016 8:19 AM

  • Marked as answer by
    Anne HeMicrosoft contingent staff
    Friday, August 5, 2016 2:54 AM