Rob Nicholson
2007-05-03 15:18:48 UTC
We've currently designing and building a pilot AD infrastructure and my
attention has turned to logon scripts. The issue of running logon scripts
asynchronously is still an issue as we're likely to map drives in the logon
script.
On NT 4, we had to set the RunLogonScriptSync registry setting manually in
the login script to cause Windows XP to wait until the logon script had
executed before loading the desktop/running the application.
This registry setting still works fine in AD when you specific a logon
script against the user on the "Profile Tab". The example logon script just
does this:
@echo off
echo Master logon script here.
pause
AD group policy makes the manual setting of RunLogonScriptSync redundant we
there is a policy setting to do this. This works a treat. Enable the setting
and Windows XP waits until a key is pressed during logon before the desktop
is displayed.
But I'd like to be able to use logon scripts against the group policy. This
will allow use to customise them for the various organisational units etc
etc.
So I've set-up an identical logon script against the domain policy. At first
I didn't think it was running but then noticed the "Run logon scripts
visibly" and turned this on and my domain logon script ran as expected.
Except Windows XP didn't wait for the domain logon script to finish before
displaying the desktop. It waited for the user profile one, but not the
domain one.
Is this a known quirk or is there another way of getting Windows XP to wait
until the domain logon scripts have executed?
Thanks, Rob.
attention has turned to logon scripts. The issue of running logon scripts
asynchronously is still an issue as we're likely to map drives in the logon
script.
On NT 4, we had to set the RunLogonScriptSync registry setting manually in
the login script to cause Windows XP to wait until the logon script had
executed before loading the desktop/running the application.
This registry setting still works fine in AD when you specific a logon
script against the user on the "Profile Tab". The example logon script just
does this:
@echo off
echo Master logon script here.
pause
AD group policy makes the manual setting of RunLogonScriptSync redundant we
there is a policy setting to do this. This works a treat. Enable the setting
and Windows XP waits until a key is pressed during logon before the desktop
is displayed.
But I'd like to be able to use logon scripts against the group policy. This
will allow use to customise them for the various organisational units etc
etc.
So I've set-up an identical logon script against the domain policy. At first
I didn't think it was running but then noticed the "Run logon scripts
visibly" and turned this on and my domain logon script ran as expected.
Except Windows XP didn't wait for the domain logon script to finish before
displaying the desktop. It waited for the user profile one, but not the
domain one.
Is this a known quirk or is there another way of getting Windows XP to wait
until the domain logon scripts have executed?
Thanks, Rob.