Discussion Locked

NT Logon Scripts not running

0 helpful
22 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm a Network Admin for a school division and we have created three different logon scripts that do a variety of things from mapping drives to installing software. We run all NT servers and 95/98 workstations. The problem we have is that the logonscripts don't run sometimes, but other times they do. I've verified that the script is on all domain controllers. Here's where it gets wierd...all scripts had read for the everyone group permission which is what it should have, but the scripts only ran about 10% of the time. After many hours of looking for a solution I decided to make the scripts permission full control. After this change, it began working 80% of the time. It makes no sense! I've asked our other netowrk admin and our network engineer and we are all stumped. I've got big points for someone who can help!

22 replies

by ejsotillo

Hi all, you should know that by default login scripts recide in the:

c:\systemroot\system32\repl\export\scripts

folder on your PDC, if you were to make changes on your login scripts, this is the place that you should look into and also make changes to. On the BDC's and proper NT workstations side, you have to make sure that you will be "replicating" to the "imports" folder following the same UNC placed previously:

c:\systemroot\system32\repl\imports\scripts

you also have to make sure that you create an "account" name whatever you want that is set to:
part of everyone's group, password never expires, allow all logon hours and make sure is part of the domain backup operators group, this account will be known as the replication user account. On each computer that will be using replication you have to make sure that directory replicator "service" is running, this should be configured as start automatically on server manager. let me know if this helps.

by nwboothe

I've checked all the obvious things liek replication, permission, profiles, accounts, etc.

by nwboothe

I've checked all the obvious things like replication, permissions, accounts, profiles.

by Former member

Questions:
Do you have the same logon scripts on EVERY DC?

On the same client, does it run sometimes and sometimes not?

by nwboothe

I have three scripts per site, 18 sites, all scripts are on all domain controllers. There are about 20 domain controllers.

Failure to run is not client specific. I sat a one workstation logged on and off 3 or 4 times and the script ran. I logged on a 5th time and it didn't. I continued to try and the script still would not run anymore. Wierd!

by anticnz

You have probably tried this .. and it is a non-technical fix :-)
Have you rebooted all the logon servers ??
Sometimes works.

by alanb

If you are SURE that scripts are being replicated to all BDC's (esp closest to user)...

One method I have found helpful is to check to see if the user can run the script once logged in. Simply map to the NETLOGON share of the nearest DC (eg \\Domain Controller\NETLOGON)and try running (double-click)the appropriate script from there.

If you can see the script but cannot run it as the user, then there must be a permission problem.

If you cannot see the script you must have a replication problem.

If neither of these is true, and you can run the script as above, another IMPORTANT setting is to enable "Run Logon Scripts Synchronously" in the Default Computer property of Policy Editor.

This ensures the Logon Script runs in its entirety before launching the users shell, which otherwise can cause logon scripts to partly work.

Good Luck and keep us all informed of progress.

Alan

by bill.parks

First, I'm assuming replication is in full effect as you've noted above.
Are you running policies for your workstations??? If so, under default computer-Network-System Policies Update-Remote Update, check that box and use Automatic Update Mode. Also check the box that says Load Balancing. By default, 9.x machines always try to reach the PDC for scripts, policies, and authentication. Selecting this box allows the machine to act as NT, try to reach any DC, not just the PDC. Quirky, I know, but it's true.
If you do not use policies, take a couple machines, open regedit and follow the steps below:
1. Open the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Update folder. You may see a key for LoadBalance. If you do, change it to "1". Ifyou don't, add a value of DWORD names "LoadBalance" and give it a value of "1". Essentially, follow the same format of DWORD Update, the should already be in the folder. This will enable the LoadBalance feature I mentioned above with policies.
Let me know how it worked.

by gregory w. smith

I'm going to guess here since you didn't point out the error in the earlier post. Scripts are EXPORTED from the repl\export\scripts on whatever machine (not necessarily the PDC) to repl\import\scripts on the logon servers.

if you look in the NETLOGON share on each server, do the scripts show up there? Because if you are using the PDC's EXPORT directory and do not have scripts in the IMPORT directory, there is your problem.

by gregory w. smith

Also, technically you do not require replication for the logon scripts to work.

They *do* need to be in each \\DOMAINCONTROLLERNAME\NETLOGON share. (And you *do* need the read permission; it won't hurt to give NTFS FULL CONTROL to EVERYONE as long as they only have READ access through the share.

The best thing I can say is open up the NETLOGON share on EVERY DC and confirm that the files are physically present.

by subbz

Your explanation rules out scripts replication or permission problems to NETLOGON share. Check out if the script gives any errors. (For example, say a drive already exists and the script tries to overwrite, or any such error.) If a script encountersany errors it stops further execution (usually). Try to observe this. This may help.

by subbz

On the same machine where the script is not getting executed, try running individual commands in the script. This will give u a clear picture asto why the script is not getting executed completely.

by kralljd

Are you running 98SE or 98?
Does this happen on 95 and 98 machines?

The following fixed me up last year when I was having similar problems... with 95

PSS ID Number: Q150589
Article last modified on 06-30-1999

SYMPTOMS

A Windows 95 workstation logging on to a Microsoft Windows NT domain controller
may not process the centralized logon script batch file.

CAUSE

This problem can occur if multiple Windows 95 workstations try to run a logon
script file (for example, the Winlogon.bat file) located on a single Windows NT
domain controller at the same time. The first time a Windows 95 workstation
access the logon script file, it does so in Read/Share/Exclusive mode. All
subsequent accesses to the file are done in Read/Share/Deny None mode.

The exclusive requests fail when another workstation has the file open in
Read/Share/Deny None mode.

RESOLUTION

This issue is resolved by the following updated file for Windows 95, and later
versions of this file:

MSNET32.DLL version 4.00.951 dated 4/18/96 60,416 bytes

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows 95. An update
to address this problem is now available, but is not fully regression tested and
should be applied only to computers experiencing this specific problem. Unless
you are severely impacted by this specific problem, Microsoft does not recommend
implementing this update at this time. Contact Microsoft Technical Support for
additional information about the availability of this update.

This issue is resolved in Microsoft Windows 98.

by kralljd

Can you send me a copy of one of your logon scripts that you are having problems with?

This discussion is closed to new replies.