One Domain Controller (DC1).
Server2 Just a member didn’t promote it to a DC.
I’m trying to setup a DHCP Failover (Hot Standby)
Add-DhcpServerv4Failover -ComputerName Server2 -Name “StandbyFilover” -PartnerServer “DC1” -ScopeId “$SopeID” -ServerRole Standby -AutoStateTransition:$True -StateSwitchInterval 00:05:00
when I stopped the DHCP server on DC1 didn’t switch over to Server2.
Is there something wrong with my PS Command let ?
I’d use the GUI (MMC) to verify that it’s all set up correctly. There’s a lot of pre-requisites beyond just running the command.
Here’s the result from 2 types of configurations (1st) from PowerShell, Second from GUI
Using Get-DhcpServerv4Failover | select *
Strangely with PowerShell CMDLET shows the partner server and Primary Servers as the Partner Server (Server2)
ScopeId : 10.1.0.0
PrimaryServerIP : 10.1.0.11
SecondaryServerIP : 10.1.0.40
AutoStateTransition : True
EnableAuth : False
LoadBalancePercent :
MaxClientLeadTime : 01:00:00
Mode : HotStandby
Name : DC1-Server2
PartnerServer : Server2
PrimaryServerName : DC1
ReservePercent : 5
SecondaryServerName : Server2
ServerRole : Active
ServerType : PrimaryServer
State : Normal
StateSwitchInterval : 01:00:00
PSComputerName :
CimClass : root/Microsoft/Windows/DHCP:DhcpServerv4Failover
CimInstanceProperties : {AutoStateTransition, EnableAuth, LoadBalancePercent, MaxClientLeadTime…}
CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties