Exchange 2010

Please bookmark this page so that you can easily access this information if needed later.

What do you need to do?

We've worked hard to minimise the disruption in moving to Exchange 2010 and to avoid the need to reconfigure email clients. However, whether you need to do anything depends a lot on which email programs you use. Recommended configurations for each client are given later.

Outlook No change required. Outlook will automatically detect that your mailbox has been moved and will ask you to restart outlook to access it.
Outlook from home The basic configuration is as before, but if using RPC over HTTP (aka Outlook Anywhere) then the Exchange Proxy server needs to be changed. See the outlook instructions.
Web Access There is no configuration of the web interface, so there is nothing to be done. However, please note the address of the new web interface, . This is compatible with both the old and new services so you can start using this straight away.
Thunderbird Please change the configuration to match the recommendation below.
Apple Mail Please change the configuration to match the recommendation below.
Apple Mail (Snow Leopard) If you are using Snow Leopard and your mailbox has been migrated to the new servers, you can reconfigure your OSX software to take full advantage of the new functionality via 'web services'. This integrates mail, calendar and contacts directly with the exchange server and is substantially faster than the usual IMAP connection.
Pine We know there are issues with pine and the new services. Please see the section on configuring pine below and edit your settings accordingly. Users using centrally managed linux systems in AOPP, Theory and PP may find that their .pinerc files have been updated for them by the system manages. Note that pine uses OpenSLL but the certificate problem described below can be avoided using the configuration recommended later.
OpenSSL Most linux programs rely on this package to provide encryption for network services like our secured IMAP and SMTP services. Unfortunately, the package does not include that `root certificate authority` certificate which is needed to validate the certificates we are issued as part of the UK academia. Anyone using OpenSSL must check functionality against our new services and perhaps install the appropriate certificate. Please contact IT Support to get the required certificate.
Other IMAP clients Treat in the same way Thunderbird.
Mobile Phones (activesync) Some mobile phones offer the option to connect to the mail server using activesync. The server should be set to (previously winfe was used). On Nokia phones, update the version of Mail for Exchange to V3 too.

Although there may be no need to change a client configuration, changing to the recommended configuration will allow us to move your mailbox sooner and thereby give you access to the new facilites.

What are the recommended configurations for each type of client ?

The following links show you the recommended settings for various types of client.

Web Interface (OWA) No configuration required.
Microsoft Outlook Outlook
IMAP Thunderbird
Apple Mail
Web Services Apple Snow Leopard integration
Entourage with Web Services (for OSX)
Other Evolution (Linux groupware client)

If you believe your client is ready, you may email IT Support and ask that your mailbox be moved ahead of the main migration.

Background to the upgrade from Exchange 2003, Sept 2010

The latest version of the Exchange email system has been installed and configured and is now ready for use. It offers better performance, more resilience and improved functionality for a wide range of clients. For many people the change is completely transparent and they need take no action themselves. However, we have identified some issues with older clients (pine and other email applications using openSLL) where some reconfiguration is required to work with the new services. More details follow.

The migration has basically two parts.

  1. The email programs must connect to the new services.
  2. The user's mailbox must be moved from the old to the new servers

Step 1 must happen before step 2. Step 2 can happen later, but the user wont get the advantages of the new services until this is done.

The easiest way to achieve step1 is to redirect all network traffic from the old services to the new ones. This works for the vast majority of users but some programs will stop working and users will then have to reconfigure before they will work. Previous tests have identified some of these issues and we are working with users to find a good solution. Alternatively, we could ask users to change the configuration of all their email programs and then to let us know when they are ready to move. This is time consuming for all involved so is to be avoided.