Skip to main content

Exchange 2010 Deployment Release Notes

Vmail is Vanderbilt's institution-wide implementation of Microsoft Exchange 2010, Service Pack 2.

Release notes as follows:

  • Outlook 2002 (or any version below) is NOT compatible with Exchange 2010.
  • Outlook 2003 -- Users who are still using Outlook 2003, RPC encryption MUST be enabled. Instructions can be found here:
  • Mac Mail--Manually configured email client (e. g. Mac Mail, etc) should be reconfigured to use after their mailboxes have been migrated to Exchange 2010.
  • Entourage--Entourage upgrade required: Older versions of Entourage no longer work with the Exchange environment. Entourage users should upgrade to Outlook 2011 or the Entourage Web Services Edition. (Known change in Exchange 2010)
  • Outlook login--Outlook prompts for login credentials: Outlook might prompt for a username and password when you try to access it. If your username and password do not allow you to log in, try entering your username in this format: vanderbilt\VUNetID .
  • Adding Delegates--Cannot add delegate(s) to an Exchange account: When you try to add a delegate to an Exchange account, you might get an error message stating you do not have permissions to perform the task. If the Exchange account is a group account, try logging into the computer as that group account, creating an Outlook profile for it, and then adding the delegate(s). If that does not work, try following the directions in this Microsoft article.

    If you are using Outlook 2010, do not install the hotfix and only make the registry changes. You will also need to use the Office 14.0 branch instead of Office 12.0, i.e.: 
  • Appointments in OWA--Inability to view all details of an appointment in OWA: When your mailbox is moved to Exchange 2010, you will receive an error if using OWA to view the details of an appointment on an Exchange 2007 shared calendar. (Known issue during the migration)
  • Exchange Web Services (EWS)--does not allow delegation of mailbox access across versions: With a user or delegate, if one of them has been moved to Exchange 2010 while the other has not been moved, the delegate will not be able to access the user's account. This issue affects Entourage 2008 EWS, iCal, and potentially any other client that uses Exchange Web Services (EWS). (Known issue during the migration)
  • Outlook 2007, 2010, Mac Outlook 2011 and Mac Entourage 2008, Web Services Edition: If Outlook is open when your account is upgraded, you may receive a prompt to close and restart it. Go ahead and restart it. If Outlook does not seem to be working correctly, restart it. If that doesn't resolve the issue, restart your computer. If you're still having problems, contact your support staff for help (Helpdesk, LAN Mgr, etc). Mac Outlook 2011 and Mac Entourage 2008, Web Services Edition users may additionally see an error that you do not have proper permissions when you try to use the "open another user's folder" option to view someone else's calendar. This indicates that the person's account has not been upgraded yet. You can use the Scheduling Assistant to see their free/busy status in the meantime.
  • Apple Mail/iCal 4 (Mac OS 10.6) or Mail/iCal 5 (Mac OS 10.7): Users may see duplicate emails in Apple Mail (but not OWA).

    If Apple Mail does not seem to be working correctly, restart it. If that doesn't resolve the issue, restart your computer. If you're still having problems, contact your support staff for help (HelpDesk, LAN Mgr, etc).
  • Apple Mail/iCal 3 or earlier (Mac OS 10.5 or earlier): Apple Mail/iCal versions prior to Mac OS 10.6 are not supported for use with Exchange 2010: Upgrade to Mac OS 10.6 or newer if possible; Switch to Entourage 2008 (Web Services Edition) or Outlook 2011, or If you cannot upgrade or switch, use Outlook Web App or set up Apple Mail/iCal to use IMAP.
  • Smart Phones (iPhones, Androids, etc.): If your phone is not connecting to your account, try turning your phone off and on. Make sure your phone has been updated to the most recent operating system it can run. Upgrade Android to OS version 2.2.1 (may not be available for all models from all vendors, check with your carrier). The "Touchdown" ActiveSync client may be an alternative until an OS upgrade is available. There is an enormous variety of devices, operating system versions, and user interfaces in use at Vanderbilt. We cannot provide specific instructions for every potential configuration.

Known Changes in Exchange 2010:

  • OWA--OWA interface changes: Significant changes to Outlook Web Access, providing a seamless and consistent interface across all web browsers and operating systems. The name will change as well; Outlook Web Access will be called Outlook Web App (OWA). See Outlook Web App. (Changes when mailbox is moved to Exchange 2010 servers starting in June.)
    • Editing or creating Notes in OWA: In Outlook Web App, you can no longer create or edit Notes. (Known change in Exchange 2010)
    • Document Access in OWA: In Outlook Web App, you can no longer access Microsoft Office SharePoint document libraries and Microsoft Windows file shares. (Known change in Exchange 2010)
    • Address Auto Complete--List of recently used addresses (auto-complete feature) will be empty initially, because the list that you had in the older version of Outlook Web Access had to be left behind. As you use the new Outlook Web App, your list will start to contain addresses.
  • Exchange Distribution Lists--Modifying members of an Exchange distribution list in the GAL: Exchange 2010 has changed the way distribution lists are managed. You will not be able to modify members of an Exchange distribution list until permissions of the list are updated. (Known change in Exchange 2010)
  • Reset Unified Messaging voice mail PIN - has moved from Outlook to OWA.  When a user resets their voice mail password or PIN, a Unified Messaging server generates a temporary PIN and sends it in an email message to the users Exchange Server account Inbox.  Once a user receives the temporary PIN, it should be used to log on to the users' mailbox [user will be redirected to OWA], and then the PIN should be changed to a PIN of the user's choice.  See for more detailed instructions.