I have just built a test windows SBS 2003 domain and the logon script will
not run for a domain user unless they are given local admin rights on the
computer. I have found from trial and error that this only happens on
Windows XP not 2000. The logon script simply maps a network drive. Once I
am logged in I can file browse to the script and run it no problem. No error
is generted after the failed mapping. Yes I have the policy set to always
wait for the network at computer logon and startup. Does anyone have any
ideas about this one?

In news:9470C741-5D5B-44E3-87E3-A056D154AD07@microsoft.com,
Travis <Travis@discussions.microsoft.com> typed:
> I have just built a test windows SBS 2003 domain and the logon script
> will not run for a domain user unless they are given local admin
> rights on the computer. I have found from trial and error that this
> only happens on Windows XP not 2000. The logon script simply maps a
> network drive. Once I am logged in I can file browse to the script
> and run it no problem. No error is generted after the failed
> mapping. Yes I have the policy set to always wait for the network at
> computer logon and startup. Does anyone have any ideas about this
> one?

What's in the login script?
You might want to try posting in m.p.windows.server.sbs.....

Seems like an xp service pack 2 issue. Please run the file manually on the
computer once and chose allow allways?

Michael Evanchik
www.michaelevanchik.com

"Travis" wrote:

> I have just built a test windows SBS 2003 domain and the logon script will
> not run for a domain user unless they are given local admin rights on the
> computer. I have found from trial and error that this only happens on
> Windows XP not 2000. The logon script simply maps a network drive. Once I
> am logged in I can file browse to the script and run it no problem. No error
> is generted after the failed mapping. Yes I have the policy set to always
> wait for the network at computer logon and startup. Does anyone have any
> ideas about this one?

It's not a service pack 2 issue. I tried using sp1 and sp2 with the same
result. The logon script is:

net use i: \\test.local\Inter-Office

I don't think the logon script is the problem. In the parameter of the
logon script I have the output going to a text file. When a domain user logs
in no file is created. When a local admin logs in the file is created, even
if the file doesn't exist it will still write to a file to say the file
doesn't exist. Like I said it works fine in 2000, so I am assuming that this
is an XP issue.

"Michael Evanchik" wrote:

> Seems like an xp service pack 2 issue. Please run the file manually on the
> computer once and chose allow allways?
>
> Michael Evanchik
> www.michaelevanchik.com
>
> "Travis" wrote:
>
> > I have just built a test windows SBS 2003 domain and the logon script will
> > not run for a domain user unless they are given local admin rights on the
> > computer. I have found from trial and error that this only happens on
> > Windows XP not 2000. The logon script simply maps a network drive. Once I
> > am logged in I can file browse to the script and run it no problem. No error
> > is generted after the failed mapping. Yes I have the policy set to always
> > wait for the network at computer logon and startup. Does anyone have any
> > ideas about this one?