Email Services/Office 365/Client Configuration Documents: Difference between revisions
< Email Services | Office 365
Jump to navigation
Jump to search
m (Lehman moved page CIS Email Services/Office 365/Client Configuration Documents to Email Services/Office 365/Client Configuration Documents) |
|||
(4 intermediate revisions by one other user not shown) | |||
Line 83: | Line 83: | ||
* No issues during migration. After migration there were no warnings, but new items would not synch | * No issues during migration. After migration there were no warnings, but new items would not synch | ||
* Resolution is to delete and recreate the account. | * Resolution is to delete and recreate the account. | ||
* After recreating the account, it took some time for the initial synch to show any appointments. Apple calendar may appear blank until that synch is complete. | |||
* If you have connectivity issues refer to [https://anl.box.com/s/usfa8hx6eioxspsil9w52vnxwxxq89r9 Apple Calendar setup] | * If you have connectivity issues refer to [https://anl.box.com/s/usfa8hx6eioxspsil9w52vnxwxxq89r9 Apple Calendar setup] | ||
Line 97: | Line 98: | ||
* If the changes above do not reestablish connectivity, You'll have to delete and recreate your Thunderbird profile. | * If the changes above do not reestablish connectivity, You'll have to delete and recreate your Thunderbird profile. | ||
* Please refer to [https://anl.box.com/s/nrzcy2jbafg2zl86ns6h1kyi8ar2fsuh Thunderbird (All Operating Systems) Setup] | * Please refer to [https://anl.box.com/s/nrzcy2jbafg2zl86ns6h1kyi8ar2fsuh Thunderbird (All Operating Systems) Setup] | ||
=== PINE or ALPINE === | |||
* <B>NOTE: BIS does not support or recommend Pine, Alpine or other open source text based mail clients, and cannot guarantee satisfactory performance with Exchange or Office365</b> | |||
* in your pine.rc file make the following changes | |||
** any reference to mail.anl.gov should be changed to outlook.office365.com. | |||
** any reference to your username should be changed to the format "[email protected]". note that if your email address and username differ, this will not be the same as your email address. | |||
** any reference to smtp.anl.gov should be changed to smtp.office365.com | |||
** below are some common line entries that need to be changed | |||
*** mail.anl.gov/ssl/novalidate-cert/user="username" to outlook.office 365.com/ssl/novalidate-cert/user="[email protected]" | |||
*** inbox-path={mail.anl.gov/ssl/user=username}inbox to inbox-path={outlook.office365.com/ssl/[email protected]}inbox | |||
*** smtp-server=mail.anl.gov should be changed to smtp-server=smtp.office365.com | |||
*** default-fcc="{mail.anl.gov/ssl}Sent Items" to default-fcc="{outlook.office365.com/ssl}Sent Items" | |||
=== Generic IMAP Settings === | === Generic IMAP Settings === | ||
Line 114: | Line 127: | ||
** change username to [email protected] | ** change username to [email protected] | ||
** change incoming server name to outlook.office365.com, port 993, SSL | ** change incoming server name to outlook.office365.com, port 993, SSL | ||
** change smtp (outgoing) server to smtp.office365.com, port 587, SSL | ** change smtp (outgoing) server to smtp.office365.com, port 587, SSL or STARTTLS (your client may require one or the other) | ||
=== Android Devices === | === Android Devices === | ||
==== IMAP Connection ==== | ==== IMAP Connection ==== |
Latest revision as of 15:44, November 2, 2017
Desktop Client Changes and Configuration Documents
Outlook on the Web
- 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
- If you have connectivity issues refer to the setup document Outlook on the Web Login
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 setup document Outlook for Windows Setup
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 setup document Outlook for Windows Setup
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
- from the Outlook menu, choose preferences
- make sure username is in the format [email protected]
- click advanced
- change the server name to https://outlook.office365.com/EWS/exchange.asmx
- If you continue to have issues, please refer to the document Outlook 2016 for Mac Setup
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 you continue to have issues, please refer to the document Outlook 2011 for Mac Setup
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 (Exchange Connection)
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 (IMAP)
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.
- After recreating the account, it took some time for the initial synch to show any appointments. Apple calendar may appear blank until that synch is complete.
- If you have connectivity issues refer to Apple Calendar 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 Thunderbird (All Operating Systems) Setup
PINE or ALPINE
- NOTE: BIS does not support or recommend Pine, Alpine or other open source text based mail clients, and cannot guarantee satisfactory performance with Exchange or Office365
- in your pine.rc file make the following changes
- any reference to mail.anl.gov should be changed to outlook.office365.com.
- any reference to your username should be changed to the format "[email protected]". note that if your email address and username differ, this will not be the same as your email address.
- any reference to smtp.anl.gov should be changed to smtp.office365.com
- below are some common line entries that need to be changed
- mail.anl.gov/ssl/novalidate-cert/user="username" to outlook.office 365.com/ssl/novalidate-cert/user="[email protected]"
- inbox-path={mail.anl.gov/ssl/user=username}inbox to inbox-path={outlook.office365.com/ssl/[email protected]}inbox
- smtp-server=mail.anl.gov should be changed to smtp-server=smtp.office365.com
- default-fcc="{mail.anl.gov/ssl}Sent Items" to default-fcc="{outlook.office365.com/ssl}Sent Items"
Generic IMAP 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
Mobile Device Changes and Configuration Documents
Outlook Mobile App
- Once your account has been migrated to Office 365, you can connect the Outlook Mobile app to your Mailbox
- Configuring the Outlook Mobile App for Office365
- Connecting the Outlook Mobile App to your Box Account
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 or STARTTLS (your client may require one or the other)
Android Devices
IMAP Connection
- received "could no longer sign in" notification
- had to change server settings
- incoming server: outlook.office365.com
- outgoing server: smtp.office365.com
- If you are connecting via IMAP and have issues, refer to Configuring Android OS Devices for Office365 IMAP
Exchange (a.k.a. Activesync) Connection
4.3 jelly bean
- error saying "email isnt responding, do you want to close it"
- closing and reopening the mail app re-established connectivity
- you may also have to respond to security settings update request
- If that does not work, see Android Activesync Device Setup
4.5.x kitkat
- error saying "couldnt log in"
- had to remove the account through settings-->accounts-->corporate
- recreated the account with same settings as old account. Refer to Android Activesync Device Setup
5.1.1 lollipop
- Had to restart mail app
- received notification in the notification list that "security policies had changed"
- you can disregard this notification
- If you experience issues see Android Activesync Device Setup
6.x Marshmallow
- no configuration changes necessary
- If you experience issues, see Android Activesync Device Setup
iOS Devices
IMAP Connection
- received "Cannot Get Mail" error, indicating username and password were incorrect
- within settings for the IMAP connectiom
- changed incoming server to outlook.office 365.com
- verified username was in the format [email protected]
- changed smtp server to smtp.office365.com
- If you are connecting via IMAP and have issues, refer to Configuring Apple iOS Devices for Office365 IMAP
Exchange (a.k.a. Activesync) Connection
- If you have ActiveSync connectivity issues refer to the notes below or refer to Configuring Apple iOS Devices for Office365
iOS 8.4 and later
- 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
- continually prompted for password to Exchange
- had to delete and recreate the exchange account
- left domain field blank and username in format [email protected]
- See Configuring Apple iOS Devices for Office365
Windows Mobile Devices
- Windows RT 8.1
- no warnings or changes required