RE: ADC Question...

  • From: "Mulnick, Al" <Al.Mulnick@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 15 Feb 2005 09:05:04 -0500

A few things to keep in mind when dealing with the ADC.

1) Keep it simple; this is a simple tool and any attempts to make it do
complex things will make you sad <G>
2) ADC Connection Agreements (CA's) and ADC instances are separate entities;
Numerous CA's can be run from the same instance.
3) Each CA needs an AD target to write to; you'll always use two-way sync
for the CA's when dealing with Exchange
4) Each CA is going to need a writeable copy of the Exchange 5.5 directory;
writeable copies are at the site level in 5.5
5) Each CA is capable of using it's own credentials for the situation you
6) Keep it simple; this is a simple tool and any attempts to make it do
complex things will make you sad <G>

You will likely need one instance of the ADC depending on bandwidth.  You
will need at least one CA for each site in the 5.5 ORG and you will not need
to have the individual NT domains upgraded *depending on your migration
plans*.  What I mean by that, is that if you don't want to have the 5.5
accounts migrate to the 2003 HQ domain, then you'll want to upgrade the
existing domains into the forest.  In which case, you'll want to upgrade
those to 2003 before installing the ADC just to make it easier.  You don't
have to, but it often makes things simpler and less chaotic. 

It's recommended to use as few domains as you can when deploying Active
Directory.  That's because there's not a lot of particular benefits to
multiple domains vs. sites and OU's. A few, but many don't need those
particular benefits when deploying.  

Depending on the overall migration strategy, you would then deploy the ADC
accordingly remembering the rules above. 

Does that help?


-----Original Message-----
From: Chris Wall [mailto:Chris.Wall@xxxxxxxxxxxxxxxxxxx] 
Sent: Monday, February 14, 2005 5:29 PM
To: [ExchangeList]
Subject: [exchangelist] ADC Question...

Hello all,

   Have a quick ADC design question for you all before running in a test


Environment Info:

   I am currently running Exchange 5.5 in one Exchange Organization with 3
different Exchange sites.  Each Site is in a different NT 4.0 Domain, which
are connected by trusts to our Corporate Domain...

   We have currently upgraded the 'Corporate' domain to Win 2003 AD.   This
'Corporate' 2003 AD domain has the internal Exchange 5.5 server that acts as
a bridgehead with x.400 and Directory Replication Connectors to the other
two Exchange 5.5 Sites.  Each of those trusted Domains have only 1 Exchange
5.5 server in their Exchange site.



   When configuring the ADC in the Corporate AD domain, I assume that I can
only connect it to the local Exchange 5.5 Site (Since AD is not running in
the other two domains).  

1. Should each site have its own ADC connector for Replication?  If so, that
means that each NT 4 Domain must be upgraded to 2003 AD first...  

2. Or can I setup one ADC connection to the local 5.5 site that contains the
Bridgehead?  If so, I assume this ADC connection will update Corporate AD
with 'contacts' for accounts in the remote Exchange 5.5 sites.  Will this
cause any issues with Public folder permissions since the 5.5 accounts will
appear as contacts?


If #2 is a viable option, and I hope it is, then what happens when I have
migrated all Exchange 5.5 accounts, public folders, contacts, etc to the new
Exchange 2003 servers...  Will I need to keep the Exchange 5.5 Bridgehead
running until I can upgrade the other 2 domains to AD so they can have their
own ADC's and not have to rely on updates from the Exchange 5.5 Bridgehead?


Kind of confusing, but none of Microsoft's books or white papers really
address this scenario.  They all seem to assume that all Exchange 5.5 are in
an AD environment prior to introducing the ADC.


Thanks for any information or thoughts...




Chris Wall

Sr. Exchange Administrator



T - 919.460.3236

F - 919.468.4889

Global Knowledge Network

LEARNING. To Make a Difference


List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking: Leading
Network Software Directory:
No.1 ISA Server Resource Site: Windows Security
Resource Site: Network Security Library: Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
al.mulnick@xxxxxxxxxx To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: