11 KiB
ms.localizationpriority, ms.mktglfcycl, ms.pagetype, description, author, ms.prod, ms.assetid, ms.reviewer, audience, manager, ms.author, title, ms.sitesec, ms.date
| ms.localizationpriority | ms.mktglfcycl | ms.pagetype | description | author | ms.prod | ms.assetid | ms.reviewer | audience | manager | ms.author | title | ms.sitesec | ms.date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| medium | deploy | appcompat | Use the Enterprise Mode Site List Manager to create and update your Enterprise Mode site list for devices running Windows 7 or Windows 8.1 Update. | dansimp | ie11 | 17c61547-82e3-48f2-908d-137a71938823 | itpro | dansimp | dansimp | Enterprise Mode schema v.1 guidance (Internet Explorer 11 for IT Pros) | library | 07/27/2017 |
Enterprise Mode schema v.1 guidance
Applies to:
- Windows 10
- Windows 8.1
- Windows 7
Use the Enterprise Mode Site List Manager (schema v.1) to create and update your Enterprise Mode site list for devices running the v.1 version of the schema, or the Enterprise Mode Site List Manager (schema v.2) to create and update your Enterprise Mode site list for devices running the v.2 version of the schema. We strongly recommend moving to the new schema, v.2. For more info, see Enterprise Mode schema v.2 guidance.
If you don't want to use the Enterprise Mode Site List Manager, you also have the option to update your XML schema using Notepad, or any other XML-editing app.
Enterprise Mode schema v.1 example
The following is an example of the Enterprise Mode schema v.1. This schema can run on devices running Windows 7 and Windows 8.1.
Important
Make sure that you don't specify a protocol when adding your URLs. Using a URL like
<domain>contoso.com</domain>automatically applies to both http://contoso.com and https://contoso.com.
<rules version="1">
<emie>
<domain exclude="false">www.cpandl.com</domain>
<domain exclude="true">www.woodgrovebank.com</domain>
<domain exclude="false" forceCompatView="true">adatum.com</domain>
<domain exclude="true">contoso.com</domain>
<domain exclude="true">relecloud.com
<path exclude="false">/about</path>
</domain>
<domain exclude="false">fabrikam.com
<path exclude="true">/products</path>
</domain>
</emie>
<docMode>
<domain>contoso.com
<path docMode="7">/travel</path>
</domain>
<domain>fabrikam.com
<path docMode="7">/products</path>
</domain>
</docMode>
</rules>
Schema elements
This table includes the elements used by the Enterprise Mode schema.
| Element | Description | Supported browser |
|---|---|---|
| <rules> | Root node for the schema.
Example <rules version="205">
<emie>
<domain>contoso.com</domain>
</emie>
</rules> |
Internet Explorer 11 and Microsoft Edge |
| <emie> | The parent node for the Enterprise Mode section of the schema. All <domain> entries will have either IE8 Enterprise Mode or IE7 Enterprise Mode applied.
Example <rules version="205">
<emie>
<domain>contoso.com</domain>
</emie>
</rules>
-or-
For IPv6 ranges: <rules version="205">
<emie>
<domain>[10.122.34.99]:8080</domain>
</emie>
</rules>
-or-
For IPv4 ranges: <rules version="205">
<emie>
<domain>10.122.34.99:8080</domain>
</emie>
</rules> |
Internet Explorer 11 and Microsoft Edge |
| <docMode> | The parent node for the document mode section of the section. All <domain> entries will get IE5 - IE11 document modes applied. If there's a <domain> element in the <docMode> section that uses the same value as a <domain> element in the <emie> section, the <emie> element is applied.
Example <rules version="205">
<docMode>
<domain docMode="7">contoso.com</domain>
</docMode>
</rules> |
Internet Explorer 11 |
| <domain> | A unique entry added for each site you want to put on the Enterprise Mode site list. The first <domain> element will overrule any additional <domain> elements that use the same value for the section. You can use port numbers for this element.
Example <emie> <domain>contoso.com:8080</domain> </emie> |
Internet Explorer 11 and Microsoft Edge |
| <path> | A unique entry added for each path under a domain you want to put on the Enterprise Mode site list. The <path> element is a child of the <domain> element. Additionally, the first <path> element will overrule any additional <path> elements in the schema section.
Example <emie>
<domain exclude="true">fabrikam.com
<path exclude="false">/products</path>
</domain>
</emie>Where https://fabrikam.com doesn't use IE8 Enterprise Mode, but https://fabrikam.com/products does. |
Internet Explorer 11 and Microsoft Edge |
Schema attributes
This table includes the attributes used by the Enterprise Mode schema.
| Attribute | Description | Supported browser |
|---|---|---|
| <version> | Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <rules> element. | Internet Explorer 11 and Microsoft Edge |
| <exclude> | Specifies the domain or path excluded from applying the behavior and is supported on the <domain> and <path> elements.
Example <emie>
<domain exclude="false">fabrikam.com
<path exclude="true">/products</path>
</domain>
</emie>Where https://fabrikam.com uses IE8 Enterprise Mode, but https://fabrikam.com/products does not. |
Internet Explorer 11 and Microsoft Edge |
| <docMode> | Specifies the document mode to apply. This attribute is only supported on <domain> or <path> elements in the <docMode> section.
Example <docMode>
<domain exclude="false">fabrikam.com
<path docMode="7">/products</path>
</domain>
</docMode> |
Internet Explorer 11 |
Using Enterprise Mode and document mode together
If you want to use both Enterprise Mode and document mode together, you need to be aware that <emie> entries override <docMode> entries for the same domain.
For example, say you want all of the sites in the contoso.com domain to open using IE8 Enterprise Mode, except test.contoso.com, which needs to open in document mode 11. Because Enterprise Mode takes precedence over document mode, if you want test.contoso.com to open using document mode, you'll need to explicitly add it as an exclusion to the <emie> parent node.
<rules version="1">
<emie>
<domain exclude="false">contoso.com</domain>
<domain exclude="true">test.contoso.com</domain>
</emie>
<docMode>
<domain docMode="11">test.contoso.com</domain>
</docMode>
</rules>
What not to include in your schema
We recommend that you not add any of the following items to your schema because they can make your compatibility list behave in unexpected ways:
- Don’t use protocols. For example,
http://,https://, or custom protocols. They break parsing. - Don’t use wildcards.
- Don’t use query strings, ampersands break parsing.
How to use trailing slashes
You can use trailing slashes at the path-level, but not at the domain-level:
- Domain-level. Don’t add trailing slashes to a domain, it breaks parsing.
- Path-level. Adding a trailing slash to a path means that the path ends at that point. By not adding a trailing slash, the rule applies to all of the sub-paths.
Example
<domain exclude="true">contoso.com
<path exclude="false">/about/</path>
</domain>
In this example, contoso.com/about/careers will use the default version of Internet Explorer, even though contoso.com/about/ uses Enterprise Mode.
How to target specific sites
If you want to target specific sites in your organization.
| Targeted site | Example | Explanation |
|---|---|---|
| You can specify subdomains in the domain tag. | <docMode> |
|
| You can specify exact URLs by listing the full path. | <emie> |
|
| You can nest paths underneath domains. | <emie> |
|
| You can’t add a path underneath a path. The file will still be parsed, but the sub-path will be ignored. | <emie> |
|