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

From Public Wiki
Jump to navigation Jump to search
Line 89: Line 89:
* No issues during migration. After migration, received error, "Login to server mail.anl.gov failed"
* 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
* To fix the issue, the username and server names need to be changed
** from the "tools" menu choose "account settT
** change username to [email protected]
** change username to [email protected]
** 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
** change user account on outgoing server to [email protected]
** enter password when prompted
** click retry if authentication fails
* If the changes above do not reestablish connectivity, You'll have to delete and recreate your Thunderbird profile. Please 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 delete and recreate your Thunderbird profile. Please refer to [[Media:Configuring_Thunderbird_for_Windows_for_Office365.pdf | Configuring Thunderbird for Office 365]]



Revision as of 21:20, April 3, 2017

Desktop Client Changes and Configuration Documents

Outlook Web Client

  • No issues during migration. At final cutover, Client may report "mailbox unavailable" for about 15-20 minutes
  • During this same time, client may redirect to fs.anl.gov for authentication but not accept the login
  • Both issues were resolved once the migration finishes completely.
  • Autocomplete of email addresses that aren't in the GAL doesn't work

Outlook 2016 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
  • Occasionally, users will receive multiple login prompts while in Outlook for the first several times after migrating. This is due to Outlook having to reestablish connectivity to shared folders and calendars. Users should enter their password each time. eventually the prompts will subside.
  • If you have connectivity issues refer to the following setup documents

Outlook 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
  • Occasionally, users will receive multiple login prompts while in Outlook for the first several times after migrating. This is due to Outlook having to reestablish connectivity to shared folders and calendars. Users should enter their password each time. eventually the prompts will subside.
  • If you have connectivity issues refer to the following setup documents

Outlook 2010 for Windows

  • NOTE: HOTFIX KB2553248 MUST BE INSTALLED OR OUTLOOK 2010 WILL NOT CONNECT TO OFFICE 365
  • 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 restablishes the connection. No client reconfiguration should be necessary
  • Occasionally, users will receive multiple login prompts while in Outlook for the first several times after migrating. This is due to Outlook having to reestablish connectivity to shared folders and calendars. Users should enter their password each time. eventually the prompts will subside.
  • 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. Users should "Accept" this notification and check the box not to re-prompt.
    • "Outlook was redirected to the server autodiscover-s.outlook.com to get new settings for your account"
    • you may receive this prompt more than once
  • To re-establish client connection do the following:
    • check the "Always use my response for this server" check box
    • click "Allow"
    • re-authenticate when prompted
    • if you do not receive a login prompt
      • from the outlook menu, choose preferences-->accounts
      • change your login name from anl\username to [email protected]
      • reenter your password
      • close and reopen Outlook
  • If connectivity fails change your server settings

Outlook 2011 for Mac

  • No issues during migration. After migration completes, Client reports the following notification. Users should "Accept" this notification and check the box not to re-prompt.
    • "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"
    • re-authenticate when prompted
    • if you do not receive a login prompt
      • from the outlook menu, choose preferences-->accounts
      • change your login name from anl\username to [email protected]
      • reenter your password
      • close and reopen Outlook
  • If connectivity fails, verify your settings. Refer to the document Configuring Outlook for Mac 2011 for Exchange

Apple Mail (Exchange Connection)

  • Tested on Sierra and El Capitan
  • 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 Mail (IMAP)

  • Tested on Yosemite
  • No issues during migration.
  • After migration the user receives a password prompt, but password is not accepted
  • Resolution is to delete and recreate the account using the new IMAP server settings.
  • If you have connectivity issues refer to Apple Mail Setup

Apple Calendar

  • Tested on Sierra and El Capitan
  • 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
    • from the "tools" menu choose "account settT
    • change username to [email protected]
    • change incoming server name to outlook.office365.com
    • change smtp (outgoing) server to smtp.office365.com
    • change user account on outgoing server to [email protected]
    • enter password when prompted
    • click retry if authentication fails
  • If the changes above do not reestablish connectivity, You'll have to delete and recreate your Thunderbird profile. Please refer to Configuring Thunderbird for Office 365

Mobile Device Changes and Configuration Documents

Outlook Mobile App

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