How to realize remote application access rights differentiation?

A problem essence in the following. There is a WinFroms application is written in (C#). You need some way to create a configuration to make the application run constantly (on the server) and it could connect users from remote computers (data entry accounts) and see the same screen that is displayed on the server. This should be able to control from within the application, at a specific point in time action can produce only one user, but the result should be displayed on all screens. The application code can be modified.

Tried out the Windows configuration Server * RemoteApp but the problem is that on every connection starts a new instance of the program (in case of permission of multiple connections), or when a new connection was lost with the previous screen of the connected user (in the case of a single connection). Maybe it can be corrected, but do not know where to dig. Problems with documentation.

Thus, you need some specific suggestions, which you can use to solve this problem (running the application in remote mode and the ability to connect to multiple users with control of their actions inside the app). Even the most bizarre. The main criterion for the admissibility of variant in this case is to not have to completely rewrite the original program.
July 2nd 19 at 16:53
2 answers
July 2nd 19 at 16:55
Than to impose restrictions on the use of RDP?
VNC-like services have coped with Your task, one person is connected with viewing and typing, the rest - only viewing.
There is no such restriction. Just tried rdp and it is either not really fit, or I'm not very good tried. Now look VNC. Thanks for the tip. - Tyrique51 commented on July 2nd 19 at 16:58
July 2nd 19 at 16:57
WCF service should help
Possible a little more? In a nutshell, how the interaction is implemented WCF - WinForms - Remote car. - Tyrique51 commented on July 2nd 19 at 17:00
: create and run on the server (supporting the desired Protocol, HTTP, TCP), the client application is already written as I understand it, connect with it, to the service, and after that implement synchronization mechanisms of user and password input and all that nafantaziruet more - Tyrique51 commented on July 2nd 19 at 17:03
: thank you for the clarification. Just the option I wanted to avoid using RDP. - Clarabelle12 commented on July 2nd 19 at 17:06

Find more questions by tags WindowsC#Remote accessRDPWindows Forms