MyChat has two independent parts, and on a terminal server they are usually kept apart:

The client is a native Win32 application — no .NET, no per-user service. One session means one mcclient.exe process with its own profile.

The server is installed the usual way — there is nothing terminal-specific about it. On a terminal server, though, it must run as a Windows system service rather than as an application inside an administrator's RDP session: otherwise the server depends on that session.

1. run the server installer on the chosen machine;
2. if the server already runs as a regular application — turn its autostart off in the settings and close it;
3. install and start the service (as administrator):

   "C:\Program Files (x86)\MyChat Server\SystemService\service_install.cmd"
   "C:\Program Files (x86)\MyChat Server\SystemService\service_start.cmd"

4. in the service properties set the startup type to "Automatic (Delayed Start)";
5. open the web admin panel at http://<server-IP> and set the administrator, domain and HTTPS.

Ports that must be reachable from the terminal server:

Install under an administrator account, once for the whole machine:

1. switch the server into application install mode:

   change user /install

2. run the client installer and keep the default directory C:\Program Files (x86)\MyChat Client;
3. switch back to the normal mode:

   change user /execute

Put the shortcut into the shared folders so that every user gets it:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\      # Start menu for all users
C:\Users\Public\Desktop\                                   # desktop for all users

On first launch the client creates the data folder of the current user by itself:

C:\Users\<USER>\AppData\Local\MyChat Client\

To avoid creating accounts by hand and handing out passwords, start the client with the self-registration parameters. Add this line to the session startup:

"C:\Program Files (x86)\MyChat Client\mcclient.exe" /auto -server:"192.168.1.50" -randompassword

Parameter values are given after a colon; the parameters themselves are separated by spaces.

Where to put the line — your choice:

• a shortcut with these parameters in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\ — the simplest way;
• a group policy: User Configuration → Policies → Windows Settings → Scripts → Logon.

For /auto to work, the server must allow registration of new users.

On a terminal server all clients should behave the same way — file receiving above all. This is configured on the server, not in each session:

1. in the server admin panel open Tools → Client settings templates;
2. create a template for terminal users: file receiving mode, download folder, sounds, autostart, appearance;
3. assign the template to a user group (for example, Guests).

The template applies both to existing members of the group and to every new one — no need to tune each session separately.

MyChat Client is a native Win32 app without .NET and idles at about 40 MB of RAM per session. That is noticeably less than Skype or Viber, so the client lives well on memory-constrained terminal servers.

The figure grows with heavy image-rich chatting and open history windows — plan a 30–50% headroom.

You may skip installing the client altogether: MyChat ships a full-featured web chat. The user opens

http://<server-IP>

in a browser and works in the same chat — groups, files, channels and conferences included.

An update runs in two stages, in this order:

1. Server. Stop the server service, install the new version over the old one, start it again.
2. Client. On the terminal server a single copy of the program is updated — as administrator, over the existing installation.

Before updating the client, close every running mcclient.exe — the program file stays locked while at least one session holds it:

change user /install
taskkill /IM mcclient.exe /F      # close the clients in all sessions
... install the new version ...
change user /execute

The RDP sessions themselves are not terminated — only the chat closes. After the install it comes back from startup at the next logon, or is launched manually from the shortcut.