3. Known issues with Exchange 2010
- Loss of WebDav. This will become apparent to you when your mailbox
is upgraded, and affect you if:
- you are a user of an old version of Entourage (on the Mac). Your solution is to upgrade to a later version of Entourage that uses Exchange Web Services (i.e. 'Entourage 2008 Web Services Edition') or 'Microsoft Office for Mac 2011' (i.e. Outlook 2011)
- you are a user of the Lightning calendar plug in for Thunderbird (or similar). Your solution here is to use the Davmail connection with Exchange Web Services (EWS). See the notes regarding Davmail and the Exchange 2010 upgrade for more information.
- you are a user of Davmail in another context. It is possible that you may be able to configure Davmail as per the same instructions.
- Loss of 'Messageware enhanced' OWA Light. This may become apparent to you when your mailbox is upgraded. Only the standard OWA Light is available. This only affects non tier 1 browsers (i.e. excluding those listed on the What differences should I expect with Exchange 2010? page), including IE6, pre-Firefox 3.0.1 and pre Safari 3.1. Significant functionality that is lost:
NTLM Authentication over IMAP. If this is a problem for you, it may
have become apparent on 16 February 2012 when the Exchange 2010 IMAP service
was enabled. If you suffer from an unexpected 'Authentication failure' (i.e.
log in failure) it may be that "NTLM" is set in your email client. This needs
to be set to "Normal" or "Normal password" (or equivalent). Check that your
client is configured as per the OUCS Nexus client
- Within the most common IMAP Email clients (Thunderbird for instance), this setting is often displayed as 'Authentication Method', 'Authentication type' or 'Secure Password Authentication (SPA)'.
- Commonly, the *correct* selection for this setting would be 'normal password' or 'plain text authentication' or it would involve NOT selecting 'Secure Password Authentication (SPA)'.
- Apple Mail (and Address Book and iCal) adding in (or removal) of ".legacy"
- Before following the instructions at http://www.oucs.ox.ac.uk/nexus/upgrade/index.xml?ID=applemail disconnect from the network. (There is a problem of new email coming down after the connection settings have been changed, and before the client is restarted, that causes the appearance of duplicates).
- If you see duplicates in Apple Mail after adding (or, later removing) the ".legacy" server connection details
- This may be cured by going and selecting Mailbox->Rebuild from the main menu. However, please ensure that the client has been restarted (Applekey-Q and restart).
- Apple Mail users who use IMAP being told to change settings to use the correct EWS connection
- This can confuse IMAP users (as Exchange Web Services should be irrelevant
to them). There are three main reasons why they could have been told to change
- They have another Mac client and that is set up to use EWS
- Address Book and/or iCal could be set up to use EWS
- Even though they may never use AB or iCal this can be why the person showed up in the logs (and was sent an informative email). If they genuinely don't use AB and iCal, then they can ignore everything and not make any changes.
- They may have received a warning regarding IMAP and NTLM
- Nothing about EWS but the IMAP settings are using NTLM in their password connection. Please check the OUCS help page and change this setting. The connection should have stopped working on 16 February 2012.
- Apple Mail users get their Apple Mail rules broken
- (N.B. This does not apply to server-side rules or rules set up via OWA.)
The namespace change (from nexus.ox.ac.uk to legacy.nexus... and - presumably -
back again) can cause rules to break within Apple Mail. There is no simple fix
for these problems after they have occurred. The advice is
- If you have Apple Mail rules, then make the Internal server: and External server: settings changes whilst off line and/or not connected to any network. This may avoid the problem.
- Double authentication to OWA?
- If you have bookmarks like
https://nexus.ox.ac.uk/CookieAuth.dll?GetLogon?curl=Z2Fowa&reason=0&formdir=2this will cause a prompt for you to log in twice. Either remove everything after the 3rd slash (i.e. Cookie....) or bookmark
https://owa.nexus.ox.ac.uk(either will work perfectly well).
- After you are upgraded, you continue seeing OWA-Light, when you were expecting the more advanced OWA-Full
- There are two main reasons for this:
- Your browser/operating system combination is incorrect. See the list of supported browsers on the What differences should I expect with Exchange 2010? page.
- You are using a correct browser/operating system combination, but you have "Use the blind and low vision experience" set as an option. To remove this setting:
- The cause could be that you have not yet been upgraded. Please check with your local IT Support staff for more information.
- You see the "Use Outlook Web Access Light. Faster interface with fewer features. If you are not using Internet Explorer 6.0 or later, this is your default interface." message each time you log in to Nexus (and you are unable to select or de-select the checkbox).
- Known issue. You may well be using a supported browser (see the list on the What differences should I expect with Exchange 2010? page). This prompt will stay with us for some time and will continue to be a little misleading. Future work (after all of the upgrades have been completed) will address this. If you prefer to use OWA-Light, you must select the 'Use the blind and low vision experience', as per the instructions above (but in reverse).
- You can't find your 'remembered' email addresses
- Instead of saving email addresses as proper 'Contacts', some people had grown to rely upon the last 100 'cached' email addresses that OWA remembered. In OWA-Light, these were collected in a little box alongside the email interface. In OWA-Full, they magically appeared as you began typing. These are not migrated between Exchange 2007 and 2010 (there are very good reasons why this would be a bad idea for most Exchange migrations). Those who rely on these lists need to re-build them by looking or searching through their Sent Items. All email addresses will be in Sent Items, as it is only by sending someone an email that their email address can be added to the cached email address list.
- Picking up external calendars (e.g. google calendars) via OWA
- In the interface, it appears that you can do this. However, it does not work as yet. We are attempting to get this functionality to work at the moment.
- OWA defaults to grouping your emails in 'Conversation view'
- This has proved to be quite unpopular (for understandable reasons). It would appear to default to that view for some, if not all, users. The Nexus Team have not been able to change this for new upgrades, so everyone (who doesn't like it) needs to uncheck the 'Conversations' checkbox that can be found within the 'Conversations by...' drop down list. (This can't be turned off 'globally', so you need to do it the first time you visit each folder).
- Using Internet Explorer, I don't see when new emails arrive
Some people have noticed that they need to keep pressing refresh to see new items. This
may be due to the namespace change and to the way Internet Explorer works with trusted
sites. The fix is to add
https://owa.nexus.ox.ac.ukas a Local intranet site. To do this:
- Go to Tools > Internet Options > and find the Security tab.
- Click on 'Local intranet' (the planet+monitor icon) and click the Sites button.
- Leave the settings in the 'Local intranet' pop up window the same as before, but click on the 'Advanced' button.
https://owa.nexus.ox.ac.ukand click 'Close', 'OK, and 'OK'.
- The figure below summarises this process.
- Adding in a mailbox where you have full access, but where that mailbox is hidden from the Global Address List (GAL)
There are some changes here which are difficult to express concisely. It is still possible to
do this, but you may have to contact the OUCS Help Centre (and then the Nexus Team) for
advice. A few pointers:
- If the person trying to connect to the hidden mailbox is using Outlook 2003, this is not possible.
- If the person trying to connect to the hidden mailbox is using Outlook 2007, please contact OUCS to have something called 'automapping' switched on.
- If the person trying to connect to the hidden mailbox is using Outlook 2010, using 'automapping' (as above) is probably the easiest option. However, the method outlined at Running multiple Nexus mailboxes under one profile (Outlook 2010) still works, but the end result is that the mailbox is displayed a in a somewhat 'unfriendly' way.
- Sharing calendars with people who are hidden from the Global Address List (GAL)
- This is difficult, although not impossible! If person A wishes to see hidden person B's calendar, and presuming person B has enabled this, person A must create a personal contact entry for person B before accessing the calendar. Full details of how to do this will shortly be documented within the general OUCS Nexus documentation.
- BlackBerry problems for people with a BIS contract
- (N.B. This does not apply to those using the Oxford Nexus BlackBerry
Enterprise Service, i.e. BES). For people who have a BlackBerry, using
BlackBerry Internet Service, (BIS) and who have found that their
connection no longer works, they should do the following only until their
mailbox is upgraded. Change the
Outlook Web AccessURL field to:
The OUCS BIS instructions provide help about configuring this on your Blackberry Smartphone.
- Certificate problems with UNIX IMAP clients
- We have heard that some UNIX IMAP email clients have shown some certificate
errors. There is no fundamental reason why this should be restricted to UNIX
clients, as the cause is a new type of certificate (Comodo) that the Nexus
service is using. However, some older systems assume that the user will take on
the responsibility of updating certificate chains etc. (Most modern Linux
systems, e.g. Ubuntu, Debian, CentOS, etc., will automatically update).
- If this affects you, then the system administrator (possibly you) need to install the root Comodo CA certificate) into the trusted certificate store. Visit https://support.comodo.com/ for more details.