Logon script running to late

We have a problem with our logonscript on windows xp computers.

When a 2000 computer logs on, the script is running before the desktop
starts.

When a XP computer logs on, the script is running After the desktop
start. This gives problems with some settings from the script.

I already set the policy Enable run scripts synchronously.

Any ideas?

I am not sure what your script does -- but can you run the script as startup
script instead of logon script?

--
Mike
Microsoft MVP - Windows Security

"ehebben" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> We have a problem with our logonscript on windows xp computers.
>
> When a 2000 computer logs on, the script is running before the desktop
> starts.
>
> When a XP computer logs on, the script is running After the desktop
> start. This gives problems with some settings from the script.
>
> I already set the policy Enable run scripts synchronously.
>
> Any ideas?
>

I am having the same problem! Our logon script maps 6 network drives.
And the end result of its delay is that one of the drive mappings gets
skipped (their home directory). It's set up in the user account to
connect H to their home directory, but it doesn't do that
automatically. So what we ended up doing is creating an additional
script to map H that we set in the Group Policy to run at logon (as
opposed to having the logon script indicated in the user account
settings). Of course, that solution works best when you only have one
login script for everyone. Did you have your logon script set through
GP, or is it indicated in each user account?

The logonscript is set in de policies. So everyone has the same
logonscript.

Melissa schreef:

> I am having the same problem! Our logon script maps 6 network drives.
> And the end result of its delay is that one of the drive mappings gets
> skipped (their home directory). It's set up in the user account to
> connect H to their home directory, but it doesn't do that
> automatically. So what we ended up doing is creating an additional
> script to map H that we set in the Group Policy to run at logon (as
> opposed to having the logon script indicated in the user account
> settings). Of course, that solution works best when you only have one
> login script for everyone. Did you have your logon script set through
> GP, or is it indicated in each user account?

Mike,

I cannot run the script as startup script. Our script sets some user
dependend settings.
Startupscripts are not running under the useraccount, so these settings
can´t be set.

How did you specify home path on the profile on the user account? Did you
enter e.g. \\server\users\%username% where server is name of the server and
"users" is name of the share? Were permissions set correctly for user
account on the "users" share?

I do have this set up in few different environments (with Windows Server
2003 and Windows XP client) and it works without any problem.

--
Mike
Microsoft MVP - Windows Security

"Melissa" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ps.com...
>I am having the same problem! Our logon script maps 6 network drives.
> And the end result of its delay is that one of the drive mappings gets
> skipped (their home directory). It's set up in the user account to
> connect H to their home directory, but it doesn't do that
> automatically. So what we ended up doing is creating an additional
> script to map H that we set in the Group Policy to run at logon (as
> opposed to having the logon script indicated in the user account
> settings). Of course, that solution works best when you only have one
> login script for everyone. Did you have your logon script set through
> GP, or is it indicated in each user account?
>

Can you be more specific what the script is setting? I guess that will be
the only way for me the help you out...

Does the script work if e.g. users brows to the script (e.g.
\\domain.com\sysvol\domain.com\scripts\script.bat) -- does the script
executes?

--
Mike
Microsoft MVP - Windows Security


"ehebben" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
Mike,

I cannot run the script as startup script. Our script sets some user
dependend settings.
Startupscripts are not running under the useraccount, so these settings
can´t be set.

Mike,

The script is running. But after the desktop starts.
All commands in the script are executed and are oké.
My only problem is the redirect from the my documents folder.

The registry key from this folder is:
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\Shell
Folders\Personal

The command in the script is:
WSHShell.RegWrite
"HKCU\Software\Microsoft\Windows\CurrentVersion\Ex plorer\User Shell
Folders\Personal", "\\sv0002ei\home\" & Gebruiker
Gebruiker is a variable with the username

We also use a logout script in which this setting is redirected to
d:\my documents\
This is done because of notebook user who work connected to the and
off-line.

When a user logs in, the registry key for my documents is set in the
registry. I checked it with regedit.
But the my documents folder on the desktop keeps redirecting to the
wrong lokation.

Hallo,

In the GPO you can force the logon script to behave as under W2K instead of
XP, the time to logon on will be a bit longer
(ComputerConfiguration/AdmTemplates/
System/Logon/AlwaysWaitForTheNetwork.)but it can help you with your issue.
Another cause can be spanning tree/port fast on (cisco) routers they allow
packets only after 30 secconds have past since the first network request.

Cheers
"ehebben" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
Mike,

The script is running. But after the desktop starts.
All commands in the script are executed and are oké.
My only problem is the redirect from the my documents folder.

The registry key from this folder is:
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\Shell
Folders\Personal

The command in the script is:
WSHShell.RegWrite
"HKCU\Software\Microsoft\Windows\CurrentVersion\Ex plorer\User Shell
Folders\Personal", "\\sv0002ei\home\" & Gebruiker
Gebruiker is a variable with the username

We also use a logout script in which this setting is redirected to
d:\my documents\
This is done because of notebook user who work connected to the and
off-line.

When a user logs in, the registry key for my documents is set in the
registry. I checked it with regedit.
But the my documents folder on the desktop keeps redirecting to the
wrong lokation.

Hee thanks,

That is working. I allready dit set this in a policy, but at the wrong
ou. Stupid me.
But, now the script is working fine. Sometimes the desktop is started
before the script is finished. But i put the setting at the start of
the script, so it's no problem anymore.

Thanks for your help.