• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 194
  • Last Modified:

Dividing Active Directory between two sites

I need conceptual help and guidance for splitting an Active Directory domain into two sites.  Here is the situation.  I've inherited an AD with one domain.  We have Exchange Server, a file server, and a web server, as well as the DC.  My manager told me last Thursday that she needs information on what is necessary to move part of the staff to another location, which means the network will have to be split.  I don't know what all is involved with doing this.

Would you experts help me by steering me in the right direction as to what would be needed to split our network or even if it is feasible.  What makes matters worse is that this is a temporary situation since I believe we all will be moving to a new location where everyone will be on the same subnet again.

We have all company files on a central file server.  There is an Exchange server with three stores (management, group1, and group2).  We host our own websites in-house.  We have a 3/4 T1 coming in.

Some specific questions.
1. How should the networks be linked so that people in site 1 can access files in site 2 and vice versa.
2. How do I go about getting AD to recognizae site2
3. How should email be handled--We use outlook 2003 connected to Exchange server

I would really appreciate your help in this.  I'm not sure what approach to take.  Thanks.

- Reggie
0
rpcr
Asked:
rpcr
1 Solution
 
Brian PiercePhotographerCommented:
Yiu don't neccessarily have to "split" Active Directory. All you have to do is take your current AD and define two sites. You can do this by defining at least one subnet for each physical location and then assign these to  logical sites in Active Directory Sites and Services. The two phisical sites would need to be connected - site-to-site VPN for example and users could contuniue to use the AD resources in much the same way as they do now.

If you want to add more resilliance you should place a domain controller in each site and also configure this and a global catalog, DNS and DHCP server. This would automatically replicate with the existing DCs and would provide resilliance. Users would normally log on to and be authenticated by their own DC reducing intersite traffic, but could automatically use the remote DC in the event of a problem.

Exchange could also continue to be used as at present, or you could add a second exchnage server if your needs warrent it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now