Logon Script not executing

[lhatwwp]

Hello,

I have created a VBS script and placed it in the correct folder i.e. \\server\SYSVOL\domain\Policies\{####}\USER\Scripts\Logon

If I browse to that location and double click the file the script executes and the drives are mapped. However if I reboot the machine and logon the script does not execute, no drives are mapped.

I did some searching around and found a KB article that advises how to force the policy to run even on a slow connection, which in this case does not apply as the machine is on a 100MB wired connection to the server. Anyway I made the suggested change and still not luck.

So I'm stumped as to the reason this script is not being executed. Any suggestions?

TIA,
Lou

 

[58sniper]

If it doesn't apply, why make that change?

When you run gpresult, does the policy show up as applied under the user settings?

Pat Richard MVP

 

[lhatwwp]

Hi Pat,

Yes the policy shows up under the user settings. Is it possible that a local drive E, F. G or H on the workstation could be preventing the script from executing? I'm not mapping to any of these drives but I know in the past I have seen settings like "First network drive = F:" So is it posible that the workstation having a drive F: would cause a problem?

Lou

 

[58sniper]

First network drive is an old Novell thing.

I don't see where any of that would apply.

I always delete an existing drive mapping for that drive first, then apply the new mapping. That way, even if they had something mapped there, you'd get the drive mapped from your script.

Pat Richard MVP

 

[lhatwwp]

Interesting discovery. I issued the command gpresult from the client and the logon script executed... the drives are mapped. Now when I logon the script seems to execute. Was the client caching and old policy?

Possibly I should hav issued the gpresult command on the client in the first place? Sorry... just seems foreign too me. I thought all of this resided on the server.

 

[58sniper]

No, you shouldn't have to issue that command remotely to get it to work. But somethings come into play here. First, on many wireless networks, login scripts don't fire because a wireless connection is established after that.

Second, there could be some latency or other reason that the machine didn't pick up the policy. In the future, try running a group policy results modeling against that machine to see if the policy is getting applied.

Pat Richard MVP

 

[lhatwwp]

Hi Pat,

I've stumbled onto a new problem. I am attempting to connect a second workstation to this server. This client workstation is identical to the first client, same hardware, software, etc.

When I issue GPRESULT the result is:

INFO: The policy object does not exist

Any idea?

Lou