We are using Authentication Manager 8.1. Would it be better to convert our appliance from a VMWare vm to a Hyper-V vm, or is it better to create a new appliance in Hyper-V instead?
Would anyone have any instructions on how to do either option?
Thanks in advance
T-Prime
If you are on 8.1.0.0.0, there is no version that can run on Hyper-V.
Hyper-V is only possible starting with 8.1.1.0.0 and up (8.1 sp1) which has a new full base installer for Hyper -V
8.1.0.0.0 vmware and hardware base installers, no Hyper-V
8.1.1.0.0 Hyper-V base installer, [vmware and hardware have patches to 8.1.1.0.0, no base installer]
8.2.0.0.0 base installers for all
8.2.1.0.0 base installers for all
8.3.0.0.0 base installers for all
Also, there is no reliable method of converting an already set-up machine to a new base platform, and we would not be able to support it. There are system fingerprints created on the first setup and the software is now tied to the machine is was installed on for security reasons. New installs on the target platform are always the path to take***.
***Hyper-V live migration or Vmware Vmotion is supported, but these do not change the system to the point of non work-ability.
---
The way to go about it would be:
Make sure the current servers are all at least 8.1.1.0.0 (8.1 sp1)
Deploy a new replica 8.1.1.0.0 into hyper-v. Later, promote for maintenance, so it becomes the new primary.
Then delete one of the replicas, and re-depoy a replica into Hyper -v. Using these or similar steps you can 'leapfrog' your way onto new platforms.
-----
In actual fact, the best and most reliable way to do it, would be get your current environment patched all the way up to 8.3.0.4.0 (8.3 patch 4) first.
Then deploy the new Hyper-V replica as base image 8.3.0.0.0, and then once set up and running, patch it to 8.3.0.4.0. Next, do the planned promotion steps and the Hyper-V becomes the primary, and the other primary demotes and becomes a replica....and you can now delete the unwanted replicas, and spin up new replicas into Hyper-V.