Pulling Hair OUT! - Logon Scripts w/ 2000 Server - HELP

[tbettend]

I really don't know what I am doing wrong here. I hope someone will be able to shed some light. I have a Windows 2000 Server machine. Two drives, C, D. On D:, I have a folder called Data, shared as datashare. Under the Data folder is all the good stuff (data). I will set permissions on these based on who is allowed to access each. I want to have each client logon to the Domain, which is successful. I want to map (from the server) each client P: to \\seatecserver\datashare
I have tried this using the Profiles under the User properties in AD, not working. I created a logon.bat also with the line NET USE P: \\seatecserver\datashare - Still nothing. Does not process the script it seems. I can map the drives manually fine, but want to do from server. Some 2000 clients and 98 Clients, two iMacs. Anybody with any knowledge please help. Seems like this should be simple as anything but seems to be kinked somehow. Thanks for all help. I will post as to what is the problem, with your suggestions.

[CJK]

1. Is the script in the right directory and can the workstations access this script through the netlogon share on the server?

2. For each user or group do you have the script specified to run?

[EvilCabbage]

Okie dokie.

Under 'user manager for domains' on the Win2k server, go to the 'profile' section, and in the login script line, stick in something like: login.bat

Now, the login.bat file needs to live in the following directory on the Win2k server:

c:\winnt\system32\repl\import\

Now, Im not sure if thats the directory letter for letter (it might have \repl\scripts\import) but that will get you running.

This is all negated if you are using ADS, but wont apply here.

Let me know if you need anything else dude.

[imaeditedbysowulo]

Make sure that the logon.bat file is also present in the above mentioned directory on any of your BDC's as well.

[futuretech]

You could also try putting the logon.bat in a shared folder that all clients can access, and from the clients browse to that folder and run the bat file to see if it works. If it does then that eliminates the batch file as a problem.
If it does it is a matter of if the permissions and path in the profile are OK.
The logon script in W2K runs very fast, and is not like NT4 where you actually get to see the file run, it does not always show the DOS box as the script runs.

[silencio]

1) I'm guessing that your calling the batch file from the users Profile/Logon script as opposed to through group policy. If so, your calling it based on the \\server\share or by simply the filename if your script is in the \\server\sysvol\scripts folder? Any file that lives under sysvol gets replicated to all domain controllers by default. Netlogon maps to sysvol\scripts for backwards compatibility with 9x/nt boxes. If this is correct, check the NTFS permissions on the folder/share/file.

2) The other way to do this is through Windows 2000 Group Policy. If you click on the container for your domain/properties/group policy/edit, you can specify startup and shutdown scripts for your computers or logon/logoff scripts for your users. If you dont want to run the scripts on all computers in the domain you might want to create a new container for those users/computers that you want the script applied to.

For instance, the default domain policy applies to all machines/users in the domain. You don't want your servers running this script so, create a new container (OU) to store your normal users/computers in. Edit the group policy of that OU to apply the scripts to only those machines.