Configure Hyper-V Replica with Kerberos Authentication on Server1

D

To use Hyper-V Replica with Kerberos authentication on the default port to replicate virtual machines from a Hyper-V failover cluster to a target server, you need to enable the Hyper-V Replica HTTP Listener (TCP-In) rule on the target server, which in this case is Server1. Therefore, the correct answer is option D.

Option A is incorrect because adding primary servers to the Hyper-V Replica Broker configuration is not required to enable Hyper-V Replica with Kerberos authentication on the default port.

Option B is also incorrect because enabling incoming and outgoing live migrations is not required for Hyper-V Replica with Kerberos authentication.

Option C is incorrect because enabling the Hyper-V Replica HTTPS Listener (TCP-In) rule is not required for Kerberos authentication on the default port. In fact, enabling the HTTPS rule would use port 443 instead of the default port for Kerberos authentication.

Therefore, the correct answer is option D, which involves enabling the Hyper-V Replica HTTP Listener (TCP-In) rule on Server1 using Windows Defender Firewall with Advanced Security. This can be done by following these steps:

1. Open Windows Defender Firewall with Advanced Security on Server1.
2. Click on Inbound Rules in the left pane.
3. Click on New Rule in the right pane.
4. In the New Inbound Rule Wizard, select Port and click Next.
5. Select TCP and specify the default port for Hyper-V Replica, which is 80, and click Next.
6. Select Allow the connection and click Next.
7. Select the network location(s) where this rule should apply and click Next.
8. Give the rule a name and click Finish.

After enabling the Hyper-V Replica HTTP Listener (TCP-In) rule on Server1, you can configure replication settings for virtual machines on the Hyper-V failover cluster named Cluster1 to replicate to Server1 using Hyper-V Replica with Kerberos authentication on the default port.