Quote:

I wonder why you use the "console" version (KiX32.exe) and not the "consoleless" WKiX32.exe since you are hiding the console anyway. BREAK has been kinda messed up in WKiX for a while too.



Because I want the user to be logged off it they terminate the script. WKiX doesn't do that. I have 2 different versions of the script, one using kixforms with no console display, and one without, where the console is set to alwaysontop in one case.
The one without kixforms is a fail safe for systems that kixforms.dll wasn't successfully loaded/registered on. The kixforms I've created are purely for looks, and not needed for the script to function.

A seperate script that has been put into a kixcrypt .exe package is loaded at the end of the logon script. One version with kixforms, one version that uses a console window. It sleeps in the background for 13 hours and 50 minutes, then pops up a message stating that domain logons are limited to 14 hours, and the user will be logged off in 10 minutes. The message displays a timer counting down from 10 minutes to 0. When the timer reaches 0, the script logs the user off.

For the version of it that uses the console... I don't have to worry about someone closing it, or ending the process, it will log them off, which is what is intended anyway. For the version without the console that uses a kixform, a user with local admin privileges can still terminate kix32.exe

Hopefully that explains it a little better.