Client and Mobile Device Configuration Changes: Difference between revisions
Jump to navigation
Jump to search
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The following tables list our most common E-mail desktop clients and mobile devices, along with a brief description of what you may expect to experience after your mailbox has been moved from Exchange 2007 to Exchange 2010. In many cases no action is required. In some cases, a simple closing and re-opening of the application or reboot of the mobile device resolves any issues. There are a few cases, most notably with some Android devices, that a configuration change is necessary. Descriptions of those changes, when necessary are listed below. | |||
If you are having issues connecting your desktop or Mobile device to your mailbox after it has been moved to the exchange 2010 servers, please reference these tables for a possible fix. If, after attempting these fix recommendations, you are still having connectivity issues, please call the helpdesk at 2-9999 option 2 for assistance. | |||
== Desktop Clients == | == Desktop Clients == | ||
{| class="wikitable" border=1 | {| class="wikitable" border=1 | ||
| Line 10: | Line 14: | ||
| 5.2 | | 5.2 | ||
| Cannot log in after move, but can access existing mail | | Cannot log in after move, but can access existing mail | ||
| | | Closing and reopening the client reestablished connectivity in most cases. Some users reported the need to change the internal and external server names from legacy.anl.gov to mail.anl.gov | ||
|- | |- | ||
| Outlook 2011 for mac | | Outlook 2011 for mac | ||
| Line 71: | Line 75: | ||
! RESOLUTION | ! RESOLUTION | ||
|- | |- | ||
| iPhone | | iPhone 3Gs | ||
| 5.1.1 | | 5.1.1 | ||
| Cannot log in to server during move | | Cannot log in to server during move | ||
| | | Server name changed automatically. Inbox had to resynch. No manual intervention required | ||
|- | |- | ||
| iPhone 3Gs | | iPhone 3Gs | ||
| | | 6.0.0 | ||
| Cannot log in to server during move | | Cannot log in to server during move | ||
| Server name changed automatically. Inbox had to resynch. No manual intervention required | | Server name changed automatically. Inbox had to resynch. No manual intervention required | ||
|- | |||
| iPhone 4 | |||
| 5.1.1 | |||
| Cannot log in to server during move | |||
| Service name changed automatically. No manual intervention required | |||
|- | |- | ||
| iPad | | iPad | ||
| Line 85: | Line 94: | ||
| Cannot log in to server during move | | Cannot log in to server during move | ||
| Service name changed automatically. No manual intervention required | | Service name changed automatically. No manual intervention required | ||
|- | |||
| Android OS | |||
| 2.2.1 (Froyo) | |||
| Cannot log in to server during move | |||
| Server value must manually be changed from legacy.anl.gov to mail.anl.gov. In some cases,mail profile must be deleted and recreated in order to facilitate the server name change. | |||
|- | |- | ||
| Android OS | | Android OS | ||
| Line 90: | Line 104: | ||
| Cannot log in to server during move | | Cannot log in to server during move | ||
| Server value must manually be changed from legacy.anl.gov to mail.anl.gov. In some cases,mail profile must be deleted and recreated in order to facilitate the server name change. | | Server value must manually be changed from legacy.anl.gov to mail.anl.gov. In some cases,mail profile must be deleted and recreated in order to facilitate the server name change. | ||
|- | |||
| Android OS | |||
| 2.3.6 (Samsung Galaxy S II) | |||
| Cannot log in to server during move | |||
| Server value must manually be changed from legacy.anl.gov to mail.anl.gov. In some cases,mail profile must be deleted and recreated in order to facilitate the server name change. Also, in some cases, an additional notification must be accepted. This can be found in the "Notifications" section, which is accessible from the menu button. | |||
|- | |- | ||
| Android OS | | Android OS | ||
| 4.0.4 | | 4.0.4 | ||
| Cannot log in to server during move | | Cannot log in to server during move | ||
| | | Some users did not need to make a configuration change. For others, the server value needed to manually be changed from legacy.anl.gov to mail.anl.gov. In some cases, mail profile must be deleted and recreated in order to facilitate the server name change. | ||
|- | |- | ||
| Android OS | | Android OS | ||
| 4.1.0 | | 4.1.0 (Jelly Bean) | ||
| Cannot log in to server during move | | Cannot log in to server during move | ||
| Server name changed automatically. No manual intervention required | | Server name changed automatically. No manual intervention required | ||
|- | |- | ||
| Blackberry | | Blackberry | ||
| 4.5.0.81 | | 4.5.0.81 | ||
| No service for about 15 minutes after move completed | | No service for about 15 minutes after move completed | ||
| Connection reestablished automatically. | | Connection reestablished automatically. | ||
|} | |} | ||
Latest revision as of 15:15, October 18, 2012
The following tables list our most common E-mail desktop clients and mobile devices, along with a brief description of what you may expect to experience after your mailbox has been moved from Exchange 2007 to Exchange 2010. In many cases no action is required. In some cases, a simple closing and re-opening of the application or reboot of the mobile device resolves any issues. There are a few cases, most notably with some Android devices, that a configuration change is necessary. Descriptions of those changes, when necessary are listed below.
If you are having issues connecting your desktop or Mobile device to your mailbox after it has been moved to the exchange 2010 servers, please reference these tables for a possible fix. If, after attempting these fix recommendations, you are still having connectivity issues, please call the helpdesk at 2-9999 option 2 for assistance.
Desktop Clients
| CLIENT | VERSION | EXPERIENCE | RESOLUTION |
|---|---|---|---|
| Mac OSX Mail (All Configurations) | 5.2 | Cannot log in after move, but can access existing mail | Closing and reopening the client reestablished connectivity in most cases. Some users reported the need to change the internal and external server names from legacy.anl.gov to mail.anl.gov |
| Outlook 2011 for mac | 14.2.3 | mailbox move warning displayed, but can access existing mail | Close and reopen the client. |
| Thunderbird | 9.0.1 | Cannot log in during move, but can access existing mail | no changes, connection restored automatically after move |
| iCal (Standalone without Mac OSX Mail) | 5.0.3 | Can acess existing appointments, but would not synch new appointments | Server names must be manually changed (internal:mail.anl.gov external:mail.anl.gov) |
| Outlook Web Access | Multiple Browsers | Mailbox move warning displayed. Cannot access mailbox | Had to log back in to re-establish connectivity |
| Outlook 2010 - Outlook Anywhere (a.k.a. RPC/HTTP) | 14.0.6112.5000 | can log in and access existing mail. New messages not coming in | prompted for password after move completed, which re-established the connection |
| Outlook 2010 - Cached Mode Enabled | 14.0.6112.5000 | Can log in and access existing mail. New messages not coming in | Received notification to restart Outlook, which restored connectivity |
| Outlook 2010 - Cached Mode Disabled | 14.0.6112.5000 | Connection lost, cannot log in to view existing mail | Outlook must be reopened, otherwise connected with no changes |
| Outlook 2007 - Outlook Anywhere (a.k.a. RPC/HTTP) | 12.0.661.5003 (SP3) | Can log in and access existing mail. New messages not coming in | prompted for password after move completed, which re-established the connection |
| Outlook 2007 - Cached Mode Enabled | 12.0.661.5003 (SP3) | Can log in and access existing mail. New messages not coming in | Received notification to restart Outlook, which restored connectivity |
| Outlook 2007 - Cached Mode Disabled | 12.0.661.5003 (SP3) | Connection lost, cannot log in to view existing mail | Outlook must be reopened, otherwise connected with no changes |
Mobile Devices
| DEVICE | VERSION/PROVIDER | EXPERIENCE | RESOLUTION |
|---|---|---|---|
| iPhone 3Gs | 5.1.1 | Cannot log in to server during move | Server name changed automatically. Inbox had to resynch. No manual intervention required |
| iPhone 3Gs | 6.0.0 | Cannot log in to server during move | Server name changed automatically. Inbox had to resynch. No manual intervention required |
| iPhone 4 | 5.1.1 | Cannot log in to server during move | Service name changed automatically. No manual intervention required |
| iPad | 6.0 | Cannot log in to server during move | Service name changed automatically. No manual intervention required |
| Android OS | 2.2.1 (Froyo) | Cannot log in to server during move | Server value must manually be changed from legacy.anl.gov to mail.anl.gov. In some cases,mail profile must be deleted and recreated in order to facilitate the server name change. |
| Android OS | 2.3.4 | Cannot log in to server during move | Server value must manually be changed from legacy.anl.gov to mail.anl.gov. In some cases,mail profile must be deleted and recreated in order to facilitate the server name change. |
| Android OS | 2.3.6 (Samsung Galaxy S II) | Cannot log in to server during move | Server value must manually be changed from legacy.anl.gov to mail.anl.gov. In some cases,mail profile must be deleted and recreated in order to facilitate the server name change. Also, in some cases, an additional notification must be accepted. This can be found in the "Notifications" section, which is accessible from the menu button. |
| Android OS | 4.0.4 | Cannot log in to server during move | Some users did not need to make a configuration change. For others, the server value needed to manually be changed from legacy.anl.gov to mail.anl.gov. In some cases, mail profile must be deleted and recreated in order to facilitate the server name change. |
| Android OS | 4.1.0 (Jelly Bean) | Cannot log in to server during move | Server name changed automatically. No manual intervention required |
| Blackberry | 4.5.0.81 | No service for about 15 minutes after move completed | Connection reestablished automatically. |