ARCHIVED: Known issues and changes for the implementation of Exchange 2007 at IU

Outlook 2002, 2003, and 2007 remain supported in Exchange 2007. Outlook 2000 is supported but not tested. Outlook 97 and 98 are not supported.

Support as of release of Exchange 2007

Evolution client no longer functions

The Linux email client Evolution no longer connects to Exchange 2007. Until a future release fixes this issue, users of this client are encouraged to access their Exchange accounts via Outlook Web Access.

Alternate user login via POP3/IMAP4

You will be unable to log into another user's mailbox via POP3/IMAP4.

Permissions for mail-enabled objects in Active Directory must inherit from the domain level

If permissions on mail-enabled objects in Active Directory are not inherited from the domain, they will cease to be manageable and may not function properly in the future. Inheriting permissions from the domain fixes this problem. For more information, consult your local support provider (LSP). LSPs can consult LSP Services for more information.

The OWA login page will change slightly due to the migration. Functionality of the login page will not change. Once logged in, the OWA interface will not change at this time.

Known change as of September 9

Previous OWA bookmarks/links may not work

Bookmarks or other links in your web browser may not function properly with the new version of Exchange 2007 Outlook Web Access (OWA). To use OWA, enter https://www.exchange.iu.edu; also, modify your bookmarks to point to that URL. Any other links are not guaranteed to work properly.

Possible issue as of September 9

SCL (Spam Confidence Level) header change

When the HUB servers are installed, the ability to read and utilize in rules the X-SCL header will cease. Once a mailbox is moved to an Exchange 2007 mailbox server, the new header X-MS-Exchange-Organization-SCL will work similarly. See ARCHIVED: In messages to my Exchange account, why am I not seeing anything in the Spam Confidence Level (SCL) field?

Change as of September 16. New headers will be introduced over several weeks starting late September.

All mail going to and from Exchange (including to and from the same server or mailbox store) will be subject to the new Exchange 2007 Forefront scanning, to including virus scanning and blocked attachment lists.

Known change when mailboxes are moved to Exchange 2007 servers

Contact and mail-enabled group alias names

Contacts or mail-enabled groups can no longer contain spaces in the "alias" field. This alias field must be changed. For more information, contact your LSP. LSPs can consult LSP Services for more information.

Known change throughout the migration

Outlook 2007 and outbound firewall rules

For users running Outlook 2007 with a host-based or network-based firewall installed and running, outbound traffic to OWA (www.exchange.iu.edu) over HTTPS (port 443) will need to be unblocked and allowed.

Known change when mailboxes are moved to Exchange 2007 servers

OWA will change drastically, especially for those using Internet Explorer on a Windows PC. More information on these changes is forthcoming.

Changes when mailbox is moved to Exchange 2007 servers

OWA and ActiveSync features lost

The following features in OWA/ActiveSync will be absent from those who have been moved to Exchange 2007 mailbox servers: custom forms; monthly calendar view; editing of personal distribution lists; deleted item recovery access; native public folder access; document viewing for Office 2007 document formats. These are expected to be remedied when Service Pack 1 for Exchange 2007 is released and installed.

Known issue for Exchange 2007; will be fixed in SP1, early in 2008

Signing or encrypting email using S/MIME in OWA is available in the Premium interface only (Internet Explorer in Windows). Signing or encrypting using published Thawte certificates is not available at this time, but certificates from other providers (e.g., Comodo) will function. Reading signed or encrypted messages will work for any certificate in the Premium interface. For more information, consult your LSP or the Support Center.

Known issue for Exchange 2007 SP1

Retention cleared at mailbox migration

When your mailbox is moved to the new Exchange 2007 mailbox servers, all data in the retention (both Deleted Items and all other folders) is cleared. A new retention of 15 days will begin after the move.

Outlook cannot access Exchange account if Windows XP LAN Manager Authentication Level is not set to Level 5

Using Windows XP, after your mailbox is moved to the Exchange 2007 servers, you may be unable to configure Outlook to access the mailbox. In Windows XP, if the LAN Manager Authentication Level is set to the default (Send LM and NTLM responses), you will not be able to complete the "Check Name" step of the Outlook configuration. To fix, change the setting to Level 5 (Send NTLMv2 response only\refuse LM & NTLM). If you use Vista, you should be unaffected, because the LAN Manager Authentication Level is set to Send NTLMv2 response only\refuse LM & NTLM by default.

Public folder access is not available in the Light interface of OWA. See Public Folder access in OWA below.

Known side effect of Exchange Service Pack 1

Entourage requires /public for Public Folder access.

Entourage 2004 will require https://www.exchange.iu.edu/public as the Public Folder server.

Entourage 2004 no longer supported

S/MIME from Exchange 2007 to Exchange 2003

Sending an S/MIME signed or encrypted message from someone on an Exchange 2007 mailbox server to someone on an Exchange 2003 mailbox server may result in the message being bounced by Antigen with the error "CompressedCorruptFile". The sender should be contacted to make sure an unsigned or unencrypted message can be sent instead. Administrators are currently working on this issue.

Known issue, resolved September 24

The ability to recover deleted items in OWA was not available in Exchange 2007.

Known issue, resolved with the installation of Service Pack 1 in December 2007

The ability to view the calendar in "month view" in OWA was not available in Exchange 2007.

Known issue, was resolved with the installation of Service Pack 1 in December 2007

Add/edit distribution lists in OWA

The ability to add or edit personal distribution lists in OWA was not available in Exchange 2007. Lists can still be used, but not edited.

Known issue, resolved with the installation of Service Pack 1 in December 2007

The menu option for access to Public Folders was not listed in OWA in Exchange 2007. You could instead type the following URL manually in your web browser to access Public Folders: https://www.exchange.iu.edu/public/.

Note: With the installation of Service Pack 1, this URL only works with the Premium interface and IE; it no longer works with the Light interface. See Public Folder access in OWA Light above.

Known issue, resolved with the installation of Service Pack 1 in December 2007

Open Other Mailbox function error

If you clicked your name in the top of OWA to bring up the "Open Other Mailbox" dialog, typing a username and clicking Open would generate the error:

"Outlook Web Access could not find a mailbox for smtp:itps@iu.edu. If the problem continues, contact technical support for your organization and tell them the following: The mailbox may be stored on a Microsoft Exchange 2000 or Microsoft Exchange 2003 server, or the Active Directory user account was created recently and has not yet replicated to the Active Directory site where this Client Access server is hosted."

If the mailbox you were trying to access had not been moved to an Exchange 2007 mailbox server, you would not be able to access the mailbox this way. Instead, you needed to use the URL https://www.exchange.iu.edu/exchange/username, where username is the username of the mailbox you are attempting to access. Once the target mailbox was moved to Exchange 2007, you were be able to access it using the Open Other Mailbox method.

Known issue until completion of mailbox moves in late 2007

The ability to add or edit message rules in OWA was not available in Exchange 2007. Rules must be created or changed through Outlook itself.

Known issue, resolved with the installation of Service Pack 1 in December 2007