Prev: Exchange 2003 updated to SP2, WM devices broken
Next: Exchange 2010 reverse lookup
From: Starbuck on 21 Jan 2010 18:54

EX2007, SVR2008.

For the most part, the OAB works, and it works well.
If I add a new account, it usually shows up the next day
after the 5am rebuild.

But occasionally we will add a new employee and the OAB simply will
not show their name. Right now I have a user account that was created
several weeks ago and no matter what I try I cannot get this users
name to show up in the OAB. On any client.

The "Hide from exchange address lists" check box seems
to have no effect. I can check the box, wait 48 hours, uncheck
the box, wait another 48 hours... makes no difference.

"get-offlineaddressbook | update-offlineaddressbook"
....also seems to be useless in this case.

I have found in the past, that when certain employees have a name
or two missing from their address book that I could delete their local
..OAB files, then download an new copy of the OAB, and the missing
names would appear. But today, this also has no effect.

So once again, I have an employee's name that simply will not appear,
no matter what I try.

Does anyone have any ideas/tips/tricks on how I can force
the OAB to behave? Maybe some suggestions on how to analize
the OAB close up to see what its doing? Is there a log file somewhere
that might indicate what the problem is?

At this point, any suggestions would be most welcome.

As always, Thanks in advance, you guys/gals are much appreciated.



*$
aa#2290
From: Ed Crowley [MVP] on 21 Jan 2010 20:02
Have other new names showed up since the one you're asking about?

The OAB can be in two places, either a system public folder, or web
services. Which ones are generated depends on the settings of the OAB.
Also configuratble is the public folder server that is used for public
folder distribution. Outlook 2007 prefers to get the OAB from web services
but older versions of Outlook need the OAB in the system public folder.
When the OAB is generated, it writes the OAB to the system public folder (if
configured), and to a set of files used by web services. Outlook downloads
the OAB from the source it's able to use as discussed before, and the
version of the OAB (2, 3a or 4) corresponding to its version.

You should check:
- which forms of distribution your OAB is configured for
- whether the appropriate form of OAB is being generated and stored
- whether the appropriate versions are being generated for the Outlook
clients you support
- whether the OAB is configured for a valid public store
- whether the system public folder has valid replicas on all public stores
- whether the client is downloading the correct version

The first place to look is the event logs of the server on which the OAB is
configured to be generated. You should see information messages there that
report on what is being generated.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Starbuck" <Starbuck(a)BogusDomain.com> wrote in message
news:djnhl5hkj0s43gg4q1iod4q022mnicisvr(a)4ax.com...
>
> EX2007, SVR2008.
>
> For the most part, the OAB works, and it works well.
> If I add a new account, it usually shows up the next day
> after the 5am rebuild.
>
> But occasionally we will add a new employee and the OAB simply will
> not show their name. Right now I have a user account that was created
> several weeks ago and no matter what I try I cannot get this users
> name to show up in the OAB. On any client.
>
> The "Hide from exchange address lists" check box seems
> to have no effect. I can check the box, wait 48 hours, uncheck
> the box, wait another 48 hours... makes no difference.
>
> "get-offlineaddressbook | update-offlineaddressbook"
> ...also seems to be useless in this case.
>
> I have found in the past, that when certain employees have a name
> or two missing from their address book that I could delete their local
> .OAB files, then download an new copy of the OAB, and the missing
> names would appear. But today, this also has no effect.
>
> So once again, I have an employee's name that simply will not appear,
> no matter what I try.
>
> Does anyone have any ideas/tips/tricks on how I can force
> the OAB to behave? Maybe some suggestions on how to analize
> the OAB close up to see what its doing? Is there a log file somewhere
> that might indicate what the problem is?
>
> At this point, any suggestions would be most welcome.
>
> As always, Thanks in advance, you guys/gals are much appreciated.
>
>
>
> *$
> aa#2290

 | 
Pages: 1
Prev: Exchange 2003 updated to SP2, WM devices broken
Next: Exchange 2010 reverse lookup