RE: ADC AD --> EX5.5
- From: "Patrick Adamek" <PatrickAdamek@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 21 Oct 2005 03:35:05 -0700
"Patrick Adamek" schrieb:
>
>
> "Patrick Adamek" schrieb:
>
> > Hallo,
> >
> > im Unternehmen ist die Frage aufgekommen, wie der ADC feststellt, auf
> > welchem Exchange 5.5 Server er für einen neuen User im AD einen "Platzhalter"
> > anlegt. Also ich habe eine 2003 Domäne und mehrere 5.5 Standorte. So ergeben
> > sich viele UserCA, welcher als Windows Entpunt die Domäne haben und als 5.5
> > Endpunkt den Standort. Wie findet der ADC nun heraus, auf welchem 5.5er er
> > den Account anlegt? Macht er dies über die Option ELagacyExchangeDN der
> > UserCA Eigenschaften? was ist wenn ich dies ausschlate, würde es dann nicht
> > mehr funktionieren?
> >
> > Vielen Dank für die Antwort.
> >
> > CU
> > Patrick
>
> Hallo Nochmal,
>
> habe gerade gesehen, dass der Haken "Create objects in location spezified by
> Exchange 5.5 DN" bei all unseren User CA´s icht gesetzt ist. Daher ist dies
> wohl nicht das Kriterium, nach dem der ADC entscheidet auf welchem 5.5er
> Server er das Objekt anlegt. Weiterhin meine ich auch das dies nur für das
> anlegen des Users auf 2003 seite ist. so habe ich zumindest die Hilfe
> verstanden.
Also... ich war ja voll auf dem falschen Dampfer...
Ich habe folgendes gefunden:
Even though the Mailbox/Distribution List connection agreements to all sites
except Seattle are non-primary to Exchange, if you create a new User in
Business Unit\User and create a mailbox on an Exchange 2000 server, ADC will
still create a new mailbox in the Exchange 5.5 directory. This is because ADC
can use the home server to determine in which site the mailbox should be
created. However, this does not apply to Exchange 5.5 mailboxes created in
Active Directory. For Exchange 5.5 mailboxes created in Active Directory to
replicate, the connection agreement must be marked as Primary Exchange.
und noch dieses hier:
You can configure multiple connection agreements in the Exchange
environment, and this is particularly important when you have multiple sites
and require two-way replication. Imagine, though, that the Active Directory
source for those connection agreements is the same container or
organizational unit. This means that as each connection agreement replicates
from Windows to Exchange, it tries to export the same objects (such as groups
and contacts) to each site. If all connection agreements were allowed to
create a new group or contact object in their own site, duplicate objects
would be created. By clearing this check box on all connection agreements
except one, the "non-primary" connection agreements replicate only changes to
objects that already exist in the Exchange directory. New objects including
Group and Contacts are not replicated through this connection agreement. Then
the connection agreement that is marked as primary is responsible for
creating new objects in Exchange 5.5, and that server can replicate the new
objects to all other servers using Exchange 5.5 directory replication.
For each container that you want to export, there should be exactly one
primary connection agreement. If you do not have any primary connection
agreements, you will be missing objects in the Exchange 5.5 directory because
ADC will not create any new objects if it cannot find an existing match and
cannot determine which site the object belongs in. If you have more than one
primary connection agreement exporting the same containers, you risk creating
duplicate objects in the Exchange 5.5 directory.
When replicating from Windows to Exchange, the Primary option works slightly
differently than the Primary Exchange to Windows option.
The "This is a primary Connection Agreement for the connected Exchange
Organization." option only takes effect if ADC cannot determine which site an
object in Windows belongs to. For mailbox-enabled users, ADC uses the
msExchHomeServerName value to determine the site. For Contacts and
mail-enabled Groups, ADC uses the legacyExchangeDN value.
If you do not have Exchange 2000 installed, or if you use the ADC version of
Active Directory Users and Computers (maildsmx.dll), and then you create a
new Contact or mail-enabled Group in Active Directory, the legacyExchangeDN
value does not get set. In this case, only a connection agreement marked as
"Primary Exchange" will create a new object in Exchange 5.5. If you use
Active Directory Users and Computers to create a new mailbox-enabled user in
Exchange 5.5, the application determines which sites the user will be
exported to, and a list is displayed.
If you create a new mailbox-enabled user in Active Directory, and create the
mailbox on an Exchange 2000 server in Site A, then even if the connection
agreement for Site A is not a primary Exchange connection agreement, ADC will
still create a mailbox in Site A to match the mailbox in Active Directory.
This is because ADC can use the msexchHomeServerName attribute to determine
which site the mailbox should be in and can make a logical choice to create
the mailbox in the correct location. This behavior does not apply to new
mail-enabled groups or Contacts created in Active Directory because they are
not implicitly associated with a particular site the way a mailbox object is.
Also, this behavior does not apply for mailbox-enabled users created in
Active Directory with mailboxes on an Exchange 5.5 server. For the Exchange
5.5 server to be listed in the available servers list when the mailbox is
being created, there must be a primary Exchange connection agreement
exporting the organizational unit the user is created in to the site where
you want to create the mailbox.
Zusammengefasst ist zu sagen, dass der ADC die 5.5 Platzhalter in der
AG/Standortes des 200x HomeServers des Users anlegt. Dies gilt jedoch nicht
für AD Benutzer mit 5.5er Postfach und Kontakte sowie Verteiler.
Kann mir jedoch jemand vielleicht dies hier erklären?
If you do not have Exchange 2000 installed, or if you use the ADC version of
Active Directory Users and Computers (maildsmx.dll), and then you create a
new Contact or mail-enabled Group in Active Directory, the legacyExchangeDN
value does not get set.
In this case, only a connection agreement marked as "Primary Exchange" will
create a new object in Exchange 5.5. If you use Active Directory Users and
Computers to create a new mailbox-enabled user in Exchange 5.5, the
application determines which sites the user will be exported to, and a list
is displayed.
Wieso wird der legadyDN nicht gesetzt und was soll der rest bedeuten?
Also, this behavior does not apply for mailbox-enabled users created in
Active Directory with mailboxes on an Exchange 5.5 server. For the Exchange
5.5 server to be listed in the available servers list when the mailbox is
being created, there must be a primary Exchange connection agreement
exporting the organizational unit the user is created in to the site where
you want to create the mailbox.
Hier verstehe ich auch nicht, was passiert.
Danke für die Antworten!
Gruß
Patrick
.
- Follow-Ups:
- RE: ADC AD --> EX5.5
- From: Patrick Adamek
- RE: ADC AD --> EX5.5
- Prev by Date: Re: Wieviele IP's für OWA, RPCoverHTTPs und SMTP
- Next by Date: RE: ADC AD --> EX5.5
- Previous by thread: Re: Fehlende Reiter in AD Benutzereigenschaften
- Next by thread: RE: ADC AD --> EX5.5
- Index(es):
Relevant Pages
|
