• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 378
  • Last Modified:

Outlook anywhare autodetect override during migration on one OU only

Short background to understand the problem:
Because our division on our company has been bought by another company we are migrationg only our OU in the AD to our new companys exchange server. the mailboxes has been exported and imported into the new domain and we have gotten new usernames and passwords on the new companys domain.
While we are in the middle of the migration process, we are still physically on the old companys domain and infrastructure and will be for at least 30 days more. the same is with our mail addresses and domain names. I am the test rabbit for this migration and I have set up my old mailaddress as an alias and send as address in my new mailbox and having the original mailserver forwarding all mail to the new server.

The problem:
Since I have the same mailaddress as I have on the old server sitting in the old companys infrastructure. Outlook autodetects my mailaddress and changes the setup back to the old mailserver every time I start Outlook. I can not shut down the autodetect for the rest of the old company, and I cannot change the send as address on the new server for at least 30 days.
I have created a local XML file that forwards the setup request to the new server, but as long as I am inside the old domain i have so far been unable to force outlook to search locally for the setup xml when it detects the old settings in the AD first.
0
ErikOlne
Asked:
ErikOlne
  • 3
1 Solution
 
ErikOlneAuthor Commented:
I have read this article for finding out how to force local xml lookup.
http://blogs.technet.com/b/ilvancri/archive/2010/02/03/some-autodiscover-fun.aspx
I am using  64 bit win7 OS and Outlook 2010 64bit.
Is it possible that there are some of the registry paths for the registry entries that is wrong in this document compared to my system?
0
 
Dave_ANDCommented:
Try editing your host file on your local PC, and put "autodiscover.yourdomain.local" to send to your new mail server.. this should stop DNS forcing you to you old server.
0
 
ErikOlneAuthor Commented:
good idea!
I hate it when others think of such things before me :-)
Will try that immediatly!
0
 
ErikOlneAuthor Commented:
Worked like a charm!
The only drawback is that Outlook complains about the certificate being wrong, but that was kind of suspected and is possible to live with during the migration.
Thank you!
(I am a bit ashamed about not thinking of this myself, but that's life) :-)
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now