11 KiB
ms.localizationpriority, ms.mktglfcycl, ms.pagetype, description, author, ms.prod, ms.assetid, title, ms.sitesec
| ms.localizationpriority | ms.mktglfcycl | ms.pagetype | description | author | ms.prod | ms.assetid | title | ms.sitesec |
|---|---|---|---|---|---|---|---|---|
| low | deploy | appcompat | Use the Enterprise Mode Site List Manager to create and update your Enterprise Mode site list for devices running Windows 10. | eross-msft | ie11 | 909ca359-5654-4df9-b9fb-921232fc05f5 | Enterprise Mode schema v.2 guidance (Internet Explorer 11 for IT Pros) | library |
Enterprise Mode schema v.2 guidance
Applies to:
- Windows 10
- Windows 8.1
- Windows 7
Use the Enterprise Mode Site List Manager to create and update your site list for devices running Windows 7, Windows 8.1, and Windows 10, using the version 2.0 (v.2) of the Enterprise Mode schema. 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.
Important
If you're running Windows 7 or Windows 8.1 and you've been using the version 1.0 (v.1) of the schema, you can continue to do so, but you won't get the benefits that come with the updated schema. For info about the v.1 schema, see Enterprise Mode schema v.1 guidance.
Enterprise Mode schema v.2 updates
Because of the schema changes, you can't combine the old version (v.1) with the new version (v.2) of the schema. If you look at your XML file, you can tell which version you're using by:
-
<rules>. If your schema root node includes this key, you're using the v.1 version of the schema.
-
<site-list>. If your schema root node includes this key, you're using the v.2 version of the schema.
You can continue to use the v.1 version of the schema on Windows 10, but you won't have the benefits of the new v.2 version schema updates and new features. Additionally, if you save the v.1 version of the schema in the new Enterprise Mode Site List Manager for Windows 10, it will automatically update the file to use the v.2 version of the schema.
Enterprise Mode v.2 schema example
The following is an example of the v.2 version of the Enterprise Mode schema.
Important
Make sure that you don't specify a protocol when adding your URLs. Using a URL like <url="contoso.com">, automatically applies to both http://contoso.com and https://contoso.com.
<site-list version="205">
<!--- File creation header --->
<created-by>
<tool>EnterpriseSitelistManager</tool>
<version>10240</version>
<date-created>20150728.135021</date-created>
</created-by>
<!--- Begin Site List --->
<site url="www.cpandl.com">
<compat-mode>IE8Enterprise</compat-mode>
<open-in>MSEdge</open-in>
</site>
<site url="www.woodgrovebank.com">
<compat-mode>default</compat-mode>
<open-in>IE11</open-in>
</site>
<site url="adatum.com">
<compat-mode>IE7Enterprise</compat-mode>
<open-in>IE11</open-in>
</site>
<site url="contoso.com">
<compat-mode>default</compat-mode>
<open-in>IE11</open-in>
</site>
<site url="relecloud.com"/>
<compat-mode>default</compat-mode>
<open-in>none</open-in>
<site url="relecloud.com/about">
<compat-mode>IE8Enterprise"</compat-mode>
</site>
<site url="contoso.com/travel">
<compat-mode>IE7</compat-mode>
<open-in>IE11</open-in>
</site>
<site url="fabrikam.com">
<compat-mode>IE8Enterprise</compat-mode>
<open-in>IE11</open-in>
</site>
<site url="fabrikam.com/products">
<compat-mode>IE7</compat-mode>
<open-in>IE11</open-in>
</site>
</site-list>
Updated schema elements
This table includes the elements used by the v.2 version of the Enterprise Mode schema.
| Element | Description | Supported browser |
|---|---|---|
| <site-list> | A new root node with this text is using the updated v.2 version of the schema. It replaces <rules>.
Example <site-list version="205">
<site url="contoso.com">
<compat-mode>IE8Enterprise</compat-mode>
<open-in>IE11</open-in>
</site>
</site-list> |
Internet Explorer 11 and Microsoft Edge |
| <site> | A unique entry added for each site you want to put on the Enterprise Mode site list. The first <site> element will overrule any additional <site> elements that use the same value for the <url> element.
Example <site url="contoso.com"> <compat-mode>default</compat-mode> <open-in>none</open-in> </site>-or- For IPv4 ranges: <site url="10.122.34.99:8080"> <compat-mode>IE8Enterprise</compat-mode> <site> -or- For IPv6 ranges: <site url="[10.122.34.99]:8080"> <compat-mode>IE8Enterprise</compat-mode> <site> You can also use the self-closing version, <url="contoso.com" />, which also sets:
|
Internet Explorer 11 and Microsoft Edge |
| <compat-mode> | A child element that controls what compatibility setting is used for specific sites or domains. This element is only supported in IE11.
Example <site url="contoso.com"> <compat-mode>IE8Enterprise</compat-mode> </site>-or- For IPv4 ranges: <site url="10.122.34.99:8080"> <compat-mode>IE8Enterprise</compat-mode> <site> -or- For IPv6 ranges: <site url="[10.122.34.99]:8080"> <compat-mode>IE8Enterprise</compat-mode> <site> Where:
|
Internet Explorer 11 |
| <open-in> | A child element that controls what browser is used for sites. This element supports the Open in IE11 or Open in Microsoft Edge experiences, for devices running Windows 10.
Example <site url="contoso.com"> <open-in>none</open-in> </site> Where:
|
Internet Explorer 11 and Microsoft Edge |
Updated schema attributes
The <url> attribute, as part of the <site> element in the v.2 version of the schema, replaces the <domain> element from the v.1 version of the schema.
| Attribute | Description | Supported browser |
|---|---|---|
| version | Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <site-list> element. | Internet Explorer 11 and Microsoft Edge |
| url | Specifies the URL (and port number using standard port conventions) to which the child elements apply. The URL can be a domain, sub-domain, or any path URL.
Note Make sure that you don't specify a protocol. Using <site url="contoso.com"> applies to both http://contoso.com and https://contoso.com. Example <site url="contoso.com:8080"> <compat-mode>IE8Enterprise</compat-mode> <open-in>IE11</open-in> </site>In this example, going to http://contoso.com:8080 using Microsoft Edge, causes the site to open in IE11 and load in IE8 Enterprise Mode. |
Internet Explorer 11 and Microsoft Edge |
Deprecated attributes
These v.1 version schema attributes have been deprecated in the v.2 version of the schema:
| Deprecated attribute | New attribute | Replacement example |
|---|---|---|
| <forceCompatView> | <compat-mode> | Replace <forceCompatView="true"> with <compat-mode>IE7Enterprise</compat-mode> |
| <docMode> | <compat-mode> | Replace <docMode="IE5"> with <compat-mode>IE5</compat-mode> |
| <doNotTransition> | <open-in> | Replace <doNotTransition="true"> with <open-in>none</open-in> |
| <domain> and <path> | <site> | Replace:
<emie> <domain exclude="false">contoso.com</domain> </emie>With: <site url="contoso.com"/> <compat-mode>IE8Enterprise</compat-mode> </site>-AND- Replace: <emie>
<domain exclude="true">contoso.com
<path exclude="false" forceCompatView="true">/about</path>
</domain>
</emie>
With:
<site url="contoso.com/about"> <compat-mode>IE7Enterprise</compat-mode> </site> |
While the old, replaced attributes aren't supported in the v.2 version of the schema, they'll continue to work in the v.1 version of the schema. If, however, you're using the v.2 version of the schema and these attributes are still there, the v.2 version schema takes precedence. We don’t recommend combining the two schemas, and instead recommend that you move to the v.2 version of the schema to take advantage of the new features.
Important
Saving your v.1 version of the file using the new Enterprise Mode Site List Manager (schema v.2) automatically updates the XML to the new v.2 version of the schema.
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.