Problems with SW license in virtualized servers with Citect 2018

Hi,

We are migrating our systems from Citect 7.40 to Citect 2018 (with the license upgrade to version 8.20) and we are facing a lot of problems in the virtualized scenarios, where we have redundant HW and a unique virtual machine that runs on one or the other depending on the avalability of them.

So, when the virtual machine changes from one node to the other, the license doesn't work anymore, it appears in a untrusted state and we need to reactivate it...so we are losing the redundancy.

It seem that some policies in the licenses have change, but is there a solution for this problem?

Thanks  

Parents
  • Hi,
    Thanks for the information...the scenario that we are using is based in an Hyper-V virtual server (Second generation and with windows 2016 (mainly) and windows 2019) .
    The structure is that we have 3 physical servers --> Supervisor, Node 1 and Node 2
    And there is one virtual machine (hosting the SW license) that the supervisor decide in which node will run (if one fails, it moves the VM to the other node, but the virtual machine is the same, it is not stopped)

    Antonio, you mean that this scenario is not longer supported??? It was before :(, and now this is a big issue for upgrading.

    Maybe if we use an older flexera SW we can work??
Reply
  • Hi,
    Thanks for the information...the scenario that we are using is based in an Hyper-V virtual server (Second generation and with windows 2016 (mainly) and windows 2019) .
    The structure is that we have 3 physical servers --> Supervisor, Node 1 and Node 2
    And there is one virtual machine (hosting the SW license) that the supervisor decide in which node will run (if one fails, it moves the VM to the other node, but the virtual machine is the same, it is not stopped)

    Antonio, you mean that this scenario is not longer supported??? It was before :(, and now this is a big issue for upgrading.

    Maybe if we use an older flexera SW we can work??
Children
No Data