Citrix and Internet Explorer 11 Enterprise Mode

Citrix and Internet Explorer 11 Enterprise Mode Part 1

This three-part article explains the use case, best practice, and design methodology to use
Internet Explorer 11 Enterprise Mode using a single XML file hosted on a central web server.
This allows for upgrading to Internet Explorer 11 on Citrix XenApp servers OR client
workstations, elimination of compatibility view mode lists, support for IE 7, 8, 9 and 10 using a
combination of IE 8 Emulation and Document Modes.

• This is not to be mistaken with Windows 10 “Microsoft Edge” – no relation.

• This is not to be mistaken with "Compatibility View" - no relation. Actually, I recommend
disabling this feature using Group Policy.

Do you leverage a different Internet Browser outside work? I do. I use Google Chrome, Mozilla
Firefox and recently IE 11 Edge Mode with Microsoft Windows 10 client OS. In the office,
workstation and servers will generally have some version of Internet Explorer. It is rare to find
anything other than IE installed on Microsoft Server operating system.

Curious why one website opens in Firefox or Chrome but not IE 11? Yet, it opened in IE 9 and
IE 10. This is a long answer but I'll trade you an easy solution instead.

In my experience most corporate environments, the standard is Microsoft Internet Explorer. For
Windows 7 client the latest browser version for download is Internet Explorer 11 + hotfixes.

Microsoft ended support for 8, 9, and 10. Long time coming. Despite the excessive warnings,
websites remain that were built for IE 8. This explains where compatibility view mode is used in
IE 9 and IE 10. Ready to turn that off?

"Microsoft today ended support for old versions of Internet Explorer, including IE8, IE9, and
IE10, as well as Windows 8. For the browsers, the company has also released a final patch
(KB3123303) that includes the latest cumulative security updates and an “End of Life” upgrade
notification." []1]

Consider a scenario where 70% of the internal websites are coded for Internet Explorer 8 and
earlier. IE 8 uses the Trident Engine and developed by Microsoft dating back to October 1997.
Upgrading from IE 8, 9 or 10 to version 11 has risks. The end-user might access internal and
external websites. In my experience, the internal websites pose the greatest risk.

I performed a recent migration from IE 9 to IE 11 for compliance reasons. The customer had
contracts where those customers of the customer mandated IE 11 to meet a security
requirement. Initial inspection of IE 9 Compatibility View Mode sites listed in Group Policy
exceeded 2000 URLs. This was done because those legacy sites worked fine IE 7 and IE 8.

1
Prior attempts to upgrade the Citrix XenApp platform to IE 11 failed. By default IE 11 may not
work with sites coded for earlier versions of Internet Explorer. Roughly 70% of the customer
websites fell in this category. The IE 8 coded sites broke in IE 11 and most of the sites were
"Intranet". Fortunately, I had performed several migrations using IE 11 Enterprise Mode with a
single XML file hosted on Microsoft IIS.

Many companies still run IE 8 whether or workstations or dedicated Citrix silos for backward
compatibility. Dedicated silos gave developers or the business an excuse to forgo upgrading the
code. Now Microsoft has dropped support for the legacy browser. IE 8 often combined with
Compatibility View for sites written in earlier versions of code suited for IE 6 and 7. The result
a large list of websites over several years and often no process for removing those website URLs
(uniform resource locator) after that website decommission. You end up with a list of 3000
websites but where 1000 of those websites no longer exist.

IE 11 Enterprise Mode is a new way for enterprise IT departments to automatically adjust to

legacy coded websites using a centrally hosted XML file. What you get is a 'full featured'
Internet Explorer 8 emulation mode having IE 11 installed to meet compliance mandate. This
effectively eliminates the need for enterprises to standardize on an almost 8-year-old browser.

The reality is more a combination of IE 8, 9 and ten browsers across the corporate environment.
Companies use Internet Explorer and Group Policy to control some of the variables. Sometimes
allowing users to "Add" sites to compatibility view mode using their workstation. This is versus
controlling this setting in Group Policy. While compatibility mode solved some issues, it is far
from a global strategy. Not to mention high maintenance.

Enterprise Mode, if implemented correctly, eliminates the need for enterprises to standardize on
an almost 8-year-old browser and embrace the new world of the modern web. Enterprise mode
implements configuration and code changes to emulate IE 8 while running IE 11. It does not
utilize IE 8 binaries; this is IE 11 emulating IE 8 with code changes and configuration
modifications that are only functional in Enterprise Mode.

2
 SITES XML FILE REQUIREMENTS

Depending on internal structure and delineation of business units determines if one or more XML
file is required. I eliminated over 3000 sites from Group Policy compatibility mode view list and
a single “sites.xml” file behind a Netscaler VIP and two Windows web servers with IIS. The XML
file hosted on a NAS share behind a DFS pointer to which the IIS virtual directory leveraged
across both web servers.

1. One sites.xml file hosted on an Internet Web Hosting platform; HTTP (TCP 80) or https (TCP

443)

2. Notepad++ with XML Module for Syntax Checking

3. A single mistype can result in outage

4. Post-Production, use the process: RFC for Test, RFC for Production

5. Test environment for sites.xml

6. Separate production environment for sites.xml

Assumptions;

1. New organizational unit defined for IE 11 upgrades for workstation and Citrix servers

2. Test OU - points to a test version of the sites.xml file hosted in a different virtual directory

3. Production OU

4. Dedicated Group Policy object with latest IE 11 ADMX files hosted in a “Central Store” []1

5. Disable Compatibility View – Make sure this is disabled so that users cannot add sites to

compatibility view mode and turn off Intranet sites use compatibility mode.

6. Web server and virtual directory path to host “sites.xml” file

7. Notepad++ with XML module or other similar tool for parsing XML logic

VERSION NUMBER

This number must be incremented with each version of the Enterprise Mode site list, letting
Internet Explorer know whether the list is new. Approximately 65 seconds after Internet
Explorer 11 starts, it compares your site list version to the stored version number. If your file
has a higher number, the newer version is loaded.

3
 EMIE TAG

This tag specifies the domains and domain paths that need special treatment and should be
rendered using Enterprise Mode or the default Internet Explorer 11 browser environment. The
“/emie” section controls IE 8 Enterprise mode by FQDN starting right to left. FQDN is "right to
left not left to right".

In the above example, the following is true:

The “mydomain.com” must use IE 8 emulation.

1. The “mydomain.com/desktop/forms” does NOT use IE 8 emulation.

2. The “qa.mydomain.com” must use IE 8 emulation.

3. The “preview.mydomain.com” must use IE 8 emulation.

To make sure your site list is up-to-date;

1. Wait 65 seconds after opening Internet Explorer

2. Check that the CurrentVersion value in the HKEY_CURRENT_USER\Software\Microsoft\Internet

Explorer\Main\EnterpriseMode\ registry key matches the version number in your file.

4
Document Mode

Introduced with Internet Explorer 8 to discourage proprietary coding for more standardized code
compatible on multiple browsers and devices. Subsequent releases after IE 8 introduced
additional document modes emulating prior supported versions while introducing new features
as defined by industry standards. IE 9 included IE 8 document mode and fundamental changes
to iframes.

IE 10 introduced the functionality to display more than one document mode in the same web
page. Also, if the website or HTML does not specify a document type displays the page in Quirks
mode. This behavior easily changed modifying the “X-UA-Compatible” meta tag.

Windows 10 does not support document modes. IE 11 introduced IE 10 document mode and
the last as Microsoft encourages developers to use IE 11 document mode formerly known as
“Edge.” The flow chart depicts how IE 11 document mode used.

(Source: https://technet.microsoft.com/en-us/library/dn321432.aspx)

5
Windows 10 does not support legacy document mode. Windows 10 leverages Microsoft Edge
(codenamed “Project Spartan”) as the new default browser built for Windows 10. Hence, IE 11
supports legacy document modes but Microsoft Edge with Windows 10 doesn’t. (Reference:
https://dev.windows.com/en-us/microsoft-edge/)

6
SITES XML FILE DESIGN

This document assumes Enterprise Mode enabled in Group Policy and the XML file centrally
hosted on a web server or multiple web servers behind a load-balancer. The XML file is a single
point of failure if were load balancing not leveraged.

The XML design is critical to the implementation and adding or removing sites from the sites.xml
file. The XML file, like DNS, is read “right to left.” As of this writing, options include; IE 11
Default, IE 8 Emulation Mode, IE 10 Document Mode, IE 9 Document Mode, IE 8 Document
Mode, IE 7 Document Mode. IE 8 Emulation Mode not to be confused with IE 8 Document Mode
– no relation.
When we modify Group Policy to point at sites.xml file, perform “ gpupdate /force” on client
machines, Enterprise Mode is enabled. Group policy instructs the Workstation and\or Citrix
server to leverage the sites.xml file to determine what mode is best fit for “mydomain.com” to
anything left or right of .mydomain.com.

Notice the winning GPO is “GPO-IE-11-Enterprise-Mode” and the URL location

is http://webserver.mydomain.com/entmode/prod/sites.xml.

Example: Commercial GPResult

Subsequently, we can validate the registry key

The corresponding registry key:

7
If the sites.xml file is empty; everything runs IE 11 by default. The example above quickest
check to validate that user registry key set by GPO set to the Enterprise Sites File location.

Beginning file:

The assumption for this exercise is EMIE (Enterprise Mode) by default is IE 11 unless we state
otherwise in the XML file. I’m hosting the XML file on IIS 7.5, but any webserver will suffice.

Anything listed in the EMIE section is your exclusion list or “false”. Ideal where the majority of
internal websites date back to IE 8, 7 or 6 version of Internet Explorer.

mydomain.com. = IE 8 Emulation Mode

Above I added mydomain.com as exclusion to EMIE to force the IE 8 emulation

So, if you mean IE 8 Emulation Mode (not compatibility mode) that is my default setting for
anything that name and anything that name to the left of that name.

8
XML, like DNS, reads right to left (parsed) and greatest to least from a potential impact
perspective. Although one error at any level results in an outage. An example about this
concept follows; (Starting with the Universe or .com.)

Everything your working within this universe which is XML and all things related to it such as
DNS and FQDN require you to understand the aforementioned concept. XML File parsing begins
with <rules version=”XX”>.

In this example, the Universe is COM. The Solar System is .mydomain.com in (dot)COM
universe. Similar to DNS Name Space without the forward slash and critical to design.

Keeping in mind the above is for demonstration purposes only. The point read right to left not
left to right. Maybe it doesn't make sense now but keep reading. Take note of the syntax. In
part two I demonstrate where the smallest mistake can cause an outage.

In part two, I provide an additional example and deep dive to custom configurations.

9
Citrix and Internet Explorer 11 Enterprise Mode Part 2

Part 1 we discussed Internet Explorer 11 Compatibility Mode settings and the importance of XML
and how the right to left style of parsing is similar to DNS.

XML, like DNS, reads right to left (parsed) and greatest to least from a potential impact
perspective, although one error at any level can result in an outage. An example about this
concept follows, starting with the Universe or .com:

This image above is conceptual and the goal is understanding how the syntax works as it relates
to Internet Explorer 11 parsing the file. Everything your working within this universe which is
XML and all things related to it such as DNS and FQDN require you to understand the
aforementioned concept. XML File parsing begins with <rules version=”XX”>.

In the above example, the Universe is COM. The Solar System is .mydomain.com
in (dot)COM universe, similar to DNS Name Space without the forward slash. .com equals
.universe for this article.

.solarsystem.universe

.earth.solarsystem.universe

Keep in mind the above is for demonstration purposes only. The point is that this is read right to
left, not left to right. Take note of the syntax. In part two I demonstrate where the smallest
mistake can cause an outage.

Note, similar to DNS it reads larger to smaller. Read right to left .com is .universe or the largest
piece of the equation. Where this differs greatly from DNS is what can be written to the right of
.universe (.com, .gov, .net, .etcetera)

.earth.solarsystem.universe/northamerica/usa/texas

Notice, anything to the right of / (right-slash) reads right to left as well but smaller to larger.
Anything right of the slash in XML universe is typically smaller for every slash (/) going right.

.earth.solarsystem.universe/northamerica/usa/texas/dallascounty/dallas

In this example, the Universe COM in Solar System MYDOMAIN is IE 8 Emulation Mode (set to
‘false’) but starting at the far right of virtual directory paths there are exclusion possibilities. This
mode allows a virtual directory path to run alternate modes. Although mydomain.com is set to
“false” I can have any combination of virtual directory paths if I parse right to left.

10
 In the image above “mydomain.com” is excluded from EMIE (Enterprise Mode) but
using <path exclude> set to true on /desktop/forms allows me to run that virtual directory
(path) to the right of FQDN as with IE 11. In this case, I want to exclude “mydomain.com” and
anything to the left of “mydomain.com” in Enterprise Mode (IE 8 Emulation) except where the
path right of “.com” is /desktop/forms. Here are a few examples;

1. Qa.mydomain.com/main = False, IE 8 (Enterprise Mode)

2. Qa.mydomain.com/desktop/forms = True, IE 11

In this scenario, recall that IE 11 is the default but .mydomain.com exists in the file and set to
“false”. Hence, .mydomain.com is by default to run in IE 8 Emulation mode, and now we have
a conflicting request that must be read right to left.

11
For every domain you must ask a question: Are the number of websites in this domain legacy
sites or compatible with IE 11? This may be a question asked by internal developers. If the site
is internal, you should have a point of contact for each website. Knowing this information is
about how you list the domain initially in the XML file.

The domain space is legacy web code or newer web code. This determines whether or not you
set the website to False or True in the EMIE section of the XML file.

If, for example, my-qa.mydomain.com/anything is all legacy code you want my-
qa.mydomain.com to run in IE 8 emulation mode. This would include anything to the left or
right of .mydomain.com. It might
be anything.anything.anything.mydomain.com/anything/anything/anything. A single
line for .mydomain.com set to False alleviates having to add all these entries to the left or right
of .mydomain.com.

If the greater is IE 11, then the least complex might be a single line with false or true preceding
the domain name.

IE 11 interprets the lines above as run everything to the left of ".mydomain.com" in IE 8

emulation mode except line 2 "my-qa." This is also read as anything to the right
of "mydomain.com" such as /anything to be run in IE 8 emulation mode except /anything
in "my-qa.mydomain.com."

XML is parsed right-to-left. Setting “mydomain.com” to false translates

as *.mydomain.com." I can change this default behavior by setting
“anything.mydomain.com” to "true". In this example, “my-qa.mydomain.com” or “my-
qa.” will run as IE 11 but “*anythingelse*.mydomain.com” is still in Enterprise Mode (IE 8
Emulation).

12
RULES VERSION AND INCREMENT

Using a centralized “sites.xml” file might incur a lot of requests if every user in the enclave
were to parse that file every single request or FQDN and where “Enter” key is pressed. To
alleviate this unnecessary traffic, a numeric value is incremented by “1” with each update. The
beginning number is 1 and each increment is synonymous with “new version”. Lines might be
added or removed, but the number can only increment and never decrement.

Beginning File

Version 2, increment change

VERSION NUMBER

This number must be incremented with each version of the Enterprise Mode site list, letting
Internet Explorer know whether the list is new. Approximately 65 seconds after Internet
Explorer 11 starts, it compares your site list version to the stored version number. If your file
has a higher number, the newer version is loaded.

13
DOCUMENT MODE

So, mydomain.com is a separate realm covering a vast space set to IE 8 Emulation Mode where
anything to the left or virtual paths to the right now requires an exclusion not to run as IE
Emulation Mode. Document mode provides a way to adjust for other document types using the
same XML file. As of this writing, options include; IE 11 Default, IE 8 Emulation Mode, IE 10
Document Mode, IE 9 Document Mode, IE 8 Document Mode, and IE 7 Document Mode. IE 8
Emulation Mode should not be confused with IE 8 Document Mode; there is no relationship
between the two.

For more knowledge see the Microsoft publication Fix web compatibility issues using document
modes and the Enterprise Mode site list

It is possible to have a domain listed as "true" or "false" in EMIE (Enterprise Mode) section of
the XML file and run domains to the left (thisisleft.mydomain.com) or to the right
(.mydomain.com/thisistotheright) in different document modes.

Important

Enterprise Mode takes precedence over document modes, so sites that are already included in
the Enterprise Mode site list won’t be affected by this update and will continue to load in
Enterprise Mode, as usual.
14
THE XML DESIGN

There are pros and cons to this design. You can limit the exposure to risks of a single file by
using redundant web servers behind a load-balanced virtual IP address to host the file. A load
balance other IP addresses requires another virtual or physical appliance to assume
responsibility for that service. The Virtual IP (or VIP) automatically load balances incoming
traffic to two or more web servers providing high-availability. See image below, a VIP in this
context is a 4th IP Address where the image below shows a load balancing device hosting a
Virtual IP of 10.10.10.5. The IIS servers arranged in a shared services model behind the Virtual
IP of 10.10.10.5. The sites.xml file hosted on network attached storage or similar high-
availability storage.

Hosting the "sites.xml" file is similar for the majority of implementations. You need a web
server, file share and have a few common choices such as whether or not to use a load balancer
or what type of storage to use.

Where every project differs is the design of the XML file. The design of the
primary XML file is the difference between success and failure. There is the hosting of the file
and what goes in the file; understanding the file architecture, how it is parsed, the version
number, and syntax is critical.

15
 XML SYNTAX ERRORS

XML files can be created or edited with standard text editors. Like PowerShell and other
languages, the syntax is critical. Unlike PowerShell or other languages IE 11 won't show an error
message but instead, won't parse the file. Regardless of where you are in the migration plan,
the following syntax errors cause an outage. In other words, users type in a website, and it
should work. Syntax errors here might cause that website to run in the wrong emulation mode,
and users cannot perform their job.

1. Extra space or missing space

2. Extra “

3. Extra /

4. Missing /

5. Missing < or > or = or “ or [space]

6. Missing characters

7. Misspelled words

Here is an example of a few mistakes that cause an outage:

1. Missing the closing quote (")

2. Comma instead of period

SUMMARY

This article provides guidance regarding the XML file and how best to structure the file based on
the assessment of internal websites to determine by domain whether to use IE 11 native mode
or IE 8 emulation mode. The next article discusses the use of "Dos and Donts".

16
NOTE

This series pertains to Windows 7 and Server 2008, 2008 R2, 2008 R2 SP1 and Internet Explorer
11. The XML schema changes slightly in Windows 8.1 and higher. At this time, different XML files
are necessary for those operating systems.

VALUE

Does this shared knowledge provide value? If this article has value, please click on "Good
Article" button to your right. Knowing this knowledge is valued by others is motivation to
continue sharing.

17
Citrix and Internet Explorer 11 Enterprise Mode Part 3

Part 1 covered XML design. The XML design is critical to the implementation and adding or

removing sites from the sites.xml file. The XML file, like DNS, is read “right to left.” As of this

writing, options include; IE 11 Default, IE 8 Emulation Mode, IE 10 Document Mode, IE 9

Document Mode, IE 8 Document Mode, and IE 7 Document Mode.

Part 2 covered XML structure and file parsing right to left and document mode. XML, like DNS,

reads right to left (parsed) and greatest to least from a potential impact perspective, although

one error at any level can result in an outage. Document mode provides a way to adjust for

other document types using the same XML file.

ADDITIONAL CONCERNS

Moving from IE 8 using compatibility mode to IE 11 Enterprise Mode with compatibility view

disabled might result in issues that are unrelated to an IE 11 Upgrade but by default, this is

assumed when the issue is related to GPO or some other factor. This section provides examples

of such scenarios.

LOCAL INTRANET ZONE USER AUTHENTICATION

By default, IE 11 without custom configuration using Group Policy has the following setting

for Local Intranet Zone; one of the several settings that results in project defects. Having

this information now resolves a future headache. This setting effectively "disables" the

integrated login for every internal website having a full FQDN. Sites without FQDN (Intranet)

sites would function but none of your sites having a full DNS name such

as site1.vcissgroup.com would resolve.

18
Unfortunately, this causes authentication errors for sites that use Integrated Logon with Active

Directory. It requires a modification to group policy objects (GPO) as follows:

19
This setting enables integrated login for anything listed in Intranet Zone, whether it is the short

name, http://vcissgroup or FQDN http://site1.vcissgroup.com

This assumes Active Directory domain joined workstations. Websites that require "Integrated

login" use Active Directory credentials: the current logon with current password. Other "type"

websites require a separate login ID and password and thus are not impacted by this

modification to group policy.

20
COMPATIBILITY VIEW VERSUS ENTERPRISE MODE

Compatibility View mode and Enterprise Mode cause many issues where one or the other must

take precedent. In other words, they must not be used together. Enterprise Mode requires

“Compatibility View Mode” to be disabled.

The quickest way to disable Compatibility Mode is a custom filter on Group Policy, Computer

Container, All Settings.

Start – Run – MMC.exe > Add or Remove Snap-ins

Group Policy Object Editor > Highlight > Click ADD (or Double Click)

Local Computer > FINISH

21
Verify >Group Policy Object Editor > Local Computer Policy > OK

Click OK

Verify in the top-left that you are at Local

Computer\Computer\Configuration\Administrative Templates\All Settings

All Settings under Computer configuration.

22
FILTER SETTINGS

To expedite this process create a custom "Filter" and search for anything with "compatibility".

Right Click > Filter

This is not considered an optional step. The strategic direction for future versions of IE

is meant to dynamically adjust compatibility. For those having to manage thousands of

websites in Group Policy will appreciate the not -optional aspect of this change.

Turn off Compatibility View = Enabled

Turn off Compatibility View button = Enabled

23
Explanation:

To disable compatibility view requires enabling the Group Policy. Disabling this prevents the

setting from applying automatically to the Intranet zones, users adding sites, or administrators

adding sites.

24
ENTERPRISE MODE – DO AND DON’T

Historically, Windows XP supported IE 6, 7 and 8. Vista only supported 9 and 10. Windows 7 and

Server 2008 shipped with IE 8. Hence, most code was written to the middle version with the

release of IE 11.

It is important to understand the logic of IE 8 Emulation mode versus running IE 8 and using

Compatibility Mode to fix something written for IE 7. IE 8 emulation mode adjusts for IE 8 and

IE 7 coded sites. It does this without Compatibility mode but instead is native to Enterprise

Mode.

It is important to understand that this version of XML and syntax is specific to Windows 7

operating system and IE 11 running in Enterprise mode. The syntax for Windows 8.1 and 10

requires a different syntax. This series is applicable for 2008 R2 / 2012 / 2012 R2 mixed mode

or native mode domain running Windows 7 client operating systems.

LIST OF DO's

1. IE 11 Enterprise mode is enabled using a dedicated Group Policy Object

2. The Group Policy should be different for each instance where a different website is hosting a

XML file

3. Create IE 11 Enterprise mode group policy objects (GPO) for Workstation and Citrix servers.

• Workstation operating system is assumed to be Windows 7

• Server operating system is assumed to be Microsoft server 2008, 2008R2, 2012, 2012 R2

4. IE 11 Enterprise mode should emulate IE 11 by default and add exclusions as needed (See

PART 1)

5. IE 11 Enterprise mode XML files are hosted on separate, dedicated web servers using HTTP

6. Due to the critical nature, multiple web servers and load balancing technology is

recommended

7. XML file and web server must be accessible by all Workstations by HTTP on TCP port 80

8. XML file and web server must be accessible by all Citrix Servers by HTTP on TCP port 80

9. Use IE 11 Enterprise mode by default

10. IE 11 Compatibility View mode is disabled

25
 LIST OF DON’Ts

1. Do not use the Compatibility Mode View list or carry these forward from previous Group Policy

settings

2. Do not add sites to Compatibility Mode View in GPO in parallel with IE 8 Emulation mode

3. Do not add sites to Compatibility Mode View in GPO before attempting IE 8 Emulation mode

4. Not applicable to Windows 8.1 or higher

GLOBAL REQUIREMENTS

1. Dedicated Server assigned per line-of-business (LOB)

2. Uses IIS 7.5 or higher

3. Does not require new Application Pool, just a virtual directory with correct permissions

4. To use port 80, already opened, a virtual directory is created under the Default Web Site

5. The XML File share should meet the requirement of being accessible by all users using IE 11 per

line-of-business (LOB). Best practice is to utilize IIS and HTTP protocol.

6. Required when enabling Enterprise Mode global and utilizing a centralized file for managing

exclusions

26
 DEDICATED OU ACTIVE DIRECTORY

The aforementioned ADMX files must be copied to the “Central Repository” used to manage each

prospective line of business.

1. None of the IE 8, 9 or 10 settings under IE sections of linked group policy objects (GPO) are

applicable and cause major problems.

2. A new Group Policy Object is required in AD that pertains to only IE 11 and has the

corresponding ADMX files must be referenced

 One for workstation operating system - Windows 7 or lower

 One policy for server operating system - Windows 2008 or higher (IE 11 is installed)

3. This GPO is then linked to the new IE 11 organizational unit (OU)

4. At implementation, no Compatibility View settings should link to the new organizational unit

(OU) for IE 11

5. Placement of the IE 11 organizational unit (OU) is key

 Legacy browser Compatibility View settings must not apply

 Sites listed in Trusted, Intranet, and Internet still apply

NOTE

This applies to the version 1 for IE 11 Enterprise Mode using Windows 7 and Internet Explorer

11

SUMMARY

This three-part series provides beginning information to implement Internet Explorer 11

Enterprise Mode. Done correctly IE 11 Enterprise mode eliminates the need for compatibility

mode and uses IE 11 emulation and document modes for internal or external websites that

require legacy modes to work.

27
https://www.experts-exchange.com/articles/25239/Citrix-and-Internet-Explorer-11-Enterprise-
Mode-Part-1.html

https://www.experts-exchange.com/articles/25319/Citrix-and-Internet-Explorer-11-Enterprise-
Mode-Part-2.html

https://www.experts-exchange.com/articles/26339/Citrix-and-Internet-Explorer-11-Enterprise-
Mode-Part-3.html

28