I use the classic authentication with vision (vers.8.1.44 on Windows 11).
I need for compliance reasons to avoid the OS exit option from standard login. If I start in full screen (as required), it is always present.
Is there a way to hide the cross? In windowed mode is not present, so should be "easy" to manage in some way...
Beyond that, would be also great to avoid the possibility to switch off the touchscreen mode (icon always present) from the same login. Also for that, is there a way?
The best way to avoid exposure of the normal desktop is to launch Vision in full screen instead of the normal desktop. This is easily accomplished with a custom .Xsession script that monitors the java process, and exits when java exits. This automatically returns the system to the OS login window, where normal auto-login has the opportunity to re-launch the Vision Client.
When the normal desktop is never launched, it cannot be made available to the user with any trickery. (The normal desktop executable could even be omitted from the system.)
Oh, snap! You said Windows 11. Sorry. (I strongly recommend not deploying Windows in production environments. That is engineering malpractice, in my not-so-humble opinion.)
You can also limit the actions in the Menubar through Vision→Client Events→Menubar in the project browser. At one point, I had a client setup where the exit was available in the Menu bar, but you had to use a password for it to execute using Shutdown-Intercept.
Thx Phil. Indeed: why the possibility to exit at OS is shown only if the vision session is un full screen? In windowed mode, there is not. It would not be possible to manage that by an option show/no show?
In windowed mode, there is always the outer frame supplied by the OS, so you cannot stop exit. The exit on the login page is superfluous. (And I bet Alt-F4 works in all cases.)
With a custom Xsession, no matter how you kill Vision, you safely log out.
There is a Windows Kiosk mode, though it appears to come with a grab bag of random restrictions, including only working on one very particular 'flavor' of Windows, apparently, so your mileage may vary.
Anything else we do in software can be defeated by a sufficiently malicious/bored/intrepid operator. You need your OS to be helping you with this; even if you managed to hide the OS framing and any other visible means to exit the session, Ctrl + Alt + Del is an OS level interrupt and allows the person in front of the computer to terminate any process.
Thx all. It is a touchscreen, so no keyboard, no USB connected.
And I need to go the standard login in order to manage the password expiration. Perfectly managed via Ignition, also with internal user source.
@Phil: the point is exactly the opposite -> in fullscreen mode it is needed to avoid the exit to OS. Honestly I thing that having the possibility to stop the exit hiding the cross would be beneficial for "normal" operator.... The matter is not protecting the system from malicious approaches (different), indeed the operator can click by mistake and jumping out. That should be avoided
If you use thin clients with remote desktop services, I don't remember the exact terminology but you can specify that a single app is launched with no desktop environment. I've set this up on thin clients managed by ThinManager with Wonderware in the past, and I'm guessing it would also work with Ignition but have never tried it. If a user does exit out of the app (or even if it crashes), it would automatically close the session and re-launch the session and app.