General discussion


AD Strucuture

By swaithe ·
Hi All

Background Information
At present I have two offices one located in Canada the other in the Caribbean. Each office has its own domain and its own Active Directory structure. The offices are connected by a VPN. A two way trust relationship is configured between Barbados and Canada. Barbados office has a 768Kbps internet connection, Canada office (Main office) has a T1 internet connection. There are also some home offices located throughout Canada which also connect to the Canadian office using VPN connections. These home offices all have T1 internet connections. The Canadian office has 35 persons, Barbados 15 persons. Each office is presently running Exchange 2003 and Windows 2003.

Future Network
I am seeking to integrate the offices. I am thinking of implementing a simple network. Where I would have one domain, and two sites.

Do I need to have a domain controller in Barbados.

Do I still need to have two Exchange servers.
Should a Global Catalog server be located in each office.

Is there a way to implement a backup link to main office if internet connection fails in Barbados.

What is the necessary Internet connection to implement this setup without comprising bandwidth.

Does trust relationships utilise more bandwidth that using Active Directory sites and services.

Do I have to implement both of these services or just one.

Could someone guide me on how I can implement this as I am not sure?

Thanks very much for your help

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by p.j.hutchison In reply to AD Strucuture

A DC in Barbados would help a lot otherwise logging in would be very slow. A Global Catalog would also help.

I do not know how to do a backup link unless you need a second line.

You should configure each site as seperate sub nets, then you can configure when AD data is updated (instead of the default 5 mins) to reduce bandwidth usage.

No, trusts do not take up bandwidth.

An ADSL or faster (256K) 'always on' type of link would suit it. T1 should suffice (not sure what speed T1 is)

See MS site for case info and technical docs.

Collapse -

by BFilmFan In reply to AD Strucuture

When you say they have their own domain, did you mean they already have an AD forest in existence at each location? Or that the domains are NT?

The simple answers are:

DC's both locations and both need to be GC's. I agree that a single domain will work, but you may want to consider a root domain for security purposes. If you put in an empty-root, peer domain, you would need 3 DC's.

Exchange servers both locations.

2 AD sites.

Internet connection speed varies. What's the utilization on the WAN link now? Is that 768K CIR? Or is it capable of bursting to that rate?

Collapse -

by swaithe In reply to AD Strucuture


Thanks for your responses. How can you measure what the utilization on the WAN link is at the moment.

How about DNS how should this be configured in an environment like this.


Collapse -

by Hector Ramos In reply to AD Strucuture

While the one domain topology would work ... consider the possibility of joining the two independent AD trees into a larger Forest.

Regardless of which way you go, you will need to keep DC's in both locations. Keep the Exchange servers at each location as well.

What you have (768k on one end and 1.5M on the other), is sufficient for the number of users you are talking about. You will need to be proactive in your site configuration; since, a badly configured replication schedule will overpower a T-1 with ease.

I would not break the trusts you've set up, remember that trusts within AD are implicit and routed through the parent domain/tree. You will need to keep your trust in case the home office drops off the line.

This is an extensive redesign. I would recommend that you spend considerable time on the front end of the project. Every minute spent planning will save you five minutes of troubleshooting a failure.

Good Luck.

Related Discussions

Related Forums