Re: Hidden recipient visible in OAB

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

You could have the unicode files however if you are unable to access the v4
folder for whatever reason the outlook clients logic will go backwards to v3
and then v2. Can you attach a zip here with the exports so I can look at
them. Something is definatly going on as you should not be having that
problem.

Dgoldman
"Danny" <Danny@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:62AEF93C-CB39-4815-89EF-25E37234682F@xxxxxxxxxxxxxxxx
Hi Dave,

I manually checked all the domain controllers and they all have the
attribute set correctly.

When I did a OABinteg (getabinfo) export of the v2, v3 and v4 OAB I
noticed
that only the v2 version holds the hidden recipients. The strange thing is
that my outlook 2003 sp2 client runs in Unicode mode so it should use the
v4
version (we use E2k3 SP2). The OAB file are the u-versions (uanrdex.oab,
udetails.oab etc). I additionally have tried the key to force the download
of
v4 on the client (after deleting the OAB files), but it makes no
difference.

I have not yet tried to turn up the logging on the Exchange server to get
more information.

Kind regards, Danny


"Dave Goldman [MSFT]" wrote:

From the sounds of it you might either be having an ad replication
problem
or pulling stale data. You will want to turn up diagnostic logging for
MSExchange\OAL Generator and regenerate the OAB. Once you do this look
for
the 9117 event and see which domain controller OABGen is using. Then from
there you can use ADSIEdit and look at that user on that domain
controller
to make sure that the changes have replicated there
(msExchHideFromAddressLists is stamped on the user). Then create a brand
new
profile and make sure that you are downloading the new OAB and see if the
changes are there.

You can also use this query in LDP to search the domain controllers for
the
objects that have that attribute set to see if there are any differences
between domain controllers:
(&(msExchHideFromAddressLists=TRUE)(objectClass=User)).

Dgoldman

"Danny" <Danny@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C50590F-148A-4777-A0B4-306DBC36937B@xxxxxxxxxxxxxxxx
Hi,

At a client we have an Exchange 2003 server cluster. Recently they
deployed
Outlook 2003.

The strange thing is that the hidden recipients are all visible in the
offline address book. They are not visible in the default GAL. The
default
OAB points at the default GAL. The various users I checked do have the
msexchhidefromaddresslists attribute set to "true" on all domain
controllers.
Some users are already hidden for months to years. Also if we try a new
user,
do a Galsync, OAB sync it is still shown in the OAB.

Anyone got an advise?

Thanks in advance,

Danny den Hartog





.

Relevant Pages

  • Re: Accessing OAB from domain other than the domain where Exchange
    ... Before reading your post I used the OABInteg test to compare the access from ... It just seems to be the public folder where the OAB ... I will test by adding the host to a client computer directly and seeing ... For example, from my experience, when Outlook tries to contact a Global ...
    (microsoft.public.exchange.admin)
  • Re: Offline Address Book download error
    ... If you have an Outlook 2003 client and Exchange 2007 it will ... attempt to connect to the public folder store and download the V4 OAB (if ... Since this is Exchange 2007 only the Outlook 2003 client will make a direct ...
    (microsoft.public.exchange.connectivity)
  • Re: Accessing OAB from domain other than the domain where Exchange 2003 lives
    ... Yeah I initially thought that it might be a GC problem but the client ... It just seems to be the public folder where the OAB ... For example, from my experience, when Outlook tries to contact a Global ...
    (microsoft.public.exchange.admin)
  • Re: Accessing OAB from domain other than the domain where Exchange
    ... It just seems to be the public folder where the OAB ... I will test by adding the host to a client computer directly and seeing ... I noticed than when the clients are not in the same domain as the Exchange ... For example, from my experience, when Outlook tries to contact a Global ...
    (microsoft.public.exchange.admin)
  • Re: Hidden recipient visible in OAB
    ... But why would the OL client refer to older OAB versions while I am able to ... I manually checked all the domain controllers and they all have the ... The strange thing is that the hidden recipients are all visible in the ...
    (microsoft.public.exchange.admin)