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,