| Setting name | -Option | -
|---|---|
| Turn on Site Discovery WMI output | -Off | -
| Turn on Site Discovery XML output | -Blank | -
| Setting name | -Option | -
|---|---|
| Turn on Site Discovery WMI output | -On | -
| Turn on Site Discovery XML output | -Blank | -
| Setting name | -Option | -
|---|---|
| Turn on Site Discovery WMI output | -Off | -
| Turn on Site Discovery XML output | -XML file path | -
| Setting name | -Option | -
|---|---|
| Turn on Site Discovery WMI output | -On | -
| Turn on Site Discovery XML output | -XML file path | -
| 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="false">fabrikam.com - <path exclude="true">/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 | -
<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="false">fabrikam.com
<path exclude="true">/products</path>
</domain>
</emie>
Where [https://fabrikam.com](https://fabrikam.com) doesn't use IE8 Enterprise Mode, but [https://fabrikam.com/products](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 that is excluded from getting the behavior applied. This attribute 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 doesn't use IE8 Enterprise Mode, but https://fabrikam.com/products does. |
-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 | -
<emie>
<domain exclude="false">fabrikam.com
<path exclude="true">/products</path>
</domain>
</emie>
Where [https://fabrikam.com](https://fabrikam.com) doesn't use IE8 Enterprise Mode, but [https://fabrikam.com/products](https://fabrikam.com/products) does.|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. diff --git a/browsers/enterprise-mode/enterprise-mode-schema-version-2-guidance.md b/browsers/enterprise-mode/enterprise-mode-schema-version-2-guidance.md index 70694a3df2..fcdaa18eee 100644 --- a/browsers/enterprise-mode/enterprise-mode-schema-version-2-guidance.md +++ b/browsers/enterprise-mode/enterprise-mode-schema-version-2-guidance.md @@ -92,194 +92,32 @@ Make sure that you don't specify a protocol when adding your URLs. Using a URL l ### 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 | -
<site-list version="205">| 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.
<site url="contoso.com">
<compat-mode>IE8Enterprise</compat-mode>
<open-in>IE11</open-in>
</site>
</site-list>
<site url="contoso.com">
<compat-mode>default</compat-mode>
<open-in>none</open-in>
</site>
<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:
**or**
<site url="contoso.com">
<compat-mode>IE8Enterprise</compat-mode>
</site>
<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
**Important**
This tag replaces the combination of the `"forceCompatView"="true"` attribute and the list of sites specified in the EmIE section of the v.1 version of the schema.
<site url="contoso.com">
<open-in>none</open-in>
</site>
Where
| Attribute | -Description | -Supported browser | -
|---|---|---|
| allow-redirect | -A boolean attribute of the <open-in> element that controls the behavior for redirected sites. Setting this attribute to "true" indicates that the site will open in IE11 or Microsoft Edge even if the site is navigated to as part of a HTTP or meta refresh redirection chain. Omitting the attribute is equivalent to "false" (sites in redirect chain will not open in another browser).
- Example - -<site url="contoso.com/travel"> - <open-in allow-redirect="true">IE11</open-in> -</site>-In this example, if https://contoso.com/travel is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer. |
-Internet Explorer 11 and Microsoft Edge | -
| 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 https://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 https://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 | -
<site url="contoso.com/travel">In this example, if [https://contoso.com/travel](https://contoso.com/travel) is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer.| Internet Explorer 11 and Microsoft Edge| +|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.
<open-in allow-redirect="true">IE11 </open-in>
</site>
<site url="contoso.com:8080">In this example, going to [https://contoso.com:8080](https://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: -
<compat-mode>IE8Enterprise</compat-mode>
<open-in>IE11</open-in>
</site>
| 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> |
-
<emie>With:
<domain exclude="false">contoso.com</domain>
</emie>
<site url="contoso.com"/>**-AND-**
<compat-mode>IE8Enterprise</compat-mode>
</site>
<emie>
<domain exclude="true">contoso.com
<path exclude="false" forceCompatView="true">/about</path>
</domain>
</emie>
<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. diff --git a/browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md b/browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md index 65fbb8eaaf..488c893951 100644 --- a/browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md +++ b/browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md @@ -205,68 +205,28 @@ You can use Group Policy to finish setting up Enterprise Site Discovery. If you You can use both the WMI and XML settings individually or together: **To turn off Enterprise Site Discovery** -
| Setting name | -Option | -
|---|---|
| Turn on Site Discovery WMI output | -Off | -
| Turn on Site Discovery XML output | -Blank | -
| Setting name | -Option | -
|---|---|
| Turn on Site Discovery WMI output | -On | -
| Turn on Site Discovery XML output | -Blank | -
| Setting name | -Option | -
|---|---|
| Turn on Site Discovery WMI output | -Off | -
| Turn on Site Discovery XML output | -XML file path | -
| Setting name | -Option | -
|---|---|
| Turn on Site Discovery WMI output | -On | -
| Turn on Site Discovery XML output | -XML file path | -
| 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 | -
<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="false">fabrikam.com
<path exclude="true">/products</path>
</domain>
</emie>
Where [https://fabrikam.com](https://fabrikam.com) doesn't use IE8 Enterprise Mode, but [https://fabrikam.com/products](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 Enterprise Mode. This attribute is only supported on the <domain> and <path> elements in the <emie> section. If this attribute is absent, it defaults to false.
- - 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 | -
| docMode | -Specifies the document mode to apply. This attribute is only supported on <domain> or <path> elements in the <docMode> section.
- - Example: --<docMode> - <domain>fabrikam.com - <path docMode="9">/products</path> - </domain> -</docMode> -Where https://fabrikam.com loads in IE11 document mode, but https://fabrikam.com/products uses IE9 document mode. |
-Internet Explorer 11 | -
| doNotTransition | -Specifies that the page should load in the current browser, otherwise it will open in IE11. This attribute is supported on all <domain> or <path> elements. If this attribute is absent, it defaults to false.
- - Example: --<emie> - <domain doNotTransition="false">fabrikam.com - <path doNotTransition="true">/products</path> - </domain> -</emie> -Where https://fabrikam.com opens in the IE11 browser, but https://fabrikam.com/products loads in the current browser (eg. Microsoft Edge). |
-Internet Explorer 11 and Microsoft Edge | -
| forceCompatView | -Specifies that the page should load in IE7 document mode (Compat View). This attribute is only supported on <domain> or <path> elements in the <emie> section. If the page is also configured to load in Enterprise Mode, it will load in IE7 Enterprise Mode. Otherwise (exclude="true"), it will load in IE11's IE7 document mode. If this attribute is absent, it defaults to false.
- - Example: --<emie> - <domain exclude="true">fabrikam.com - <path forceCompatView="true">/products</path> - </domain> -</emie> -Where https://fabrikam.com does not use Enterprise Mode, but https://fabrikam.com/products uses IE7 Enterprise Mode. |
-Internet Explorer 11 | -
<emie>
<domain exclude="false">fabrikam.com
<path exclude="true">/products</path>
</domain>
</emie>
Where [https://fabrikam.com](https://fabrikam.com) doesn't use IE8 Enterprise Mode, but [https://fabrikam.com/products](https://fabrikam.com/products) does.|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="9">/products</path>
</domain>
</docMode>|Internet Explorer 11| +|doNotTransition| Specifies that the page should load in the current browser, otherwise it will open in IE11. This attribute is supported on all <domain> or <path> elements. If this attribute is absent, it defaults to false.
**Example**<emie>
<domain doNotTransition="false">fabrikam.com
<path doNotTransition="true">/products</path>
</domain>
</emie>Where [https://fabrikam.com](https://fabrikam.com) opens in the IE11 browser, but [https://fabrikam.com/products](https://fabrikam.com/products) loads in the current browser (eg. Microsoft Edge)|Internet Explorer 11 and Microsoft Edge| +|forceCompatView|Specifies that the page should load in IE7 document mode (Compat View). This attribute is only supported on <domain> or <path> elements in the <emie> section. If the page is also configured to load in Enterprise Mode, it will load in IE7 Enterprise Mode. Otherwise (exclude="true"), it will load in IE11's IE7 document mode. If this attribute is absent, it defaults to false.
**Example**<emie>
<domain doNotTransition="false">fabrikam.com
<path doNotTransition="true">/products</path>
</domain>
</emie>Where [https://fabrikam.com](https://fabrikam.com) does not use Enterprise Mode, but [https://fabrikam.com/products](https://fabrikam.com/products) uses IE7 Enterprise Mode.|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. diff --git a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md index 299c6c093f..d9e6edd663 100644 --- a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md +++ b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md @@ -97,197 +97,31 @@ The following is an example of the v.2 version of the Enterprise Mode schema. ### 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 | -
<site-list version="205">| 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.
<site url="contoso.com">
<compat-mode>IE8Enterprise</compat-mode>
<open-in>IE11</open-in>
</site>
</site-list>
<site url="contoso.com">
<compat-mode>default</compat-mode>
<open-in>none</open-in>
</site>
<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:
**or**
<site url="contoso.com">
<compat-mode>IE8Enterprise</compat-mode>
</site>
<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
**Important**
This tag replaces the combination of the `"forceCompatView"="true"` attribute and the list of sites specified in the EmIE section of the v.1 version of the schema.
<site url="contoso.com">
<open-in>none</open-in>
</site>
Where
| Attribute | -Description | -Supported browser | -
|---|---|---|
| allow-redirect | -A boolean attribute of the <open-in> element that controls the behavior for redirected sites. Setting this attribute to "true" indicates that the site will open in IE11 or Microsoft Edge even if the site is navigated to as part of a HTTP or meta refresh redirection chain. Omitting the attribute is equivalent to "false" (sites in redirect chain will not open in another browser).
- Example - -<site url="contoso.com/travel"> - <open-in allow-redirect="true">IE11</open-in> -</site>-In this example, if https://contoso.com/travel is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer. |
-Internet Explorer 11 and Microsoft Edge | -
| 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 https://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 | -
<site url="contoso.com/travel">In this example, if [https://contoso.com/travel](https://contoso.com/travel) is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer.
<open-in allow-redirect="true">IE11 </open-in>
</site>
<site url="contoso.com:8080">In this example, going to [https://contoso.com:8080](https://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: -
<compat-mode>IE8Enterprise</compat-mode>
<open-in>IE11</open-in>
</site>
| Deprecated element/attribute | -New element | -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>contoso.com</domain> -</emie>-With: - -<site url="contoso.com"/> - <compat-mode>IE8Enterprise</compat-mode> - <open-in>IE11</open-in> -</site>--AND- -Replace: - -<emie> - <domain exclude="true" doNotTransition="true"> - contoso.com - <path forceCompatView="true">/about</path> - </domain> -</emie>-With: - -<site url="contoso.com/about"> - <compat-mode>IE7Enterprise</compat-mode> - <open-in>IE11</open-in> -</site> |
-
<emie>With:
<domain exclude="false">contoso.com</domain>
</emie>
<site url="contoso.com"/>**-AND-**
<compat-mode>IE8Enterprise</compat-mode>
</site>
<emie>
<domain exclude="true">contoso.com
<path exclude="false" forceCompatView="true">/about</path>
</domain>
</emie>
<site url="contoso.com/about">
<compat-mode>IE7Enterprise</compat-mode>
<open-in>IE11</open-in>
</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. diff --git a/education/windows/chromebook-migration-guide.md b/education/windows/chromebook-migration-guide.md index 2fb2324ddc..af0ea18ce1 100644 --- a/education/windows/chromebook-migration-guide.md +++ b/education/windows/chromebook-migration-guide.md @@ -126,96 +126,22 @@ Table 2 lists the settings in the Device Management node in the Google Admin Con Table 2. Settings in the Device Management node in the Google Admin Console -
| Section | -Settings | -
|---|---|
| Network | -These settings configure the network connections for Chromebook devices and include the following settings categories: -
|
-
| Mobile | -These settings configure and manage companion devices (such as smartphones or tablets) that are used in conjunction with the Chromebook devices and include the following settings categories: -
|
-
| Chrome management | -These settings configure and manage companion devices (such as smartphones or tablets) that are used in conjunction with the Chromebook devices and include the following settings categories: -
|
-
These settings configure the network connections for Chromebook devices and include the following settings categories:
| Section | -Settings | -
|---|---|
Basic settings |
-These settings configure password management and whether or not two-factor authentication (2FA) is configured. You can set the minimum password length, the maximum password length, if non-admin users can recover their own passwords, and enable 2FA. -Record these settings and use them to help configure your on-premises Active Directory or Azure Active Directory (Azure AD) to mirror the current behavior of your Chromebook environment. |
-
Password monitoring |
-This section is used to monitor the strength of user passwords. You don’t need to migrate any settings in this section. |
-
API reference |
-This section is used to enable access to various Google Apps Administrative APIs. You don’t need to migrate any settings in this section. |
-
Set up single sign-on (SSO) |
-This section is used to configure SSO for Google web-based apps (such as Google Apps Gmail or Google Apps Calendar). While you don’t need to migrate any settings in this section, you probably will want to configure Azure Active Directory synchronization to replace Google-based SSO. |
-
Advanced settings |
-This section is used to configure administrative access to user data and to configure the Google Secure Data Connector (which allows Google Apps to access data on your local network). You don’t need to migrate any settings in this section. |
-
| If you plan to... | -On-premises AD DS | -Azure AD | -Hybrid | -
|---|---|---|---|
| Use Office 365 | -- | X | -X | -
| Use Intune for management | -- | X | -X | -
| Use Microsoft Endpoint Manager for management | -X | -- | X | -
| Use Group Policy for management | -X | -- | X | -
| Have devices that are domain-joined | -X | -- | X | -
| Allow faculty and students to Bring Your Own Device (BYOD) which are not domain-joined | -- | X | -X | -
| Desired feature | -Windows provisioning packages | -Group Policy | -Configuration Manager | -Intune | -MDT | -Windows Software Update Services | -
|---|---|---|---|---|---|---|
| Deploy operating system images | -X | -- | X | -- | X | -- |
| Deploy apps during operating system deployment | -X | -- | X | -- | X | -- |
| Deploy apps after operating system deployment | -X | -X | -X | -- | - | - |
| Deploy software updates during operating system deployment | -- | - | X | -- | X | -- |
| Deploy software updates after operating system deployment | -X | -X | -X | -X | -- | X | -
| Support devices that are domain-joined | -X | -X | -X | -X | -X | -- |
| Support devices that are not domain-joined | -X | -- | - | X | -X | -- |
| Use on-premises resources | -X | -X | -X | -- | X | -- |
| Use cloud-based services | -- | - | - | X | -- | - |
| Product or technology | -Resources | -
|---|---|
| DHCP | -- |
| DNS | -- |
| Product or technology | -Resources | -
|---|---|
| AD DS | -- |
| Azure AD | -- |
| Management system | -Resources | -
|---|---|
| Windows provisioning packages | -- |
| Group Policy | -- |
| Configuration Manager | -- |
| Intune | -- |
| MDT | -- |
| Management system | -Resources | -
|---|---|
| Group Policy | -- |
| Configuration Manager | -- |
| Intune | -- |
| Method | -Description | -
|---|---|
| MDT | -MDT is an on-premises solution that supports initial operating system deployment and upgrade. You can use MDT to deploy and upgrade Windows 10. In addition, you can initially deploy Windows desktop and Microsoft Store apps and software updates.
The advantages of this method are that: -
The disadvantages of this method are that it: - -
|
-
| Microsoft Endpoint Configuration Manager | -Configuration Manager is an on-premises solution that supports operating system management throughout the entire operating system life cycle. You can use Configuration Manager to deploy and upgrade Windows 10. In addition, you can manage Windows desktop and Microsoft Store apps and software updates as well as provide antivirus and antimalware protection.
The advantages of this method are that: -
The disadvantages of this method are that it: -
|
-
| Method | -Description | -
|---|---|
| Group Policy | -Group Policy is an integral part of AD DS and allows you to specify configuration settings for Windows 10 and previous versions of Windows.
The advantages of this method include: -
The disadvantages of this method are that it: -
|
-
| Intune | -Intune is a cloud-based management system that allows you to specify configuration settings for Windows 10, previous versions of Windows, and other operating systems (such as iOS or Android). Intune is a subscription-based cloud service that integrates with Office 365 and Azure AD.
The advantages of this method are that: -
The disadvantages of this method are that it: -
|
-
| Selection | -Management method | -
|---|---|
| Microsoft Endpoint Configuration Manager | -Configuration Manager is an on-premises solution that allows you to specify configuration settings for Windows 10; previous versions of Windows; and other operating systems, such as iOS or Android, through integration with Intune.
The advantages of this method are that: -
The disadvantages of this method are that it: -
|
-
| Intune | -Intune is a cloud-based solution that allows you to manage apps and software updates for Windows 10, previous versions of Windows, and other operating systems (such as iOS or Android). Intune is a subscription-based cloud service that integrates with Office 365 and Azure AD.
The advantages of this method are that: -
The disadvantages of this method are that it: -
|
-
| Microsoft Endpoint Manager and Intune (hybrid) | -Configuration Manager and Intune together extend Configuration Manager from an on-premises management system for domain-joined devices to a solution that can manage devices regardless of their location and connectivity options. This hybrid option provides the benefits of both Configuration Manager and Intune.
The advantages of this method are that: -
The disadvantages of this method are that it: -
|
-
| Method | -Description and reason to select this method | - -
|---|---|
| Windows Deployment Services | -This method: -
Select this method when you want to deploy Windows over-the-network and perform diskless booting. The advantage of this method is that the diskless media are generic and typically don’t require updates after you create them (LTI and ZTI access the centrally located deployment content over the network). The disadvantage of this method is that over-the-network deployments are slower than deployments from local media, and you must deploy a Windows Deployment Services server. - |
-
| Bootable media | -This method: -
Select this method when you want to deploy Windows over the network and are willing to boot the target device from local media. The advantage of this method is that the media are generic and typically don’t require updates after you create them (LTI and ZTI access the centrally located deployment content over the network). The disadvantage of this method is that over-the-network deployments are slower than deployment from local media. - |
-
| Deployment media | -This method: -
Select this method when you want to perform local deployments and are willing to boot the target device from a local USB hard disk. The advantage of this method is that local deployments are faster than over-the-network deployments. The disadvantage of this method is that each time you change the deployment share or distribution point content, you must regenerate the deployment media and update the USB hard disk. - |
-
| Task | -Description | - -
|---|---|
| 1. Import operating systems | -Import the operating systems that you selected in the Select the operating systems section into the deployment share. For more information about how to import operating systems, see Import an Operating System into the Deployment Workbench. | -
| 2. Import device drivers | -Device drivers allow Windows 10 to know a device’s hardware resources and connected hardware accessories. Without the proper device drivers, certain features may be unavailable. For example, without the proper audio driver, a device cannot play sounds; without the proper camera driver, the device cannot take photos or use video chat. -Import device drivers for each device in your institution. For more information about how to import device drivers, see Import Device Drivers into the Deployment Workbench. - |
-
| 3. Create MDT applications for Microsoft Store apps | -Create an MDT application for each Microsoft Store app you want to deploy. You can deploy Microsoft Store apps by using sideloading, which allows you to use the Add-AppxPackage Windows PowerShell cmdlet to deploy the .appx files associated with the app (called provisioned apps). Use this method to deploy up to 24 apps to Windows 10. - Prior to sideloading the .appx files, obtain the Microsoft Store .appx files that you will use to deploy (sideload) the apps in your provisioning package. For apps in Microsoft Store, you will need to obtain the .appx files by performing one of the following tasks: -
If you are unable to obtain the .appx files from the app software vendor, then you or the students will need to install the apps on the student devices directly from Microsoft Store or Microsoft Store for Business. -If you have Intune or Microsoft Endpoint Configuration Manager, you can deploy Microsoft Store apps after you deploy Windows 10, as described in the Deploy and manage apps by using Intune and Deploy and manage apps by using Microsoft Endpoint Configuration Manager sections. This method provides granular deployment of Microsoft Store apps, and you can use it for ongoing management of Microsoft Store apps. This is the preferred method of deploying and managing Microsoft Store apps. -In addition, you must prepare your environment for sideloading Microsoft Store apps. For more information about how to: -
|
-
| 4. Create MDT applications for Windows desktop apps | -You need to create an MDT application for each Windows desktop app you want to deploy. You can obtain the Windows desktop apps from any source, but ensure that you have sufficient licenses for them. -To help reduce the effort needed to deploy Microsoft Office 2016 desktop apps, use the Office Deployment Tool, as described in Deploy Click-to-Run for Office 365 products by using the Office Deployment Tool. -If you have Intune, you can deploy Windows desktop apps after you deploy Windows 10, as described in the Deploy and manage apps by using Intune section. This method provides granular deployment of Windows desktop apps, and you can use it for ongoing management of the apps. This is the preferred method for deploying and managing Windows desktop apps. - -Note You can also deploy Windows desktop apps after you deploy Windows 10, as described in the Deploy and manage apps by using Intune section. - -For more information about how to create an MDT application for Window desktop apps, see [Create a New Application in the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt). - - |
-
| 5. Create task sequences | -You must create separate task sequences for each Windows 10 edition, processor architecture, operating system upgrade process, and new operating system deployment process. Minimally, create a task sequence for each Windows 10 operating system you imported in step 1—for example, (1) if you want to deploy Windows 10 Education to new devices or refresh existing devices with a new deployment of Windows 10 Education, (2) if you want to upgrade existing devices running Windows 8.1 or Windows 7 to Windows 10 Education, or (3) if you want to run deployments and upgrades for both 32-bit and 64-bit versions of Windows 10. To do so, you must create task sequences that will: -
Again, you will create the task sequences based on the operating systems that you imported in step 1. For more information about how to create a task sequence, see Create a New Task Sequence in the Deployment Workbench. - - |
-
| 6. Update the deployment share | -Updating a deployment share generates the MDT boot images you use to initiate the Windows 10 deployment process. You can configure the process to create 32-bit and 64-bit versions of the .iso and .wim files you can use to create bootable media or in Windows Deployment Services. -For more information about how to update a deployment share, see Update a Deployment Share in the Deployment Workbench. - - |
-
| Recommendation | -Description | - -
|---|---|
| Use of Microsoft accounts | -You want faculty and students to use only Azure AD accounts for institution-owned devices. For these devices, do not use Microsoft accounts or associate a Microsoft account with the Azure AD accounts. - -**Note** Personal devices typically use Microsoft accounts. Faculty and students can associate their Microsoft account with their Azure AD account on these devices. -**Group Policy.** Configure the [Accounts: Block Microsoft accounts](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj966262(v=ws.11)) Group Policy setting to use the **Users can’t add Microsoft accounts** setting option. -**Intune.** To enable or disable the use of Microsoft accounts, use the **Allow Microsoft account**, **Allow adding non-Microsoft accounts manually**, and **Allow settings synchronization for Microsoft accounts** policy settings under the **Accounts and Synchronization** section of a **Windows 10 General Configuration** policy. - - |
-
| Restrict the local administrator accounts on the devices | -Ensure that only authorized users are local administrators on institution-owned devices. Typically, you don’t want students to be administrators on instruction-owned devices. Explicitly specify the users who will be local administrators on a group of devices. -Group Policy. Create a Local Group Group Policy preference to limit the local administrators group membership. Select the Delete all member users and Delete all member groups check boxes to remove any existing members. For more information about how to configure Local Group preferences, see Configure a Local Group Item. -Intune. Not available. - - |
-
| Manage the built-in administrator account created during device deployment | -When you use MDT to deploy Windows 10, the MDT deployment process automatically creates a local Administrator account with the password you specified. As a security best practice, rename the built-in Administrator account and (optionally) disable it. -Group Policy. To rename the built-in Administrator account, use the Accounts: Rename administrator account Group Policy setting. For more information about how to rename the built-in Administrator account, see To rename the Administrator account using the Group Policy Management Console. You specify the new name for the Administrator account. To disable the built-in Administrator account, use the Accounts: Administrator account status Group Policy setting. For more information about how to disable the built-in Administrator account, see Accounts: Administrator account status. -Intune. Not available. - - |
-
| Control Microsoft Store access | -You can control access to Microsoft Store and whether existing Microsoft Store apps receive updates. You can only disable the Microsoft Store app in Windows 10 Education and Windows 10 Enterprise. -Group Policy. To disable the Microsoft Store app, use the Turn off the Store Application group policy setting. To prevent Microsoft Store apps from receiving updates, use the Turn off Automatic Download and Install of updates Group Policy setting. For more information about configuring these settings, see Can I use Group Policy to control the Microsoft Store in my enterprise environment?. -Intune. To enable or disable Microsoft Store access, use the Allow application store policy setting in the Apps section of a Windows 10 General Configuration policy. - - |
-
| Use of Remote Desktop connections to devices | -Remote Desktop connections could allow unauthorized access to the device. Depending on your institution’s policies, you may want to disable Remote Desktop connections on your devices. -Group Policy. To enable or disable Remote Desktop connections to devices, use the Allow Users to connect remotely using Remote Desktop setting in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections. -Intune. Not available. - - |
-
| Use of camera | -A device’s camera can be a source of disclosure or privacy issues in an education environment. Depending on your institution’s policies, you may want to disable the camera on your devices. -Group Policy. Not available. -Intune. To enable or disable the camera, use the Allow camera policy setting in the Hardware section of a Windows 10 General Configuration policy. - - |
-
| Use of audio recording | -Audio recording (by using the Sound Recorder app) can be a source of disclosure or privacy issues in an education environment. Depending on your institution’s policies, you may want to disable the Sound Recorder app on your devices. -Group Policy. To disable the Sound Recorder app, use the Do not allow Sound Recorder to run Group Policy setting. You can disable other audio recording apps by using AppLocker policies. To create AppLocker policies, use the information in Editing an AppLocker Policy and Create Your AppLocker Policies. -Intune. To enable or disable audio recording, use the Allow voice recording policy setting in the Features section of a Windows 10 General Configuration policy. - - |
-
| Use of screen capture | -Screen captures can be a source of disclosure or privacy issues in an education environment. Depending on your institution’s policies, you may want to disable the ability to perform screen captures on your devices. -Group Policy. Not available. -Intune. To enable or disable screen capture, use the Allow screen capture policy setting in the System section of a Windows 10 General Configuration policy. - - |
-
| Use of location services | -Providing a device’s location can be a source of disclosure or privacy issues in an education environment. Depending on your institution’s policies, you may want to disable the location service on your devices. -Group Policy. To enable or disable location services, use the Turn off location group policy setting in User Configuration\Windows Components\Location and Sensors. -Intune. To enable or disable location services, use the Allow geolocation policy setting in the Hardware section of a Windows 10 General Configuration policy. - - |
-
| Changing wallpaper | -Custom wallpapers can be a source of disclosure or privacy issues in an education environment (if the wallpaper displays information about the user or device). Depending on your institution’s policies, you may want to prevent users from changing the wallpaper on institution-owned devices. -Group Policy. To configure the wallpaper, use the Desktop WallPaper setting in User Configuration\Administrative Templates\Desktop\Desktop. -Intune. Not available. - - |
-
| Task and resources | -Monthly | -New semester or academic year | -As required | -
|---|---|---|---|
| Verify that Windows Update is active and current with operating system and software updates. -For more information about completing this task when you have: -
|
-x | -x | -x | -
| Verify that Windows Defender is active and current with malware Security intelligence. -For more information about completing this task, see Turn Windows Defender on or off and Updating Windows Defender. - |
-x | -x | -x | -
| Verify that Windows Defender has run a scan in the past week and that no viruses or malware were found. -For more information about completing this task, see the “How do I find and remove a virus?” topic in Protect my PC from viruses. - |
-x | -x | -x | -
| Download and approve updates for Windows 10, apps, device driver, and other software. -For more information, see: - - |
-x | -x | -x | -
| Verify that you’re using the appropriate Windows 10 servicing options for updates and upgrades (such as selecting whether you want to use Current Branch or Current Branch for Business). -For more information about Windows 10 servicing options for updates and upgrades, see Windows 10 servicing options. - |
-- | x | -x | -
| Refresh the operating system and apps on devices. -For more information about completing this task, see the following resources: - - |
-- | x | -x | -
| Install any new Windows desktop apps, or update any Windows desktop apps used in the curriculum. -For more information, see: - - |
-- | x | -x | -
| Install new or update existing Microsoft Store apps used in the curriculum. -Microsoft Store apps are automatically updated from Microsoft Store. The menu bar in the Microsoft Store app shows whether any Microsoft Store app updates are available for download. -You can also deploy Microsoft Store apps directly to devices by using Intune, Microsoft Endpoint Configuration Manager, or both in a hybrid configuration. For more information, see: - - |
-- | x | -x | -
| Remove unnecessary user accounts (and corresponding licenses) from AD DS and Office 365 (if you have an on-premises AD DS infrastructure). -For more information about how to: -
|
-- | x | -x | -
| Add new accounts (and corresponding licenses) to AD DS (if you have an on-premises AD DS infrastructure). -For more information about how to: -
|
-- | x | -x | -
| Remove unnecessary user accounts (and corresponding licenses) from Office 365 (if you do not have an on-premises AD DS infrastructure). -For more information about how to: -
|
-- | x | -x | -
| Add new accounts (and corresponding licenses) to Office 365 (if you don’t have an on-premises AD DS infrastructure). -For more information about how to: -
|
-- | x | -x | -
| Create or modify security groups, and manage group membership in Office 365. -For more information about how to: -
|
-- | x | -x | -
| Create or modify Exchange Online or Microsoft Exchange Server distribution lists in Office 365. -For more information about how to create or modify Exchange Online or Exchange Server distribution lists in Office 365, see Create and manage distribution groups and Create, edit, or delete a security group. - |
-- | x | -x | -
| Install new student devices. -Follow the same steps you followed in the Deploy Windows 10 to devices section. - |
-- | - | x | -
| Supports all free and paid products | -|||
|---|---|---|---|
-
|
-
-
|
-
-
|
-
-
|
-
| Setting | -Description | -
|---|---|
ReportingEnabled |
- Enables the client to return information to a reporting server. This setting is required for the client to collect the reporting data on the client. |
-
ReportingServerURL |
- Specifies the location on the reporting server where client information is saved. For example, https://<reportingservername>:<reportingportnumber>. -
- Note
- This is the port number that was assigned during the Reporting Server setup -
-
- |
-
Reporting Start Time |
- This is set to schedule the client to automatically send the data to the server. This setting will indicate the hour at which the reporting data will start to send. It is in the 24 hour format and will take a number between 0-23. |
-
ReportingRandomDelay |
- Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and ReportingRandomDelay and will wait the specified duration before sending data. |
-
ReportingInterval |
- Specifies the retry interval that the client will use to resend data to the reporting server. |
-
ReportingDataCacheLimit |
- Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. |
-
ReportingDataBlockSize |
- Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. |
-
| Cmdlet | -Examples | -
|---|---|
Enable-AppVClientConnectionGroup |
- Enable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345 |
-
Disable-AppVClientConnectionGroup |
- Disable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345 |
-
| Cmdlet | -Parameter and values | -Example | -
|---|---|---|
Set-AppvClientConfiguration |
- -RequirePublishAsAdmin -
|
- Set-AppvClientConfiguration -RequirePublishAsAdmin 1 |
-
| - | Describes the connection group virtual environment. |
-
| - | Describes the connection group file. |
-
| - | Explains how to create a new connection group. |
-
How to Create a Connection Group with User-Published and Globally Published Packages |
-Explains how to create a new connection group that contains a mix of packages that are published to the user and published globally. |
-
| - | Explains how to delete a connection group. |
-
| - | Explains how to publish a connection group. |
-
| - | Explains how to configure a connection group to accept any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create. |
-
How to Allow Only Administrators to Enable Connection Groups |
-Explains how to configure the App-V client so that only administrators (not end users) can enable or disable connection groups. |
-
| New in App-V for Windows client | -Prior to App-V for Windows 10 | -
|---|---|
New .xml files are created corresponding to the .osd files associated with a package; these files include the following information: -
You can now choose to add information from a subset of the .osd files in the source directory to the package using the |
-Registry information and scripts included in .osd files associated with a package were not included in package converter output. -The package converter would populate the new package with information from all of the .osd files in the source directory. |
-
| These Source directory files… | -…are converted to these Destination directory files… | -…and will contain these items | -Description | -
|---|---|---|---|
|
-
|
-
|
-Each .osd file is converted to a separate, corresponding .xml file that contains the items listed here in App-V deployment configuration format. These items can then be copied from these .xml files and placed in the deployment configuration or user configuration files as desired. -In this example, there are three .xml files, corresponding with the three .osd files in the source directory. Each .xml file contains the environment variables, shortcuts, file type associations, registry information, and scripts in its corresponding .osd file. |
-
|
-
|
-
|
-The information from the .osd files specified in the In this example, environment variables, shortcuts, and file type associations included in X.osd and Y.osd were converted and placed in the App-V package, and some of this information was also included in the deployment configuration and user configuration files. X.osd and Y.osd were used because they were included as arguments to the |
-
| Issue | -Workaround | -
|---|---|
Virtual packages using DSC are not linked after conversion. |
-Link the packages using connection groups. See Managing Connection Groups. |
-
Environment variable conflicts are detected during conversion. |
-Resolve any conflicts in the associated .osd file. |
-
Hard-coded paths are detected during conversion. |
-Hard-coded paths are difficult to convert correctly. The package converter will detect and return packages with files that contain hard-coded paths. View the file with the hard-coded path, and determine whether the package requires the file. If so, it is recommended to re-sequence the package. |
-
| Task | -More Information | -
|---|---|
Review prerequisites. |
-- |
Enable the App-V client. |
-- |
Install App-V Server. |
-- |
Migrate existing packages. |
-See Converting packages created using a prior version of App-V earlier in this topic. |
-