Citect 2016 + Thin Client

Hello all,

We retrofit a redundant system MonitorPro to Citect 2016 on W10 pro, also redundant.

We will have 7 thin client. I would like to know if we loose Server1 (application crash or Server1 electrically shut down), does thin client swap automatically to Server2 or do we need an additionnal tool to do that?

Thank you.

Philippe

Parents
  • Hello Philippe

    I'm not sure what you want to implement as thin client. Do you have Citect runtime install on the thin client or a RDP session to some server?


    If you have the citect on the thin clients and the project is well configured and the redundancy licenses installed in secondary server the clients change automatically.

    If is a RDP connection to other server (different form Server1 and Server2) it also works automatically. In this scenario you will need a RDP server with CALLs, and if that RDP shuts down all the clients go down, unless you use the servers also as clients. 

    If the RDP connection is to one of the servers, then you need something else, like other RDP connection to the other server.

    Anyway, its easy to test and it's a good idea to do it.

Reply
  • Hello Philippe

    I'm not sure what you want to implement as thin client. Do you have Citect runtime install on the thin client or a RDP session to some server?


    If you have the citect on the thin clients and the project is well configured and the redundancy licenses installed in secondary server the clients change automatically.

    If is a RDP connection to other server (different form Server1 and Server2) it also works automatically. In this scenario you will need a RDP server with CALLs, and if that RDP shuts down all the clients go down, unless you use the servers also as clients. 

    If the RDP connection is to one of the servers, then you need something else, like other RDP connection to the other server.

    Anyway, its easy to test and it's a good idea to do it.

Children