Exchange 07 OAB download problems
I have a handful of users that are running Outlook 2007 in cached mode that cannot manually download the OAB. Hence, new changes in the GAL are never seen by these users. NOTE: People not in cached mode do not have the issue. However we have a large remote force that needs to be in cached mode.
The facts:
**************************
This is a new build of Exchange 07 in a CCR cluster with 2 servers having the mailbox role and 2 servers havng the Hub transport and CAS server role, the CAS servers configure in NLB. Mailboxes were migrated from an 03 SP2 server.
In EMC under Org Config - Mailbox - Offline Address book tab:
1. Have all the client support checked
2. I have 'Web Distribution' set up corrent pointing to \\cas-server1 and \\cas-server2
3. Have public folder distribution enabled.
Also in EMC under Server Config - Client Access -Offline Address book Distro tab:
both \\cas-server1 and \\cas-server2 are listed respectively
The URL syntax is as follows
http://cas-server1/mydomain.com/OAB
Tests in Mapi Connectivity result in seeing \\cas-server1 sometimes \\cas-server2.
The OAB is at https://cas-server1 /OAB/64228a00-66ea-4c25-ac
I can access this without any problems both internally and externally on the same url both using http and https. I get the pages of XML that you'd expect, both from affected cached mode systems and non cached mode systems.
Most Outlook clients have been upgraded from Outlook 2003.
I am specifically seeing Event ID's: Event ID 9360 and Event ID 9340. The fix that is rec'd in the event log as:
**************************
OALGen can be forced to post a full offline address list by creating the DWORD registry key 'HKEY_LOCAL_MACHINE\SYSTEM
Will this reg hack require a reboot? Will this clear the issue going forward?
I see no other event log messages pertaining to this issue and is remarkably clean considering.
I have googled this extensively and have not found a definitive answer. Is there anyone who can provide a step by step guide that will solve this?
The facts:
**************************
This is a new build of Exchange 07 in a CCR cluster with 2 servers having the mailbox role and 2 servers havng the Hub transport and CAS server role, the CAS servers configure in NLB. Mailboxes were migrated from an 03 SP2 server.
In EMC under Org Config - Mailbox - Offline Address book tab:
1. Have all the client support checked
2. I have 'Web Distribution' set up corrent pointing to \\cas-server1 and \\cas-server2
3. Have public folder distribution enabled.
Also in EMC under Server Config - Client Access -Offline Address book Distro tab:
both \\cas-server1 and \\cas-server2 are listed respectively
The URL syntax is as follows
http://cas-server1/mydomain.com/OAB
Tests in Mapi Connectivity result in seeing \\cas-server1 sometimes \\cas-server2.
The OAB is at https://cas-server1 /OAB/64228a00-66ea-4c25-ac
I can access this without any problems both internally and externally on the same url both using http and https. I get the pages of XML that you'd expect, both from affected cached mode systems and non cached mode systems.
Most Outlook clients have been upgraded from Outlook 2003.
I am specifically seeing Event ID's: Event ID 9360 and Event ID 9340. The fix that is rec'd in the event log as:
**************************
OALGen can be forced to post a full offline address list by creating the DWORD registry key 'HKEY_LOCAL_MACHINE\SYSTEM
Will this reg hack require a reboot? Will this clear the issue going forward?
I see no other event log messages pertaining to this issue and is remarkably clean considering.
I have googled this extensively and have not found a definitive answer. Is there anyone who can provide a step by step guide that will solve this?
Can you make sure that you have pointed databases to correct OAB. Right click on database, tab - Client Settings.
ASKER
I have found out some more info. We still have 1 foot in an Exchange 2003 environment and 1 foot in the 2007 environment. I suspect this is the cause.
When looking into the above response, I noticed half of my storage group DB's are pointing to the old addressbooks on the old mail server as evidenced by the following in the default Public Folder DB under client settings of the DB properties in 07 EMC:
OLDMAIL\First Storage Group\Public Folder Store (OLDMAIL)
some do point to
NEWMAIL\Second Storage Group\Public Folders
I tried running the 2 following cmdlets from the powershell:
Get-GlobalAddressList | Update-GlobalAddressList
Get-AddressList | Update-AddressList
but recieved the following errors:
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/Schedule+ Free Busy Information - First Administrative Group" is
invalid and could not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/Offline Address Book - First Administrative Group" is invalid and could
not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/Offline Address Book - \/o=Domain\/cn=addrlists\/
invalid and could not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/OAB Version 2" is invalid and could not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/OAB Version 3a" is invalid and could not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/OAB Version 4" is invalid and could not be updated.
domain.com is the actual AD name for the domain, howver all of our mail enabled users use and accept email from the domainb.com namespace. Could that be causing the issue? If so is there a way to plug that in when running the update commands?
What has been fixing this as one offs is recreating the Outlook profile, however with as many users experiencing the issue, this really is not the solution.
Is there a way to fix this and have my 03 and 07 systems co-exist? N ot sure where to go from here. Any step by step would be helpful.
When looking into the above response, I noticed half of my storage group DB's are pointing to the old addressbooks on the old mail server as evidenced by the following in the default Public Folder DB under client settings of the DB properties in 07 EMC:
OLDMAIL\First Storage Group\Public Folder Store (OLDMAIL)
some do point to
NEWMAIL\Second Storage Group\Public Folders
I tried running the 2 following cmdlets from the powershell:
Get-GlobalAddressList | Update-GlobalAddressList
Get-AddressList | Update-AddressList
but recieved the following errors:
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/Schedule+ Free Busy Information - First Administrative Group" is
invalid and could not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/Offline Address Book - First Administrative Group" is invalid and could
not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/Offline Address Book - \/o=Domain\/cn=addrlists\/
invalid and could not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/OAB Version 2" is invalid and could not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/OAB Version 3a" is invalid and could not be updated.
WARNING: The recipient "domain.com/Microsoft Exchange System
Objects/OAB Version 4" is invalid and could not be updated.
domain.com is the actual AD name for the domain, howver all of our mail enabled users use and accept email from the domainb.com namespace. Could that be causing the issue? If so is there a way to plug that in when running the update commands?
What has been fixing this as one offs is recreating the Outlook profile, however with as many users experiencing the issue, this really is not the solution.
Is there a way to fix this and have my 03 and 07 systems co-exist? N ot sure where to go from here. Any step by step would be helpful.
ASKER
I was able to clear this error running the address book update cmdlet. But I STILL have random users that are not getting an update from the GAL and cannot download the OAB. Any help or pointers would be great.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.