RE: OAB Replication

  • From: "Michael B. Smith" <michael@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 8 Jun 2005 21:41:31 -0400

NSPI (GAL) lookups already use the "closest" GC.
 
OAB (any PF change) requires a recreation of the profile. Let's see,
from my book:
 
The process of accessing information from a public folder, because of
the referral mechanism, is fairly complicated; but very versatile. It is
designed to give a user multiple efficient paths to access replicas of
any given public folder. If a particular replica should not be
available, then another (hopefully identical) replica is chosen from
which the user will retrieve information.

The process goes like this:

*         A user requests data from a public folder

*         The Information Store (IS) returns a list of all the replica's
that hold that data (for example, see Figure 6-1)

*         The IS requests the Routing Engine (RE) to assign a cost to
each replica

*         Replicas that have infinite cost are discarded by the IS

*         Replicas whose connectors are known to be down are discarded
by the IS

*         The IS sorts the remaining replicas by cost within the current
Routing Group, and then by cost outside the current Routing Group

*         If the user is on the same server, then the IS directs the
request to that server

*         If there is an available replica in the current Routing Group,
then the IS directs the request to that server (if there are multiple
choices at the same lowest cost, then the client picks a server at
random from the available choices)

*         If the available replicas are in a different Routing Group,
then the IS directs the request to a server in the Routing Group with
the lowest cost (if there are multiple choices at the same cost, then
the client picks a server at random from the available choices)

*         If there are no replicas available, the user is denied access

From the client messaging application perspective, it requests
information about where to access a public folder, and the application
is returned a list of direct access locations, of which it can choose
any.

All the complexity is hidden within the Information Store and Outlook.

A user will, by default, reuse the same selected server each time a
particular public folder is accessed. 
...
For more detailed information on public folder referrals, see Microsoft
KB 273479.


________________________________

From: Harding, Devon [mailto:dharding@xxxxxxxxxxxxxxxx] 
Sent: Wednesday, June 08, 2005 4:40 PM
To: [ExchangeList]
Subject: [exchangelist] RE: OAB Replication


http://www.MSExchange.org/


So if a user in another AG is running Outlook 2003 w/cached mode
enabled, they'll use their local Exchange server for GAL/OAB if I choose
to replicate to all?

 

________________________________

From: Michael B. Smith [mailto:michael@xxxxxxxxxx] 
Sent: Wednesday, June 08, 2005 4:18 PM
To: [ExchangeList]
Subject: [exchangelist] RE: OAB Replication

 

http://www.MSExchange.org/

"Should" is an interesting question.

 

They aren't by default.

 

In Exchange 2000 and 2003, they are public folders. So if you replicate
them and you recreate a user's profile, they will use the "closest" PF
server after that.

 

________________________________

From: Harding, Devon [mailto:dharding@xxxxxxxxxxxxxxxx] 
Sent: Wednesday, June 08, 2005 4:09 PM
To: [ExchangeList]
Subject: [exchangelist] OAB Replication

http://www.MSExchange.org/

We have 20 Exchange servers in 12 Admin Groups.  Should the Offline
Address Book (Version 2 & 3a) be replicated to all Exchange servers?

 

Devon Harding

Windows Systems Engineer

Southern Wine & Spirits - GSD

954-602-2469

Other related posts: