Windows Forum

Ask something
Discussion Locked

Intermittent login script failure.

0 helpful
11 replies

by hegemon

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
One of the businesses my company provides support to has recently changed the user logins from personal name based to position based ie the sales manager now logs on to the NT4 domain as sal00. All the workstations are running NT4 with service pack 6a. However, since the changeover, some of the staff's login scripts do not process, leaving them without mapped drives etc. Is there a way to force the login script to run every time?

11 replies

by nt/2000/sql

Try to login with one of the accounts having trouble and run the login script manually ( using this path : \\\netlogon\

by mhinckley

Could be a couple of things. If the script never runs for a user it's probably not in the user profile - and if you just created a lot of new accounts, that's something to look at first.

Could also be that you have replication problems (assumingPDC\BDC setup) and the script doesn't exist in the netlogon share of the server that authenticates the user. Make sure the script is in the netlogon share. But, as above, this would explain the problem only if the script never executes for the user.

If the problem is intermittant for a user, meaning sometimes it runs and sometimes it doesn't it's possible that replication is faulty, that the script is on some BDCs and not others, and the script runs depending on which BDC authenticates his logon.

Good luck.

Mike

by calves

With a similar problem, my solutions was to copy the batch onto the ...scripts\import folders on all the DCs. It seems that it was a synchronization problem. Now, whenever I make a change to the batches, using a batch file and a xcopy command, I copy the batches from a folder on my PC, straight into all the DCs. Thus avoiding to rely on the synchronization.

Good luck!

by bmiles

Local user probably have not been set to local machine administrator or whatever level the old account was set for at the local computer.

by mark_taylor

Check the eventlog, sometimes there may be timing issues with switched networks and you will get a netlogon error in the eventlog, the fix for this is to disable some parameter on the switches - not sure what though. (whatever it is called it speedsup the switches synchronisation time with the PC.)

This discussion is closed to new replies.