Outlook Anywhere and Exchange Server 2007 – Round 2
December 25th, 2008. Published under Uncategorized. No Comments.
OK, I didn’t know I was going to have a “round 2″ here (round 1 is here), but apparently I was not done configuring things. Hey, I never claimed to be perfect. In fact, this install is the first time I’ve touched Exchange 2007, so I’m learning as I go. But its all working now (as far as I know, at least).
The first issue we noticed was a syncronization error in the “Sync Issues” folder (sounds appropriate). More like a bunch of errors, but they all said the same thing (names changed to protect the innocent, of course):
17:11:46 Synchronizer Version 12.0.631517:11:46 Synchronizing Mailbox ‘Domain User‘17:11:46 Synchronizing Hierarchy17:11:47 Done17:12:13 Microsoft Exchange offline address book17:12:13 Not downloading Offline address book files. A server (URL) could not be located.17:12:13 0X8004010F
This didn’t seem to break any functionality, as the user could still open and use the Global Address List. But these stacked up quickly, I believe every time a Send/Receive occurred. It is worth noting these Outlook Address Book sync issues occurred on only Outlook Anywhere (OA) users and only when connected to the internal network and only when the laptops were not joined to the domain. When they were externally-connected these issues did not occur. The internally-connected computers joined to the domain did not have this issue.
The second issue was with the Out of Office Assistant (OAA). Users would receive the following error when opening OOA:
Your Out of Office settings cannot be displayed, because the server is currently unavailable.
This of course was not true; Exchange was working beyond these issues. What’s more, OA users, when accessing Exchange from outside the LAN, had no problems with OAA connectivity, but this time the internally-connected domain members did have the issue. Still, OAA worked fine from Outlook Web Access, so I knew it was not an issue with the OAA mechanism itself.
Using the Test E-mail Autoconfiguration tool by doing a CTRL + right-click on the Outlook icon in the System Tray verified I was having internal DNS issues. These issues were due, I presume, to my original choice of domain namespace, using the “corp” subdomain for the Active Directory domain name (corp.domain.com).
To fix, I created a new Forward Lookup Zone namespace for “domain.com” internally. This was a Primary zone stored in Active Directory. This of course would break the ability for internal clients to browse to domain.com, since this website is hosted externally. No problem, I just made a “same as parent folder” A record and a “www” A record, both pointing to the same IP address the external A record for domain.com.
To solve the issues breaking OAB sync for internally-connected OA users and OAA connectivity for everyone, I added the following records to the internal namespace:
- “owa” A record pointing to the internal IP address of the Exchange server
- “autodiscover” A record pointing to the internal IP address of the Exchange server
Once the clients picked up the changes, both issues went away. Again, maybe I should not have created “corp.domain.com” for the internal AD namespace. It has worked in the past for me, so I stuck with it when building this network.
I welcome any comments in regard to internal namespace structure.