Automatic syncing of configuration changes between 2 DHCP failover servers

DHCP Failover is a new feature in Windows Server 2012 which provides for high availability of DHCP service. The PowerShell tool provided here allows an admin to setup automatic synchronization of configuration changes between 2 DHCP servers which have been configured for failover

 
 
 
 
 
4.5 Star
(17)
16,039 times
Add to favorites
Networking
2/19/2014
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Works on Windows Server 2016?
    1 Posts | Last post July 04, 2017
    • Someone tested on Windows Server 2016 ? 
  • Query about Windows Server 2008 DHCP Scope replication
    1 Posts | Last post April 04, 2016
    • Hi, In our environment, we have only Windows server 2008 DHCP Scopes, this scripts will be applicable of scope replicate to one of our disaster Windows-2008 DHCP Server which contains all the same scope copy/identical set on this central dhcp server. Please advice. Appreciate your advice. Thanks
  • Please publish on github
    1 Posts | Last post January 18, 2016
    • As a lot of Microsoft scripts and tools are moved to github, contributions to this tool are possible, if moved as well.
  • First sync prior to start the toll. Sytem account to run the task
    1 Posts | Last post November 25, 2015
    • What is the command to run to sync scope relationship without destroying the target DHCP scope?
      Is-there any issue to do not run a sync before running the tool?
      Would-it be easier to run the task with the system account? More secure no account or password to give.
      
  • Schedule task for this script is terminating
    1 Posts | Last post November 09, 2015
    • I just have installed this tool and given the permission to the account as dhcp administrator and added into winrmusers group.When I start the task, it just run the tool and says completed in the logs. It doest stay on running status. However, when i run the script through manually through powershell, it just stays as running and never terminates. I did check the schedule tasks settings everything seems to be fine as per the guide in the tool.
  • reservation replication intermittently pushes bad mac to secondary server
    3 Posts | Last post June 16, 2015
    • The replication of new or update reservations works most the time, but we see several cases where the replicated mac is replicated as "0z2fc40a0000000000".  It always seems to be 10 trailing zeros when it happens.  Environment:  2 2012R2 standard server, virtual, servers at geographically separate sites, load balanced 50/50.  Not sure how much this happens, but it happens enough that the DHCP admins have to check the replicated reservation on the secondary server every time.  Thoughts?
    • Was there any update to this? We may have the same issue.
      
      Thank you, kind regards.
    • I've noticed this issue too... any resolution would be great.
  • Sync tool
    1 Posts | Last post March 27, 2015
    • I tested it but it works otherway.
      
      #whateven changes to scope made on HS failover server is getting replicated to primary, i need this otherway, changes made on Primary should be reflected on HS failover server.
      
      please note that "DhcpFailoverAutoConfigSyncTool" is installed on dedicated Hot stnadby failover server.
      
      how to achieve this? i don't want to configure "DhcpFailoverAutoConfigSyncTool" on all primary server and my requirment is to have a "DhcpFailoverAutoConfigSyncTool" tool configured on centralized dedicated hotstandby failover server and whenever changes are made on primary it should pull the data and update the scopes on itself.
      
  • Sync tool
    1 Posts | Last post March 27, 2015
    • Hey,
      
      I have following setup in my org
      
      One Hotfailover standby setup and multiple primary DHCP servers spread across the globe.and HS failover relation has been configured between primary and centralized Hotfailover standby server.
      
      i have configured "DHCPFailoverAutoConfigSyncTool" on centralized hot failover standby server with "•	Default Replication mode: The tool monitors and synchronizes configurations of all scopes of all failover relationships that the server is a part of"
      
      but for testing purpose, i made some changes on primary dhcp server (created IP exclusion range for one of the scope) and waited for 30-45 mins but even after it didn't reflect on failover server scopes.
      
      my question is what is recommendation to configure this tool, is it on a failover server or on all primary servers.
      
      when i do a manuall replication from the dhcp console it works. 
      
      
      
  • Failover partner server scope keeps getting deactivated
    1 Posts | Last post March 12, 2015
    • Hi - for some reason the replicated scope on my partner server keeps getting deactivated whenever the sync tool runs.  Is there something I did wrong to explain why this keeps happening?
  • Log file is growing quickly
    4 Posts | Last post October 29, 2014
    • I did not change any settings in XLM file.  It works but the log file (.\dhcpautosynclogfile.txt) is growing at a fast rate.  Entries for sync complete and automatically sync again are being posted at rate of 3 or 4 times per second.  File grew to 10MB in less than 5 minutes.  Had to disable the scheduled task to stop from filling up the drive.
    • I made the account running the scheduled task a member of local admin group on the DHCP server running DFACS.  That did the trick.  I had already 
      - granted permission to the account in the registry path noted
      - added the account to the WinRMRemoteWMIUsers_ group
      As noted by post from SupportS2L, I was having same issue.
      
      Unless I am missing something else (not in most recent tool guide), I think the document needs to be updated to reflect that account needs to be member of local admin on the server.
    • You need to grant read/write to C:\Windows\Temp folder for the account to fix the logfile growing at an exponential rate.  This also fixes CPU issue.
    • You need to grant only read permissions to C:\Windows\Temp for the account running the scheduled task to fix the logfile growth issue. Write permissions or local admin group membership are not required.
      Guys please update the UsageGuide doc.
11 - 20 of 27 Items