"Joe Blow" <joe@xxxxxx> wrote in message
> "Richard Mueller [MVP]" <rlmueller-nospam@xxxxxx> wrote in
> message news:umFIdSOcJHA.1704@xxxxxx
> Definitely not logged locally, he said he logged in, got the error, I went
>> The behavior suggests the user logged in locally and not to the domain.
>> Is that possible? Or was the domain not available and he use cached
>> Richard Mueller
>> MVP Directory Services
>> Hilltop Lab - http://www.rlmueller.net
> over to his box and showed him how to manually run the script and it
> worked fine.
> Seems like I read of a method to force the login script to wait until the
> network is up/active prior to running. Does that ring a bell? I do have
> the script assigned via GPO in AD.
A delay was required in Windows 95/98, but not since. By default logon
scripts run with a full user token (representing group memberships), even
though a limited token is used afterwards (due to UAC). I'm not sure if this
applies here (as no permissions are required to retrieve objSysInfo.userName
other than authenticated user), but here is a link discussing why drives
mapped in a logon script cannot be viewed and how to fix:
Basically, the logon script can map the drives but the user cannot view
them. Or the logon script prompts for permission and the user doesn't see
One fix is a *.wsf file that basically runs the logon script as a separate
task, so they run in what is called UAP mode. There's a good example in the
link. The other fix is a group policy setting, but I think it only applies
to Administrators. Let us know if this helps.
If you want to try a delay, simply insert the following in the VBScript
This pauses for 1000 milliseconds. I used to use 100 milliseconds in Win9x.
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net