Where you need to be aware of using Windows Server2012 or R2 DHCP failover clustering

1 Data synchronization:

Only the lease information is synchronized in real time

Scope options and reserved IPs need to be synchronized manually.

2 Maximum client lead time

This time is the time to provide failover, or the additional time that is provided to the DHCP client after the lease expires.

3 The scope information (including lease retention or scope option information) is synchronized at the end of the cluster, regardless of which scope of the two-side node is being replicated.

4 Error (Unable to get superscope information on DHCP server 172.28.33.12) when setting up pssession remote execution scope information via PowerShell. )。 This may be my personal error at present in the degree Niang or Google did not find the relevant solution.

Code information:

$DHCP =new-pssession-computername dhcp2012-01import-pssession–session $DHCP Invoke-dhcpserverv4failoverreplicationinvoke-dhcpserverv4failoverreplication-computername Dhcp2012-01-scopeid 172.28.11.0

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// Img1.51cto.com/attachment/201407/23/705126_1406098878sncr.png "height="/>

At present do not know how to solve, hope to have friends can try to solve it!

Where you need to be aware of using Windows Server2012 or R2 DHCP failover clustering