After shutting down or rebooting the Hyper-V host which is hosting the SCVMM server, certain operations in SCVMM may not reflect correctly in the VMM Console. E.g. Jobs which power on/off a VM, change hardware configuration, etc may appear to succeed, but power status or properties of the VM itself do not appear to change in the VMM Console. This also could affect Zerto operations, possibly causing Zerto tasks to fail.
It's been discovered that Hyper-V hosts which have, as one of their guest machines, the SCVMM server which controls them may suffer a data synchronization issue after the host is powered off/on or rebooted. The cause of this appears to be the Automatic Stop Action as defined in the Virtual Machine's settings under the Hyper-V console. If the SCVMM VM has its Automatic Stop action set to "Save the virtual machine state", when the Host comes back up, the VM will act as if it hadn't been shut down. This appears to lead to an issue where the SCVMM services and the Hyper-V host become unsynchronized, and results in commands being sent from SCVMM succeeding, but the changes failing to appear in the VMM console and the SCVMM cmdlets which Zerto Virtual Replication uses to interact with the environment.
If an environment is affected by this issue, the recommendation is to change the 'Automatic Stop Action' for the VM running the SCVMM server to either "Turn Off the virtual machine" or "Shut down the guest operating system". This will cause the SCVMM to perform a full boot sequence when the Hyper-V host is powered off/on or rebooted, which allows the SCVMM server to resynchronize with its hosts.