logon script issue!!!

[RetrogradePAK]

i have an NT domain with a PDC and BDC , all the clients have WinXP Pro SP2. Having the following issue with users related to logon script:

1. For some users it works every time they log on
2. For some users it sometimes works and sometimes does'nt
3. For some users it does not work at all

 

[WhoKilledKenny]

Sounds like your logon script is not replicating between your two Domain Controllers... So your clients are only running the script when the DC that has the script is the one doing the authentiction.
On both of your domain controllers make sure the script is present. Script should be located in C:\Winnt\system32\repl\import\Scripts You should see your LogonScript.bat file on both servers. If not copy it from one to the other in the location above. NT file replication was always a PITA.
Also make sure the Scipts folder is being shared. A quick way to do this is to UNC to the server and look for a share called NETLOGON.
Eg. \\PDC01 Do you see a NETLOGON Share? if Yes, Open it. Do you see your logon script there? if Yes, server is ok. If no NETLOGON Share, that's the issue - the scripts directory is not shared as NETLOGON. If yes to the share, but no to the script being there - just copy script into the NETLOGON Share.

Also Check:
In UserManager select a user account that is not working. On the profile tab of the user properties make sure the name of the logon script is present.

 

[RetrogradePAK]

well i have the script at both the PDC and BDC and exactly where you mentioned but the problem remains, the only solution i have is to copy the script of the user's desktop and teach them to run it every time they dont see the shared drives.

Oh forgot to mention that the script is mainly being used for mapping drivers

 

[WhoKilledKenny]

Make sure the script does the following when mapping drives.

Net Use x: /delete
Net Use x: \\servername\sharename

Ive seen issue where clients already have a drive mapping and the script fails to map the share. By deleting any instance of the drive you wish to map, insures that the second command that maps X: works.

I'm sure you already thought of that but, since I can't see your code I thought I would throw that out there.

 

[RetrogradePAK]

thanks for the tip really appreciate this. I mentioned that for some users the script sometimes does not work so they do not see any drive mappings...

anyway will try what you mentioned and let's see what happens

 

[Gareth1978]

If you want to see if the problem is only when a specific server is validating the login at the desktop PC open the command prompt and type echo %logonserver% this will tell you which server has validated the login

**One day, I will find a question that no one else has answered........and will also know the answer to it ! **