Email Services/Office 365/Client Configuration Documents: Difference between revisions

From Public Wiki
Jump to navigation Jump to search
Line 46: Line 46:
** change incoming server name to outlook.office365.com
** change incoming server name to outlook.office365.com
** change smtp (outgoing) server to smtp.office365.com
** change smtp (outgoing) server to smtp.office365.com
* If the changes above do not reestablish connectivity, refer to [[Media:Configuring_Thunderbird_for_Windows_for_Office365.pdf | Configuring Thunderbird for Office 365]]
* If the changes above do not reestablish connectivity, You'll have to recreate your Thunderbird profile. Please refer to [[Media:Configuring_Thunderbird_for_Windows_for_Office365.pdf | Configuring Thunderbird for Office 365]]


=== Mobile Device Changes and Configuration Documents ===
=== Mobile Device Changes and Configuration Documents ===

Revision as of 15:37, December 15, 2015

Desktop Client Changes and Configuration Documents

Outlook 2010 or 2013 for Windows

  • No issues during migration. After migration completes, Client reports the following notification
    • "The Microsoft Exchange Administrator has made a change that requires you to quit and restart outlook"
  • Restarting Outlook reestablishes the connection. No client reconfiguration should be necessary
  • If you have connectivity issues refer to the following setup documents

Outlook 2016 for Mac

  • No issues during migration. After migration completes, Client reports the following notification
    • "Outlook was redirected to the server autodiscover-s.outlook.com to get new settings for your account"
  • To re-establish client connection do the following:
    • check the "Always use my response for this server" check box
    • click "Allow"
  • If connectivity fails change your server settings

Outlook 2011 for Mac

  • No issues during migration. After migration completes, Client reports the following notification
    • "Outlook was redirected to the server autodiscover-s.outlook.com to get new settings for your account"
  • To re-establish client connection do the following:
    • check the "Always use my response for this server" check box
    • click "Allow"
  • If connectivity fails, verify your settings. Refer to the document Configuring Outlook for Mac 2011 for Exchange

Apple Mail

  • Tested version 8.2 (OS 10.10.5)
  • No issues during migration. After migration there were no warnings, but new mail would not synch
  • Resolution is to delete and recreate the account.
  • If you have connectivity issues refer to Apple Mail Setup

Apple Calendar

  • Tested version 8.0 (OS 10.10.5)
  • No issues during migration. After migration there were no warnings, but new items would not synch
  • Resolution is to delete and recreate the account.
  • If you have connectivity issues refer to Apple Calendar and Address Book Setup

Thunderbird (All Operating Systems)

  • No issues during migration. After migration, received error, "Login to server mail.anl.gov failed"
  • To fix the issue, the username and server names need to be changed
    • change username to [email protected]
    • change incoming server name to outlook.office365.com
    • change smtp (outgoing) server to smtp.office365.com
  • If the changes above do not reestablish connectivity, You'll have to recreate your Thunderbird profile. Please refer to Configuring Thunderbird for Office 365

Mobile Device Changes and Configuration Documents

Generic Settings

  • For Generic IMAP setup, you'll have to delete and recreate the account, using the following settings
    • change username to [email protected]
    • change incoming server name to outlook.office365.com, port 993, SSL
    • change smtp (outgoing) server to smtp.office365.com, port 587, SSL

Android Devices

iOS Devices

  • If you are connecting via IMAP and have issues, refer to Configuring Apple iOS Devices for Office365 IMAP
  • If you have ActiveSync connectivity issues refer to the notes below or refer to iOS Activesync Device Setup
  • iOS 9.02
    • received a could not connect error initially, but did not have to reconfigure
    • device reboot re-esatblished connectivity
    • users who have "ANL" the "domain" field configured for the Exchange connection will have to clear that field
    • users whose username field does not contain their username in the supported syntax "[email protected]" will have to edit that field appropriately.
    • Please refer to Configuring Apple iOS Devices for Office365 for configuration examples
  • iOS 8.4
    • received a could not connect error initially, but did not have to reconfigure
    • device reboot re-esatblished connectivity
    • users who have "ANL" the "domain" field configured for the Exchange connection will have to clear that field
    • users whose username field does not contain their username in the supported syntax "[email protected]" will have to edit that field appropriately.
    • Please refer to Configuring Apple iOS Devices for Office365 for configuration examples
  • iOS 5.1.1

Windows Mobile Devices

  • Windows RT 8.1
    • no warnings or changes required