Windows Forum

Ask something
Discussion Locked

Login script not working

0 helpful
2 replies

by jorge.gonzalez

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

We have a multiple sites accross the country with a single W2k DC running DNS, Exch 2K for all the sites.

I am having problems running the logging scripts. could this problem be caused by not having a individual DC on each site. what will be the best way to deploy such setup.

ALL the workstations are Win2k Pro.

any input is appreciated.

2 replies

by joseph moore

I would expect that you would have problems if your clients are going over the WAN to authenticate from a single DC.
Yes, a DC in each remote location is a good thing. They can call be part of the same domain, if you don't want to deal with multiple child domains. Set up a DC in each site, and make the remote DC in its own Site (with the workstations at that site in the Site).
Replicate the logon scripts amongts the DCs and make sure that users at the remote sites pull from their local DC (just put the name of the logon script in the user profile; do not specify a DC name.) Users start their authentication against the DC in the Site they are in first. So, if the logon scripts are on all DCs, then your users should authenticate and run scripts from their local DC.
That should improve performance.
Also, set up the DCs as Bridgehead servers, pointing to the central DC at the home office.

hope this helps

by jorge.gonzalez

Thanks Joseph for your comments.

I have finally added a DC on another site, everything seems to work ok (replication etc.), but loging scripts are not working.

i tried two ways with and with out specifying the server name, but it dooes not work.

the loging script i am testing is to map a netwok drive:
net use l: \\local-server-name\updates

but the map letter is not listed.

any comments?

TX

This discussion is closed to new replies.