Updated to remove IP range limitations and to update the TOC

This commit is contained in:
LizRoss
2016-08-17 13:43:46 -07:00
parent f2af099b46
commit 157289a32b
3 changed files with 37 additions and 24 deletions

View File

@ -15,8 +15,9 @@ ms.sitesec: library
**Applies to:**
- Windows 8.1
- Windows 7
- 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](enterprise-mode-schema-version-2-guidance.md).
@ -86,7 +87,14 @@ This table includes the elements used by the Enterprise Mode schema.
<emie>
<domain>contoso.com</domain>
</emie>
&lt;/rules>&gt;</pre></td>
&lt;/rules&gt;</pre>
<strong>-or-</strong>
<pre class="syntax">&lt;rules version="205"&gt;
&lt;emie&gt;
&lt;domain&gt;[10.122.34.99]:8080&lt;/domain&gt;
&lt;/emie&gt;
&lt;/rules&gt;</pre>
</td>
<td>Internet Explorer 11 and Microsoft Edge</td>
</tr>
<tr>
@ -191,7 +199,6 @@ For example, say you want all of the sites in the contoso.com domain to open usi
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:
- Dont use protocols. For example, `http://`, `https://`, or custom protocols. They break parsing.
- Dont use wildcards.
- Don't use IP Addresses.
- Dont use query strings, ampersands break parsing.
## How to use trailing slashes
@ -283,5 +290,4 @@ If you want to target specific sites in your organization.
<li>contoso.com/about and everything underneath that node will load in Enterprise Mode, including contoso.com/about/business because the last rule is ignored.</li>
</ul>
</td></tr>
</table>
</table>

View File

@ -118,7 +118,11 @@ This table includes the elements used by the v.2 version of the Enterprise Mode
&lt;site url="contoso.com"&gt;
&lt;compat-mode&gt;default&lt;/compat-mode&gt;
&lt;open-in&gt;none&lt;/open-in&gt;
&lt;/site&gt;</pre><p>
&lt;/site&gt;</pre>
<strong>-or-</strong>
<pre class="syntax">&lt;site url="[10.122.34.99]:8080"&gt;
&lt;compat-mode&gt;IE8Enterprise&lt;/compat-mode&gt;
&lt;site&gt;</pre><p>
You can also use the self-closing version, &lt;url="contoso.com" /&gt;, which also sets:
<ul>
<li>&lt;compat-mode&gt;default&lt;/compat-mode&gt;</li>
@ -133,7 +137,11 @@ You can also use the self-closing version, &lt;url="contoso.com" /&gt;, which al
<pre class="syntax">
&lt;site url="contoso.com"&gt;
&lt;compat-mode&gt;IE8Enterprise&lt;/compat-mode&gt;
&lt;/site&gt;</pre><p>
&lt;/site&gt;</pre>
<strong>-or-</strong>
<pre class="syntax">&lt;site url="[10.122.34.99]:8080"&gt;
&lt;compat-mode&gt;IE8Enterprise&lt;/compat-mode&gt;
&lt;site&gt;</pre><p>
Where:
<ul>
<li><b>IE8Enterprise.</b> Loads the site in IE8 Enterprise Mode.<br>This element is required for sites included in the <b>EmIE</b> section of the v.1 schema and is needed to load in IE8 Enterprise Mode.</li><p>
@ -260,7 +268,6 @@ We recommend that you not add any of the following items to your schema because
- Dont use protocols. For example, http://, https://, or custom protocols. They break parsing.
- Dont use wildcards.
- Don't use IP Addresses.
- Dont use query strings, ampersands break parsing.
## Related topics