Solved Hyper V Server 2019 - Windows Install of 3cx Gen 1 vs Gen 2

[jvbac]

Hello,
The Hyper v guide indicates gen one for a debian install.
However, for a windows 2019 3cx windows install (on Hyper-v 2019), it there a reason why Gen two is not supported? Gen 2 offers better hardware and performance. (per doc's anyway )
thx

 

[Evolute IT]

Hello,
The Hyper v guide indicates gen one for a debian install.
However, for a windows 2019 3cx windows install (on Hyper-v 2019), it there a reason why Gen two is not supported? Gen 2 offers better hardware and performance. (per doc's anyway )
thx

@JohnS_3CX should be able to answer that.

I would stick with Debian in a VM but it's up to you.

 

[jvbac]

Thanks for the reply.
Any particular reason? Anything I found researching the difference really did not produce more than whatever OS you can / will support. Product-wise I did not see any difference between the two.

Thanks again!

 

[Evolute IT]

Thanks for the reply.
Any particular reason? Anything I found researching the difference really did not produce more than whatever OS you can / will support. Product-wise I did not see any difference between the two.

Thanks again!

Windows is much more resource-eater. Debian isn't.

Windows requires a license (unless you have a Datacenter edition of WS2019).

Linux is more flexible and also allows for easier updates. For example, V15.5 to V16 required a reinstall on Windows, not on Linux.

Lastly, for a VM, Debian has a greater stability in my experience. Windows VMs are not the best, specially since you need to use Gen1 for 3CX (for networking reasons if my memory serves).

 

[jvbac]

Thanks for the reply!
Yeah, this will sit on a pretty beefy Hyper v Cluster that already has datacenter licensing.
Note taken on the upgrades.

 

[StefanW]

the reason is gen2 comes with secure boot preventing the Debian 9 instances to start.

https://docs.microsoft.com/en-us/wi.../supported-debian-virtual-machines-on-hyper-v

On Windows Server 2012 R2 Generation 2 virtual machines have secure boot enabled by default and some Linux virtual machines will not boot unless the secure boot option is disabled. You can disable secure boot in the Firmware section of the settings for the virtual machine in Hyper-V Manager

In our observation, this statement from MS also applies to 2019.

 

[dmayer]

We use Gen2's when the 3CX server is Windows based, no issues. Also in regards to secure boot for Linux on Hyper-V, they do support it, you just need to change the Secure boot template from "Microsoft Windows" to "Microsoft UEFI Certificate Authority" under the Security section of the VM settings and as long as the distro is supported for UEFI under Hyper-V, it will work with secure boot.