Your domain controllers are all NT4, correct? All of your Win2K Servers are only member servers of your NT4 domain?
Ok. So, now you want your users located in each location (don't call them sites, since Sites are only established when Active Directory is running, and you can't have AD with NT4 PDC/BDCs running) to get their login scripts from the local Win2K Server.
You can do this, but you need to keep in mind that the Win2K Servers are not configured as domain controllers. Since your domain is NT4, you can't have 2K Servers as Domain Controllers. You would need to upgrade to Active Directory, run all 2KServers as Domain Controllers, then you could set up AD Sites and have local users use the local AD DC for authentication and to get their login scripts.
The workaround is to configure each user in User Manager for Domains on the PDC (or PDCs if you have multiple NT4 resource domains). Set up a share on each Win2K Server at each physical location that you have users at. Put thelogin scripts that users at that location will use in this shared folder.
Then in User Manager for Domains, select the users at these remote locations, select Profile, and in the Login Script Name box, put the full UNC path to the remote Win2K Server share name and login script file.
For example, say you have a remote office in Suburb. There is a Win2K Server there called \\SUBURB1 and you have 2 users who work there, BOB and JENN. These users are all members of the NT4 domain DOMAIN. All users use the login script called LOGIN.BAT.
So, make a share on \\SUBURB1. Call it Scripts. Copy LOGIN.BAT from your PDC's Netlogon share to \\SUBURB1\SCRIPTS.
Then open User Manager for Domains. Select BOB. Click Profiles. In the Login Script Name box, put in \\SUBURB1\SCRIPTS\LOGIN.BAT
click OK.
that is it. hope this helps