By: Emiley J Viewed: 649 times Printer Friendly Format
Recently while doing a migration for one of the customers, we had a tough time with the first migration batch. Luckily the first batch was only 3 emails and all of them were from their IT department. Their setup was using On-Premise Exchange 2003, On-Premise AD also running 2003. And the migration method we chose was using ADFS for Single Sign On and Directory Sync for synchronization of users. Everything went well until we did the first batch migration.
Configuring their outlook was a pain. As the autodiscover dns entries in their network was pointing to the local exchange server and the MX records are also pointing to their on-premise exchange server as we are doing a staged migration. Therefore while trying to configure outlook, it always tries to connect to the local exchange and it fails.
Solution: Searching the web, some suggested to add a CNAME entry for autodiscover to point to autodiscover.outlook.com. But we have to wait quite a long time if we change the external DNS entries. So we decided to configure the outlook for these three people using their email@example.com email addresses and it worked like a charm. Just choose the normal Exchange server configuration. Email type firstname.lastname@example.org, and key in the password. It auto detects and configures. If you are using SSO with ADFS, it will again prompt you for the username/password. Just key in and you are done.
Most Viewed Articles (in Office365 )
Latest Articles (in Office365)
Comment on this tutorial
- Cloud Computing
- Java Beans
- Mac OS X
- Office 365
- Tech Reviews
Subscribe to Tutorials
1. This can also prevent Outlook from using the autod
View Tutorial By: Morgster79 at 2012-03-21 05:07:42