If we use something like the start or cmd commands to start it off under a separate shell/process, it runs until the startup script finishes, at which point Windows seems to clean up any and all child processes of the script.
If we just run it, via our startup script (set via group policy), it holds the script open and the machine never makes it to the login prompt. The app uses a Timer to update the ip address, deepfreeze status, and clock every second, and it checks to see if a user has logged in and kills itself when it detects such a condition. This was to replace our previous information block, which was set statically at startup and actually embedded text into the background, with something a little more dynamic and functional.
I wrote a tiny C# app a while back that displays the hostname, ip address, imaged date, thaw status (we use DeepFreeze), current domain, and the current date/time, to display on the welcome screen of our Windows 7 lab machines.
0 kommentar(er)
