Userlocation issue

I’m assuming you are running Citect as a Service on the server.

The user location shows the server IP.
If you look in the details of Windows task manager on the server, you will see a few Citect32.exe under the system Account and for every user logged in and running Plant SCADA / Citect a Citect32.exe. The Citect 32.exe of the User get the information from the Serer.

To get information from the thin client Wtsapi32.dll looks promising. 
see: projectwww.codeproject.com/.../Grabbing-Information-of-a-Terminal-Services-Sessio

looks like the Wtsapi32.dll is able to gather the client's IP address, I wondering if the Citect server can log the client IP address and display at the column "Userlocation"

Also, you can read windows environment variables in a thin client session. Computername tells you the name of the PC. If you're connected to that PC using remote desktop, there's an extra variable named ClientName tells you the name of the thin client PC. You can read those variables with the GetEnv() function in Citect, like ThinClientPC = GetEnv("CLIENTNAME")

Unfortunately, I don't think you can make the alarm server record that as the user location.

I believe the only way to achieve this is by logging the Client Ack events manually using a custom cicode function that is called instead of the normal alarm acknowledge-function. This custom function should either

a) log ACK-events as a new SOE-entry, replacing the system mechanism

b) let the system log the SOE entry, and then modify the UserLocation field afterwards

Edit: typo

I believe the only way to achieve this is by logging the Client Ack events manually using a custom cicode function that is called instead of the normal alarm acknowledge-function. This custom function should either

a) log ACK-events as a new SOE-entry, replacing the system mechanism

b) let the system log the SOE entry, and then modify the UserLocation field afterwards

Edit: typo