logon scripts issue

[Mark Radant]

Hi all

I run a logon script which is defined at the GPO level . The logon
script is a .bat file that launches a kixtart script .scr.

I have been trying to have the .scr script launch an application
(like notepad.exe) that should remain open on the user desktop even
after the script ends.

Up to now what happens is that Notepad is executed but it closes when
the logon script (.scr) ends.

At script level, I have tried all the possible combinations of the
various Run, Shell, Start.

It looks like there is a sort of rule somewhere that says that
anything that is run from within the login script terminates when the
login script terminates.

Does this have anything to do with some A.D. / GPO setting and can it
be modified?

thank you!

 

[Herb Martin]

I run a logon script which is defined at the GPO level . The logon
script is a .bat file that launches a kixtart script .scr.

I have been trying to have the .scr script launch an application
(like notepad.exe) that should remain open on the user desktop even
after the script ends.

Have the first script run it "Start /Separate notepad"

In theory /Separate is ONLY supposed to be for running 16-Bit Windows
programs (i.e., Win 3.1) in a separate "memory space" instead of in the
default
shared WOW.

BUT, in practice when running from a batch file, "start /separate" works for
starting graphical programs as independent windows AND not wait on them
to complete.

 

[Carl Chipman]

I'd usually do that kind of thing with this line:

ReturnVal = WshShell.Run("cmd /K " & CommandLine, 1, True) in VBScript.

the "cmd /K" should launch your notepad app in another process...