{"id":138,"date":"2014-07-13T13:45:42","date_gmt":"2014-07-13T11:45:42","guid":{"rendered":"https:\/\/www.vioreliftode.com\/?p=138"},"modified":"2016-04-15T13:34:08","modified_gmt":"2016-04-15T11:34:08","slug":"how-you-should-configure-ie-11-to-run-well-with-your-sharepoint-2013-sites","status":"publish","type":"post","link":"https:\/\/www.vioreliftode.com\/index.php\/how-you-should-configure-ie-11-to-run-well-with-your-sharepoint-2013-sites\/","title":{"rendered":"How you should configure IE 11 to run well with your SharePoint 2013 sites?"},"content":{"rendered":"

I simply can’t resist to not make\u00a0the following observation:\u00a0Internet Explorer 11 has been released on 17 October 2013<\/a>\u00a0and Microsoft SharePoint 2013 has been released in October 2012<\/a>. My\u00a0expectation is in these days (July 2014) SharePoint 2013 and Internet Explorer 11 to\u00a0run without issues. Internet Explorer 11 is in the supported list of browsers for SharePoint 2013<\/a>\u00a0and the SP1 version of SharePoint 2013<\/a>\u00a0(re-released version of SP1 \ud83d\ude42<\/span><\/em>)\u00a0“improves compatibility with Internet Explorer 11<\/span>“.
\n<\/em>Well … even with\u00a0June 2014 Cumulative Update<\/a> installed on SharePoint 2013 (the latest cumulative update available at the moment when I am writing this post) you will still have issues if in your company you deployed Internet Explorer 11.<\/p>\n

 <\/p>\n

The most noticeable issue (and believe me it was even before SP1) is the\u00a0Calendar Web Part.<\/p>\n

\"IE11_and_SP2013_Calendar_View\"<\/a>
SharePoint 2013 Calendar View using Internet Explorer 11<\/figcaption><\/figure>\n
\"IE11_and_SP2013_Calendar_Compatibility_View\"<\/a>
SharePoint 2013 Calendar View using Internet Explorer 11 (compatibility view enabled)<\/figcaption><\/figure>\n

 <\/p>\n

Another issue\u00a0with IE 11 and SharePoint 2013 is the disabled\u00a0Web Part Properties.<\/p>\n

\"IE11_and_SP2013_Web_Part_Properties\"<\/a>
SharePoint 2013 Web Part properties using Internet Explorer 11<\/figcaption><\/figure>\n
\"IE11_and_SP2013_Web_Part_Properties_Compatibility_View\"<\/a>
SharePoint 2013 Web Part properties using Internet Explorer 11 (compatibility view enabled)<\/figcaption><\/figure>\n

There are more other\u00a0issues I experienced with native IE 11 on SharePoint 2013 sites.
\nI mentioned just two of them to give you an idea about what to expect and also the possibility to verify and reproduce them\u00a0in your environment.<\/em><\/p>\n

 <\/p>\n


\nThere are two solutions<\/strong><\/span><\/p>\n

    \n
  1. Enable compatibility view for your SharePoint sites.
    \n<\/span>The simplest solution is to\u00a0define a Group Policy Object that will force IE 11 to run in compatibility view when you access your SharePoint sites.
    \n<\/span>[Computer Configuration\\Administrative Templates\\Windows Components\\Internet Explorer\\Compatibility View\\Use Policy List of Quirks Mode sites]\nor
    \n<\/span>[User Configuration\\Administrative Templates\\Windows Components\\Internet Explorer\\Compatibility View\\Use Policy List of Quirks Mode sites]\n<\/span>    \"IE11_and_SP2013_GPO_Compatibility_View_01\"<\/a>\u00a0\u00a0\"IE11_and_SP2013_GPO_Compatibility_View_02\"
    \n<\/a>If you don’t find this setting in your GPO, most likely you are missing any kind of Internet Explorer\u00a0Administrative Templates. In this case\u00a0download the\u00a0    Administrative Templates for Internet Explorer 11<\/a>\u00a0and add the template to your GPO.<\/em><\/li>\n

     <\/p>\n

  2. Enable the\u00a0Internet Explorer 11 Enterprise Mode
    \n<\/span>Recently I’ve been in a\u00a0situation where IE 11 with Enterprise Mode On broke a specific custom functionality added to the production SharePoint farms. That happen because the output\u00a0(HTML response)\u00a0<\/span><\/span>SharePoint 2013 will provide when you use IE 11 with Enterprise Mode On is different\u00a0than\u00a0the output SharePoint 2013 will provide\u00a0when you use native IE 11, or IE 11 with compatibility view enabled<\/span>. OK, honestly not a IE 11 or\u00a0SharePoint 2013 issue – as I said it was a custom functionality added on top of SharePoint (something specific to the company\u00a0I work for). Nothing to blame, but be aware of this HTML output\u00a0differences\u00a0in case for example you are using CSS overwriting (SharePoint branding).
    \n<\/em>
    \nA little bit outside the topic:\u00a0IE 11 Enterprise Mode On will make     IE 11 to <\/a><\/em>use a true IE 8 emulation mode<\/a>\u00a0which can cut specific features for other websites – not a problem in case of SharePoint 2013, but can be a problem for other custom sites (so don’t be radical and activate Enterprise Mode\u00a0everywhere).<\/em><\/span><\/span>Again, GPO simplifies the task.\u00a0In case you don’t find these settings in your GPO you need to\u00a0install Administrative Templates for Internet Explorer 11<\/a>\u00a0and add the template.[Computer Configuration\\Administrative Templates\\Windows Components\\Internet Explorer\\Use the Enterprise Mode IE website list]\nor
    \n<\/span>[User Configuration\\Administrative Templates\\Windows Components\\Internet Explorer\\Use the Enterprise Mode IE website list]\n<\/span>    \"IE11_and_SP2013_GPO_Enterprise_Mode_01\"
    \n<\/a>
    \nUsing\u00a0    Enterprise Mode Site List Manager<\/a>\u00a0you can generate the XML file that\u00a0will “tell” IE 11 to run\u00a0the Enterprise Mode only for specific domains. This XML can be stored on a web server, on a shared folder, or do regular copies of this file on the\u00a0client\u00a0machines.
    \n
    \nIn my case I used a DFS location (\\\\itech.local\\Enterprise_mode\\Enterprise_mode_sites.xml).
    \n<\/em>[Computer Configuration\\Administrative Templates\\Windows Components\\Internet Explorer\\Let users turn on and use Enterprise Mode from the Tools menu]\nor<\/span>
    \n[User Configuration\\Administrative Templates\\Windows Components\\Internet Explorer\\Let users turn on and use Enterprise Mode from the Tools menu]\n<\/span>    \"IE11_and_SP2013_GPO_Enterprise_Mode_02\"<\/a><\/li>\n<\/ol>\n

     <\/p>\n

     <\/p>\n

    Be aware<\/span><\/strong>
    \nIf you have\u00a0a domain added to the Compatibility View list and also to the Enterprise Mode list, IE 11 will use the\u00a0Enterprise Mode\u00a0for that domain.
    \n    Compatibility View and\u00a0Enterprise Mode are two separate things<\/a> and even if SharePoint 2013 sites are well rendered, the output will not be the same\u00a0\ud83d\ude42 <\/span>.<\/p>\n

    \"IE11_and_SP2013_Calendar_Compatibility_View\"<\/a>
    SharePoint 2013 Calendar View using Internet Explorer 11 (compatibility view enabled)<\/figcaption><\/figure>\n
    \"IE11_and_SP2013_Calendar_Enterprise_Mode\"<\/a>
    SharePoint 2013 Calendar View using Internet Explorer 11 (Enterprise Mode On)<\/figcaption><\/figure>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    I simply can’t resist to not make\u00a0the following observation:\u00a0Internet Explorer 11 has been released on 17 October 2013\u00a0and Microsoft SharePoint 2013 has been released in October 2012. My\u00a0expectation is in these days (July 2014) SharePoint 2013 and Internet Explorer 11 to\u00a0run without issues. Internet Explorer 11 is in the supported list of browsers for SharePoint … Continue reading How you should configure IE 11 to run well with your SharePoint 2013 sites?<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"How you should configure IE 11 to run well with your SharePoint 2013 sites? http:\/\/wp.me\/p4NfDd-2e","jetpack_is_tweetstorm":false},"categories":[29],"tags":[44,45,9],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p4NfDd-2e","_links":{"self":[{"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/posts\/138"}],"collection":[{"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/comments?post=138"}],"version-history":[{"count":0,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/posts\/138\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/media?parent=138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/categories?post=138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vioreliftode.com\/index.php\/wp-json\/wp\/v2\/tags?post=138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}