The administrator has to make sure that all users have the same shortcut to MONITOR (monwin.exe) in the client directory on the terminal server.Remote access users can share a MONITOR client that has been installed on a terminal server. However, local users in the network can also share this MONITOR client.
It is also possible to have the MONITOR client as a "shared application" on a terminal server, in case you do not want remote users to have access to the entire remote desktop. For this you need Windows Terminal Services or another application server (e.g. Citrix) as terminal server.
Keep in mind that a terminal server requires a substantial amount of main memory (RAM), especially if there are many simultaneous users running the MONITOR client from it. For each user that runs MONITOR, a separate process is started by monwin2.exe on the terminal server. Therefore you should estimate the amount of RAM based on how many users that will be using MONITOR on the terminal server at the same time, and add the amount required by the operating system and other applications, if any. It is estimated that a MONITOR process (monwin2.exe) on average needs about 200 MB.
A client installation of MONITOR is made in "administrative mode" on the terminal server, that is via the Add/Remove program in the Control Panel. Then the MONITOR client will be correctly installed and the startup setting L="[file path to local client directory]" is included in the startup command in the shortcut to MONITOR on the terminal server. Read more about start-up settings in the Configuration of Client section under Database Connection and Performance in this guide.
The administrator has to make sure that all users have the same shortcut to MONITOR (monwin.exe) in the client directory on the terminal server.