I have a Hyper-V environment with two servers:

• Server A: Primary (Main) Hyper-V host

• Server B: Replica Hyper-V host (using Hyper-V Replica)

SolidCP Portal is installed and configured on Server A, and customers normally use it to manage their virtual machines hosted on A.

Recently, I performed a failover of the VMs from Server A to Server B using Hyper-V Replica. The VMs are now running successfully on Server B.

However, after the failover:

• SolidCP (running on Server A) cannot control or manage the VMs on Server B

• Even when I configure Server B as a Replica Server in SolidCP, the portal still cannot perform actions (start, stop, manage) on the failed-over VMs

My questions:

1. Is SolidCP supposed to manage Hyper-V Replica failover scenarios automatically?

2. Does SolidCP require the VMs to exist on the primary host only to remain manageable?

3. Is there a supported way to make SolidCP fully manage VMs after they are failed over to the replica server?

4. Do I need to re-import, re-sync, or reassign the VMs in SolidCP after failover?

Any guidance, best practices, or real-world experience with SolidCP + Hyper-V Replica would be greatly appreciated.