Understanding the Impact of DNS Autodiscover Record Created for BPOS Transition

Posted on Updated on

As many customers are looking to move into Office 365, the Admin Checklist, which helps BPOS admins understand the tasks they are required to perform to get their users and online company ready for Transition into Office 365.  Step #5 in the Admin Checklist: http://www.microsoft.com/online/help/en-us/helphowto/8939e90a-59dc-4f0f-aec0-19a899c0af75.htm, it states to create this record so mobile devices and Outlook clients can track down their BPOS moved mailbox, which now resides in Exchange Online 365.

As an admin creates this record, any BPOS Outlook users will see a NEW Autodiscover popup, asking them whether they would like to allow this operation, as seen below:

Reason: A BPOS Sign-In Client (SIC) configured Outlook client is manually configured to use autodiscover from BPOS EXO, by using a registry setting that leverages the PreferLocalXML key, which points to an actual autodiscover.xml, which points Outlook to BPOS EXO.  However Outlook always looks for a DNS Autodiscover record and because a record has been created, Outlook begins the Autodiscover “discoverY’ process.  Outlook will continue to use the setting used in PreferLocalXML and the newly created Autodiscover record for Office 365 will NOT impact Outlook usage.

Resolution: Once an Admin has created this new DNS Autodiscover record, they should send out information to their End-Users that they will see a new Popup, asking to allow Outlook to continue with this operation.  Users should select “Don’t ask me about this website again” and click OK.  At this point Outlook will continue to work as expected.

Note – This is an annoyance and does NOT impact Outlook connectivity and usability.  As the BPOS tenant is Transitioned into Office 365, the Sign-In Client (SIC) will remove this PreferLocalXML registry entry and autodiscover.xml file.  Once done Outlook will find the newly created DNS Autodiscover record, which points to autodiscover.outlook.com, with Outlook connecting, authentication and reconnecting to their moved BPOS mailbox which now resides in Exchange Online 365.

Workaround

Outlook does have a way to workaround this issue by define a Fully Qualified Domain Name (FQDN) for this server, so that this redirect pop-up does not display.  To learn more about this workaround, please use the following URL.  Note that this solution requires modification of the Registry and as such should be used with caution, as modifying the registry can cause problems with the PC.  Due to this, your administrator should look into this option as a way to modify your registry to suppress this popup:

One thought on “Understanding the Impact of DNS Autodiscover Record Created for BPOS Transition

    Loryan Strant said:
    March 28, 2012 at 12:37 pm

    Reblogged this on The Cloud Mouth.

Whatcha thinkin?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s