Forum Discussion

domus's avatar
domus
Level 3
7 years ago

Exchange OWA url change => No EV Entries in the menu ?

Hi everybody, Exchange 2010 / EVault v10.0.1.1189 Recently we change url of our owa from https://mail.domaina.com/owa to https://mail.domainb.com CAS servers remain the same, its just the OWA url t...
  • ChrisLangevin's avatar
    ChrisLangevin
    7 years ago

    Yeah, you are still using the same browser, but nonetheless it is the browser that's the problem. Here's the proof from your log:

    13/04/2018 10:04:42 [4172,88] [EVContext::IsValidBrowser] Checking browser...
    13/04/2018 10:04:42 [4172,88] [EVContext::IsValidBrowser] User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko
    13/04/2018 10:04:42 [4172,88] [EVContext::IsValidBrowser] Checking for MSIE in user agent
    13/04/2018 10:04:42 [4172,88] [EVContext::IsValidBrowser] Returning: False

    Because our OWA extensions are only supported using legacy IE, we check the browser's user agent string for the substring "MSIE" to see if we should enable the extensions. IE 11, when it is not using compatibility view, does not include this substring. If you add a particular URL to the compatibility view list, you will see when you visit that URL that the user agent will change and IE 11 will include the "MSIE" substring, in keeping with IE versions of old.

    So what's happened is that you have changed the OWA URL, and you only have the old OWA URL listed in your IE compatibility view list. Thus when you visit the new URL, IE is not using compatibility view, and therefore not passing the "MSIE" version of the user agent string, and therefore our extensions are not detecting it as a compatible browser, and so the extensions disable themselves, and suddenly it seems like the EV OWA integration has stopped working.

    Andrew_G_ nailed this on Friday, admittedly without much in the way of explanation. But that's clearly what's going on, and it will start working again once you get IE to use compatibility view for the new OWA URL.

    --Chris