Re: LdapSrvWeight in Exchange and DR Sites?

Tech-Archive recommends: Fix windows errors by optimizing your registry



km,

I'll echo a great deal of what Ace says - a smarter guy on this topic you're not likely to find.

I do agree with your creation of a site for isolating GCs for use by Exchange. So, in that regrard, the priority or the weighting doesn't really play much of a part. By that I mean if you create the site to contain the GCs for lookups and prevening added traffic to those DCs (such as authentication), it will make it easier to track performance of the Exchange architecture, query against the GCs, and to make decisions on when to upgrade. As you well know, capacity planning in an Exchange environment is hugely important to sustained health.
---

Rick [msft]

This posting is provided "AS IS" with no warranties, and confers no rights.





-----Original Message-----
From: km
Posted At: Thursday, November 24, 2005 3:46 PM
Posted To: microsoft.public.windows.server.dns
Conversation: LdapSrvWeight in Exchange and DR Sites?
Subject: Re: LdapSrvWeight in Exchange and DR Sites?



I am referring to an Exchange site in AD...The creation of an Exchange site was recommended by Microsoft during our yearly "Exchange health check."

If the weight is not considered- why was it mentioned in the technet document I linked above?

I was confused about the necessity as well...

The concepts of sites in AD works- but it does not isolate traffic to/from particular DCs. We have DCs in a DR site with a priority of 2- and clients still authenticate against them.

THat being the case, we would like to remove any client traffic to/from the DCS in 1) Exchange AD site and 2) our DR site. OUr users should only authenticate with the DCs in the datacenter. Exchange should only use the DC/GCs in the AD Exchange site for Directory Access.

"Ace Fekay [MVP]" wrote:

> In news:D0EEDBEE-BE76-48C6-BDDB-A954DBFCD8D6@xxxxxxxxxxxxx,
> km <km@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
> commented about below:
> > So if I understand this correctly, my topology should be as follows:
> >
> > two sites- Datacenter and Exchange
> > two DCs/GCs in each site
> > Datacenter site has DCs with priority of 0 and weight of 50 Exchange
> > site has DCs with priority of 1 and weight of 100
> >
> > This will cause clients to ignore Exchange sites to authentication,
> > and Exchange to send DA requests to the DCs in it's own site at a
> > 2:1 ratio compared to the Datacenter site?
>
> First, there is no "Exchange Sites", unless you are using Exchange 55,
> but that isn't the case here. Exchang uses Routing Groups (formerly
> Exchange 55
> sites) and are just used to control how mail flows thru an
> organization, or in a design consideration when attempting to control
> who can access Public Folders, etc.
>
> Honestly if you have Active Directory Sites setup properly in AD Sites
> and Services with the correct subnet objects created and associated
> with the AD SItes you created, there is really no need to do this.
> This is more for controlling traffic to where they are going to go
> between specific DCs in one AD Site. If you have ALL of your DCs in
> one site with weights set to 50, then they will equally be used by
> Exchange at any given time, just as if you were to have left it alone in it's default configuration.
>
> Exchange is fully AD Site aware and will utilize that when choosing
> which Site in selecting which DC/GC to use. Make sense?
>
> Otherwise, maybe you may want to elaborate a bit more as to what you
> are trying to accomplish that simply creating an AD Site will not take
> care of by default?
>
> Ace
>
>
>
.



Relevant Pages

  • Re: custom address list?
    ... > Hi Ace. ... > the exchange accounts from the users OU to another OU, ... the OU example they give you is to control who can see the ... they can still see it thru the OWA. ...
    (microsoft.public.exchange2000.admin)
  • Re: Sites & Services - DSAccess w/E2K3 SP2
    ... I don't believe the firewalls are the issue as they are set to any-any among ... the all the DCs and exchange server. ... All the DCs replicate information in a mesh ... Immediately after upgrading to Exchange 2003 SP2, ...
    (microsoft.public.exchange.admin)
  • RE: Migrating from 2000 AD to 2003 AD
    ... Promote 2003 DCs ... If you've updated the domain schema when you installed exchange 2003 than ... > that is running on Windows 2000. ... Again people who've gone through the migration process can you ...
    (microsoft.public.windows.server.general)
  • Re: Active Directory FSMO, GC and Exchange Proper Setup
    ... Exchange server processors to 1 GC processor. ... The DSAccess Module in Exchange creates a list of GCs and DCs, ... DCs in all sites are eligible to be entered in this list (to a max of 10 I ...
    (microsoft.public.windows.server.active_directory)
  • Outlook client 2002 and 2000 are hang when restart DCs
    ... has atleast one DCs with GC role, The head office have two DCs (DC1 and DC2) ... There is only one exchange 2000 in Head office on MS ... Now when ever we restart any one DC either 1 or 2, ...
    (microsoft.public.exchange.admin)