The MyQ MS Cluster high-availability solution consists of multiple nodes in the active/passive configuration with the MyQ Server installed on each node. MS Cluster administers the MyQ services and if the currently active node becomes unavailable, it switches to one of the available passive nodes.
Compatibility with Windows Servers
The MyQ MS Cluster solution is supported by the following Windows Server versions and editions:
|
Windows Server |
Editions |
|---|---|
|
Windows Server 2025 |
Standard, Datacenter |
|
Windows Server 2022 |
Standard, Datacenter |
|
Windows Server 2019 |
Standard, Datacenter |
|
Windows Server 2016 |
Standard, Datacenter |
-
A prepared failover cluster with at least two nodes and storage for MyQ data is needed. Each node must meet the system requirements of the MyQ Server and its components.
-
The same time zone has to be set on each of the nodes.
If your setup includes embedded terminals, make sure that the required .NET framework version installed in each cluster node. If not, the embedded terminal installation will fail. Further information can be found in the related MyQ Embedded terminal manuals.
If the MyQ Desktop Client, MyQ Smart Job Manager or the MyQ Smart Print Services applications are to be used on the MyQ users workstations, the IP address or hostname of the cluster has to be set in the applications (not the IP address or hostname of the nodes).
Licenses
Only one installation key is needed to use MyQ in a MS Cluster. The HW code is taken from the whole cluster, not individual nodes, so the license is activated against the cluster’s HW, and not a single node.