Discussion Locked

logon script.bat

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
We are using NT SVR 4.0
We've currently have changed our logon script with setting up for mapping drives for the users. It was working from before, but now for some reason after we made the changes it don't seem to work anymore. It is set on the PDC under c:\winnt\system32\repl\import\scripts.

It is also set as export scripts too. Please help.

Thanks

12 replies

by perry

The location is correct but make sure that in user manager the users profile is using the right script name

by admin-stuart

From your add-on comment about synchronization, I assume you are running at least one BDC. It would help to see a copy of the script, but I'll take a stab at one common problem and say that if you aren't successfully mapping at some users PCs, check to see if the drive letter assignments are conflicting with existing drive letters already in use on the particular user's PC. Otherwise, let me take a look at your script. Thanks.

by sphynx

In order to correct this. Copy all your login script to your BDC under :\winnt\system32\repl\import\scripts.

Once it work try to enable directory replication on all bdc so you won't manually copy every changes you made.

Hopes it work.

by bcheng1877

Thankyou for your help. Tested it out and works better than cutting butter with a hot knife.

by curious_george

Most of the guys above have hit all the possible reasons.

#1 Replication may not be working, but since it was in the past it probably is ok, just turn off all of your BDCs leaving only the PDC running and see if the script works. If it does work replication is not working, fix that. Also note if the old script is still running when users logon replication is not working. I'd suggest making a dumby script that does something like this just to test replication functionality:

@echo logon scirpt is working properly.
pause

Then you will be able to determine if it is being run by all the workstations.

#2 The name of the script has changed and profiles have not been updated to reflect this change. save the old script and rename the new revised versio to the same name and location as the previous one.

#3 The script may not be writtin correctly. I'd suggest having it reviewed by a competent scriptor or posting it here. Some of us here, including myself are quite expert in thisarea.

Good luck.

by bcheng1877

I've tried to add it in the bdc from the recommendation of another user and it worked out, thanks for your help though.

This discussion is closed to new replies.