|
Hi
We are having the opposite problen, i.e. we need to keep the application (notepad or whatever) running after the script closes.
The really funny thing is that the script behaves differently depending on whether it was invoked (1) through group policy or (2) manually; in (1) all applications called from the script close when the script is closed by the user (there is a progress window that the user can close by clicking OK); in (2) all applications remain active (which is what we want).
The win32 specification quoted earlier on in this thread doesn't seem to explain the (1) scenario... but I read somewhere that the GPO thing starts a WSH session in which the login script runs and I am guessing that closing the script also closes the WSH and everything running in it.
| 
