User login change.

[[Ri...]]

How can I determine when a user change has occurred in Calypso, particularly when in AutoRun.

Is there a log file of user changes or some other file I can look at?

 

[[Ma...]]

I can not find anything which would be like a log.

Perhaps there is a file rewriting it's content which could contain user change, but i doubt that.

[[Ri...]]

I couldn't find anything either.

If this is not logged, it should be.

I think I have an issue where one or more users are logging in and out of Master and messing around with settings.

I am changing the master user pword, again, problem is, a savvy user would know how to find the master pword and change it.

I know I can change the master pword to what I want and then change it back to what it was.

[[No...]]

Don't you think a user savvy enough to know how to change the pw would also mess with the log if one existed? 🤔

Like I always said: Calypso's security is a stale joke. 

[[Sv...]]

I have configured Calypso so that AutoRun opens automatically upon startup and the production user logs in. This user has just enough privileges to launch programs; they aren't even allowed to move an image. This works great for us. Furthermore, the production user cannot exit AutoRun to open Calypso.

[[No...]]

Even then it is possible to circumvent all those measures and become Master. Security is on - hmmm - Windows 3.1 level? 😄

[[Ma...]]

Please sign in to view this username.

Problem is, that you can change user logined in even from autorun mode.

Please sign in to view this username.

I found one file, in which is stored actual user - so read it constantly and you can log it.
Here is my git, where is something to this matter https://github.com/justyand/CalypsoAPI

This file is here "c:\Users\Public\Documents\Zeiss\cmmObserver\observerFile.txt" and "operid" is changing

[[Ri...]]

It's a start, I appreciate the effort and time involved.

[[Ma...]]

Here is powershell script which will cover changes.

observer.ps1 - script itself - correct paths and names for files

observer-task.vbs - script for windows task scheduller - correct full path to "observer.ps1" - make new task -> trigger = login -> action = this file
it will run hidden

This script will result in this log file

[2026-10-13 12:44:17] SERVICE STARTED (Monitoring 'operid' every 1s)
[2026-10-13 12:44:17] operid changed: m.jansky
[2026-10-13 12:45:17] operid changed: zeiss
[2026-10-13 12:49:13] SERVICE STARTED (Monitoring 'operid' every 1s)
[2026-10-13 12:49:13] operid changed: m.jansky
[2026-10-13 12:50:20] SERVICE TERMINATED

observer.ps1observer-task.vbs