Restored replica (windows not activated)

[kaboomza]

Hi there, we recently had to revert to a replica that was being managed by Veeam, and we have found that this replica in question has an issue with windows activation, and windows is not activated? Is this expected behavior or can anybody provide some insight on what could cause this? The original VM that was being replicated was in a perfect state with No OS or activation issues etc...

Regards,
Jaques

[Mildur]

It could be the new hardware (your target hypervisor).
Windows needs to be reactivated if hardware was changed.

[soncscy]

Second the hardware activation. MAK-Activation for example is really sensitive to this and any sensed hardware change will likely trigger re-activation. Even same CPU family on your host might be "different" enough for reactivation to trigger, so likely you need to check and understand why Windows thinks it needs to be activated (should be in Event Logs), and see if there's anything that can be accommodated for.