cjewett
asked on
2003 servers at remote sites
I have 3 remote locations currently and they all connect to HQ by means of T1 lines. I would like to eliminate some of the traffic that is being pulled over these lines by putting a server at each of the remote sites. My goal would be to have DHCP, DNS, Document Redirection, User Authentication and so on happen on local server as opposed to pulling it accross the link. My questions are:
What role should these servers be?
How do you tell the users at that site to get group policy and authentication from the local server as opposed to the main DC?
What role should these servers be?
How do you tell the users at that site to get group policy and authentication from the local server as opposed to the main DC?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
yes, make it a DC before you configure sites and services...make sure its replicating also =)
YOu don't 'have' to do the config at the rmeote site...I usually bring up the server locally and promote them...to make sure their are no comm problems.
YOu don't 'have' to do the config at the rmeote site...I usually bring up the server locally and promote them...to make sure their are no comm problems.
ASKER
So it would be ok to promote it while it has an IP address in the HQ subnet?
Then I move it to the proper subnet when I move the server?
Is there anything special I have to do for the configuration of DHCP, WINS, DNS for it to funcion properly at the remote site?
Then I move it to the proper subnet when I move the server?
Is there anything special I have to do for the configuration of DHCP, WINS, DNS for it to funcion properly at the remote site?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So when you are doing the dcpromo /adv you do it at you HQ or at the remte site?
If you do it at the HQ, make sure it has the IP address of the remote site, or if you have a fully routed network, which it appears that you have, just enable remote desktop or make sure you have a pair of smart hands on site, and do it at the location. The beautiful part about IFM is that you do not have to have connectivity to the rest of the domain.
ASKER