Discussion Locked

Planning MS infrastructure/environment

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

i have been asking some questions on the microsoft technet forum regarding "proper" planning and implementation of MS environment and i got some good answers but i am curious to find out how other people tackle following issues:

let?s say that I am deploying a brand new setup for a company of 100 users. i have two offices (main and branch) and i have exchange server in the datacenter. from the architecture perspective my options are:
1. using single domain, place domain controllers at each of the three location and change firewall rules to allow communication between three dc server.
2. same as above but not have a dc at the datacenter just make sure that exchange can talk to a dc at the main office
3. same as above but use lan-to-lan vpn to protect communication between dc servers
4. create multiple domains
5. something else...

let's say that money is not an issue. what i am interested in is "white paper"/"industry standard" on how to architecture ms based solution. thanks in advance...

7 replies

by kjell_andorsen

Your hypothetical setup in many ways resembles the environment I'm currently administrating. You didn't mention what kind of bandwidth you have for the connections between the sites, but if cost is not a major issue I would definitly keep a DC at each site. Also I'd make sure the DC at the datacenter would be a GC, and preferably a DNS server just to mkae Exchange extra happy.

Creating permanent VPN tunnels between the sites is a good idea if you don't have dedicated leased lines.

by signup

let's say i have full t1 lines at the main office and at the branch. how does that affect whether or not i run the traffic between three locations through VPN tunnel? can sync traffic between three DCs be encrypted? is there need to do so or am i to paranoid?

by kjell_andorsen

If the lines are not private leased lines that connect the sites together without access the internet I would definitely use VPN for security. Any company data that goes out across the internet should always be encrypted especially sensitive information like DC replication. Provided there are no other problems with routing your DCs should not have a problem with the replication data being encrypted.

by the listed 'g man'

Three Exchange Servers
3 Global Cat DC's
Further 3 DC's for fault tolerance
Dedicated DNS Servers, 1 each site
Dedicated DHCP Servers, 1 each site
100 M bit Fiber Lines connections between sites
1Gbyte LAN connections
Dedicated File Servers

DR Site
Replicated data to copy DR site. DR site can take over if needed

by signup

Why stop at that? Why not hire Santa Claus to administer my network and put tooth fairy in charge of security?

On a more serious note, why run 3 domains? Wouldn't that be an administrative burden? Run trusts?

by the listed 'g man'

Depends on what Exchange setup you are running. If 2003 then ideally you would like a GC at every site. If 2007 then the need is not so important. 2007 uses the multimaster replication of windows domains opposed to exchange sites.

A domain can have many GC's depending on need.

by signup

microsoft has an article describing how to encrypt dc-to-dc replication traffic:

http://support.microsoft.com/kb/254949

they say that in this case IPSec is used in transport mode - so the original IP headers are not encrypted. would this type of solution be considered a bad idea? and i am really interested in an "industry standard" and not what MS (or any other vendor) suggests what can be done.

This discussion is closed to new replies.