Citect 2016 + Thin Client

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.

Hello Nuna,

Maybe I wasn't enough clear in my explanation.

My server 1&2 are redundant.

I need to give access to runtime Citect to administrative computers that have not Citect 2016 installed neither Citect Runtime. I want to access through Web page only.

Previously with Monitor Pro, they used web client and click onto shortcut with server1's address (IP or Host) then reach runtime project. If server1 was lost, it swapped automatically to server2 without any click by customer on adminstrative computer.

I want to implement that solution with new Citect2016 version.

For HTML you will need Citect Anywhere, 

I never used it, so don't know practical details about redundancy, but I think the best approach will be use a separate server to have Citect Anywhere and all clients connect to it.

For HTML you will need Citect Anywhere, 

I never used it, so don't know practical details about redundancy, but I think the best approach will be use a separate server to have Citect Anywhere and all clients connect to it.

Thanks for your answer, I will follow my investigations.