Login Scripts

[aidan]

We have a windows 2000 SP4 domain controller and 10 X XP Clients. Non of
the clients will run the login scripts. The scrips are in the correct
directoy and specified on the user accounts in AD. Any assistance would be
much appreciated.

Thanks in advance

Aid

 

[Pegasus \(MVP\)]

We have a windows 2000 SP4 domain controller and 10 X XP Clients. Non of
the clients will run the login scripts. The scrips are in the correct
directoy and specified on the user accounts in AD. Any assistance would be
much appreciated.

Thanks in advance

Aid

Since things don't work for you, you need to be
highly specific:
- Where exactly are the login scripts located?
- What exactly is the name of one of them?
- Where and how exactly did you specify the logon
script in the user profile?
- How do you know that the script does not execute?
For example: Does it execute if this batch file is
stored in the Startup folder of a workstation?
@echo off
\\YourServer\netlogon\SomeScript.bat

 

[aidan]

Thanks for the responce.

the scripts are stored in the
C:\WINNT\SYSVOL\sysvol\FORECOURTS.local\scripts

folder on the server.

I know they dont work because we dont get any drives mapped. If the script
is run manually from the machine then this works ok. They are specified on
the user account on the profile tab. Not tried putting one in the startup
folder of the workstation but I suspect this will work.

 

[Pegasus \(MVP\)]

It is irrelevant in which folder the logon scripts are stored in.
What is important, however, is that the scripts are stored
in the "netlogon" share.

Your deduction that the scripts don't work because
shares don't get mapped is inconclusive. There are
several other reasons why shares don't get mapped.
An instruction such as

echo %date% %time% %ComputerName% %UserName% >> c:\test.log

would be far more conclusive.

To "suspect" (your word) that the scripts will work when
invoked from the Startup folder is inappropriate during
the troubleshooting phase. Suspicions and assumptions
could make you walk right past the real cause. You must
really take the time and test it.

I note that you did not answer any of my questions about
exact names etc. I can think of several reasons why an
incorrect syntax can cause your script to fail.

 

[aidan]

The scripts are in the netlogon share of the server. The scripts are named
using the user names ie john.bat. I will test the startup folder and let
you know.
thanks again..

 

[aidan]

I have tested the startup folder and only one of the drives specified in the
login script gets mapped this is the same as when the script comes from the
server. I then mapped the drives using the NET USE command and they all
mapped ok.

 

[Pegasus \(MVP\)]

Hmm. . . You are now telling us two things:

a) When the script runs from the Startup folder, it maps only one
drive.
b) When the script runs from the Netlogon share, it does the same thing.

This tells us two things:

1. The script DOES actually run, regardless of what you claim.
2. There is a problem in your script.

I think it is time for you to have a close look at your logon script:
- Remove the "@echo off" line
- Place a Pause command at the end of the script

With respect to your initial claim that the script does not run:
When trouble-shooting, never assume anything. Add some
very basic diagnostics to your script. A simple Pause statement
at the beginning of the logon script would have revealed straight
away that the script does run.