Logon script not running unless Admin

[Monkey36]

It's just come to my attention that one of our Windows 2000 (professional) machines does not execute the domain logon script when the user logging on does not have administrative rights on the machine.

However, if I log on as a non-admin user and start up the command prompt, I can successfully call the script from there.

I just don't have any idea where I should be looking to attack this problem, I've been having problems googling for the specific situation.

Can anyone give me a push in the right direction?
All help much appreciated!

Cheers,
Monkey.

 

[Monkey36]

Hmm.. I think actually that it is all of the W2K machines that are not executing the logon script unless the user has admin rights.

I'm sure this wouldn't have escaped my notice until now! But I can't think what I could have changed.

This is not a problem on any of the Windows XP clients.

Ayone with any pointers??

Cheers,
Monkey.

 

[bhunji]

is it trying to create or modify files that users don't have permission to?

 

[Monkey36]

No, it's not. I've further convinced myself of this because if I wait for the logon to complete and then open a command prompt, I can run the script successfully from there. Also, if the same user logs on at a Windows XP machine, then it runs successfully.

??

 

[bhunji]

are the paths correct? if you are calling something in c:\windows in XP, for win2000 normally its in C:\winnt...

have you tried adding a pause to your script to see if it will display an error message when run?

 

[Monkey36]

No, the script is on a network share on the server, so it's the same from any PC. It's a batch file - executed but not displayed. It must just not be running at all, as it will leave a log file to say its executed and re-map network drives.

??

Confused!

 

[bhunji]

It might be looking locally on the machine, instead of the server for the batch file, or items the batch file calls...

You could try copying the batch file locally to a 2000 machine, in the same path as it is on the server, and see if the domain policy then executes it...

Are you able to temporarily display the batchfile to debug it?

If possible you could create a new computer ou and toss a test machine in and apply the script as a policy, but don't hide the script and toss a couple pauses in so you can see what its doing...

 

[RITec]

Is this being called from a domain group policy?
are the computers on the same subnet?
What is the script trying to do?

I have had some instances where bhunji suggestion works very well. try haveing the script copy to the local temp directory and then run it.

RITec