MS Exchange GAL and OAB not matching

We converted a client from a single Exchange 2010 box to a cluster, 2 CAS, 2 MB, 1 DAG. Ever since the conversion, some users do not show up in the GAL (they do if you do an advanced find, but not in the GAL list) if you use an OAB. As soon as I turn off the OAB, everything is fine. Turn on OAB and download it, they disappear. Catch is, this seems to only affect certain users. I have come up with  the reg hack to stop OAB download and use the GAL from the server, but I dont want to implement that for all users. I can log in with my account and all is well. Affected user can delete OAB and redownload and the issue returns.

Anyone seen this before?
LVL 7
BelushiLomaxAsked:
Who is Participating?
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
4) The MB Servers also have another OAB in C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB with a Mod date 4 months ago...Can I safely delete this one? - Yes you surely can ........ maybe some old OAB :)

Are the Outlook clients using Autodiscover if so they would pick the data from SCP \ OAB URL if not then they would be using PF .... so need to understand this.

Is the issue with all Users or just a few .... maybe then their Mailbox Database isnt pointing to correct RPCClientAccess server ? and the database is pointing to the OAB ?

- Rancy
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Turn on OAB and download it, they disappear - OAB issues
So users show up fine in GAL one OWA and Online mode .... right

Which is the Generation server .... does the OAB get generated fine on Mailbox server ?
Then you need to check that its copied fine to the CAS server .... FDS service is what copies the content from Mailbox to CAS and then makes available for end Outlook cache users.

Check for any events in the App log on both machines that can help.

- Rancy
0
 
BelushiLomaxAuthor Commented:
Rancy,
It does appear to be an FDS issue between the CAS and MB servers. Thanks...will update soon.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
It does appear to be an FDS issue between the CAS and MB servers. Thanks...will update soon - try restarting FDS on the CAS server and let me know :)

- Rancy
0
 
BelushiLomaxAuthor Commented:
OK, so I have confirmed the following and noticed other items too:
1) OAB generation in happy on the MB01 server
2) OAB is set to publish both web and Public Folder
3) OAB is successfully replicated to the CAS Servers. Verified by GUID and Mod date in C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB on CAS Servers. The GUID matches the GUID on the MB Servers.
4) The MB Servers also have another OAB in C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB with a Mod date 4 months ago...Can I safely delete this one?
5) In Public Folder Management, I have OAB version 2, 3a and 4 but when I click Update Content, it fails with a replication partner issue.

Meanwhile, cached still doesnt work and other methods do.
0
 
BelushiLomaxAuthor Commented:
Rancy,
I apologize for the delay...I am working this issue but am covered up at the moment, so I cant dedicate as much time to this issue as I'd like. I am still working it and very much appreciate your assistance. I just dont know that the issue is resolved yet.

Thanks again for the help and patience,

BL
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
I will be awaiting your update and no issues as i am an Engineer and can understand work pressure :)

- Rancy
0
 
BelushiLomaxAuthor Commented:
So sorry for the delay in updating this. I went on a week-long cruise and another engineer was assigned to the issue. Now I'm starting another long project and am finally getting time to update you, but currently there is still no confirmed resolution. I did come up with a workaround that so far hasn't seemed to cause any spike in network traffic (approx 8,000 users across a dozen sites on a 100 meg metro-e), so I'm posting it for others.

Rancy, thank you for your help. Exchange (especially in a DAG/CAS configuration) is not my strongest skill and your help has been a big tutorial in how this process works.

If I ever find the resolution, I'll update this, but I'm going to close it.

Meanwhile this is what I did:
I created a top level GPO (Group Policy Object) called "Outlook Addressbook Fix" which did 2 things at the USER level (since addressbooks are profile driven) using Group Policy Preferences:
     -Deleted %userprofile%\Local Settings\Application Data\Microsoft\Outlook\FILENAME.oab (delete all .OAB files)
     -Set the registry key and value:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Cached Mode\DownloadOAB \REG_DWORD\0x0 (0)

The reg_dword value of 0 keeps them from downloading the addressbook while they are using cached Exchange mode.

The other side is that this wasnt an issue for everyone. From what I understand, it was only some users who experienced this. I never got onsite to confirm this and find the difference.

Thanks again Rancy, I appreciate your assistance.

Steve (aka BelushiLomax)
0
 
BelushiLomaxAuthor Commented:
This did not solve the issue I was have but it does have good information. The issue still exists.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.