User has standalone intouch application with primary alarm provider and logger node and RDS node. When looking at events specifically (such as changing alarm setpoint) the operator logged in does not reflect properly in alarm/event viewer. For example, when logging into alarm provider node with username, and having a different user logged in on the RDS node, it does not reflect the correct operator logged in in the alarm/event viewer.
[RESOLUTION]: WAD. Refer past CR L00137387). It is marked as Enhancement request. Here is more info from that CR.
Some of the tests:
It's a very simple InTouch application, two users created (administrator and roger), one output field showing the currently logged on user so I can be sure that I'm logged on properly and one input field that changes the value in my Siemens PLC (logged event). Using the AlarmDBLogger to log the events to the WWALMDB using the query \\rogerslaptop\InTouch!$System.
If I'm on the console session logged on as administrator and change the tag it goes in to the database with the operator "administrator" and the correct newly changed value. If I log on through remote desktop services (using a different logon) and log on to the InTouch app as "roger" and make a change to the tag it gets logged in the WWALMDB with the operator "administrator".
It doesn't seem to matter what user I've logged on to the terminal server with, or what user I'm logged on to the InTouch app with, it still logs the name of the user that logged on to the InTouch app running on the console.
I've gone over the IT for TS deployment guide and I don't see anything that I'm doing wrong here. The data is being logged correctly, just the user is wrong. This looks like the same thing that Halton is seeing on their application now. Previously when they were running on Windows 2003 they wouldn't have a user logged on to the console session since InTouch could start as a service. They only started to see this after migrating to InTouch 2012 R2 and Windows 2008.
