Month: March 2012

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:, 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, with Outlook connecting, authentication and reconnecting to their moved BPOS mailbox which now resides in Exchange Online 365.


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:

Understanding Message Limits & Restrictions between BPOS and EXO365

Posted on Updated on

As customers start to transition out of BPOS and into Office 365, each and every administrator should be looking to the Office 365 Service Description documents, which outline the features, functions, and capabilities of these new services.  Specifically as users start using EXO365 they may find that the amount of messages, message sizes, etc are not what they are used to seeing and using.  This is because BPOS EXO and EXO365 do use different Messaging settings, with a specific callout here. 

Example of Change Between BPOS & EXO365

Message Limits in BPOS are set to 1200 messages every 90 minutes, while EXO365 limits are set to 1500 per 24 hours.

For additional Messaging Settings within Exchange Online 365, you should review the Service Description to fully understand these differences and/or changes:

Understanding SharePoint & Lync Online Integration

Posted on Updated on

Using Office 365 online services allows you to leverage one or more of these services while working.  For example, while logged into Lync Online using the Lync 2010 client, you can see Presence information about others in your online company within SharePoint Online.  These presence jelly-beans provide a way to see whether a user is online, offline, busy, etc and also to quickly start an IM conversation.  This cross-service functionality also extends into Messaging as well, where Presence and IM conversation capabilities can be used within Outlook Web Access (OWA) and/or Outlook.  To understand how this cross-service functionality works and how the Lync Client can view Presence and provide IM capabilities, the following shows the inner-workings of this client-side operation:


Creating & Managing Shared Mailboxes in Exchange Online 365

Posted on


A great posting on how to create and managed Exchange Online 365 Shared Mailboxes.  In additional to using the Exchange Control Panel and Remote PowerShell, a new tool has been created to help in these efforts.  To learn more, please review the following Office 365 Community posting:

Microsoft Script Explorer for Windows PowerShell (Pre-Release)

Posted on

For those Online Service Admins who love to manage via PowerShell, the new Microsoft Script Explorer for Windows PowerShell has been released as a pre-release to let people bang on the tool and provide feedback.  To download and being playing with this unique PowerShell Module, Script, Snippets and How-To Guidance search tool, please refer to:

While this tool does not provide a Scripting interface, you can use this to quickly find the script/snippet you are looking for with an easy to use interface to copy your needed content into your own PowerShell ISE:


Identify Yourself – One or Two Passwords?

Posted on

Great posting on the differences between Online versus Federated Identities and the usability and the management requirements for Federation.