Users Logging in at different Sites -Need Help

[PreviousPoster]

My company just opened a new office. We are in a Win 2k3 Native Mode domain. The company totals 4 offices, 3 being remote offices, and 1 being our headquarters. The PDC Emulator is located at headquarters, along with the other DC- and all FSMO roles are shared among the two. Each remote office has been set up as an Active Directory Site, on a different subnet (192.168.10.0, 192.168.20.0, etc...) Each DC is a Global Catalog server. All servers are 2003 R2. In ADUC, I have different OU's set up for the different offices (example: OU=CHARLESTON, OU=TAMPA, etc...). In each root level OU, are sub OU's for Users, Workstations, Groups, etc... All objects specific to their site, are sorted accordingly.

Of the three remote offices, I just set one up last week. It has a DC, and this office has been set up as an AD Site, in a different subnet from the other offices. In this remote office, I will have users from the other remote offices, periodically coming in to do work- along with Users who will specifically work from this office. At each Site, there is a different logon script, which maps them to their local network's CIFS shares.
Here is an example of the script I am using at each location. I have named each logon script (BAT file), the name of the DC (Logonserver) at their respective site. All Login Scripts have been applied at the SITE level. This one below is named MYCOMPDC04.BAT:
#begin>
CALL %LOGONSERVER%.bat

NET USE /DELETE I:
NET USE /DELETE K:
NET USE /DELETE P:
NET USE /DELETE R:
NET USE /DELETE T:
NET USE /DELETE U:
NET USE /DELETE X:

NET USE I: \\NASSERVER\Vol2 /persistent:yes
NET USE K: \\NASSERVER\vol1 /persistent:yes
NET USE P: \\NASSERVER\Jobs /persistent:yes
NET USE R: \\NASSERVER\Jobs2 /persistent:yes
NET USE T: \\NASSERVERAccounting /persistent:yes
NET USE U: \\NASSERVER\home\%username% /persistent:yes
NET USE X: \\NASSERVERXerox\%username% /persistent:yes

#end>

Ok so from above you can see that I have a login script, where the execution of it becomes dynamic based on which server they log into. So theoretically, if a user from headquarters comes to the remote office I just set up, and logs in to a workstation, they should receive THIS remote site's login script. The problem is that this is not working! Arghhhhh.

When a user from headquarters logs into a machine in this new remote site, not only does he gets his Headquarter's Login script (and not the site at which he is at), when he goes to a command prompt and run the SET LOGONSERVER command, it displays the DC at Headquarters (and it should be the DC at THIS remote site).

Everything in Sites and Services is set up correctly, down to the Subnets. DNS SRV records are in place and accurate. I ran the nltest /sc_reset utility from a workstation at the new remote office, and it still shows headquarter's DC.

Now, of course when I log in to a workstation at that site as a user in that site, the SET LOGONSERVER shows the site's DC, the site's logon script processes correctly and gives him the site specific mappings, etc...

What could be going on here? I would think regardless of what site they are logging into, they should be authenticating to that site's DC, and processing that site's GPO's. Please help!!

[PreviousPoster]

I didn't understand if you ment that they bring their own computer to the other site or use an existing?

The variable %LOGONSERVER% is not really something that you should trust since I also noticed that it's not always this value changes when it should...

Maybe you can alter your script to check the IP or something instead?