Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm having an issue with running Outlook clients between domains. Essentially, the computers that Outlook is installed on are joined to Domain 1. They, however, must connect to Domain 2 which is over the Internet/Outlook Anywhere. I'm trying to create a .prf file that can be deployed automatically across the domain. We've already done this and ran into a problem: The GAL sometimes uses Domain 1 instead of 2.

Backstory: a division is being sold to a different company. Domain 1 was the original domain; users have accounts and email addresses on Domain 1. The Domain 1 email addresses are needed for the interrim until all data has been properly moved to Domain 2; the necessary data is being forwarded by Domain 1. Domain 2 uses different usernames and email addresses; I need to automate giving Domain 1 users access to Domain 2 email. This is working fine, except for the GAL. Users still need to send email to both Domain 1 and 2, the wrong GAL causes routing issues for emails to Domain 1.

New domain is authed over Outlook Anywhere. I've been turning off some auto-configure settings in registry, but results have been spotty. What I think the issue is, is that the GAL is still sometimes being pulled via LDAP instead of what is defined in the Domain 2 autodiscover.xml file. But, disabling LDAP authentication in Outlook doesn't seem to change anything.

Is there a way of forcing the correct GAL to be chosen when assigning an Outlook profile? I'm an outside contractor to both companies, so I have no control over either Exchange servers. However, this is a "desktop" issue, so it falls within my realm. Both servers are Exchange 2010. As far as I know, Multi-tenant and On-Premises modes are not in use.

Let me know what you think. Thanks,

share|improve this question
Your question is a bit confusing and is probably missing some relevant details. What do you mean "forcing the correct GAL"? The GAL doesn't have anything to do with domains. Are you referring to AD domains? Domain names that Exchange is authoritative for? Are you hosting multiple companies/customers on this Exchange server? Are you running Exchange in Multi-Tenant mode or On-Premises mode? If the latter are you using Address Book Policies? – joeqwerty Jun 18 '13 at 0:13
Are you essentially saying you want to have your users log into the DC in the second domain as well? You're saying that their are two GAL lists, one in domain one and one in domain two, correct? You are also saying that you want your users to connect to the domain number 2's GAL instead of one, right? I am a little confused when you say you don't have access to either Exchange Server, aren't the Systems Admin? – user178178 Jun 18 '13 at 2:55
No, I mean the GAL. I don't have access to their Exchange servers as I'm an external contractor to the two companies involved. The GAL is actually interlinked with Active Directory pretty deeply, in ways I don't fully understand, and is normally generated based on which domain your Outlook logs into. No we are not hosting multiple domains on the Exchange server; yes to multiple divisions. No to Multi-Tenant mode and On-Premises modes afaik. Updated the question with more information. – Insomnia Jun 18 '13 at 16:50
As for the GAL having nothing to do with AD, that's wrong. It does. GAL basically tracks user accounts and distro-groups by OU. It then determines if an email being sent is to a local account. If it's local, it replaces the email address with the username in order to create a non-routable message. Basically it creates a shortcut for all internal email. The Outlook address book then keeps a local copy of this data so it doesn't constantly have to request the server for AD information. – Insomnia Jun 18 '13 at 16:55
A GAL/AL does not track user accounts. A GAL/AL can be filtered by OU (I believe), but a GAL/AL isn't involved in the message creation, modification or delivery process. Exchange 2010 can be installed in Multi-Tenant mode or in On-Premises mode but it can't be installed in neither mode. It's one or the other but it's not neither. If you could link to some documentation that supports your statements about the GAL/AL I'd like to read it because if it's the case then I'm seriously misunderstanding the GAL and AL's. Thanks. – joeqwerty Jun 18 '13 at 17:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.