This issue was resolved in an update released by Microsoft in late June and applied to the Exchange servers on 7/1/2007. Messages that arrived post 7/1/2007 will display correctly in Outlook 2003. Messages that arrived pre 7/1/2007 may still require the workaround listed in the FAQs section.

While the central Exchange servers are configured to allow attachments up to 50 MB in size, problems have been encountered in some instances when large attachments are sent from an Entourage e-mail client. This issue can cause a user's Entourage client to "hang" and/or the message not being successfully sent. Also, when the problem occurs, server side monitoring tools indicate an increased load on the server hosting a user's mailbox. Until this issue is resolved, workarounds include either using Outlook Web Access or an Outlook client on a PC to send large attachments. If you are currently experiencing this problem, please restart your computer and delete the large message from your outbox in Entourage before attempting to use either of the workarounds.

This problem occurs for users who log in to their PCs using a child domain account and use Outlook 2007 (Outlook 2003 does not exhibit the same problem) as their e-mail client. As of August 2008, a hotfix addressing this issue can be downloaded from Microsoft at http://support.microsoft.com/kb/954574. Note to IT Administrators: Please install and test the application of this hotfix in a controlled environment before deploying it on multiple PCs. Alternatively, people wanting to set out of office settings without having to apply the hotfix can do so from Outlook Web Access (OWA). The out of office settings are available in OWA by clicking Options > Out of Office Assistant.

Calendar sharing permissions granted to users who are marked as a delegate for a room or equipment resource in Exchange are reset to "Editor" whenever the resource is updated via the Resource Coordinator Tools. In most cases, this change isn't noticeable to an end user because "Editor" permissions generally allow a person to do everything they need to do on a given calendar - including adding, modifying, and deleting meetings and appointments. Permission settings for users not acting as a delegate for the resource calendar are not affected.

If a person or distribution list has been granted at least the "Free/Busy time, subject, location" privelege (a different set of permissions is available when sharing a calendar from an Outlook 2003 client versus an Outlook 2007 client) for another user's calendar, the user would expect to see details for the shared calendar when viewing the calendar in a group view or while using the Scheduling Assistant. However, if the user is logged into a PC with a child domain account and is using Outlook 2007, occupied time slots are blocked out but details do not appear. The workaround is to grant the "Default" user the "Free/Busy time, subject, location" permission on the Calendar Permissions tab of the shared calendar - note that this will allow all Exchange users the ability to see the time, subject, and location details for the calendar being shared. Alternatively, users can log in to their PCs with their eID (rather than a child domain account) or us the "RunAs" command to launch Outlook with their eID credentials.

As a result of the US and Canadian governments' decision to extend the observed dates of daylight saving time starting in 2007, calendar appointments between 3/11-4/1 and 10/28-11/4 may appear an hour off - either an hour early or late depending upon how the meeting was scheduled and on what device it is being viewed. Please visit http://help.mail.colostate.edu/ki_timezones.aspx for more details regarding this issue along with steps to correct misplaced meetings and howto update computers and devices to prevent future problems.

Evolution (a popular e-mail client for Unix/Linux) cannot connect to central Exchange when the server type is set to "Exchange". Unix/Linux users can access central Exchange using Outlook Web Access.

If you encounter a problem where a user with appropriate permissions is unable to add, edit, or modify events on a resource calendar, it may be the result of the permissions having been granted to the resource from an Outlook client connecting to Exchange in cached mode. When this happens, try updating your Outlook configuration to disable cached mode and then re-apply the shared permissions for the resource's calendar. To check and/or update the cached mode setting withing Outlook, use the steps below.

1. From within Outlook 2007, go to "Tools" > "Account Settings"
2. Click "Change"
3. Underneath the "Microsoft Exchange Server" textbox is a checkbox labeled "Use Cached Exchange Mode". Uncheck it to disable cached mode.
4. Click "Next" and "Finish" to save the change.
5. If you were prompted to do so, restart Outlook.
6. After opening Outlook, re-apply the shared calendar's permissions by accessing the "Properties" window of the calendar in question, clicking the "Permissions" tab, and clicking "OK

Some users with Plam Pre phones are reporting having problems playing WAV files attached to email messages, including voice mail messages sent as attachments. We are trying to determine if this affects all people currently using a Palm Pre. We are also working Sprint and Palm to get official guidance regarding this problem. In the mean time, users can access their voice mail by dialing 491-5500 or via e-mail from a PC or device other than the Palm Pre.

Palm Pre and Pixi devices did not display calendar entries (i.e. a person's view of their calendar from a Palm Pre or Pixi would appear empty even though meetings and appointments did exist) due to an issue with the turn of the year to 2010 for webOS versions prior to 1.3.5.1. Palm released version 1.3.5.1 on 1/5/2010, which fixes the problem.

iPhones that were upgraded to iOS 4 or iOS 4.0.1 encounter problems syncing with Exchange. The most common reported behavior is messages getting stuck in the Outbox. After a reboot of the device, people are typically able to send one or two messages before subsequent messages remain in the Outbox. Assuming there are no e-mails in the Outbox, people are usually able to receive new e-mail. Also, it has been reported that iPhones that shipped (i.e. left the factory) with iOS 4.0.1 do not exhibit the problem.

After the installation of Exchange 2010 Service Pack 1 on 12/28/2010, the option to listen to a voicemail from Outlook 2007 does not work. Workarounds for this are to either upgrade to Outlook 2010 or to use the "Play on Phone" option viewable when accessing the voicemail message when logged into Outlook Web App.

After the installation of Exchange 2010 Service Pack 1 on 12/28/2010, eID accounts that do not have a mailbox on the system but have been granted access to a shared mailbox through membership in the shared mailbox's permissions group encounter an error when attempting to move or delete items in the mailbox when accessing the mailbox from Outlook Web App. The resulting error message states "The mailbox you're trying to access isn't currrently available. Please try again in a few minutes." Access from a full Outlook client installed on a PC is not affected. We are working with Microsoft to resolve this issue and will update this post as updates are available.

1. Access OWA using the specially formatted URL for a shared mailbox – ex: https://mail.colostate.edu/owa/demo_helpdesk@mail.colostate.edu.
2. Check the option "Use the light version of Outlook Web App". NOTE: This workaround only works with the light version of OWA!
3. Log in with your eID.
4. Click on the subject of any e-mail to read the e-mail. OWA will present the user with a second logon (usually). Logon again using the same credentials used before. Once logged in, the message that you clicked on previously will appear.
5. Return to the Inbox.
6. At this point, a user should be able to delete and move e-mail without encountering an error.