mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 14:27:22 +00:00
Merge pull request #5976 from MicrosoftDocs/master
OOB Publish 10a.m. Pacific
This commit is contained in:
Diana Hanson
GitHub
commit
10b49d794c
@ -201,68 +201,32 @@ 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:
|
You can use both the WMI and XML settings individually or together:
|
||||||
|
|
||||||
**To turn off Enterprise Site Discovery**
|
**To turn off Enterprise Site Discovery**
|
||||||
<table>
|
|
||||||
<tr>
|
|Setting name |Option |
|
||||||
<th>Setting name</th>
|
|---------|---------|
|
||||||
<th>Option</th>
|
|Turn on Site Discovery WMI output | Off |
|
||||||
</tr>
|
|Turn on Site Discovery XML output | Blank |
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery WMI output</td>
|
|
||||||
<td>Off</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery XML output</td>
|
|
||||||
<td>Blank</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
**Turn on WMI recording only**
|
**Turn on WMI recording only**
|
||||||
<table>
|
|
||||||
<tr>
|
|Setting name |Option |
|
||||||
<th>Setting name</th>
|
|---------|---------|
|
||||||
<th>Option</th>
|
|Turn on Site Discovery WMI output | On |
|
||||||
</tr>
|
|Turn on Site Discovery XML output | Blank |
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery WMI output</td>
|
|
||||||
<td>On</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery XML output</td>
|
|
||||||
<td>Blank</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
**To turn on XML recording only**
|
**To turn on XML recording only**
|
||||||
<table>
|
|
||||||
<tr>
|
|Setting name |Option |
|
||||||
<th>Setting name</th>
|
|---------|---------|
|
||||||
<th>Option</th>
|
|Turn on Site Discovery WMI output | Off |
|
||||||
</tr>
|
|Turn on Site Discovery XML output | XML file path |
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery WMI output</td>
|
|
||||||
<td>Off</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery XML output</td>
|
|
||||||
<td>XML file path</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
**To turn on both WMI and XML recording**
|
**To turn on both WMI and XML recording**
|
||||||
<table>
|
|
||||||
<tr>
|
|Setting name |Option |
|
||||||
<th>Setting name</th>
|
|---------|---------|
|
||||||
<th>Option</th>
|
|Turn on Site Discovery WMI output | On |
|
||||||
</tr>
|
|Turn on Site Discovery XML output | XML file path |
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery WMI output</td>
|
|
||||||
<td>On</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery XML output</td>
|
|
||||||
<td>XML file path</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
## Use Configuration Manager to collect your data
|
## Use Configuration Manager to collect your data
|
||||||
After you’ve collected your data, you’ll need to get the local files off of your employee’s computers. To do this, use the hardware inventory process in Configuration Manager, using one of these options:
|
After you’ve collected your data, you’ll need to get the local files off of your employee’s computers. To do this, use the hardware inventory process in Configuration Manager, using one of these options:
|
||||||
|
|||||||
@ -60,132 +60,21 @@ Make sure that you don't specify a protocol when adding your URLs. Using a URL l
|
|||||||
|
|
||||||
### Schema elements
|
### Schema elements
|
||||||
This table includes the elements used by the Enterprise Mode schema.
|
This table includes the elements used by the Enterprise Mode schema.
|
||||||
|
|Element |Description |Supported browser |
|
||||||
<table>
|
|---------|---------|---------|
|
||||||
<thead>
|
|<rules> | Root node for the schema.<br>**Example** <pre class="syntax"><rules version="205"> <br> <emie> <br> <domain>contoso.com</domain> <br> </emie><br> </rules> |Internet Explorer 11 and Microsoft Edge |
|
||||||
<tr class="header">
|
|<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. <br> **Example** <pre class="syntax"><rules version="205"> <br> <emie> <br> <domain>contoso.com</domain> <br> </emie><br></rules> <br> </pre><p> **or** <br> For IPv6 ranges: <pre class="syntax"><br><rules version="205"> <br> <emie> <br> <domain>[10.122.34.99]:8080</domain> <br> </emie><br></rules> </pre><p> <br> **or**<br> For IPv4 ranges:<pre class="syntax"><rules version="205"> <br> <emie> <br> <domain>[10.122.34.99]:8080</domain> <br> </emie><br></rules> | Internet Explorer 11 and Microsoft Edge |
|
||||||
<th>Element</th>
|
|<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. <br> **Example** <pre class="syntax"> <br/><rules version="205"> <br> <docmode> <br> <domain docMode="7">contoso.com</domain> <br> </docmode><br></rules> |Internet Explorer 11 |
|
||||||
<th>Description</th>
|
|<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. <br> **Example** <pre class="syntax"> <br/><emie> <br> <domain>contoso.com:8080</domain><br></emie> |Internet Explorer 11 and Microsoft Edge |
|
||||||
<th>Supported browser</th>
|
|<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.<br> **Example** <pre class="syntax"> <br/><emie> <br> <domain exclude="false">fabrikam.com <br> <path exclude="true">/products</path><br> </domain><br></emie></pre><p> <br> 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 |
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td><rules></td>
|
|
||||||
<td>Root node for the schema.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<rules version="205">
|
|
||||||
<emie>
|
|
||||||
<domain>contoso.com</domain>
|
|
||||||
</emie>
|
|
||||||
</rules></pre></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><emie></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<rules version="205">
|
|
||||||
<emie>
|
|
||||||
<domain>contoso.com</domain>
|
|
||||||
</emie>
|
|
||||||
</rules></pre>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv6 ranges:<pre class="syntax"><rules version="205">
|
|
||||||
<emie>
|
|
||||||
<domain>[10.122.34.99]:8080</domain>
|
|
||||||
</emie>
|
|
||||||
</rules></pre>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv4 ranges:<pre class="syntax"><rules version="205">
|
|
||||||
<emie>
|
|
||||||
<domain>10.122.34.99:8080</domain>
|
|
||||||
</emie>
|
|
||||||
</rules></pre></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><docMode></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<rules version="205">
|
|
||||||
<docMode>
|
|
||||||
<domain docMode="7">contoso.com</domain>
|
|
||||||
</docMode>
|
|
||||||
</rules></pre></td>
|
|
||||||
<td>Internet Explorer 11</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><domain></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain>contoso.com:8080</domain>
|
|
||||||
</emie></pre></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><path></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain exclude="false">fabrikam.com
|
|
||||||
<path exclude="true">/products</path>
|
|
||||||
</domain>
|
|
||||||
</emie></pre><p>
|
|
||||||
Where https://fabrikam.com doesn't use IE8 Enterprise Mode, but https://fabrikam.com/products does.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Schema attributes
|
### Schema attributes
|
||||||
This table includes the attributes used by the Enterprise Mode schema.
|
This table includes the attributes used by the Enterprise Mode schema.
|
||||||
|
|Attribute|Description|Supported browser|
|
||||||
<table>
|
|--- |--- |--- |
|
||||||
<thead>
|
|<version>|Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <rules> element.|Internet Explorer 11 and Microsoft Edge|
|
||||||
<tr class="header">
|
|<exclude>|Specifies the domain or path that is excluded from getting the behavior applied. This attribute is supported on the <domain> and <path> elements.<br> **Example** <pre class="syntax"><emie><br> <domain exclude="false">fabrikam.com <br> <path exclude="true">/products</path><br> </domain><br></emie> </pre><p> 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|
|
||||||
<th>Attribute</th>
|
|<docMode>|Specifies the document mode to apply. This attribute is only supported on <domain> or <path>elements in the <docMode> section.<br> **Example**<pre class="syntax"><docMode> <br> <domain exclude="false">fabrikam.com <br> <path docMode="7">/products</path><br> </domain><br></docMode>|Internet Explorer 11|
|
||||||
<th>Description</th>
|
|
||||||
<th>Supported browser</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td><version></td>
|
|
||||||
<td>Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <rules> element.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><exclude></td>
|
|
||||||
<td>Specifies the domain or path that is excluded from getting the behavior applied. This attribute is supported on the <domain> and <path> elements.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain exclude="false">fabrikam.com
|
|
||||||
<path exclude="true">/products</path>
|
|
||||||
</domain>
|
|
||||||
</emie></pre><p>
|
|
||||||
Where https://fabrikam.com doesn't use IE8 Enterprise Mode, but https://fabrikam.com/products does.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><docMode></td>
|
|
||||||
<td>Specifies the document mode to apply. This attribute is only supported on <domain> or <path> elements in the <docMode> section.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<docMode>
|
|
||||||
<domain exclude="false">fabrikam.com
|
|
||||||
<path docMode="7">/products</path>
|
|
||||||
</domain>
|
|
||||||
</docMode></pre></td>
|
|
||||||
<td>Internet Explorer 11</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Using Enterprise Mode and document mode together
|
### 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.
|
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.
|
||||||
|
|||||||
@ -92,194 +92,32 @@ Make sure that you don't specify a protocol when adding your URLs. Using a URL l
|
|||||||
### Updated schema elements
|
### Updated schema elements
|
||||||
This table includes the elements used by the v.2 version of the Enterprise Mode schema.
|
This table includes the elements used by the v.2 version of the Enterprise Mode schema.
|
||||||
|
|
||||||
<table>
|
|
||||||
<thead>
|
|Element |Description |Supported browser |
|
||||||
<tr class="header">
|
|---------|---------|---------|
|
||||||
<th>Element</th>
|
|<site-list> |A new root node with this text is using the updated v.2 version of the schema. It replaces <rules>. <br> **Example** <br> <pre class="syntax"><site-list version="205"><br> <site url="contoso.com"><br> <compat-mode>IE8Enterprise</compat-mode><br> <open-in>IE11</open-in><br> </site><br></site-list></pre> | Internet Explorer 11 and Microsoft Edge |
|
||||||
<th>Description</th>
|
|<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. <br> **Example** <pre class="syntax"><site url="contoso.com"><br> <compat-mode>default</compat-mode><br> <open-in>none</open-in><br></site></pre> <br> **or** For IPv4 ranges: <br> <pre class="syntax"><site url="10.122.34.99:8080"><br> <compat-mode>IE8Enterprise</compat-mode><br><site></pre><p> <br> **or** For IPv6 ranges:<pre class="syntax"><site url="[10.122.34.99]:8080"><br> <compat-mode>IE8Enterprise</compat-mode><br><site></pre><p> <br> You can also use the self-closing version, <url="contoso.com" />, which also sets:<ul><li><compat-mode>default</compat-mode></li><li><open-in>none</open-in></li>| Internet Explorer 11 and Microsoft Edge |
|
||||||
<th>Supported browser</th>
|
|<compat-mode> |A child element that controls what compatibility setting is used for specific sites or domains. This element is only supported in IE11. <br> **Example** <pre class="syntax"><br><site url="contoso.com"><br> <compat-mode>IE8Enterprise</compat-mode><br></site></pre> **or** <br> For IPv4 ranges:<pre class="syntax"><site url="10.122.34.99:8080"><br> <compat-mode>IE8Enterprise</compat-mode><br><site></pre><p> **or** For IPv6 ranges:<pre class="syntax"><site url="[10.122.34.99]:8080"><br> <compat-mode>IE8Enterprise</compat-mode><br><site></pre><p> Where<ul><li>**IE8Enterprise.** Loads the site in IE8 Enterprise Mode.<br>This element is required for sites included in the **EmIE** section of the v.1 schema and is needed to load in IE8 Enterprise Mode.</li><p><li>**IE7Enterprise.** Loads the site in IE7 Enterprise Mode.<br>This element is required for sites included in the **EmIE** section of the v.1 schema and is needed to load in IE7 Enterprise Mode<p>**Important**<br>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.<li>**IE<i>[x]</i>**. Where <i>[x]</i> is the document mode number into which the site loads.<li>**Default or not specified.** Loads the site using the default compatibility mode for the page. In this situation, X-UA-compatible meta tags or HTTP headers are honored.</li> |Internet Explorer 11 |
|
||||||
</tr>
|
|<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.<br> **Examples**<pre class="syntax"><site url="contoso.com"><br> <open-in>none</open-in> <br></site></pre><p> <br> Where<ul><li><b>IE11.</b> Opens the site in IE11, regardless of which browser is opened by the employee.<li><b>MSEdge.</b> Opens the site in Microsoft Edge, regardless of which browser is opened by the employee.<li><b>None or not specified.</b> Opens in whatever browser the employee chooses.</li> | Internet Explorer 11 and Microsoft Edge |
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td><site-list></td>
|
|
||||||
<td>A new root node with this text is using the updated v.2 version of the schema. It replaces <rules>.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site-list version="205">
|
|
||||||
<site url="contoso.com">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<open-in>IE11</open-in>
|
|
||||||
</site>
|
|
||||||
</site-list></pre></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><site></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com">
|
|
||||||
<compat-mode>default</compat-mode>
|
|
||||||
<open-in>none</open-in>
|
|
||||||
</site></pre>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv4 ranges:<pre class="syntax"><site url="10.122.34.99:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<site></pre><p>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv6 ranges:<pre class="syntax"><site url="[10.122.34.99]:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<site></pre><p>
|
|
||||||
You can also use the self-closing version, <url="contoso.com" />, which also sets:
|
|
||||||
<ul>
|
|
||||||
<li><compat-mode>default</compat-mode></li>
|
|
||||||
<li><open-in>none</open-in></li>
|
|
||||||
</ul></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><compat-mode></td>
|
|
||||||
<td>A child element that controls what compatibility setting is used for specific sites or domains. This element is only supported in IE11.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
</site></pre>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv4 ranges:<pre class="syntax"><site url="10.122.34.99:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<site></pre><p>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv6 ranges:<pre class="syntax"><site url="[10.122.34.99]:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<site></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>
|
|
||||||
<li><b>IE7Enterprise.</b> Loads the site in IE7 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 IE7 Enterprise Mode.<p><b>Important</b><br>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.</li><p>
|
|
||||||
<li><b>IE<i>[x]</i>.</b> Where <i>[x]</i> is the document mode number into which the site loads.</li><p>
|
|
||||||
<li><b>Default or not specified.</b> Loads the site using the default compatibility mode for the page. In this situation, X-UA-compatible meta tags or HTTP headers are honored.</li>
|
|
||||||
</ul></td>
|
|
||||||
<td>Internet Explorer 11</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><open-in></td>
|
|
||||||
<td>A child element that controls what browser is used for sites. This element supports the <b>Open in IE11</b> or <b>Open in Microsoft Edge</b> experiences, for devices running Windows 10.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com">
|
|
||||||
<open-in>none</open-in>
|
|
||||||
</site></pre><p>
|
|
||||||
Where:
|
|
||||||
<ul>
|
|
||||||
<li><b>IE11.</b> Opens the site in IE11, regardless of which browser is opened by the employee.</li><p>
|
|
||||||
<li><b>MSEdge.</b> Opens the site in Microsoft Edge, regardless of which browser is opened by the employee.</li><p>
|
|
||||||
<li><b>None or not specified.</b> Opens in whatever browser the employee chooses.</li>
|
|
||||||
</ul></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Updated schema attributes
|
### 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.
|
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.
|
||||||
|
|
||||||
<table>
|
|Attribute|Description|Supported browser|
|
||||||
<thead>
|
|---------|---------|---------|
|
||||||
<tr class="header">
|
|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).<br>**Example**<pre class="syntax"><site url="contoso.com/travel"><br> <open-in allow-redirect="true">IE11 </open-in><br></site> </pre> 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.</li>| Internet Explorer 11 and Microsoft Edge|
|
||||||
<th>Attribute</th>
|
|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|
|
||||||
<th>Description</th>
|
|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.<br> **Note**<br> Make sure that you don't specify a protocol. Using <site url="contoso.com"> applies to both [https://contoso.com](https://contoso.com) and [https://contoso.com](https://contoso.com). <br> **Example**<pre class="syntax"><site url="contoso.com:8080"><br> <compat-mode>IE8Enterprise</compat-mode> <br> <open-in>IE11</open-in><br></site></pre>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|
|
||||||
<th>Supported browser</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td>allow-redirect</td>
|
|
||||||
<td>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).
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com/travel">
|
|
||||||
<open-in allow-redirect="true">IE11</open-in>
|
|
||||||
</site></pre>
|
|
||||||
In this example, if https://contoso.com/travel is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>version</td>
|
|
||||||
<td>Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <site-list> element.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>url</td>
|
|
||||||
<td>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.
|
|
||||||
<br><b>Note</b><br>
|
|
||||||
Make sure that you don't specify a protocol. Using <site url="contoso.com"> applies to both https://contoso.com and https://contoso.com.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<open-in>IE11</open-in>
|
|
||||||
</site></pre>
|
|
||||||
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.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Deprecated attributes
|
### Deprecated attributes
|
||||||
These v.1 version schema attributes have been deprecated in the v.2 version of the schema:
|
These v.1 version schema attributes have been deprecated in the v.2 version of the schema:
|
||||||
|
|
||||||
<table>
|
|Deprecated attribute|New attribute|Replacement example|
|
||||||
<thead>
|
|--- |--- |--- |
|
||||||
<tr class="header">
|
|<forceCompatView>|<compat-mode>|Replace <forceCompatView="true"> with <compat-mode>IE7Enterprise</compat-mode>|
|
||||||
<th>Deprecated attribute</th>
|
|<docMode>|<compat-mode>|Replace <docMode="IE5"> with <compat-mode>IE5</compat-mode>|
|
||||||
<th>New attribute</th>
|
|<doNotTransition>|<open-in>|Replace:<br> <doNotTransition="true"> with <open-in>none</open-in>|
|
||||||
<th>Replacement example</th>
|
|<domain> and <path>|<site>|Replace:<pre class="syntax"><emie><br> <domain exclude="false">contoso.com</domain><br></emie></pre>With:<pre class="syntax"><site url="contoso.com"/> <br> <compat-mode>IE8Enterprise</compat-mode><br></site></pre>**-AND-** <br>Replace:<pre class="syntax"><emie> <br> <domain exclude="true">contoso.com <br> <path exclude="false" forceCompatView="true">/about</path><br> </domain><br></emie></pre><br> With:<pre class="syntax"><site url="contoso.com/about"><br> <compat-mode>IE7Enterprise</compat-mode><br></site>|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td><forceCompatView></td>
|
|
||||||
<td><compat-mode></td>
|
|
||||||
<td>Replace <forceCompatView="true"> with <compat-mode>IE7Enterprise</compat-mode></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><docMode></td>
|
|
||||||
<td><compat-mode></td>
|
|
||||||
<td>Replace <docMode="IE5"> with <compat-mode>IE5</compat-mode></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><doNotTransition></td>
|
|
||||||
<td><open-in></td>
|
|
||||||
<td>Replace <doNotTransition="true"> with <open-in>none</open-in></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><domain> and <path></td>
|
|
||||||
<td><site></td>
|
|
||||||
<td>Replace:
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain exclude="false">contoso.com</domain>
|
|
||||||
</emie></pre>
|
|
||||||
With:
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com"/>
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
</site></pre>
|
|
||||||
<b>-AND-</b><p>
|
|
||||||
Replace:
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain exclude="true">contoso.com
|
|
||||||
<path exclude="false" forceCompatView="true">/about</path>
|
|
||||||
</domain>
|
|
||||||
</emie></pre>
|
|
||||||
With:
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com/about">
|
|
||||||
<compat-mode>IE7Enterprise</compat-mode>
|
|
||||||
</site></pre></td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
|
|||||||
@ -63,17 +63,17 @@ Data is collected on the configuration characteristics of IE and the sites it br
|
|||||||
|
|
||||||
|Data point |IE11 |IE10 |IE9 |IE8 |Description |
|
|Data point |IE11 |IE10 |IE9 |IE8 |Description |
|
||||||
|------------------------|-----|-----|-----|-----|------------------------------------------------------------------------|
|
|------------------------|-----|-----|-----|-----|------------------------------------------------------------------------|
|
||||||
|URL | X | X | X | X |URL of the browsed site, including any parameters included in the URL. |
|
|URL | ✔️ | ✔️ | ✔️ | ✔️ |URL of the browsed site, including any parameters included in the URL. |
|
||||||
|Domain | X | X | X | X |Top-level domain of the browsed site. |
|
|Domain | ✔️ | ✔️ | ✔️ | ✔️ |Top-level domain of the browsed site. |
|
||||||
|ActiveX GUID | X | X | X | X |GUID of the ActiveX controls loaded by the site. |
|
|ActiveX GUID | ✔️ | ✔️ | ✔️ | ✔️ |GUID of the ActiveX controls loaded by the site. |
|
||||||
|Document mode | X | X | X | X |Document mode used by IE for a site, based on page characteristics. |
|
|Document mode | ✔️ | ✔️ | ✔️ | ✔️ |Document mode used by IE for a site, based on page characteristics. |
|
||||||
|Document mode reason | X | X | | |The reason why a document mode was set by IE. |
|
|Document mode reason | ✔️ | ✔️ | | |The reason why a document mode was set by IE. |
|
||||||
|Browser state reason | X | X | | |Additional information about why the browser is in its current state. Also called, browser mode. |
|
|Browser state reason | ✔️ | ✔️ | | |Additional information about why the browser is in its current state. Also called, browser mode. |
|
||||||
|Hang count | X | X | X | X |Number of visits to the URL when the browser hung. |
|
|Hang count | ✔️ | ✔️ | ✔️ | ✔️ |Number of visits to the URL when the browser hung. |
|
||||||
|Crash count | X | X | X | X |Number of visits to the URL when the browser crashed. |
|
|Crash count | ✔️ | ✔️ | ✔️ | ✔️ |Number of visits to the URL when the browser crashed. |
|
||||||
|Most recent navigation failure (and count) | X | X | X | X |Description of the most recent navigation failure (like, a 404 bad request or 500 internal server error) and the number of times it happened. |
|
|Most recent navigation failure (and count) | ✔️ | ✔️ | ✔️ | ✔️ |Description of the most recent navigation failure (like, a 404 bad request or 500 internal server error) and the number of times it happened. |
|
||||||
|Number of visits | X | X | X | X |Number of times a site has been visited. |
|
|Number of visits | ✔️ | ✔️ | ✔️ | ✔️ |Number of times a site has been visited. |
|
||||||
|Zone | X | X | X | X |Zone used by IE to browse sites, based on browser settings. |
|
|Zone | ✔️ | ✔️ | ✔️ | ✔️ |Zone used by IE to browse sites, based on browser settings. |
|
||||||
|
|
||||||
|
|
||||||
>**Important**<br>By default, IE doesn’t collect this data; you have to turn this feature on if you want to use it. After you turn on this feature, data is collected on all sites visited by IE, except during InPrivate sessions. Additionally, the data collection process is silent, so there’s no notification to the employee. Therefore, you must get consent from the employee before you start collecting info. You must also make sure that using this feature complies with all applicable local laws and regulatory requirements.
|
>**Important**<br>By default, IE doesn’t collect this data; you have to turn this feature on if you want to use it. After you turn on this feature, data is collected on all sites visited by IE, except during InPrivate sessions. Additionally, the data collection process is silent, so there’s no notification to the employee. Therefore, you must get consent from the employee before you start collecting info. You must also make sure that using this feature complies with all applicable local laws and regulatory requirements.
|
||||||
@ -205,68 +205,32 @@ 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:
|
You can use both the WMI and XML settings individually or together:
|
||||||
|
|
||||||
**To turn off Enterprise Site Discovery**
|
**To turn off Enterprise Site Discovery**
|
||||||
<table>
|
|
||||||
<tr>
|
|Setting name|Option|
|
||||||
<th>Setting name</th>
|
|--- |--- |
|
||||||
<th>Option</th>
|
|Turn on Site Discovery WMI output|Off|
|
||||||
</tr>
|
|Turn on Site Discovery XML output|Blank|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery WMI output</td>
|
|
||||||
<td>Off</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery XML output</td>
|
|
||||||
<td>Blank</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
**Turn on WMI recording only**
|
**Turn on WMI recording only**
|
||||||
<table>
|
|
||||||
<tr>
|
|Setting name|Option|
|
||||||
<th>Setting name</th>
|
|--- |--- |
|
||||||
<th>Option</th>
|
|Turn on Site Discovery WMI output|On|
|
||||||
</tr>
|
|Turn on Site Discovery XML output|Blank|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery WMI output</td>
|
|
||||||
<td>On</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery XML output</td>
|
|
||||||
<td>Blank</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
**To turn on XML recording only**
|
**To turn on XML recording only**
|
||||||
<table>
|
|
||||||
<tr>
|
|
||||||
<th>Setting name</th>
|
|
||||||
<th>Option</th>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery WMI output</td>
|
|
||||||
<td>Off</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery XML output</td>
|
|
||||||
<td>XML file path</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
<strong>To turn on both WMI and XML recording</strong>
|
|Setting name|Option|
|
||||||
<table>
|
|--- |--- |
|
||||||
<tr>
|
|Turn on Site Discovery WMI output|Off|
|
||||||
<th>Setting name</th>
|
|Turn on Site Discovery XML output|XML file path|
|
||||||
<th>Option</th>
|
|
||||||
</tr>
|
**To turn on both WMI and XML recording**
|
||||||
<tr>
|
|
||||||
<td>Turn on Site Discovery WMI output</td>
|
|Setting name|Option|
|
||||||
<td>On</td>
|
|--- |--- |
|
||||||
</tr>
|
|Turn on Site Discovery WMI output|On|
|
||||||
<tr>
|
|Turn on Site Discovery XML output|XML file path|
|
||||||
<td>Turn on Site Discovery XML output</td>
|
|
||||||
<td>XML file path</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
## Use Configuration Manager to collect your data
|
## Use Configuration Manager to collect your data
|
||||||
After you’ve collected your data, you’ll need to get the local files off of your employee’s computers. To do this, use the hardware inventory process in Configuration Manager, using one of these options:
|
After you’ve collected your data, you’ll need to get the local files off of your employee’s computers. To do this, use the hardware inventory process in Configuration Manager, using one of these options:
|
||||||
|
|||||||
@ -65,162 +65,24 @@ The following is an example of the Enterprise Mode schema v.1. This schema can r
|
|||||||
### Schema elements
|
### Schema elements
|
||||||
This table includes the elements used by the Enterprise Mode schema.
|
This table includes the elements used by the Enterprise Mode schema.
|
||||||
|
|
||||||
<table>
|
|Element |Description |Supported browser |
|
||||||
<thead>
|
|---------|---------|---------|
|
||||||
<tr class="header">
|
|<rules> | Root node for the schema.<br>**Example** <pre class="syntax"><rules version="205"> <br> <emie> <br> <domain>contoso.com</domain> <br> </emie><br> </rules> |Internet Explorer 11 and Microsoft Edge |
|
||||||
<th>Element</th>
|
|<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. <br> **Example** <pre class="syntax"><rules version="205"> <br> <emie> <br> <domain>contoso.com</domain> <br> </emie><br></rules> <br> </pre><p> **or** <br> For IPv6 ranges: <pre class="syntax"><br><rules version="205"> <br> <emie> <br> <domain>[10.122.34.99]:8080</domain> <br> </emie><br></rules> </pre><p> <br> **or**<br> For IPv4 ranges:<pre class="syntax"><rules version="205"> <br> <emie> <br> <domain>[10.122.34.99]:8080</domain> <br> </emie><br></rules> | Internet Explorer 11 and Microsoft Edge |
|
||||||
<th>Description</th>
|
|<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. <br> **Example** <pre class="syntax"> <br/><rules version="205"> <br> <docmode> <br> <domain docMode="7">contoso.com</domain> <br> </docmode><br></rules> |Internet Explorer 11 |
|
||||||
<th>Supported browser</th>
|
|<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. <br> **Example** <pre class="syntax"> <br/><emie> <br> <domain>contoso.com:8080</domain><br></emie> |Internet Explorer 11 and Microsoft Edge |
|
||||||
</tr>
|
|<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.<br> **Example** <pre class="syntax"> <br/><emie> <br> <domain exclude="true">fabrikam.com <br> <path exclude="false">/products</path><br> </domain><br></emie></pre><p> <br> 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 |
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td><rules></td>
|
|
||||||
<td>Root node for the schema.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<rules version="205">
|
|
||||||
<emie>
|
|
||||||
<domain>contoso.com</domain>
|
|
||||||
</emie>
|
|
||||||
</rules></pre></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><emie></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<rules version="205">
|
|
||||||
<emie>
|
|
||||||
<domain>contoso.com</domain>
|
|
||||||
</emie>
|
|
||||||
</rules></pre>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv6 ranges:<pre class="syntax"><rules version="205">
|
|
||||||
<emie>
|
|
||||||
<domain>[10.122.34.99]:8080</domain>
|
|
||||||
</emie>
|
|
||||||
</rules></pre>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv4 ranges:<pre class="syntax"><rules version="205">
|
|
||||||
<emie>
|
|
||||||
<domain>10.122.34.99:8080</domain>
|
|
||||||
</emie>
|
|
||||||
</rules></pre></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><docMode></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<rules version="205">
|
|
||||||
<docMode>
|
|
||||||
<domain docMode="7">contoso.com</domain>
|
|
||||||
</docMode>
|
|
||||||
</rules></pre></td>
|
|
||||||
<td>Internet Explorer 11</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><domain></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain>contoso.com:8080</domain>
|
|
||||||
</emie></pre></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><path></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain exclude="true">fabrikam.com
|
|
||||||
<path exclude="false">/products</path>
|
|
||||||
</domain>
|
|
||||||
</emie></pre><p>
|
|
||||||
Where <a href="https://fabrikam.com" data-raw-source="https://fabrikam.com">https://fabrikam.com</a> doesn't use IE8 Enterprise Mode, but <a href="https://fabrikam.com/products" data-raw-source="https://fabrikam.com/products">https://fabrikam.com/products</a> does.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Schema attributes
|
### Schema attributes
|
||||||
This table includes the attributes used by the Enterprise Mode schema.
|
This table includes the attributes used by the Enterprise Mode schema.
|
||||||
|
|
||||||
<table>
|
|Attribute|Description|Supported browser|
|
||||||
<thead>
|
|--- |--- |--- |
|
||||||
<tr class="header">
|
|version|Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <rules> element.|Internet Explorer 11 and Microsoft Edge|
|
||||||
<th>Attribute</th>
|
|exclude|Specifies the domain or path that is excluded from getting the behavior applied. This attribute is supported on the <domain> and <path> elements.<br> **Example** <pre class="syntax"><emie><br> <domain exclude="false">fabrikam.com <br> <path exclude="true">/products</path><br> </domain><br></emie> </pre><p> 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|
|
||||||
<th>Description</th>
|
|docMode|Specifies the document mode to apply. This attribute is only supported on <domain> or <path>elements in the <docMode> section.<br> **Example**<pre class="syntax"><docMode> <br> <domain exclude="false">fabrikam.com <br> <path docMode="9">/products</path><br> </domain><br></docMode>|Internet Explorer 11|
|
||||||
<th>Supported browser</th>
|
|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.<br> **Example**<pre class="syntax"><emie><br> <domain doNotTransition="false">fabrikam.com <br> <path doNotTransition="true">/products</path><br> </domain><br></emie></pre><p>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|
|
||||||
</tr>
|
|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. <br> **Example**<pre class="syntax"><emie><br> <domain exclude="true">fabrikam.com <br> <path forcecompatview="true">/products</path><br> </domain><br></emie></pre><p>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|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td>version</td>
|
|
||||||
<td>Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <rules> element.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>exclude</td>
|
|
||||||
<td>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.
|
|
||||||
<br />
|
|
||||||
<p><b>Example:</b></p>
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain exclude="false">fabrikam.com
|
|
||||||
<path exclude="true">/products</path>
|
|
||||||
</domain>
|
|
||||||
</emie></pre><p>
|
|
||||||
Where <a href="https://fabrikam.com" data-raw-source="https://fabrikam.com">https://fabrikam.com</a> uses IE8 Enterprise Mode, but <a href="https://fabrikam.com/products" data-raw-source="https://fabrikam.com/products">https://fabrikam.com/products</a> does not.</p></td>
|
|
||||||
<td>Internet Explorer 11</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>docMode</td>
|
|
||||||
<td>Specifies the document mode to apply. This attribute is only supported on <domain> or <path> elements in the <docMode> section.
|
|
||||||
<br />
|
|
||||||
<p><b>Example:</b></p>
|
|
||||||
<pre class="syntax">
|
|
||||||
<docMode>
|
|
||||||
<domain>fabrikam.com
|
|
||||||
<path docMode="9">/products</path>
|
|
||||||
</domain>
|
|
||||||
</docMode></pre><p>
|
|
||||||
Where <a href="https://fabrikam.com" data-raw-source="https://fabrikam.com">https://fabrikam.com</a> loads in IE11 document mode, but <a href="https://fabrikam.com/products" data-raw-source="https://fabrikam.com/products">https://fabrikam.com/products</a> uses IE9 document mode.</p></td>
|
|
||||||
<td>Internet Explorer 11</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>doNotTransition</td>
|
|
||||||
<td>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.
|
|
||||||
<br />
|
|
||||||
<p><b>Example:</b></p>
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain doNotTransition="false">fabrikam.com
|
|
||||||
<path doNotTransition="true">/products</path>
|
|
||||||
</domain>
|
|
||||||
</emie></pre><p>
|
|
||||||
Where <a href="https://fabrikam.com" data-raw-source="https://fabrikam.com">https://fabrikam.com</a> opens in the IE11 browser, but <a href="https://fabrikam.com/products" data-raw-source="https://fabrikam.com/products">https://fabrikam.com/products</a> loads in the current browser (eg. Microsoft Edge).</p></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>forceCompatView</td>
|
|
||||||
<td>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.
|
|
||||||
<br />
|
|
||||||
<p><b>Example:</b></p>
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain exclude="true">fabrikam.com
|
|
||||||
<path forceCompatView="true">/products</path>
|
|
||||||
</domain>
|
|
||||||
</emie></pre><p>
|
|
||||||
Where <a href="https://fabrikam.com" data-raw-source="https://fabrikam.com">https://fabrikam.com</a> does not use Enterprise Mode, but <a href="https://fabrikam.com/products" data-raw-source="https://fabrikam.com/products">https://fabrikam.com/products</a> uses IE7 Enterprise Mode.</p></td>
|
|
||||||
<td>Internet Explorer 11</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Using Enterprise Mode and document mode together
|
### 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.
|
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.
|
||||||
|
|||||||
@ -97,197 +97,31 @@ The following is an example of the v.2 version of the Enterprise Mode schema.
|
|||||||
### Updated schema elements
|
### Updated schema elements
|
||||||
This table includes the elements used by the v.2 version of the Enterprise Mode schema.
|
This table includes the elements used by the v.2 version of the Enterprise Mode schema.
|
||||||
|
|
||||||
<table>
|
|Element |Description |Supported browser |
|
||||||
<thead>
|
|---------|---------|---------|
|
||||||
<tr class="header">
|
|<site-list> |A new root node with this text is using the updated v.2 version of the schema. It replaces <rules>. <br> **Example** <br> <pre class="syntax"><site-list version="205"><br> <site url="contoso.com"><br> <compat-mode>IE8Enterprise</compat-mode><br> <open-in>IE11</open-in><br> </site><br></site-list></pre> | Internet Explorer 11 and Microsoft Edge |
|
||||||
<th>Element</th>
|
|<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. <br> **Example** <pre class="syntax"><site url="contoso.com"><br> <compat-mode>default</compat-mode><br> <open-in>none</open-in><br></site></pre> <br> **or** For IPv4 ranges: <br> <pre class="syntax"><site url="10.122.34.99:8080"><br> <compat-mode>IE8Enterprise</compat-mode><br><site></pre><p> <br> **or** For IPv6 ranges:<pre class="syntax"><site url="[10.122.34.99]:8080"><br> <compat-mode>IE8Enterprise</compat-mode><br><site></pre><p> <br> You can also use the self-closing version, <url="contoso.com" />, which also sets:<ul><li><compat-mode>default</compat-mode></li><li><open-in>none</open-in></li>| Internet Explorer 11 and Microsoft Edge |
|
||||||
<th>Description</th>
|
|<compat-mode> |A child element that controls what compatibility setting is used for specific sites or domains. This element is only supported in IE11. <br> **Example** <pre class="syntax"><br><site url="contoso.com"><br> <compat-mode>IE8Enterprise</compat-mode><br></site></pre> **or** <br> For IPv4 ranges:<pre class="syntax"><site url="10.122.34.99:8080"><br> <compat-mode>IE8Enterprise</compat-mode><br><site></pre><p> **or** For IPv6 ranges:<pre class="syntax"><site url="[10.122.34.99]:8080"><br> <compat-mode>IE8Enterprise</compat-mode><br><site></pre><p> Where<ul><li>**IE8Enterprise.** Loads the site in IE8 Enterprise Mode.<br>This element is required for sites included in the **EmIE** section of the v.1 schema and is needed to load in IE8 Enterprise Mode.</li><p><li>**IE7Enterprise.** Loads the site in IE7 Enterprise Mode.<br>This element is required for sites included in the **EmIE** section of the v.1 schema and is needed to load in IE7 Enterprise Mode<p>**Important**<br>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.<li>**IE<i>[x]</i>**. Where <i>[x]</i> is the document mode number into which the site loads.<li>**Default or not specified.** Loads the site using the default compatibility mode for the page. In this situation, X-UA-compatible meta tags or HTTP headers are honored.</li> |Internet Explorer 11 |
|
||||||
<th>Supported browser</th>
|
|<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.<br> **Examples**<pre class="syntax"><site url="contoso.com"><br> <open-in>none</open-in> <br></site></pre><p> <br> Where<ul><li><b>IE11.</b> Opens the site in IE11, regardless of which browser is opened by the employee.<li><b>MSEdge.</b> Opens the site in Microsoft Edge, regardless of which browser is opened by the employee.<li><b>None or not specified.</b> Opens in whatever browser the employee chooses.</li> | Internet Explorer 11 and Microsoft Edge |
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td><site-list></td>
|
|
||||||
<td>A new root node with this text is using the updated v.2 version of the schema. It replaces <rules>.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site-list version="205">
|
|
||||||
<site url="contoso.com">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<open-in>IE11</open-in>
|
|
||||||
</site>
|
|
||||||
</site-list></pre></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><site></td>
|
|
||||||
<td>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.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com">
|
|
||||||
<compat-mode>default</compat-mode>
|
|
||||||
<open-in>none</open-in>
|
|
||||||
</site></pre>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv4 ranges:<pre class="syntax"><site url="10.122.34.99:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<site></pre><p>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv6 ranges:<pre class="syntax"><site url="[10.122.34.99]:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<site></pre><p>
|
|
||||||
You can also use the self-closing version, <url="contoso.com" />, which also sets:
|
|
||||||
<ul>
|
|
||||||
<li><compat-mode>default</compat-mode></li>
|
|
||||||
<li><open-in>none</open-in></li>
|
|
||||||
</ul></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><compat-mode></td>
|
|
||||||
<td>A child element that controls what compatibility setting is used for specific sites or domains. This element is only supported in IE11.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
</site></pre>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv4 ranges:<pre class="syntax"><site url="10.122.34.99:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<site></pre><p>
|
|
||||||
<strong>-or-</strong>
|
|
||||||
<p>For IPv6 ranges:<pre class="syntax"><site url="[10.122.34.99]:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<site></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>
|
|
||||||
<li><b>IE7Enterprise.</b> Loads the site in IE7 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 IE7 Enterprise Mode.<p><b>Important</b><br>This tag replaces the combination of the <code>"forceCompatView"="true"</code> attribute and the list of sites specified in the EmIE section of the v.1 version of the schema.</li><p>
|
|
||||||
<li><b>IE<i>[x]</i>.</b> Where <i>[x]</i> is the document mode number into which the site loads.</li><p>
|
|
||||||
<li><b>Default or not specified.</b> Loads the site using the default compatibility mode for the page. In this situation, X-UA-compatible meta tags or HTTP headers are honored.</li>
|
|
||||||
</ul></td>
|
|
||||||
<td>Internet Explorer 11</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><open-in></td>
|
|
||||||
<td>A child element that controls what browser is used for sites. This element supports the <b>Open in IE11</b> or <b>Open in Microsoft Edge</b> experiences, for devices running Windows 10.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com">
|
|
||||||
<open-in>none</open-in>
|
|
||||||
</site></pre><p>
|
|
||||||
Where:
|
|
||||||
<ul>
|
|
||||||
<li><b>IE11.</b> Opens the site in IE11, regardless of which browser is opened by the employee.</li><p>
|
|
||||||
<li><b>MSEdge.</b> Opens the site in Microsoft Edge, regardless of which browser is opened by the employee.</li><p>
|
|
||||||
<li><b>None or not specified.</b> Opens in whatever browser the employee chooses.</li>
|
|
||||||
</ul></td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Updated schema attributes
|
### 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.
|
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.
|
||||||
|
|
||||||
<table>
|
|Attribute|Description|Supported browser|
|
||||||
<thead>
|
|---------|---------|---------|
|
||||||
<tr class="header">
|
|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).<br>**Example**<pre class="syntax"><site url="contoso.com/travel"><br> <open-in allow-redirect="true">IE11 </open-in><br></site></pre> 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. <li>| Internet Explorer 11 and Microsoft Edge|
|
||||||
<th>Attribute</th>
|
|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|
|
||||||
<th>Description</th>
|
|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.<br> **Note**<br> Make sure that you don't specify a protocol. Using <site url="contoso.com"> applies to both [https://contoso.com](https://contoso.com) and [https://contoso.com](https://contoso.com). <br> **Example**<pre class="syntax"><site url="contoso.com:8080"><br> <compat-mode>IE8Enterprise</compat-mode> <br> <open-in>IE11</open-in><br></site></pre>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|
|
||||||
<th>Supported browser</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td>allow-redirect</td>
|
|
||||||
<td>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).
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com/travel">
|
|
||||||
<open-in allow-redirect="true">IE11</open-in>
|
|
||||||
</site></pre>
|
|
||||||
In this example, if <a href="https://contoso.com/travel" data-raw-source="https://contoso.com/travel">https://contoso.com/travel</a> is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>version</td>
|
|
||||||
<td>Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <site-list> element.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>url</td>
|
|
||||||
<td>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.
|
|
||||||
<br><b>Note</b><br>
|
|
||||||
Make sure that you don't specify a protocol. Using <site url="contoso.com"> applies to both <a href="http://contoso.com" data-raw-source="http://contoso.com">http://contoso.com</a> and <a href="https://contoso.com" data-raw-source="https://contoso.com">https://contoso.com</a>.
|
|
||||||
<p><b>Example</b>
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com:8080">
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<open-in>IE11</open-in>
|
|
||||||
</site></pre>
|
|
||||||
In this example, going to <a href="https://contoso.com:8080" data-raw-source="https://contoso.com:8080">https://contoso.com:8080</a> using Microsoft Edge, causes the site to open in IE11 and load in IE8 Enterprise Mode.</td>
|
|
||||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Deprecated attributes
|
### Deprecated attributes
|
||||||
These v.1 version schema attributes have been deprecated in the v.2 version of the schema:
|
These v.1 version schema attributes have been deprecated in the v.2 version of the schema:
|
||||||
|
|
||||||
<table>
|
|Deprecated attribute|New attribute|Replacement example|
|
||||||
<thead>
|
|--- |--- |--- |
|
||||||
<tr class="header">
|
|forceCompatView|<compat-mode>|Replace <forceCompatView="true"> with <compat-mode>IE7Enterprise</compat-mode>|
|
||||||
<th>Deprecated element/attribute</th>
|
|docMode|<compat-mode>|Replace <docMode="IE5"> with <compat-mode>IE5</compat-mode>|
|
||||||
<th>New element</th>
|
|doNotTransition|<open-in>|Replace:<br> <doNotTransition="true"> with <open-in>none</open-in>|
|
||||||
<th>Replacement example</th>
|
|<domain> and <path>|<site>|Replace:<pre class="syntax"><emie><br> <domain>contoso.com</domain><br></emie></pre>With:<pre class="syntax"><site url="contoso.com"/> <br> <compat-mode>IE8Enterprise</compat-mode><br> <open-in>IE11</open-in><br></site></pre>**-AND-** <br>Replace:<pre class="syntax"><emie> <br> <domain exclude="true" donotTransition="true">contoso.com <br> <path forceCompatView="true">/about</path><br> </domain><br></emie></pre><br> With:<pre class="syntax"><site url="contoso.com/about"><br> <compat-mode>IE7Enterprise</compat-mode><br> <open-in>IE11</open-in><br></site>|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td>forceCompatView</td>
|
|
||||||
<td><compat-mode></td>
|
|
||||||
<td>Replace forceCompatView="true" with <compat-mode>IE7Enterprise</compat-mode></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>docMode</td>
|
|
||||||
<td><compat-mode></td>
|
|
||||||
<td>Replace docMode="IE5" with <compat-mode>IE5</compat-mode></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>doNotTransition</td>
|
|
||||||
<td><open-in></td>
|
|
||||||
<td>Replace doNotTransition="true" with <open-in>none</open-in></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td><domain> and <path></td>
|
|
||||||
<td><site></td>
|
|
||||||
<td>Replace:
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain>contoso.com</domain>
|
|
||||||
</emie></pre>
|
|
||||||
With:
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com"/>
|
|
||||||
<compat-mode>IE8Enterprise</compat-mode>
|
|
||||||
<open-in>IE11</open-in>
|
|
||||||
</site></pre>
|
|
||||||
<b>-AND-</b><p>
|
|
||||||
Replace:
|
|
||||||
<pre class="syntax">
|
|
||||||
<emie>
|
|
||||||
<domain exclude="true" doNotTransition="true">
|
|
||||||
contoso.com
|
|
||||||
<path forceCompatView="true">/about</path>
|
|
||||||
</domain>
|
|
||||||
</emie></pre>
|
|
||||||
With:
|
|
||||||
<pre class="syntax">
|
|
||||||
<site url="contoso.com/about">
|
|
||||||
<compat-mode>IE7Enterprise</compat-mode>
|
|
||||||
<open-in>IE11</open-in>
|
|
||||||
</site></pre></td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
|
|||||||
@ -126,96 +126,23 @@ 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
|
Table 2. Settings in the Device Management node in the Google Admin Console
|
||||||
|
|
||||||
<table>
|
|Section |Settings |
|
||||||
<colgroup>
|
|---------|---------|
|
||||||
<col width="50%" />
|
|Network | <p>These settings configure the network connections for Chromebook devices and include the following settings categories:<ul></p><li> **Wi-Fi.** Configures the Wi-Fi connections that are available. The Windows devices will need these configuration settings to connect to the same Wi-Fi networks.</p></li> <li>**Ethernet.** Configures authentication for secured, wired Ethernet connections (802.1x). The Windows devices will need these configuration settings to connect to the network.</p><li>**VPN.** Specifies the VPN network connections used by devices when not directly connected to your intranet. The Windows devices will need the same VPN network connections for users to remotely connect to your intranet.</p><li>**Certificates.** Contains the certificates used for network authentication. The Windows devices will need these certificates to connect to the network.</p> |
|
||||||
<col width="50%" />
|
|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:<ul> <li>**Device management settings.** Configures settings for mobile (companion) devices, such as device synchronization, password settings, auditing, enable remote wipe, and other settings. Record these settings so that you can ensure the same settings are applied when the devices are being managed by Microsoft Intune or another mobile device management (MDM) provider.<li>**Device activation.** Contains a list of mobile (companion) devices that need to be approved for management by using the Google Admin Console. Approve or block any devices in this list so that the list of managed devices accurately reflects active managed devices.<li>**Managed devices.** Performs management tasks on mobile (companion) devices that are managed by the Google Admin Console. Record the list of companion devices on this page so that you can ensure the same devices are managed by Intune or another MDM provider.<li> **Set Up Apple Push Certificate.** Configures the certificate that is essentially the digital signature that lets the Google Admin Console manage iOS devices. You will need this certificate if you plan to manage iOS devices by using Intune or another MDM provider. <li>**Set Up Android for Work.** Authorizes the Google Admin Console to be the MDM provider for Android devices by providing an Enterprise Mobility Management (EMM) token. You will need this token if you plan to manage Android devices by using another MDM provider. |
|
||||||
</colgroup>
|
|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:<ul> <li>**User settings.** Configures user-based settings for the Chrome browser and Chromebook devices. Most of these Chromebook user-based settings can be mapped to a corresponding setting in Windows. Record the settings and then map them to settings in Group Policy or Intune.<li>**Public session settings.** Configures Public Sessions for Chrome devices that are used as kiosks, loaner devices, shared computers, or for any other work or school-related purpose for which users don't need to sign in with their credentials. You can configure Windows devices similarly by using Assigned Access. Record the settings and apps that are available in Public Sessions so that you can provide similar configuration in Assigned Access.<li> **Device settings.** Configures device-based settings for the Chrome browser and Chromebook devices. You can map most of these Chromebook device-based settings to a corresponding setting in Windows. Record the settings and then map them to settings in Group Policy or Intune.<li>**Devices.** Manages Chrome device management licenses. The number of licenses recorded here should correspond to the number of licenses you will need for your new management system, such as Intune. Record the number of licenses and use those to determine how many licenses you will need to manage your Windows devices <li>**App Management.** Provides configuration settings for Chrome apps. Record the settings for any apps that you have identified that will run on Windows devices. |
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Section</th>
|
|
||||||
<th align="left">Settings</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Network</td>
|
|
||||||
<td align="left"><p>These settings configure the network connections for Chromebook devices and include the following settings categories:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p><strong>Wi-Fi.</strong> Configures the Wi-Fi connections that are available. The Windows devices will need these configuration settings to connect to the same Wi-Fi networks.</p></li>
|
|
||||||
<li><p><strong>Ethernet.</strong> Configures authentication for secured, wired Ethernet connections (802.1x). The Windows devices will need these configuration settings to connect to the network.</p></li>
|
|
||||||
<li><p><strong>VPN.</strong> Specifies the VPN network connections used by devices when not directly connected to your intranet. The Windows devices will need the same VPN network connections for users to remotely connect to your intranet.</p></li>
|
|
||||||
<li><p><strong>Certificates.</strong> Contains the certificates used for network authentication. The Windows devices will need these certificates to connect to the network.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Mobile</td>
|
|
||||||
<td align="left"><p>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:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p><strong>Device management settings.</strong> Configures settings for mobile (companion) devices, such as device synchronization, password settings, auditing, enable remote wipe, and other settings. Record these settings so that you can ensure the same settings are applied when the devices are being managed by Microsoft Intune or another mobile device management (MDM) provider.</p></li>
|
|
||||||
<li><p><strong>Device activation.</strong> Contains a list of mobile (companion) devices that need to be approved for management by using the Google Admin Console. Approve or block any devices in this list so that the list of managed devices accurately reflects active managed devices.</p></li>
|
|
||||||
<li><p><strong>Managed devices.</strong> Performs management tasks on mobile (companion) devices that are managed by the Google Admin Console. Record the list of companion devices on this page so that you can ensure the same devices are managed by Intune or another MDM provider.</p></li>
|
|
||||||
<li><p><strong>Set Up Apple Push Certificate.</strong> Configures the certificate that is essentially the digital signature that lets the Google Admin Console manage iOS devices. You will need this certificate if you plan to manage iOS devices by using Intune or another MDM provider.</p></li>
|
|
||||||
<li><p><strong>Set Up Android for Work.</strong> Authorizes the Google Admin Console to be the MDM provider for Android devices by providing an Enterprise Mobility Management (EMM) token. You will need this token if you plan to manage Android devices by using another MDM provider.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Chrome management</td>
|
|
||||||
<td align="left"><p>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:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p><strong>User settings.</strong> Configures user-based settings for the Chrome browser and Chromebook devices. Most of these Chromebook user-based settings can be mapped to a corresponding setting in Windows. Record the settings and then map them to settings in Group Policy or Intune.</p></li>
|
|
||||||
<li><p><strong>Public session settings.</strong> Configures Public Sessions for Chrome devices that are used as kiosks, loaner devices, shared computers, or for any other work or school-related purpose for which users don't need to sign in with their credentials. You can configure Windows devices similarly by using Assigned Access. Record the settings and apps that are available in Public Sessions so that you can provide similar configuration in Assigned Access.</p></li>
|
|
||||||
<li><p><strong>Device settings.</strong> Configures device-based settings for the Chrome browser and Chromebook devices. You can map most of these Chromebook device-based settings to a corresponding setting in Windows. Record the settings and then map them to settings in Group Policy or Intune.</p></li>
|
|
||||||
<li><p><strong>Devices.</strong> Manages Chrome device management licenses. The number of licenses recorded here should correspond to the number of licenses you will need for your new management system, such as Intune. Record the number of licenses and use those to determine how many licenses you will need to manage your Windows devices.</p></li>
|
|
||||||
<li><p><strong>App Management.</strong> Provides configuration settings for Chrome apps. Record the settings for any apps that you have identified that will run on Windows devices.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Table 3 lists the settings in the Security node in the Google Admin Console. Review the settings and determine which settings you will migrate to Windows.
|
Table 3 lists the settings in the Security node in the Google Admin Console. Review the settings and determine which settings you will migrate to Windows.
|
||||||
|
|
||||||
Table 3. Settings in the Security node in the Google Admin Console
|
Table 3. Settings in the Security node in the Google Admin Console
|
||||||
|
|
||||||
<table>
|
|Section|Settings|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|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.<br> 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.|
|
||||||
<col width="50%" />
|
|Password monitoring|This section is used to monitor the strength of user passwords. You don’t need to migrate any settings in this section.|
|
||||||
</colgroup>
|
|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.|
|
||||||
<thead>
|
|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.|
|
||||||
<tr class="header">
|
|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.|
|
||||||
<th align="left">Section</th>
|
|
||||||
<th align="left">Settings</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Basic settings</p></td>
|
|
||||||
<td align="left"><p>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.</p>
|
|
||||||
<p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Password monitoring</p></td>
|
|
||||||
<td align="left"><p>This section is used to monitor the strength of user passwords. You don’t need to migrate any settings in this section.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>API reference</p></td>
|
|
||||||
<td align="left"><p>This section is used to enable access to various Google Apps Administrative APIs. You don’t need to migrate any settings in this section.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Set up single sign-on (SSO)</p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Advanced settings</p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Identify locally-configured settings to migrate**
|
**Identify locally-configured settings to migrate**
|
||||||
|
|
||||||
@ -428,62 +355,14 @@ Table 5 is a decision matrix that helps you decide if you can use only on-premis
|
|||||||
|
|
||||||
Table 5. Select on-premises AD DS, Azure AD, or hybrid
|
Table 5. Select on-premises AD DS, Azure AD, or hybrid
|
||||||
|
|
||||||
<table>
|
|If you plan to...|On-premises AD DS|Azure AD|Hybrid|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|Use Office 365||✔️|✔️|
|
||||||
<col width="25%" />
|
|Use Intune for management||✔️|✔️|
|
||||||
<col width="25%" />
|
|Use Microsoft Endpoint Manager for management|✔️||✔️|
|
||||||
<col width="25%" />
|
|Use Group Policy for management|✔️||✔️|
|
||||||
</colgroup>
|
|Have devices that are domain-joined|✔️||✔️|
|
||||||
<thead>
|
|Allow faculty and students to Bring Your Own Device (BYOD) which are not domain-joined||✔️|✔️|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">If you plan to...</th>
|
|
||||||
<th align="left">On-premises AD DS</th>
|
|
||||||
<th align="left">Azure AD</th>
|
|
||||||
<th align="left">Hybrid</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Use Office 365</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Use Intune for management</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Use Microsoft Endpoint Manager for management</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Use Group Policy for management</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Have devices that are domain-joined</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Allow faculty and students to Bring Your Own Device (BYOD) which are not domain-joined</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### <a href="" id="plan-userdevapp-manage"></a>
|
### <a href="" id="plan-userdevapp-manage"></a>
|
||||||
|
|
||||||
@ -497,113 +376,17 @@ Table 6 is a decision matrix that lists the device, user, and app management pro
|
|||||||
|
|
||||||
Table 6. Device, user, and app management products and technologies
|
Table 6. Device, user, and app management products and technologies
|
||||||
|
|
||||||
<table>
|
|Desired feature|Windows provisioning packages|Group Policy|Configuration Manager|Intune|MDT|Windows Software Update Services|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |--- |--- |--- |
|
||||||
<col width="14%" />
|
|Deploy operating system images|✔️||✔️||✔️||
|
||||||
<col width="14%" />
|
|Deploy apps during operating system deployment|✔️||✔️||✔️||
|
||||||
<col width="14%" />
|
|Deploy apps after operating system deployment|✔️|✔️|✔️||||
|
||||||
<col width="14%" />
|
|Deploy software updates during operating system deployment|||✔️||✔️||
|
||||||
<col width="14%" />
|
|Deploy software updates after operating system deployment|✔️|✔️|✔️|✔️||✔️|
|
||||||
<col width="14%" />
|
|Support devices that are domain-joined|✔️|✔️|✔️|✔️|✔️||
|
||||||
<col width="14%" />
|
|Support devices that are not domain-joined|✔️|||✔️|✔️||
|
||||||
</colgroup>
|
|Use on-premises resources|✔️|✔️|✔️||✔️||
|
||||||
<thead>
|
|Use cloud-based services||||✔️|||
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Desired feature</th>
|
|
||||||
<th align="left">Windows provisioning packages</th>
|
|
||||||
<th align="left">Group Policy</th>
|
|
||||||
<th align="left">Configuration Manager</th>
|
|
||||||
<th align="left">Intune</th>
|
|
||||||
<th align="left">MDT</th>
|
|
||||||
<th align="left">Windows Software Update Services</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Deploy operating system images</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Deploy apps during operating system deployment</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Deploy apps after operating system deployment</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left"></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Deploy software updates during operating system deployment</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Deploy software updates after operating system deployment</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Support devices that are domain-joined</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Support devices that are not domain-joined</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Use on-premises resources</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Use cloud-based services</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left">X</td>
|
|
||||||
<td align="left"></td>
|
|
||||||
<td align="left"></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
You can use Configuration Manager and Intune in conjunction with each other to provide features from both products and technologies. In some instances you may need only one of these products or technologies. In other instances, you may need two or more to meet the device, user, and app management needs for your institution.
|
You can use Configuration Manager and Intune in conjunction with each other to provide features from both products and technologies. In some instances you may need only one of these products or technologies. In other instances, you may need two or more to meet the device, user, and app management needs for your institution.
|
||||||
|
|
||||||
@ -665,35 +448,10 @@ It is important that you perform any network infrastructure remediation first be
|
|||||||
|
|
||||||
Table 7. Network infrastructure products and technologies and deployment resources
|
Table 7. Network infrastructure products and technologies and deployment resources
|
||||||
|
|
||||||
<table>
|
|Product or technology|Resources|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|DHCP|<li> [Core Network Guide](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11)) <li> [DHCP Deployment Guide](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd283051(v=ws.10))|
|
||||||
<col width="50%" />
|
|DNS|<li>[Core Network Guide](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11)) <li>[Deploying Domain Name System (DNS)](/previous-versions/windows/it-pro/windows-server-2003/cc780661(v=ws.10))|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Product or technology</th>
|
|
||||||
<th align="left">Resources</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">DHCP</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11)" data-raw-source="[Core Network Guide](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11))">Core Network Guide</a></p></li>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd283051(v=ws.10)" data-raw-source="[DHCP Deployment Guide](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd283051(v=ws.10))">DHCP Deployment Guide</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">DNS</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11)" data-raw-source="[Core Network Guide](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11))">Core Network Guide</a></p></li>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2003/cc780661(v=ws.10)" data-raw-source="[Deploying Domain Name System (DNS)](/previous-versions/windows/it-pro/windows-server-2003/cc780661(v=ws.10))">Deploying Domain Name System (DNS)</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If you use network infrastructure products and technologies from other vendors, refer to the vendor documentation on how to perform the necessary remediation. If you determined that no remediation is necessary, you can skip this section.
|
If you use network infrastructure products and technologies from other vendors, refer to the vendor documentation on how to perform the necessary remediation. If you determined that no remediation is necessary, you can skip this section.
|
||||||
@ -707,37 +465,10 @@ In the [Plan for Active Directory services](#plan-adservices) section, you deter
|
|||||||
|
|
||||||
Table 8. AD DS, Azure AD and deployment resources
|
Table 8. AD DS, Azure AD and deployment resources
|
||||||
|
|
||||||
<table>
|
|Product or technology|Resources|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|AD DS| <li> [Core Network Guide](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11)) <li>[Active Directory Domain Services Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831484(v=ws.11))|
|
||||||
<col width="50%" />
|
|Azure AD| <li> [Azure Active Directory documentation](/azure/active-directory/) <li>[Manage and support Azure Active Directory Premium](https://go.microsoft.com/fwlink/p/?LinkId=690259) <li>[Guidelines for Deploying Windows Server Active Directory on Azure Virtual Machines](/windows-server/identity/ad-ds/introduction-to-active-directory-domain-services-ad-ds-virtualization-level-100)|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Product or technology</th>
|
|
||||||
<th align="left">Resources</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">AD DS</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11)" data-raw-source="[Core Network Guide](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh911995(v=ws.11))">Core Network Guide</a></p></li>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831484(v=ws.11)" data-raw-source="[Active Directory Domain Services Overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831484(v=ws.11))">Active Directory Domain Services Overview</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Azure AD</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/azure/active-directory/" data-raw-source="[Azure Active Directory documentation](/azure/active-directory/)">Azure Active Directory documentation</a></p></li>
|
|
||||||
<li><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=690259" data-raw-source="[Manage and support Azure Active Directory Premium](https://go.microsoft.com/fwlink/p/?LinkId=690259)">Manage and support Azure Active Directory Premium</a></p></li>
|
|
||||||
<li><p><a href="/windows-server/identity/ad-ds/introduction-to-active-directory-domain-services-ad-ds-virtualization-level-100" data-raw-source="[Guidelines for Deploying Windows Server Active Directory on Azure Virtual Machines](/windows-server/identity/ad-ds/introduction-to-active-directory-domain-services-ad-ds-virtualization-level-100)">Guidelines for Deploying Windows Server Active Directory on Azure Virtual Machines</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If you decided not to migrate to AD DS or Azure AD as a part of the migration, or if you determined that no remediation is necessary, you can skip this section. If you use identity products and technologies from another vendor, refer to the vendor documentation on how to perform the necessary steps.
|
If you decided not to migrate to AD DS or Azure AD as a part of the migration, or if you determined that no remediation is necessary, you can skip this section. If you use identity products and technologies from another vendor, refer to the vendor documentation on how to perform the necessary steps.
|
||||||
|
|
||||||
@ -750,59 +481,13 @@ Table 9 lists the Microsoft management systems and the deployment resources for
|
|||||||
|
|
||||||
Table 9. Management systems and deployment resources
|
Table 9. Management systems and deployment resources
|
||||||
|
|
||||||
<table>
|
|Management system|Resources|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Windows provisioning packages| <li> [Build and apply a provisioning package](/windows/configuration/provisioning-packages/provisioning-create-package) <li>[Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd) <li> [Step-By-Step: Building Windows 10 Provisioning Packages](/archive/blogs/canitpro/step-by-step-building-windows-10-provisioning-packages)|
|
||||||
<col width="50%" />
|
|Group Policy|<li> [Core Network Companion Guide: Group Policy Deployment](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj899807(v=ws.11)) <li> [Deploying Group Policy](/previous-versions/windows/it-pro/windows-server-2003/cc737330(v=ws.10))"|
|
||||||
</colgroup>
|
|Configuration Manager| <li> [Site Administration for System Center 2012 Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg681983(v=technet.10)) <li> [Deploying Clients for System Center 2012 Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg699391(v=technet.10))|
|
||||||
<thead>
|
|Intune| <li> [Set up and manage devices with Microsoft Intune](https://go.microsoft.com/fwlink/p/?LinkId=690262) <li> [Smoother Management Of Office 365 Deployments with Windows Intune](https://go.microsoft.com/fwlink/p/?LinkId=690263) <li> [System Center 2012 R2 Configuration Manager &amp; Windows Intune](/learn/?l=fCzIjVKy_6404984382)|
|
||||||
<tr class="header">
|
|MDT| <li>[MDT documentation in the Microsoft Deployment Toolkit (MDT) 2013](https://go.microsoft.com/fwlink/p/?LinkId=690324) <li> [Step-By-Step: Installing Windows 8.1 From A USB Key](/archive/blogs/canitpro/step-by-step-installing-windows-8-1-from-a-usb-key)|
|
||||||
<th align="left">Management system</th>
|
|
||||||
<th align="left">Resources</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Windows provisioning packages</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/windows/configuration/provisioning-packages/provisioning-create-package" data-raw-source="[Build and apply a provisioning package](/windows/configuration/provisioning-packages/provisioning-create-package)">Build and apply a provisioning package</a></p></li>
|
|
||||||
<li><p><a href="/windows/configuration/provisioning-packages/provisioning-install-icd" data-raw-source="[Windows Imaging and Configuration Designer](/windows/configuration/provisioning-packages/provisioning-install-icd)">Windows Imaging and Configuration Designer</a></p></li>
|
|
||||||
<li><p><a href="/archive/blogs/canitpro/step-by-step-building-windows-10-provisioning-packages" data-raw-source="[Step-By-Step: Building Windows 10 Provisioning Packages](/archive/blogs/canitpro/step-by-step-building-windows-10-provisioning-packages)">Step-By-Step: Building Windows 10 Provisioning Packages</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Group Policy</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj899807(v=ws.11)" data-raw-source="[Core Network Companion Guide: Group Policy Deployment](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj899807(v=ws.11))">Core Network Companion Guide: Group Policy Deployment</a></p></li>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2003/cc737330(v=ws.10)" data-raw-source="[Deploying Group Policy](/previous-versions/windows/it-pro/windows-server-2003/cc737330(v=ws.10))">Deploying Group Policy</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Configuration Manager</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/previous-versions/system-center/system-center-2012-R2/gg681983(v=technet.10)" data-raw-source="[Site Administration for System Center 2012 Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg681983(v=technet.10))">Site Administration for System Center 2012 Configuration Manager</a></p></li>
|
|
||||||
<li><p><a href="/previous-versions/system-center/system-center-2012-R2/gg699391(v=technet.10)" data-raw-source="[Deploying Clients for System Center 2012 Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg699391(v=technet.10))">Deploying Clients for System Center 2012 Configuration Manager</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Intune</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=690262" data-raw-source="[Set up and manage devices with Microsoft Intune](https://go.microsoft.com/fwlink/p/?LinkId=690262)">Set up and manage devices with Microsoft Intune</a></p></li>
|
|
||||||
<li><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=690263" data-raw-source="[Smoother Management Of Office 365 Deployments with Windows Intune](https://go.microsoft.com/fwlink/p/?LinkId=690263)">Smoother Management Of Office 365 Deployments with Windows Intune</a></p></li>
|
|
||||||
<li><p><a href="/learn/?l=fCzIjVKy_6404984382" data-raw-source="[System Center 2012 R2 Configuration Manager &amp; Windows Intune](/learn/?l=fCzIjVKy_6404984382)">System Center 2012 R2 Configuration Manager & Windows Intune</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">MDT</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=690324" data-raw-source="[MDT documentation in the Microsoft Deployment Toolkit (MDT) 2013](https://go.microsoft.com/fwlink/p/?LinkId=690324)">MDT documentation in the Microsoft Deployment Toolkit (MDT) 2013</a></p></li>
|
|
||||||
<li><p><a href="/archive/blogs/canitpro/step-by-step-installing-windows-8-1-from-a-usb-key" data-raw-source="[Step-By-Step: Installing Windows 8.1 From A USB Key](/archive/blogs/canitpro/step-by-step-installing-windows-8-1-from-a-usb-key)">Step-By-Step: Installing Windows 8.1 From A USB Key</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If you determined that no new management system or no remediation of existing systems is necessary, you can skip this section. If you use a management system from another vendor, refer to the vendor documentation on how to perform the necessary steps.
|
If you determined that no new management system or no remediation of existing systems is necessary, you can skip this section. If you use a management system from another vendor, refer to the vendor documentation on how to perform the necessary steps.
|
||||||
|
|
||||||
@ -815,44 +500,11 @@ In this step, you need to configure your management system to deploy the apps to
|
|||||||
|
|
||||||
Table 10. Management systems and app deployment resources
|
Table 10. Management systems and app deployment resources
|
||||||
|
|
||||||
<table>
|
|Management system|Resources|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Group Policy| <li> [Editing an AppLocker Policy](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee791894(v=ws.10)) <li> [Group Policy Software Deployment Background](/previous-versions/windows/it-pro/windows-server-2003/cc739305(v=ws.10)) <li> [Assigning and Publishing Software](/previous-versions/windows/it-pro/windows-server-2003/cc783635(v=ws.10))|
|
||||||
<col width="50%" />
|
|Configuration Manager| <li> [How to Deploy Applications in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682082(v=technet.10)) <li> [Application Management in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg699373(v=technet.10))|
|
||||||
</colgroup>
|
|Intune| <li> [Deploy apps to mobile devices in Microsoft Intune](https://go.microsoft.com/fwlink/p/?LinkId=733913) <li> [Manage apps with Microsoft Intune](/mem/intune/)|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Management system</th>
|
|
||||||
<th align="left">Resources</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Group Policy</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee791894(v=ws.10)" data-raw-source="[Editing an AppLocker Policy](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee791894(v=ws.10))">Editing an AppLocker Policy</a></p></li>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2003/cc739305(v=ws.10)" data-raw-source="[Group Policy Software Deployment Background](/previous-versions/windows/it-pro/windows-server-2003/cc739305(v=ws.10))">Group Policy Software Deployment Background</a></p></li>
|
|
||||||
<li><p><a href="/previous-versions/windows/it-pro/windows-server-2003/cc783635(v=ws.10)" data-raw-source="[Assigning and Publishing Software](/previous-versions/windows/it-pro/windows-server-2003/cc783635(v=ws.10))">Assigning and Publishing Software</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Configuration Manager</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="/previous-versions/system-center/system-center-2012-R2/gg682082(v=technet.10)" data-raw-source="[How to Deploy Applications in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682082(v=technet.10))">How to Deploy Applications in Configuration Manager</a></p></li>
|
|
||||||
<li><p><a href="/previous-versions/system-center/system-center-2012-R2/gg699373(v=technet.10)" data-raw-source="[Application Management in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg699373(v=technet.10))">Application Management in Configuration Manager</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Intune</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=733913" data-raw-source="[Deploy apps to mobile devices in Microsoft Intune](https://go.microsoft.com/fwlink/p/?LinkId=733913)">Deploy apps to mobile devices in Microsoft Intune</a></p></li>
|
|
||||||
<li><p><a href="/mem/intune/" data-raw-source="[Manage apps with Microsoft Intune](/mem/intune/)">Manage apps with Microsoft Intune</a></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If you determined that no deployment of apps is necessary, you can skip this section. If you use a management system from another vendor, refer to the vendor documentation on how to perform the necessary steps.
|
If you determined that no deployment of apps is necessary, you can skip this section. If you use a management system from another vendor, refer to the vendor documentation on how to perform the necessary steps.
|
||||||
|
|
||||||
|
|||||||
@ -83,7 +83,7 @@ This district configuration has the following characteristics:
|
|||||||
|
|
||||||
* If you have on-premises AD DS, you can [integrate Azure AD with on-premises AD DS](/azure/active-directory/hybrid/whatis-hybrid-identity).
|
* If you have on-premises AD DS, you can [integrate Azure AD with on-premises AD DS](/azure/active-directory/hybrid/whatis-hybrid-identity).
|
||||||
|
|
||||||
* Use [Intune](/intune/), [Mobile Device Management for Office 365](https://support.office.com/en-us/article/Set-up-Mobile-Device-Management-MDM-in-Office-365-dd892318-bc44-4eb1-af00-9db5430be3cd?ui=en-US&rs=en-US&ad=US), or [Group Policy in AD DS](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc725828(v=ws.10)) to manage devices.
|
* Use [Intune](/intune/), [Mobile Device Management for Office 365](/microsoft-365/admin/basic-mobility-security/set-up), or [Group Policy in AD DS](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc725828(v=ws.10)) to manage devices.
|
||||||
|
|
||||||
* Each device supports a one-student-per-device or multiple-students-per-device scenario.
|
* Each device supports a one-student-per-device or multiple-students-per-device scenario.
|
||||||
|
|
||||||
@ -128,7 +128,7 @@ Office 365 Education allows:
|
|||||||
|
|
||||||
* Students and faculty to access classroom resources from anywhere on any device (including iOS and Android devices).
|
* Students and faculty to access classroom resources from anywhere on any device (including iOS and Android devices).
|
||||||
|
|
||||||
For more information about Office 365 Education features and an FAQ, go to [Office 365 Education plans and pricing](https://products.office.com/en-us/academic).
|
For more information about Office 365 Education features and an FAQ, go to [Office 365 Education plans and pricing](https://www.microsoft.com/microsoft-365/academic/compare-office-365-education-plans).
|
||||||
|
|
||||||
### How to configure a district
|
### How to configure a district
|
||||||
|
|
||||||
@ -225,80 +225,10 @@ Use the cloud-centric scenario and on-premises and cloud scenario as a guide for
|
|||||||
|
|
||||||
To deploy Windows 10 and your apps, you can use MDT by itself or Microsoft Endpoint Manager and MDT together. For a district, there are a few ways to deploy Windows 10 to devices. Table 2 lists the methods that this guide describes and recommends. Use this information to determine which combination of deployment methods is right for your institution.
|
To deploy Windows 10 and your apps, you can use MDT by itself or Microsoft Endpoint Manager and MDT together. For a district, there are a few ways to deploy Windows 10 to devices. Table 2 lists the methods that this guide describes and recommends. Use this information to determine which combination of deployment methods is right for your institution.
|
||||||
|
|
||||||
<table>
|
|Method|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="25%" />
|
|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.<br> Select this method when you: <li> Want to deploy Windows 10 to institution-owned and personal devices. (Devices need not be domain joined.) <li> Don’t have an existing AD DS infrastructure. <li> Need to manage devices regardless of where they are (on or off premises). <br>The advantages of this method are that: <br> <li> You can deploy Windows 10 operating systems <li> You can manage device drivers during initial deployment. <li>You can deploy Windows desktop apps (during initial deployment)<li> It doesn’t require an AD DS infrastructure.<li>It doesn’t have additional infrastructure requirements.<li>MDT doesn’t incur additional cost: it’s a free tool.<li>You can deploy Windows 10 operating systems to institution-owned and personal devices. <br> The disadvantages of this method are that it:<br> <li>Can’t manage applications throughout entire application life cycle (by itself).<li>Can’t manage software updates for Windows 10 and apps (by itself).<li>Doesn’t provide antivirus and malware protection (by itself).<li>Has limited scaling to large numbers of users and devices.|
|
||||||
<col width="75%" />
|
|Microsoft Endpoint Configuration Manager|<li> Configuration Manager is an on-premises solution that supports operating system management throughout the entire operating system life cycle <li>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. <br> Select this method when you: <li> Want to deploy Windows 10 to institution-owned devices that are domain joined (personal devices are typically not domain joined). <li>Have an existing AD DS infrastructure (or plan to deploy an AD DS infrastructure). <li>Typically deploy Windows 10 to on-premises devices. <br> The advantages of this method are that: <li>You can deploy Windows 10 operating systems.<li>You can manage (deploy) Windows desktop and Microsoft Store apps throughout entire application life cycle.<li>You can manage software updates for Windows 10 and apps.<li>You can manage antivirus and malware protection.<li>It scales to large number of users and devices. <br>The disadvantages of this method are that it:<li>Carries an additional cost for Microsoft Endpoint Manager server licenses (if the institution does not have Configuration Manager already).<li>Can deploy Windows 10 only to domain-joined (institution-owned devices).<li>Requires an AD DS infrastructure (if the institution does not have AD DS already).|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Method</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">MDT</td>
|
|
||||||
<td><p>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.<br/><br/>
|
|
||||||
Select this method when you:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Want to deploy Windows 10 to institution-owned and personal devices. (Devices need not be domain joined.)</li>
|
|
||||||
<li>Don’t have an existing AD DS infrastructure.</li>
|
|
||||||
<li>Need to manage devices regardless of where they are (on or off premises).</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<p>The advantages of this method are that:</p>
|
|
||||||
<ul>
|
|
||||||
<li>You can deploy Windows 10 operating systems.</li>
|
|
||||||
<li>You can manage device drivers during initial deployment.</li>
|
|
||||||
<li>You can deploy Windows desktop apps (during initial deployment)</li>
|
|
||||||
<li>It doesn’t require an AD DS infrastructure.</li>
|
|
||||||
<li>It doesn’t have additional infrastructure requirements.</li>
|
|
||||||
<li>MDT doesn’t incur additional cost: it’s a free tool.</li>
|
|
||||||
<li>You can deploy Windows 10 operating systems to institution-owned and personal devices.</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<p>The disadvantages of this method are that it:</p>
|
|
||||||
|
|
||||||
<ul>
|
|
||||||
<li>Can’t manage applications throughout entire application life cycle (by itself).</li>
|
|
||||||
<li>Can’t manage software updates for Windows 10 and apps (by itself).</li>
|
|
||||||
<li>Doesn’t provide antivirus and malware protection (by itself).</li>
|
|
||||||
<li>Has limited scaling to large numbers of users and devices.</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Microsoft Endpoint Configuration Manager</td>
|
|
||||||
<td><p>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.<br/><br/>
|
|
||||||
Select this method when you:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Want to deploy Windows 10 to institution-owned devices that are domain joined (personal devices are typically not domain joined).</li>
|
|
||||||
<li>Have an existing AD DS infrastructure (or plan to deploy an AD DS infrastructure).</li>
|
|
||||||
<li>Typically deploy Windows 10 to on-premises devices.</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<p>The advantages of this method are that:</p>
|
|
||||||
<ul>
|
|
||||||
<li>You can deploy Windows 10 operating systems.</li>
|
|
||||||
<li>You can manage (deploy) Windows desktop and Microsoft Store apps throughout entire application life cycle.</li>
|
|
||||||
<li>You can manage software updates for Windows 10 and apps.</li>
|
|
||||||
<li>You can manage antivirus and malware protection.</li>
|
|
||||||
<li>It scales to large number of users and devices.</li>
|
|
||||||
</ul>
|
|
||||||
<p>The disadvantages of this method are that it:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Carries an additional cost for Microsoft Endpoint Manager server licenses (if the institution does not have Configuration Manager already).</li>
|
|
||||||
<li>Can deploy Windows 10 only to domain-joined (institution-owned devices).</li>
|
|
||||||
<li>Requires an AD DS infrastructure (if the institution does not have AD DS already).</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
*Table 2. Deployment methods*
|
*Table 2. Deployment methods*
|
||||||
|
|
||||||
@ -317,81 +247,10 @@ If you have only one device to configure, manually configuring that one device i
|
|||||||
|
|
||||||
For a district, there are many ways to manage the configuration setting for users and devices. Table 4 lists the methods that this guide describes and recommends. Use this information to determine which combination of configuration setting management methods is right for your institution.
|
For a district, there are many ways to manage the configuration setting for users and devices. Table 4 lists the methods that this guide describes and recommends. Use this information to determine which combination of configuration setting management methods is right for your institution.
|
||||||
|
|
||||||
<table>
|
|Method|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="25%" />
|
|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. <br> Select this method when you <li>Want to manage institution-owned devices that are domain joined (personal devices are typically not domain joined).<li> Want more granular control of device and user settings. <li>Have an existing AD DS infrastructure.<li>Typically manage on-premises devices.<li>Can manage a required setting only by using Group Policy. <br>The advantages of this method include: <li>No cost beyond the AD DS infrastructure. <li>A larger number of settings (compared to Intune).<br>The disadvantages of this method are that it:<li>Can only manage domain-joined (institution-owned devices).<li>Requires an AD DS infrastructure (if the institution does not have AD DS already).<li>Typically manages on-premises devices (unless devices use a virtual private network [VPN] or Microsoft DirectAccess to connect).<li> Has rudimentary app management capabilities.<li> Cannot deploy Windows 10 operating systems.|
|
||||||
<col width="75%" />
|
|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.<br>Intune is the cloud-based management system described in this guide, but you can use other MDM providers. If you use an MDM provider other than Intune, integration with Configuration Manager is unavailable.<br>Select this method when you:<li> Want to manage institution-owned and personal devices (does not require that the device be domain joined).<li>Don’t need granular control over device and user settings (compared to Group Policy).<li>Don’t have an existing AD DS infrastructure.<li>Need to manage devices regardless of where they are (on or off premises).<li>Want to provide application management for the entire application life cycle.<li>Can manage a required setting only by using Intune.<br>The advantages of this method are that:<li>You can manage institution-owned and personal devices.<li>It doesn’t require that devices be domain joined.<li>It doesn’t require any on-premises infrastructure.<li>It can manage devices regardless of their location (on or off premises).<br>The disadvantages of this method are that it:<li>Carries an additional cost for Intune subscription licenses.<li>Doesn’t offer granular control over device and user settings (compared to Group Policy).<li>Cannot deploy Windows 10 operating systems.|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Method</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Group Policy</td>
|
|
||||||
<td><p>Group Policy is an integral part of AD DS and allows you to specify configuration settings for Windows 10 and previous versions of Windows.<br/><br/>
|
|
||||||
Select this method when you:</p>
|
|
||||||
|
|
||||||
<ul>
|
|
||||||
<li>Want to manage institution-owned devices that are domain joined (personal devices are typically not domain joined).</li>
|
|
||||||
<li>Want more granular control of device and user settings.</li>
|
|
||||||
<li>Have an existing AD DS infrastructure.</li>
|
|
||||||
<li>Typically manage on-premises devices.</li>
|
|
||||||
<li>Can manage a required setting only by using Group Policy.</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<p>The advantages of this method include:</p>
|
|
||||||
<ul>
|
|
||||||
<li>No cost beyond the AD DS infrastructure.</li>
|
|
||||||
<li>A larger number of settings (compared to Intune).</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<p>The disadvantages of this method are that it:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Can only manage domain-joined (institution-owned devices).</li>
|
|
||||||
<li>Requires an AD DS infrastructure (if the institution does not have AD DS already).</li>
|
|
||||||
<li>Typically manages on-premises devices (unless devices use a virtual private network [VPN] or Microsoft DirectAccess to connect).</li>
|
|
||||||
<li>Has rudimentary app management capabilities.</li>
|
|
||||||
<li>Cannot deploy Windows 10 operating systems.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Intune</td>
|
|
||||||
<td><p>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.<br/><br/>
|
|
||||||
Intune is the cloud-based management system described in this guide, but you can use other MDM providers. If you use an MDM provider other than Intune, integration with Configuration Manager is unavailable.<br/><br/>
|
|
||||||
Select this method when you:</p>
|
|
||||||
|
|
||||||
<ul>
|
|
||||||
<li>Want to manage institution-owned and personal devices (does not require that the device be domain joined).</li>
|
|
||||||
<li>Don’t need granular control over device and user settings (compared to Group Policy).</li>
|
|
||||||
<li>Don’t have an existing AD DS infrastructure.</li>
|
|
||||||
<li>Need to manage devices regardless of where they are (on or off premises).</li>
|
|
||||||
<li>Want to provide application management for the entire application life cycle.</li>
|
|
||||||
<li>Can manage a required setting only by using Intune.</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<p>The advantages of this method are that:</p>
|
|
||||||
<ul>
|
|
||||||
<li>You can manage institution-owned and personal devices.</li>
|
|
||||||
<li>It doesn’t require that devices be domain joined.</li>
|
|
||||||
<li>It doesn’t require any on-premises infrastructure.</li>
|
|
||||||
<li>It can manage devices regardless of their location (on or off premises).</li>
|
|
||||||
</ul>
|
|
||||||
<p>The disadvantages of this method are that it:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Carries an additional cost for Intune subscription licenses.</li>
|
|
||||||
<li>Doesn’t offer granular control over device and user settings (compared to Group Policy).</li>
|
|
||||||
<li>Cannot deploy Windows 10 operating systems.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
*Table 4. Configuration setting management methods*
|
*Table 4. Configuration setting management methods*
|
||||||
|
|
||||||
@ -410,114 +269,11 @@ For a district, there are many ways to manage apps and software updates. Table 6
|
|||||||
|
|
||||||
Use the information in Table 6 to determine which combination of app and update management products is right for your district.
|
Use the information in Table 6 to determine which combination of app and update management products is right for your district.
|
||||||
|
|
||||||
<table>
|
|Selection|Management method|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="25%" />
|
|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.Configuration Manager supports application management throughout the entire application life cycle. You can deploy, upgrade, manage multiple versions, and retire applications by using Configuration Manager. You can also manage Windows desktop and Microsoft Store applications. Select this method when you:<li>Selected Configuration Manager to deploy Windows 10.<li>Want to manage institution-owned devices that are domain joined (personally owned devices are typically not domain joined).<li>Want to manage AD DS domain-joined devices.<li>Have an existing AD DS infrastructure.<li>Typically manage on-premises devices.<li>Want to deploy operating systems.<li>Want to provide application management for the entire application life cycle.<br>The advantages of this method are that:<li>You can deploy Windows 10 operating systems.<li>You can manage applications throughout the entire application life cycle.<li>You can manage software updates for Windows 10 and apps.<li>You can manage antivirus and malware protection.<li>It scales to large numbers of users and devices.<br>The disadvantages of this method are that it:<li>Carries an additional cost for Configuration Manager server licenses (if the institution does not have Configuration Manager already).<li>Carries an additional cost for Windows Server licenses and the corresponding server hardware.<li>Can only manage domain-joined (institution-owned devices).<li>Requires an AD DS infrastructure (if the institution does not have AD DS already).<li>Typically manages on-premises devices (unless devices through VPN or DirectAccess).|
|
||||||
<col width="75%" />
|
|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.<br>Select this method when you:<li>Selected MDT only to deploy Windows 10.<li>Want to manage institution-owned and personal devices that are not domain joined.<li>Want to manage Azure AD domain-joined devices.<li>Need to manage devices regardless of where they are (on or off premises).<li>Want to provide application management for the entire application life cycle.<br>The advantages of this method are that:<li>You can manage institution-owned and personal devices.<li>It doesn’t require that devices be domain joined.<li>It doesn’t require on-premises infrastructure.vIt can manage devices regardless of their location (on or off premises).<li>You can deploy keys to perform in-place Windows 10 upgrades (such as upgrading from Windows 10 Pro to Windows 10 Education edition).<br>The disadvantages of this method are that it:<li>Carries an additional cost for Intune subscription licenses.<li>Cannot deploy Windows 10 operating systems.|
|
||||||
</colgroup>
|
|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.<br>Configuration Manager and Intune in the hybrid configuration allow you to support application management throughout the entire application life cycle. You can deploy, upgrade, manage multiple versions, and retire applications by using Configuration Manager, and you can manage Windows desktop and Microsoft Store applications for both institution-owned and personal devices. <br>Select this method when you:<li>Selected Microsoft Endpoint Manager to deploy Windows 10.<li>Want to manage institution-owned and personal devices (does not require that the device be domain joined).<li>Want to manage domain-joined devices.<li>Want to manage Azure AD domain-joined devices.<li>Have an existing AD DS infrastructure.<li>Want to manage devices regardless of their connectivity.vWant to deploy operating systems.<li>Want to provide application management for the entire application life cycle.<br>The advantages of this method are that:<li>You can deploy operating systems.<li>You can manage applications throughout the entire application life cycle.<li>You can scale to large numbers of users and devices.<li>You can support institution-owned and personal devices.<li>It doesn’t require that devices be domain joined.<li>It can manage devices regardless of their location (on or off premises).<br>The disadvantages of this method are that it:<li>Carries an additional cost for Configuration Manager server licenses (if the institution does not have Configuration Manager already).<li>Carries an additional cost for Windows Server licenses and the corresponding server hardware.<li>Carries an additional cost for Intune subscription licenses.<li>Requires an AD DS infrastructure (if the institution does not have AD DS already).|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Selection</th>
|
|
||||||
<th align="left">Management method</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Microsoft Endpoint Configuration Manager</td>
|
|
||||||
<td><p>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.<br/><br/>Configuration Manager supports application management throughout the entire application life cycle. You can deploy, upgrade, manage multiple versions, and retire applications by using Configuration Manager. You can also manage Windows desktop and Microsoft Store applications.<br/><br/>Select this method when you:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Selected Configuration Manager to deploy Windows 10.</li>
|
|
||||||
<li>Want to manage institution-owned devices that are domain joined (personally owned devices are typically not domain joined).</li>
|
|
||||||
<li>Want to manage AD DS domain-joined devices.</li>
|
|
||||||
<li>Have an existing AD DS infrastructure.</li>
|
|
||||||
<li>Typically manage on-premises devices.</li>
|
|
||||||
<li>Want to deploy operating systems.</li>
|
|
||||||
<li>Want to provide application management for the entire application life cycle.</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
<p>The advantages of this method are that:</p>
|
|
||||||
<ul>
|
|
||||||
<li>You can deploy Windows 10 operating systems.</li>
|
|
||||||
<li>You can manage applications throughout the entire application life cycle.</li>
|
|
||||||
<li>You can manage software updates for Windows 10 and apps.</li>
|
|
||||||
<li>You can manage antivirus and malware protection.</li>
|
|
||||||
<li>It scales to large numbers of users and devices.</li>
|
|
||||||
</ul>
|
|
||||||
<p>The disadvantages of this method are that it:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Carries an additional cost for Configuration Manager server licenses (if the institution does not have Configuration Manager already).</li>
|
|
||||||
<li>Carries an additional cost for Windows Server licenses and the corresponding server hardware.</li>
|
|
||||||
<li>Can only manage domain-joined (institution-owned devices).</li>
|
|
||||||
<li>Requires an AD DS infrastructure (if the institution does not have AD DS already).</li>
|
|
||||||
<li>Typically manages on-premises devices (unless devices through VPN or DirectAccess).</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Intune</td>
|
|
||||||
<td><p>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.<br/><br/>
|
|
||||||
Select this method when you:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Selected MDT only to deploy Windows 10.</li>
|
|
||||||
<li>Want to manage institution-owned and personal devices that are not domain joined.</li>
|
|
||||||
<li>Want to manage Azure AD domain-joined devices.</li>
|
|
||||||
<li>Need to manage devices regardless of where they are (on or off premises).</li>
|
|
||||||
<li>Want to provide application management for the entire application life cycle.</li>
|
|
||||||
</ul>
|
|
||||||
<p>The advantages of this method are that:</p>
|
|
||||||
<ul>
|
|
||||||
<li>You can manage institution-owned and personal devices.</li>
|
|
||||||
<li>It doesn’t require that devices be domain joined.</li>
|
|
||||||
<li>It doesn’t require on-premises infrastructure.</li>
|
|
||||||
<li>It can manage devices regardless of their location (on or off premises).</li>
|
|
||||||
<li>You can deploy keys to perform in-place Windows 10 upgrades (such as upgrading from Windows 10 Pro to Windows 10 Education edition).</li>
|
|
||||||
</ul>
|
|
||||||
<p>The disadvantages of this method are that it:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Carries an additional cost for Intune subscription licenses.</li>
|
|
||||||
<li>Cannot deploy Windows 10 operating systems.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Microsoft Endpoint Manager and Intune (hybrid)</td>
|
|
||||||
<td><p>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.<br/><br/>
|
|
||||||
Configuration Manager and Intune in the hybrid configuration allow you to support application management throughout the entire application life cycle. You can deploy, upgrade, manage multiple versions, and retire applications by using Configuration Manager, and you can manage Windows desktop and Microsoft Store applications for both institution-owned and personal devices.<br/><br/>
|
|
||||||
Select this method when you:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Selected Microsoft Endpoint Manager to deploy Windows 10.</li>
|
|
||||||
<li>Want to manage institution-owned and personal devices (does not require that the device be domain joined).</li>
|
|
||||||
<li>Want to manage domain-joined devices.</li>
|
|
||||||
<li>Want to manage Azure AD domain-joined devices.</li>
|
|
||||||
<li>Have an existing AD DS infrastructure.</li>
|
|
||||||
<li>Want to manage devices regardless of their connectivity.</li>
|
|
||||||
<li>Want to deploy operating systems.</li>
|
|
||||||
<li>Want to provide application management for the entire application life cycle.</li>
|
|
||||||
</ul>
|
|
||||||
<p>The advantages of this method are that:</p>
|
|
||||||
<ul>
|
|
||||||
<li>You can deploy operating systems.</li>
|
|
||||||
<li>You can manage applications throughout the entire application life cycle.</li>
|
|
||||||
<li>You can scale to large numbers of users and devices.</li>
|
|
||||||
<li>You can support institution-owned and personal devices.</li>
|
|
||||||
<li>It doesn’t require that devices be domain joined.</li>
|
|
||||||
<li>It can manage devices regardless of their location (on or off premises).</li>
|
|
||||||
</ul>
|
|
||||||
<p>The disadvantages of this method are that it:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Carries an additional cost for Configuration Manager server licenses (if the institution does not have Configuration Manager already).</li>
|
|
||||||
<li>Carries an additional cost for Windows Server licenses and the corresponding server hardware.</li>
|
|
||||||
<li>Carries an additional cost for Intune subscription licenses.</li>
|
|
||||||
<li>Requires an AD DS infrastructure (if the institution does not have AD DS already).</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
*Table 6. App and update management products*
|
*Table 6. App and update management products*
|
||||||
|
|
||||||
@ -683,7 +439,7 @@ Now that you have created your new Office 365 Education subscription, add the do
|
|||||||
To make it easier for faculty and students to join your Office 365 Education subscription (or *tenant*), allow them to automatically sign up to your tenant (*automatic tenant join*). In automatic tenant join, when a faculty member or student signs up for Office 365, Office 365 automatically adds (joins) the user to your Office 365 tenant.
|
To make it easier for faculty and students to join your Office 365 Education subscription (or *tenant*), allow them to automatically sign up to your tenant (*automatic tenant join*). In automatic tenant join, when a faculty member or student signs up for Office 365, Office 365 automatically adds (joins) the user to your Office 365 tenant.
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> By default, automatic tenant join is enabled in Office 365 Education, with the exception of certain areas in Europe, the Middle East, and Africa. These countries/regions require opt-in steps to add new users to existing Office 365 tenants. Check your country/region requirements to determine the automatic tenant join default configuration. Also, if you use Azure AD Connect, then automatic tenant join is disabled. For more information, see [Office 365 Education Self-Sign up: Technical FAQ](https://support.office.com/en-us/article/Office-365-Education-Self-Sign-up-Technical-FAQ-7fb1b2f9-94c2-4cbb-b01e-a6eca34261d6?ui=en-US&rs=en-US&ad=US&WT.mc_id=eml_CXM__33537_MOD_EDU_Student_Advantage_Rush).
|
> By default, automatic tenant join is enabled in Office 365 Education, with the exception of certain areas in Europe, the Middle East, and Africa. These countries/regions require opt-in steps to add new users to existing Office 365 tenants. Check your country/region requirements to determine the automatic tenant join default configuration. Also, if you use Azure AD Connect, then automatic tenant join is disabled. For more information, see [Office 365 Education Self-Sign up FAQ](/microsoft-365/education/deploy/office-365-education-self-sign-up).
|
||||||
|
|
||||||
Office 365 uses the domain portion of the user’s email address to know which Office 365 tenant to join. For example, if a faculty member or student provides an email address of user@contoso.edu, then Office 365 automatically performs one of the following tasks:
|
Office 365 uses the domain portion of the user’s email address to know which Office 365 tenant to join. For example, if a faculty member or student provides an email address of user@contoso.edu, then Office 365 automatically performs one of the following tasks:
|
||||||
|
|
||||||
@ -695,7 +451,7 @@ You will always want faculty and students to join the Office 365 tenant that you
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> You cannot merge multiple tenants, so any faculty or students who create their own tenant will need to abandon their existing tenant and join yours.
|
> You cannot merge multiple tenants, so any faculty or students who create their own tenant will need to abandon their existing tenant and join yours.
|
||||||
|
|
||||||
By default, all new Office 365 Education subscriptions have automatic tenant join enabled, but you can enable or disable automatic tenant join by using the Windows PowerShell commands in Table 10. For more information about how to run these commands, see [How can I prevent students from joining my existing Office 365 tenant](https://support.office.com/en-us/article/Office-365-Education-Self-Sign-up-Technical-FAQ-7fb1b2f9-94c2-4cbb-b01e-a6eca34261d6?ui=en-US&rs=en-US&ad=US#BKMK_PreventJoins).
|
By default, all new Office 365 Education subscriptions have automatic tenant join enabled, but you can enable or disable automatic tenant join by using the Windows PowerShell commands in Table 10. For more information about how to run these commands, see [How can I prevent students from joining my existing Office 365 tenant](/microsoft-365/education/deploy/office-365-education-self-sign-up).
|
||||||
|
|
||||||
|Action |Windows PowerShell command|
|
|Action |Windows PowerShell command|
|
||||||
|-------|--------------------------|
|
|-------|--------------------------|
|
||||||
@ -714,7 +470,7 @@ To reduce your administrative effort, automatically assign Office 365 Education
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> By default, automatic licensing is enabled in Office 365 Education. If you want to use automatic licensing, then skip this section and go to the next section.
|
> By default, automatic licensing is enabled in Office 365 Education. If you want to use automatic licensing, then skip this section and go to the next section.
|
||||||
|
|
||||||
Although all new Office 365 Education subscriptions have automatic licensing enabled by default, you can enable or disable it for your Office 365 tenant by using the Windows PowerShell commands in Table 11. For more information about how to run these commands, see [How can I prevent students from joining my existing Office 365 tenant](https://support.office.com/en-us/article/Office-365-Education-Self-Sign-up-Technical-FAQ-7fb1b2f9-94c2-4cbb-b01e-a6eca34261d6?ui=en-US&rs=en-US&ad=US#BKMK_PreventJoins).
|
Although all new Office 365 Education subscriptions have automatic licensing enabled by default, you can enable or disable it for your Office 365 tenant by using the Windows PowerShell commands in Table 11. For more information about how to run these commands, see [How can I prevent students from joining my existing Office 365 tenant](/microsoft-365/education/deploy/office-365-education-self-sign-up).
|
||||||
|
|
||||||
|Action |Windows PowerShell command|
|
|Action |Windows PowerShell command|
|
||||||
|-------|--------------------------|
|
|-------|--------------------------|
|
||||||
@ -935,7 +691,7 @@ You can use the Microsoft 365 admin center to add individual Office 365 accounts
|
|||||||
|
|
||||||
The bulk-add process assigns the same Office 365 Education license plan to all users on the list. Therefore, you must create a separate list for each license plan you recorded in Table 9. Depending on the number of faculty members who need to use the classroom, you may want to add the faculty Office 365 accounts manually; however, use the bulk-add process to add student accounts.
|
The bulk-add process assigns the same Office 365 Education license plan to all users on the list. Therefore, you must create a separate list for each license plan you recorded in Table 9. Depending on the number of faculty members who need to use the classroom, you may want to add the faculty Office 365 accounts manually; however, use the bulk-add process to add student accounts.
|
||||||
|
|
||||||
For more information about how to bulk-add users to Office 365, see [Add several users at the same time to Office 365 - Admin help](https://support.office.com/en-us/article/Add-several-users-at-the-same-time-to-Office-365-Admin-Help-1f5767ed-e717-4f24-969c-6ea9d412ca88?ui=en-US&rs=en-US&ad=US).
|
For more information about how to bulk-add users to Office 365, see [Add several users at the same time to Microsoft 365](/microsoft-365/enterprise/add-several-users-at-the-same-time).
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> If you encountered errors during bulk add, resolve them before you continue the bulk-add process. You can view the log file to see which users caused the errors, and then modify the .csv file to correct the problems. Click **Back** to retry the verification process.
|
> If you encountered errors during bulk add, resolve them before you continue the bulk-add process. You can view the log file to see which users caused the errors, and then modify the .csv file to correct the problems. Click **Back** to retry the verification process.
|
||||||
@ -949,7 +705,7 @@ Assign SharePoint Online resource permissions to Office 365 security groups, not
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> If your institution has AD DS, don’t create security accounts in Office 365. Instead, create the security groups in AD DS, and then use Azure AD integration to synchronize the security groups with your Office 365 tenant.
|
> If your institution has AD DS, don’t create security accounts in Office 365. Instead, create the security groups in AD DS, and then use Azure AD integration to synchronize the security groups with your Office 365 tenant.
|
||||||
|
|
||||||
For information about creating security groups, see [Create an Office 365 Group in the admin center](https://support.office.com/en-us/article/Create-an-Office-365-Group-in-the-admin-center-74a1ef8b-3844-4d08-9980-9f8f7a36000f?ui=en-US&rs=en-001&ad=US).
|
For information about creating security groups, see [Create an Office 365 Group in the admin center](/microsoft-365/admin/create-groups/create-groups).
|
||||||
|
|
||||||
You can add and remove users from security groups at any time.
|
You can add and remove users from security groups at any time.
|
||||||
|
|
||||||
@ -966,7 +722,7 @@ You can create email distribution groups based on job role (such as teacher, adm
|
|||||||
> Office 365 can take some time to complete the Exchange Online creation process. You will have to wait until the creation process ends before you can perform the following steps.
|
> Office 365 can take some time to complete the Exchange Online creation process. You will have to wait until the creation process ends before you can perform the following steps.
|
||||||
|
|
||||||
|
|
||||||
For information about creating email distribution groups, see [Create an Office 365 Group in the admin center](https://support.office.com/en-us/article/Create-an-Office-365-Group-in-the-admin-center-74a1ef8b-3844-4d08-9980-9f8f7a36000f?ui=en-US&rs=en-001&ad=US).
|
For information about creating email distribution groups, see [Create a Microsoft 365 group in the admin center](/microsoft-365/admin/create-groups/create-groups).
|
||||||
|
|
||||||
#### Summary
|
#### Summary
|
||||||
|
|
||||||
@ -1083,63 +839,11 @@ This guide discusses thick image deployment. For information about thin image de
|
|||||||
### Select a method to initiate deployment
|
### Select a method to initiate deployment
|
||||||
The LTI deployment process is highly automated: it requires minimal information to deploy or upgrade Windows 10. The ZTI deployment process is fully automated, but you must manually initiate it. To do so, use the method listed in Table 15 that best meets the needs of your institution.
|
The LTI deployment process is highly automated: it requires minimal information to deploy or upgrade Windows 10. The ZTI deployment process is fully automated, but you must manually initiate it. To do so, use the method listed in Table 15 that best meets the needs of your institution.
|
||||||
|
|
||||||
<table>
|
|Method|Description and reason to select this method|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="25%" />
|
|Windows Deployment Services|This method:<li>Uses diskless booting to initiate LTI and ZTI deployments.<li>Works only with devices that support PXE boot.<li>Deploys Windows 10 over the network, which consumes more network bandwidth than deployment from local media.<li>Deploys images more slowly than when you use local media.<li>Requires that you deploy a Windows Deployment Services server.<br><br>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.|
|
||||||
<col width="75%" />
|
|Bootable media|This method:<li>Initiates LTI or ZTI deployment by booting from local media, including from USB drives, DVD, or CD.<li>Deploys Windows 10 over the network, which consumes more network bandwidth than deployment from local media.<li>Deploys images more slowly than when using local media.<li>Requires no additional infrastructure.<br> <br>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:<li>Initiates LTI or ZTI deployment by booting from a local USB hard disk.<li>Deploys Windows 10 from local media, which consumes less network bandwidth than over-the-network methods.<li>Deploys images more quickly than network-based methods do.<li>Requires a USB hard disk because of the deployment share’s storage requirements (up to 100 GB).<br> <br>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.
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Method</th>
|
|
||||||
<th align="left">Description and reason to select this method</th>
|
|
||||||
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Windows Deployment Services</td>
|
|
||||||
<td><p>This method:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Uses diskless booting to initiate LTI and ZTI deployments.</li>
|
|
||||||
<li>Works only with devices that support PXE boot.</li>
|
|
||||||
<li>Deploys Windows 10 over the network, which consumes more network bandwidth than deployment from local media.</li>
|
|
||||||
<li>Deploys images more slowly than when you use local media.</li>
|
|
||||||
<li>Requires that you deploy a Windows Deployment Services server.</li>
|
|
||||||
</ul>
|
|
||||||
<br/>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.
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Bootable media</td>
|
|
||||||
<td><p>This method:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Initiates LTI or ZTI deployment by booting from local media, including from USB drives, DVD, or CD.</li>
|
|
||||||
<li>Deploys Windows 10 over the network, which consumes more network bandwidth than deployment from local media.</li>
|
|
||||||
<li>Deploys images more slowly than when using local media.</li>
|
|
||||||
<li>Requires no additional infrastructure.</li>
|
|
||||||
</ul>
|
|
||||||
<br/>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.
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Deployment media</td>
|
|
||||||
<td><p>This method:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Initiates LTI or ZTI deployment by booting from a local USB hard disk.</li>
|
|
||||||
<li>Deploys Windows 10 from local media, which consumes less network bandwidth than over-the-network methods.</li>
|
|
||||||
<li>Deploys images more quickly than network-based methods do.</li>
|
|
||||||
<li>Requires a USB hard disk because of the deployment share’s storage requirements (up to 100 GB).</li>
|
|
||||||
</ul>
|
|
||||||
<br/>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.
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
*Table 15. Methods to initiate LTI and ZTI deployments*
|
*Table 15. Methods to initiate LTI and ZTI deployments*
|
||||||
|
|
||||||
@ -1154,91 +858,14 @@ Before you can deploy Windows 10 and your apps to devices, you need to prepare y
|
|||||||
|
|
||||||
The first step in preparing for Windows 10 deployment is to configure—that is, *populate*—the MDT deployment share. Table 16 lists the MDT deployment share configuration tasks that you must perform. Perform the tasks in the order represented in Table 16.
|
The first step in preparing for Windows 10 deployment is to configure—that is, *populate*—the MDT deployment share. Table 16 lists the MDT deployment share configuration tasks that you must perform. Perform the tasks in the order represented in Table 16.
|
||||||
|
|
||||||
<table>
|
|Task|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="25%" />
|
|1. Import operating systems|Import the operating systems that you selected in the [Select the operating systems](#select-the-operating-systems) section into the deployment share. For more information about how to import operating systems, see [Import Device Drivers into the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt#ImportDeviceDriversintotheDeploymentWorkbench)|
|
||||||
<col width="75%" />
|
|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.<br>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](/mem/configmgr/mdt/use-the-mdt#ImportDeviceDriversintotheDeploymentWorkbench)|
|
||||||
|
|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.<br>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:<li>For offline-licensed apps, download the .appx files from the Microsoft Store for Business.<li>For apps that are not offline licensed, obtain the .appx files from the app software vendor directly.<br> <br> 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.<br>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](#deploy-and-manage-apps-by-using-intune) and [Deploy and manage apps by using Microsoft Endpoint Configuration Manager](#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager). 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.<br>In addition, you must prepare your environment for sideloading Microsoft Store apps. For more information about how to:<li>Prepare your environment for sideloading, see [Try it out: sideload Microsoft Store apps](/previous-versions/windows/).<li>Create an MDT application, see [Create a New Application in the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt#CreateaNewApplicationintheDeploymentWorkbench).|
|
||||||
</colgroup>
|
|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.<br>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](/deployoffice/deploy-microsoft-365-apps-local-source).<br> If you have Intune, you can [Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune), 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.<br>This is the preferred method for deploying and managing Windows desktop apps.<br>**Note:** You can also deploy Windows desktop apps after you deploy Windows 10, as described in the [Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune) <br>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).|
|
||||||
<thead>
|
|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:<li>Deploy 64-bit Windows 10 Education to devices.<li>Deploy 32-bit Windows 10 Education to devices.<li>Upgrade existing devices to 64-bit Windows 10 Education.<li>Upgrade existing devices to 32-bit Windows 10 Education.<br> <br>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](/mem/configmgr/mdt/use-the-mdt#CreateaNewTaskSequenceintheDeploymentWorkbench).|
|
||||||
<tr class="header">
|
|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.<br>For more information about how to update a deployment share, see [Update a Deployment Share in the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt#UpdateaDeploymentShareintheDeploymentWorkbench).|
|
||||||
<th align="left">Task</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">1. Import operating systems</td>
|
|
||||||
<td>Import the operating systems that you selected in the <a href="#select-the-operating-systems" data-raw-source="[Select the operating systems](#select-the-operating-systems)">Select the operating systems</a> section into the deployment share. For more information about how to import operating systems, see <a href="/mem/configmgr/mdt/use-the-mdt#ImportanOperatingSystemintotheDeploymentWorkbench" data-raw-source="[Import an Operating System into the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt#ImportanOperatingSystemintotheDeploymentWorkbench)">Import an Operating System into the Deployment Workbench</a>.</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">2. Import device drivers</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
Import device drivers for each device in your institution. For more information about how to import device drivers, see <a href="/mem/configmgr/mdt/use-the-mdt#ImportDeviceDriversintotheDeploymentWorkbench" data-raw-source="[Import Device Drivers into the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt#ImportDeviceDriversintotheDeploymentWorkbench)">Import Device Drivers into the Deployment Workbench</a>.
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">3. Create MDT applications for Microsoft Store apps</td>
|
|
||||||
<td>Create an MDT application for each Microsoft Store app you want to deploy. You can deploy Microsoft Store apps by using <i>sideloading</i>, which allows you to use the <strong>Add-AppxPackage</strong> Windows PowerShell cmdlet to deploy the .appx files associated with the app (called <em>provisioned apps</em>). Use this method to deploy up to 24 apps to Windows 10.<br/><br/>
|
|
||||||
<p>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:</p>
|
|
||||||
<ul>
|
|
||||||
<li>For offline-licensed apps, download the .appx files from the Microsoft Store for Business.</li>
|
|
||||||
<li>For apps that are not offline licensed, obtain the .appx files from the app software vendor directly.</li>
|
|
||||||
</ul>
|
|
||||||
<br/>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.<br/><br/>
|
|
||||||
If you have Intune or Microsoft Endpoint Configuration Manager, you can deploy Microsoft Store apps after you deploy Windows 10, as described in the <a href="#deploy-and-manage-apps-by-using-intune" data-raw-source="[Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune)">Deploy and manage apps by using Intune</a> and <a href="#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager" data-raw-source="[Deploy and manage apps by using Microsoft Endpoint Configuration Manager](#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager)">Deploy and manage apps by using Microsoft Endpoint Configuration Manager</a> 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.<br/><br/>
|
|
||||||
In addition, you must prepare your environment for sideloading Microsoft Store apps. For more information about how to:<br/><br/>
|
|
||||||
<ul>
|
|
||||||
<li>Prepare your environment for sideloading, see <a href="/previous-versions/windows/" data-raw-source="[Try it out: sideload Microsoft Store apps](/previous-versions/windows/)">Try it out: sideload Microsoft Store apps</a>.</li>
|
|
||||||
<li>Create an MDT application, see <a href="/mem/configmgr/mdt/use-the-mdt#CreateaNewApplicationintheDeploymentWorkbench" data-raw-source="[Create a New Application in the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt#CreateaNewApplicationintheDeploymentWorkbench)">Create a New Application in the Deployment Workbench</a>.</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">4. Create MDT applications for Windows desktop apps</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
To help reduce the effort needed to deploy Microsoft Office 2016 desktop apps, use the Office Deployment Tool, as described in <a href="/deployoffice/deploy-microsoft-365-apps-local-source" data-raw-source="[Deploy Click-to-Run for Office 365 products by using the Office Deployment Tool](/deployoffice/deploy-microsoft-365-apps-local-source)">Deploy Click-to-Run for Office 365 products by using the Office Deployment Tool</a>.<br/><br/>
|
|
||||||
If you have Intune, you can deploy Windows desktop apps after you deploy Windows 10, as described in the <a href="#deploy-and-manage-apps-by-using-intune" data-raw-source="[Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune)">Deploy and manage apps by using Intune</a> 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.
|
|
||||||
<br/><br/>
|
|
||||||
<strong>Note</strong> You can also deploy Windows desktop apps after you deploy Windows 10, as described in the <a href="#deploy-and-manage-apps-by-using-intune" data-raw-source="[Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune)">Deploy and manage apps by using Intune</a> 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).
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">5. Create task sequences</td>
|
|
||||||
<td><p>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:</p>
|
|
||||||
<ul>
|
|
||||||
<li>Deploy 64-bit Windows 10 Education to devices.</li>
|
|
||||||
<li>Deploy 32-bit Windows 10 Education to devices.</li>
|
|
||||||
<li>Upgrade existing devices to 64-bit Windows 10 Education.</li>
|
|
||||||
<li>Upgrade existing devices to 32-bit Windows 10 Education.</li>
|
|
||||||
</ul>
|
|
||||||
<br/>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 <a href="/mem/configmgr/mdt/use-the-mdt#CreateaNewTaskSequenceintheDeploymentWorkbench" data-raw-source="[Create a New Task Sequence in the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt#CreateaNewTaskSequenceintheDeploymentWorkbench)">Create a New Task Sequence in the Deployment Workbench</a>.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">6. Update the deployment share</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
For more information about how to update a deployment share, see <a href="/mem/configmgr/mdt/use-the-mdt#UpdateaDeploymentShareintheDeploymentWorkbench" data-raw-source="[Update a Deployment Share in the Deployment Workbench](/mem/configmgr/mdt/use-the-mdt#UpdateaDeploymentShareintheDeploymentWorkbench)">Update a Deployment Share in the Deployment Workbench</a>.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
*Table 16. Tasks to configure the MDT deployment share*
|
*Table 16. Tasks to configure the MDT deployment share*
|
||||||
|
|
||||||
@ -1430,116 +1057,20 @@ Microsoft has several recommended settings for educational institutions. Table 1
|
|||||||
|
|
||||||
Use the information in Table 17 to help you determine whether you need to configure the setting and which method you will use to do so. At the end, you will have a list of settings that you want to apply to the Windows 10 devices and know which management method you will use to configure the settings.
|
Use the information in Table 17 to help you determine whether you need to configure the setting and which method you will use to do so. At the end, you will have a list of settings that you want to apply to the Windows 10 devices and know which management method you will use to configure the settings.
|
||||||
|
|
||||||
<table>
|
|Recommendation|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="75%" />
|
|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.<br>**Note** Personal devices typically use Microsoft accounts. Faculty and students can associate their Microsoft account with their Azure AD account on these devices. <br>**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.<br>****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.|
|
||||||
<col width="25%" />
|
|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.<br>**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. <br>**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.<br> **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](/previous-versions/windows/it-pro/windows-server-essentials-sbs/cc747484(v=ws.10)). 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](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj852165(v=ws.11)).<br> **Intune**. Not available.|
|
||||||
</colgroup>
|
|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.<br>**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?<br>**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.|
|
||||||
<thead>
|
|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.<br>**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.<br>**Intune**. Not available.|
|
||||||
<tr class="header">
|
|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.<br>**Group policy**. Not available.<br>**Intune**. To enable or disable the camera, use the Allow camera policy setting in the Hardware section of a Windows 10 General Configuration policy.|
|
||||||
<th align="left">Recommendation</th>
|
|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.<br>**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](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee791894(v=ws.10)) and [Create Your AppLocker Policies](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/ee791899(v=ws.11)).<br>**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.|
|
||||||
<th align="left">Description</th>
|
|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.<br>**Group policy**. Not available.<br>**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.<br>**Group policy**. To enable or disable location services, use the Turn off location group policy setting in User Configuration\Windows Components\Location and Sensors.<br>**Intune**. To enable or disable location services, use the Allow geolocation policy setting in the Hardware section of a Windows 10 General Configuration policy.|
|
||||||
</tr>
|
|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.<br>**Group policy**. To configure the wallpaper, use the Desktop WallPaper setting in User Configuration\Administrative Templates\Desktop\Desktop.<br>**Intune**. Not available.|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Use of Microsoft accounts</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
|
|
||||||
**Note** Personal devices typically use Microsoft accounts. Faculty and students can associate their Microsoft account with their Azure AD account on these devices.<br/><br/>
|
|
||||||
**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.<br/><br/>
|
|
||||||
**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.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Restrict the local administrator accounts on the devices</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> Create a <strong>Local Group</strong> 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.<br/><br/>
|
|
||||||
<strong>Intune.</strong> Not available.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Manage the built-in administrator account created during device deployment</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> To rename the built-in Administrator account, use the <strong>Accounts: Rename administrator account</strong> Group Policy setting. For more information about how to rename the built-in Administrator account, see <a href="/previous-versions/windows/it-pro/windows-server-essentials-sbs/cc747484(v=ws.10)" data-raw-source="[To rename the Administrator account using the Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-essentials-sbs/cc747484(v=ws.10))">To rename the Administrator account using the Group Policy Management Console</a>. You specify the new name for the Administrator account. To disable the built-in Administrator account, use the <strong>Accounts: Administrator account status</strong> Group Policy setting. For more information about how to disable the built-in Administrator account, see <a href="/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj852165(v=ws.11)" data-raw-source="[Accounts: Administrator account status](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj852165(v=ws.11))">Accounts: Administrator account status</a>.<br/><br/>
|
|
||||||
<strong>Intune.</strong> Not available.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Control Microsoft Store access</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> To disable the Microsoft Store app, use the <strong>Turn off the Store Application</strong> group policy setting. To prevent Microsoft Store apps from receiving updates, use the <strong>Turn off Automatic Download and Install of updates</strong> Group Policy setting. For more information about configuring these settings, see <a href="/previous-versions/windows/it-pro/windows-8.1-and-8/hh832040(v=ws.11)#BKMK_UseGP" data-raw-source="[Can I use Group Policy to control the Microsoft Store in my enterprise environment?](/previous-versions/windows/it-pro/windows-8.1-and-8/hh832040(v=ws.11)#BKMK_UseGP)">Can I use Group Policy to control the Microsoft Store in my enterprise environment?</a>.<br/><br/>
|
|
||||||
<strong>Intune.</strong> To enable or disable Microsoft Store access, use the <strong>Allow application store</strong> policy setting in the <strong>Apps</strong> section of a <strong>Windows 10 General Configuration policy</strong>.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Use of Remote Desktop connections to devices</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> To enable or disable Remote Desktop connections to devices, use the <strong>Allow Users to connect remotely using Remote Desktop</strong> setting in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections.<br/><br/>
|
|
||||||
<strong>Intune.</strong> Not available.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Use of camera</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> Not available.<br/><br/>
|
|
||||||
<strong>Intune.</strong> To enable or disable the camera, use the <strong>Allow camera</strong> policy setting in the <strong>Hardware</strong> section of a <strong>Windows 10 General Configuration</strong> policy.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Use of audio recording</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> To disable the Sound Recorder app, use the <strong>Do not allow Sound Recorder to run</strong> Group Policy setting. You can disable other audio recording apps by using AppLocker policies. To create AppLocker policies, use the information in <a href="/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee791894(v=ws.10)" data-raw-source="[Editing an AppLocker Policy](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee791894(v=ws.10))">Editing an AppLocker Policy</a> and <a href="/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/ee791899(v=ws.11)" data-raw-source="[Create Your AppLocker Policies](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/ee791899(v=ws.11))">Create Your AppLocker Policies</a>.<br/><br/>
|
|
||||||
<strong>Intune.</strong> To enable or disable audio recording, use the <strong>Allow voice recording</strong> policy setting in the <strong>Features</strong> section of a <strong>Windows 10 General Configuration</strong> policy.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Use of screen capture</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> Not available.<br/><br/>
|
|
||||||
<strong>Intune.</strong> To enable or disable screen capture, use the <strong>Allow screen capture</strong> policy setting in the <strong>System</strong> section of a <strong>Windows 10 General Configuration</strong> policy.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Use of location services</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> To enable or disable location services, use the <strong>Turn off location</strong> group policy setting in User Configuration\Windows Components\Location and Sensors.<br/><br/>
|
|
||||||
<strong>Intune.</strong> To enable or disable location services, use the <strong>Allow geolocation</strong> policy setting in the <strong>Hardware</strong> section of a <strong>Windows 10 General Configuration</strong> policy.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td valign="top">Changing wallpaper</td>
|
|
||||||
<td>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.<br/><br/>
|
|
||||||
<strong>Group Policy.</strong> To configure the wallpaper, use the <strong>Desktop WallPaper</strong> setting in User Configuration\Administrative Templates\Desktop\Desktop.<br/><br/>
|
|
||||||
<strong>Intune.</strong> Not available.
|
|
||||||
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
<br/>
|
<br/>
|
||||||
<em>Table 17. Recommended settings for educational institutions</em>
|
<em>Table 17. Recommended settings for educational institutions</em>
|
||||||
|
|
||||||
@ -1719,205 +1250,23 @@ After the initial deployment, you need to perform certain tasks to maintain the
|
|||||||
|
|
||||||
Table 19 lists the school and individual classroom maintenance tasks, the resources for performing the tasks, and the schedule (or frequency) on which you should perform the tasks.
|
Table 19 lists the school and individual classroom maintenance tasks, the resources for performing the tasks, and the schedule (or frequency) on which you should perform the tasks.
|
||||||
|
|
||||||
<table>
|
|Task and resources|Monthly|New semester or academic year|As required|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="10%" />
|
|Verify that Windows Update is active and current with operating system and software updates.<br>For more information about completing this task when you have:<li>Intune, see [Keep Windows PCs up to date with software updates in Microsoft Intune](/intune/deploy-use/keep-windows-pcs-up-to-date-with-software-updates-in-microsoft-intune)<li>Group Policy, see [Windows Update for Business](/windows/deployment/update/waas-manage-updates-wufb).<li>WSUS, see [Windows Server Update Services](/windows/deployment/deploy-whats-new).<br>Neither Intune, Group Policy, nor WSUS, see “Install, upgrade, & activate” in Windows 10 help.|✔️|✔️|✔️|
|
||||||
<col width="10%" />
|
|Verify that Windows Defender is active and current with malware Security intelligence.<br>For more information about completing this task, see [Turn Windows Defender on or off](https://support.microsoft.com/instantanswers/742778f2-6aad-4a8d-8f5d-db59cebc4f24/how-to-protect-your-windows-10-pc#v1h=tab02)and [Updating Windows Defender](https://support.microsoft.com/instantanswers/742778f2-6aad-4a8d-8f5d-db59cebc4f24/how-to-protect-your-windows-10-pc#v1h=tab03).|✔️|✔️|✔️|
|
||||||
<col width="10%" />
|
|Verify that Windows Defender has run a scan in the past week and that no viruses or malware were found.<br>For more information about completing this task, see the “How do I find and remove a virus?” topic in [Protect my PC from viruses](https://support.microsoft.com/help/17228/windows-protect-my-pc-from-viruses).|✔️|✔️|✔️|
|
||||||
<col width="70%" />
|
|Download and approve updates for Windows 10, apps, device driver, and other software.<br>For more information, see:<li>[Manage updates by using Intune](#manage-updates-by-using-intune)<li>[Manage updates by using Microsoft Endpoint Configuration Manager](#manage-updates-by-using-microsoft-endpoint-configuration-manager)|✔️|✔️|✔️|
|
||||||
</colgroup>
|
|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).<br>For more information about Windows 10 servicing options for updates and upgrades, see [Windows 10 servicing options](/windows/deployment/update/).||✔️|✔️|
|
||||||
<thead>
|
|Refresh the operating system and apps on devices.<br>For more information about completing this task, see the following resources:<li>[Prepare for deployment](#prepare-for-deployment)<li>[Capture the reference image](#capture-the-reference-image)<li>[Deploy Windows 10 to devices](#deploy-windows-10-to-devices)||✔️|✔️|
|
||||||
<tr class="header">
|
|Install any new Windows desktop apps, or update any Windows desktop apps used in the curriculum.<br>For more information, see:<li>[Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune)<li>[Deploy and manage apps by using Microsoft Endpoint Configuration Manager](#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager)||✔️|✔️|
|
||||||
<th align="left">Task and resources</th>
|
|Install new or update existing Microsoft Store apps used in the curriculum.<br>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.<br>You can also deploy Microsoft Store apps directly to devices by using Intune, Microsoft Endpoint Configuration Manager, or both in a hybrid configuration. <br>For more information, see:<li>[Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune)<li>[Deploy and manage apps by using Microsoft Endpoint Configuration Manager](#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager)||✔️|✔️|
|
||||||
<th align="left">Monthly</th>
|
|Remove unnecessary user accounts (and corresponding licenses) from AD DS and Office 365 (if you have an on-premises AD DS infrastructure).<br>For more information about how to:<li>Remove unnecessary user accounts, see [Active Directory Administrative Center](/windows-server/identity/ad-ds/get-started/adac/active-directory-administrative-center) <li>Remove licenses, see [Add users and assign licenses](/microsoft-365/admin/add-users/add-users)||✔️|✔️|
|
||||||
<th align="left">New semester or academic year</th>
|
|Add new accounts (and corresponding licenses) to AD DS (if you have an on-premises AD DS infrastructure).<br>For more information about how to:<li>Add user accounts, see [Bulk-import user and group accounts into AD DS](#bulk-import-user-and-group-accounts-into-ad-ds)<li>Assign licenses, see [Add users and assign licenses](/microsoft-365/admin/add-users/add-users)||✔️|✔️|
|
||||||
<th align="left">As required</th>
|
|Remove unnecessary user accounts (and corresponding licenses) from Office 365 (if you do not have an on-premises AD DS infrastructure).<br>For more information about how to:<li>Remove unnecessary user accounts, see [Delete or restore users](/microsoft-365/admin/add-users/delete-a-user)<li> Remove licenses, [Assign or remove licenses for Microsoft 365](/microsoft-365/admin/add-users/add-users).||✔️|✔️|
|
||||||
</tr>
|
|Add new accounts (and corresponding licenses) to Office 365 (if you don’t have an on-premises AD DS infrastructure).<br>For more information about how to:<li>Add user accounts, see [Add users to Microsoft 365](/microsoft-365/admin/add-users/add-users) and [Add users individually or in bulk to Office 365](https://www.youtube.com/watch?v=zDs3VltTJps).<li>Assign licenses, see [Add users to Microsoft 365](/microsoft-365/admin/add-users/add-users).||✔️|✔️|
|
||||||
</thead>
|
|Create or modify security groups, and manage group membership in Office 365.<br>For more information about how to:<li>Create or modify security groups, see [Create a Microsoft 365 group](/microsoft-365/admin/create-groups/create-groups)<li>Manage group membership, see [Manage Group membership](/microsoft-365/admin/create-groups/add-or-remove-members-from-groups).||✔️|✔️|
|
||||||
<tbody>
|
|Create or modify Exchange Online or Microsoft Exchange Server distribution lists in Office 365.<br>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](/exchange/recipients-in-exchange-online/manage-distribution-groups/manage-distribution-groups) and [Create, edit, or delete a security group](/microsoft-365/admin/email/create-edit-or-delete-a-security-group).||✔️|✔️|
|
||||||
<tr>
|
|Install new student devices.<br> Follow the same steps you followed in the[Deploy Windows 10 to devices](#deploy-windows-10-to-devices) section.|||✔️|
|
||||||
<td>Verify that Windows Update is active and current with operating system and software updates.<br/><br/>
|
|
||||||
For more information about completing this task when you have:
|
|
||||||
<ul>
|
|
||||||
<li>Intune, see <a href="/intune/deploy-use/keep-windows-pcs-up-to-date-with-software-updates-in-microsoft-intune" data-raw-source="[Keep Windows PCs up to date with software updates in Microsoft Intune](/intune/deploy-use/keep-windows-pcs-up-to-date-with-software-updates-in-microsoft-intune)">Keep Windows PCs up to date with software updates in Microsoft Intune</a>.</li>
|
|
||||||
<li>Group Policy, see <a href="/windows/deployment/update/waas-manage-updates-wufb" data-raw-source="[Windows Update for Business](/windows/deployment/update/waas-manage-updates-wufb)">Windows Update for Business</a>.</li>
|
|
||||||
<li>WSUS, see <a href="/windows/deployment/deploy-whats-new" data-raw-source="[Windows Server Update Services](/windows/deployment/deploy-whats-new)">Windows Server Update Services</a>.</li>
|
|
||||||
<li>Neither Intune, Group Policy, nor WSUS, see “Install, upgrade, & activate” in <a href="https://support.microsoft.com/products/windows?os=windows-10" data-raw-source="[Windows 10 help](https://support.microsoft.com/products/windows?os=windows-10)">Windows 10 help</a>.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Verify that Windows Defender is active and current with malware Security intelligence.<br/><br/>
|
|
||||||
For more information about completing this task, see <a href="https://support.microsoft.com/instantanswers/742778f2-6aad-4a8d-8f5d-db59cebc4f24/how-to-protect-your-windows-10-pc#v1h=tab02" data-raw-source="[Turn Windows Defender on or off](https://support.microsoft.com/instantanswers/742778f2-6aad-4a8d-8f5d-db59cebc4f24/how-to-protect-your-windows-10-pc#v1h=tab02)">Turn Windows Defender on or off</a> and <a href="https://support.microsoft.com/instantanswers/742778f2-6aad-4a8d-8f5d-db59cebc4f24/how-to-protect-your-windows-10-pc#v1h=tab03" data-raw-source="[Updating Windows Defender](https://support.microsoft.com/instantanswers/742778f2-6aad-4a8d-8f5d-db59cebc4f24/how-to-protect-your-windows-10-pc#v1h=tab03)">Updating Windows Defender</a>.
|
|
||||||
</td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Verify that Windows Defender has run a scan in the past week and that no viruses or malware were found.<br/><br/>
|
|
||||||
For more information about completing this task, see the “How do I find and remove a virus?” topic in <a href="https://support.microsoft.com/help/17228/windows-protect-my-pc-from-viruses" data-raw-source="[Protect my PC from viruses](https://support.microsoft.com/help/17228/windows-protect-my-pc-from-viruses)">Protect my PC from viruses</a>.
|
|
||||||
</td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Download and approve updates for Windows 10, apps, device driver, and other software.<br/><br/>
|
|
||||||
For more information, see:
|
|
||||||
<ul>
|
|
||||||
<li><a href="#manage-updates-by-using-intune" data-raw-source="[Manage updates by using Intune](#manage-updates-by-using-intune)">Manage updates by using Intune</a></li>
|
|
||||||
<li><a href="#manage-updates-by-using-microsoft-endpoint-configuration-manager" data-raw-source="[Manage updates by using Microsoft Endpoint Configuration Manager](#manage-updates-by-using-microsoft-endpoint-configuration-manager)">Manage updates by using Microsoft Endpoint Configuration Manager</a></li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>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).<br/><br/>
|
|
||||||
For more information about Windows 10 servicing options for updates and upgrades, see <a href="/windows/deployment/update/" data-raw-source="[Windows 10 servicing options](/windows/deployment/update/)">Windows 10 servicing options</a>.
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Refresh the operating system and apps on devices.<br/><br/>
|
|
||||||
For more information about completing this task, see the following resources:
|
|
||||||
<ul>
|
|
||||||
<li><a href="#prepare-for-deployment" data-raw-source="[Prepare for deployment](#prepare-for-deployment)">Prepare for deployment</a></li>
|
|
||||||
<li><a href="#capture-the-reference-image" data-raw-source="[Capture the reference image](#capture-the-reference-image)">Capture the reference image</a></li>
|
|
||||||
<li><a href="#deploy-windows-10-to-devices" data-raw-source="[Deploy Windows 10 to devices](#deploy-windows-10-to-devices)">Deploy Windows 10 to devices</a></li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Install any new Windows desktop apps, or update any Windows desktop apps used in the curriculum.<br/><br/>
|
|
||||||
For more information, see:
|
|
||||||
<ul>
|
|
||||||
<li><a href="#deploy-and-manage-apps-by-using-intune" data-raw-source="[Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune)">Deploy and manage apps by using Intune</a></li>
|
|
||||||
<li><a href="#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager" data-raw-source="[Deploy and manage apps by using Microsoft Endpoint Configuration Manager](#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager)">Deploy and manage apps by using Microsoft Endpoint Configuration Manager</a></li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Install new or update existing Microsoft Store apps used in the curriculum.<br/><br/>
|
|
||||||
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.<br/><br/>
|
|
||||||
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:
|
|
||||||
<ul>
|
|
||||||
<li><a href="#deploy-and-manage-apps-by-using-intune" data-raw-source="[Deploy and manage apps by using Intune](#deploy-and-manage-apps-by-using-intune)">Deploy and manage apps by using Intune</a></li>
|
|
||||||
<li><a href="#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager" data-raw-source="[Deploy and manage apps by using Microsoft Endpoint Configuration Manager](#deploy-and-manage-apps-by-using-microsoft-endpoint-configuration-manager)">Deploy and manage apps by using Microsoft Endpoint Configuration Manager</a></li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Remove unnecessary user accounts (and corresponding licenses) from AD DS and Office 365 (if you have an on-premises AD DS infrastructure).<br/><br/>
|
|
||||||
For more information about how to:
|
|
||||||
<ul>
|
|
||||||
<li>Remove unnecessary user accounts, see <a href="/windows-server/identity/ad-ds/get-started/adac/active-directory-administrative-center" data-raw-source="[Active Directory Administrative Center](/windows-server/identity/ad-ds/get-started/adac/active-directory-administrative-center)">Active Directory Administrative Center</a>.</li>
|
|
||||||
<li>Remove licenses, see <a href="https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc?ui=en-US&rs=en-US&ad=US" data-raw-source="[Assign or remove licenses for Office 365 for business](https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc?ui=en-US&rs=en-US&ad=US)">Assign or remove licenses for Office 365 for business</a>.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Add new accounts (and corresponding licenses) to AD DS (if you have an on-premises AD DS infrastructure).<br/><br/>
|
|
||||||
For more information about how to:
|
|
||||||
<ul>
|
|
||||||
<li>Add user accounts, see <a href="#bulk-import-user-and-group-accounts-into-ad-ds" data-raw-source="[Bulk-import user and group accounts into AD DS](#bulk-import-user-and-group-accounts-into-ad-ds)">Bulk-import user and group accounts into AD DS</a>.</li>
|
|
||||||
<li>Assign licenses, see <a href="https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc?ui=en-US&rs=en-US&ad=US" data-raw-source="[Assign or remove licenses for Office 365 for business](https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc?ui=en-US&rs=en-US&ad=US)">Assign or remove licenses for Office 365 for business</a>.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Remove unnecessary user accounts (and corresponding licenses) from Office 365 (if you do not have an on-premises AD DS infrastructure).<br/><br/>
|
|
||||||
For more information about how to:
|
|
||||||
<ul>
|
|
||||||
<li>Remove unnecessary user accounts, see <a href="https://support.office.com/en-us/article/Delete-or-restore-users-d5155593-3bac-4d8d-9d8b-f4513a81479e" data-raw-source="[Delete or restore users](https://support.office.com/en-us/article/Delete-or-restore-users-d5155593-3bac-4d8d-9d8b-f4513a81479e)">Delete or restore users</a>.</li>
|
|
||||||
<li>Remove licenses, see <a href="https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc?ui=en-US&rs=en-US&ad=US" data-raw-source="[Assign or remove licenses for Office 365 for business](https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc?ui=en-US&rs=en-US&ad=US)">Assign or remove licenses for Office 365 for business</a>.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Add new accounts (and corresponding licenses) to Office 365 (if you don’t have an on-premises AD DS infrastructure).<br/><br/>
|
|
||||||
For more information about how to:
|
|
||||||
<ul>
|
|
||||||
<li>Add user accounts, see <a href="https://support.office.com/en-us/article/Add-users-to-Office-365-for-business-435ccec3-09dd-4587-9ebd-2f3cad6bc2bc" data-raw-source="[Add users to Office 365 for business](https://support.office.com/en-us/article/Add-users-to-Office-365-for-business-435ccec3-09dd-4587-9ebd-2f3cad6bc2bc)">Add users to Office 365 for business</a> and <a href="https://www.youtube.com/watch?v=zDs3VltTJps" data-raw-source="[Add users individually or in bulk to Office 365](https://www.youtube.com/watch?v=zDs3VltTJps)">Add users individually or in bulk to Office 365</a>.</li>
|
|
||||||
<li>Assign licenses, see <a href="https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc?ui=en-US&rs=en-US&ad=US" data-raw-source="[Assign or remove licenses for Office 365 for business](https://support.office.com/en-us/article/Assign-or-remove-licenses-for-Office-365-for-business-997596b5-4173-4627-b915-36abac6786dc?ui=en-US&rs=en-US&ad=US)">Assign or remove licenses for Office 365 for business</a>.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Create or modify security groups, and manage group membership in Office 365.<br/><br/>
|
|
||||||
For more information about how to:
|
|
||||||
<ul>
|
|
||||||
<li>Create or modify security groups, see <a href="https://support.office.com/en-us/article/Create-an-Office-365-Group-in-the-admin-center-74a1ef8b-3844-4d08-9980-9f8f7a36000f?ui=en-US&rs=en-001&ad=US" data-raw-source="[Create an Office 365 Group in the admin center](https://support.office.com/en-us/article/Create-an-Office-365-Group-in-the-admin-center-74a1ef8b-3844-4d08-9980-9f8f7a36000f?ui=en-US&rs=en-001&ad=US)">Create an Office 365 Group in the admin center</a>.</li>
|
|
||||||
<li>Manage group membership, see <a href="https://support.office.com/en-us/article/Manage-Group-membership-in-the-Office-365-admin-center-e186d224-a324-4afa-8300-0e4fc0c3000a" data-raw-source="[Manage Group membership in the admin center](https://support.office.com/en-us/article/Manage-Group-membership-in-the-Office-365-admin-center-e186d224-a324-4afa-8300-0e4fc0c3000a)">Manage Group membership in the admin center</a>.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Create or modify Exchange Online or Microsoft Exchange Server distribution lists in Office 365.<br/><br/>
|
|
||||||
For more information about how to create or modify Exchange Online or Exchange Server distribution lists in Office 365, see <a href="/exchange/recipients-in-exchange-online/manage-distribution-groups/manage-distribution-groups" data-raw-source="[Create and manage distribution groups](/exchange/recipients-in-exchange-online/manage-distribution-groups/manage-distribution-groups)">Create and manage distribution groups</a> and <a href="https://support.office.com/en-us/article/Create-edit-or-delete-a-security-group-55C96B32-E086-4C9E-948B-A018B44510CB" data-raw-source="[Create, edit, or delete a security group](https://support.office.com/en-us/article/Create-edit-or-delete-a-security-group-55C96B32-E086-4C9E-948B-A018B44510CB)">Create, edit, or delete a security group</a>.
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
<tr>
|
|
||||||
<td>Install new student devices.<br/><br/>
|
|
||||||
Follow the same steps you followed in the <a href="#deploy-windows-10-to-devices" data-raw-source="[Deploy Windows 10 to devices](#deploy-windows-10-to-devices)">Deploy Windows 10 to devices</a> section.
|
|
||||||
</td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td>x</td>
|
|
||||||
</tr>
|
|
||||||
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
<br/>
|
|
||||||
|
|
||||||
*Table 19. School and individual classroom maintenance tasks, with resources and the schedule for performing them*
|
*Table 19. School and individual classroom maintenance tasks, with resources and the schedule for performing them*
|
||||||
|
|
||||||
|
|||||||
@ -164,184 +164,164 @@ For more information, see [Manage settings in the Store for Business](manage-set
|
|||||||
Store for Business and Education is currently available in these markets.
|
Store for Business and Education is currently available in these markets.
|
||||||
|
|
||||||
### Support for free and paid products
|
### Support for free and paid products
|
||||||
<table>
|
|
||||||
<tr>
|
- Afghanistan
|
||||||
<th align="center" colspan="4">Supports all free and paid products</th>
|
- Algeria
|
||||||
</tr>
|
- Andorra
|
||||||
<tr align="left">
|
- Angola
|
||||||
<td>
|
- Anguilla
|
||||||
<ul>
|
- Antigua and Barbuda
|
||||||
<li>Afghanistan</li>
|
- Argentina
|
||||||
<li>Algeria</li>
|
- Australia
|
||||||
<li>Andorra</li>
|
- Austria
|
||||||
<li>Angola</li>
|
- Bahamas
|
||||||
<li>Anguilla</li>
|
- Bahrain
|
||||||
<li>Antigua and Barbuda</li>
|
- Bangladesh
|
||||||
<li>Argentina</li>
|
- Barbados
|
||||||
<li>Australia</li>
|
- Belgium
|
||||||
<li>Austria</li>
|
- Belize
|
||||||
<li>Bahamas</li>
|
- Bermuda
|
||||||
<li>Bahrain</li>
|
- Benin
|
||||||
<li>Bangladesh</li>
|
- Bhutan
|
||||||
<li>Barbados</li>
|
- Bolivia
|
||||||
<li>Belgium</li>
|
- Bonaire
|
||||||
<li>Belize</li>
|
- Botswana
|
||||||
<li>Bermuda</li>
|
- Brunei Darussalam
|
||||||
<li>Benin</li>
|
- Bulgaria
|
||||||
<li>Bhutan</li>
|
- Burundi
|
||||||
<li>Bolivia</li>
|
- Cambodia
|
||||||
<li>Bonaire</li>
|
- Cameroon
|
||||||
<li>Botswana</li>
|
- Canada
|
||||||
<li>Brunei Darussalam</li>
|
- Cayman Islands
|
||||||
<li>Bulgaria</li>
|
- Chile
|
||||||
<li>Burundi</li>
|
- Colombia
|
||||||
<li>Cambodia</li>
|
- Comoros
|
||||||
<li>Cameroon</li>
|
- Costa Rica
|
||||||
<li>Canada</li>
|
- Côte D'ivoire
|
||||||
<li>Cayman Islands</li>
|
- Croatia
|
||||||
<li>Chile</li>
|
- Curçao
|
||||||
<li>Colombia</li>
|
- Cyprus
|
||||||
<li>Comoros</li>
|
- Czech Republic
|
||||||
<li>Costa Rica</li>
|
- Denmark
|
||||||
<li>Côte D'ivoire</li>
|
- Dominican Republic
|
||||||
<li>Croatia</li>
|
- Ecuador
|
||||||
<li>Curçao</li>
|
- Egypt
|
||||||
<li>Cyprus</li>
|
- El Salvador
|
||||||
<li>Czech Republic</li>
|
- Estonia
|
||||||
<li>Denmark</li>
|
- Ethiopia
|
||||||
<li>Dominican Republic</li>
|
- Faroe Islands
|
||||||
<li>Ecuador</li>
|
- Fiji
|
||||||
</ul>
|
- Finland
|
||||||
</td>
|
- France
|
||||||
<td>
|
- French Guiana
|
||||||
<ul>
|
- French Polynesia
|
||||||
<li>Egypt</li>
|
- Germany
|
||||||
<li>El Salvador</li>
|
- Ghana
|
||||||
<li>Estonia</li>
|
- Greece
|
||||||
<li>Ethiopia</li>
|
- Greenland
|
||||||
<li>Faroe Islands</li>
|
- Guadeloupe
|
||||||
<li>Fiji</li>
|
- Guatemala
|
||||||
<li>Finland</li>
|
- Honduras
|
||||||
<li>France</li>
|
- Hong Kong SAR
|
||||||
<li>French Guiana</li>
|
- Hungary
|
||||||
<li>French Polynesia</li>
|
- Iceland
|
||||||
<li>Germany</li>
|
- Indonesia
|
||||||
<li>Ghana</li>
|
- Iraq
|
||||||
<li>Greece</li>
|
- Ireland
|
||||||
<li>Greenland</li>
|
- Israel
|
||||||
<li>Guadeloupe</li>
|
- Italy
|
||||||
<li>Guatemala</li>
|
- Jamaica
|
||||||
<li>Honduras</li>
|
- Japan
|
||||||
<li>Hong Kong SAR</li>
|
- Jersey
|
||||||
<li>Hungary</li>
|
- Jordan
|
||||||
<li>Iceland</li>
|
- Kenya
|
||||||
<li>Indonesia</li>
|
- Kuwait
|
||||||
<li>Iraq</li>
|
- Laos
|
||||||
<li>Ireland</li>
|
- Latvia
|
||||||
<li>Israel</li>
|
- Lebanon
|
||||||
<li>Italy</li>
|
- Libya
|
||||||
<li>Jamaica</li>
|
- Liechtenstein
|
||||||
<li>Japan</li>
|
- Lithuania
|
||||||
<li>Jersey</li>
|
- Luxembourg
|
||||||
<li>Jordan</li>
|
- Macedonia
|
||||||
<li>Kenya</li>
|
- Madagascar
|
||||||
<li>Kuwait</li>
|
- Malawi
|
||||||
<li>Laos</li>
|
- Malaysia
|
||||||
<li>Latvia</li>
|
- Maldives
|
||||||
<li>Lebanon</li>
|
- Mali
|
||||||
<li>Libya</li>
|
- Malta
|
||||||
<li>Liechtenstein</li>
|
- Marshall Islands
|
||||||
<li>Lithuania</li>
|
- Martinique
|
||||||
<li>Luxembourg</li>
|
- Mauritius
|
||||||
<li>Macedonia</li>
|
- Mayotte
|
||||||
<li>Madagascar</li>
|
- Mexico
|
||||||
</ul>
|
- Mongolia
|
||||||
</td>
|
- Montenegro
|
||||||
<td>
|
- Morocco
|
||||||
<ul>
|
- Mozambique
|
||||||
<li>Malawi</li>
|
- Myanamar
|
||||||
<li>Malaysia</li>
|
- Namibia
|
||||||
<li>Maldives</li>
|
- Nepal
|
||||||
<li>Mali</li>
|
- Netherlands
|
||||||
<li>Malta</li>
|
- New Caledonia
|
||||||
<li>Marshall Islands</li>
|
- New Zealand
|
||||||
<li>Martinique</li>
|
- Nicaragua
|
||||||
<li>Mauritius</li>
|
- Nigeria
|
||||||
<li>Mayotte</li>
|
- Norway
|
||||||
<li>Mexico</li>
|
- Oman
|
||||||
<li>Mongolia</li>
|
- Pakistan
|
||||||
<li>Montenegro</li>
|
- Palestinian Authority
|
||||||
<li>Morocco</li>
|
- Panama
|
||||||
<li>Mozambique</li>
|
- Papua New Guinea
|
||||||
<li>Myanamar</li>
|
- Paraguay
|
||||||
<li>Namibia</li>
|
- Peru
|
||||||
<li>Nepal</li>
|
- Philippines
|
||||||
<li>Netherlands</li>
|
- Poland
|
||||||
<li>New Caledonia</li>
|
- Portugal
|
||||||
<li>New Zealand</li>
|
- Qatar
|
||||||
<li>Nicaragua</li>
|
- Republic of Cabo Verde
|
||||||
<li>Nigeria</li>
|
- Reunion
|
||||||
<li>Norway</li>
|
- Romania
|
||||||
<li>Oman</li>
|
- Rwanda
|
||||||
<li>Pakistan</li>
|
- Saint Kitts and Nevis
|
||||||
<li>Palestinian Authority</li>
|
- Saint Lucia
|
||||||
<li>Panama</li>
|
- Saint Martin
|
||||||
<li>Papua New Guinea</li>
|
- Saint Vincent and the Grenadines
|
||||||
<li>Paraguay</li>
|
- San marino
|
||||||
<li>Peru</li>
|
- Saudi Arabia
|
||||||
<li>Philippines</li>
|
- Senegal
|
||||||
<li>Poland</li>
|
- Serbia
|
||||||
<li>Portugal</li>
|
- Seychelles
|
||||||
<li>Qatar</li>
|
- Singapore
|
||||||
<li>Republic of Cabo Verde</li>
|
- Sint Maarten
|
||||||
<li>Reunion</li>
|
- Slovakia
|
||||||
<li>Romania</li>
|
- Slovenia
|
||||||
<li>Rwanda</li>
|
- South Africa
|
||||||
<li>Saint Kitts and Nevis</li>
|
- Spain
|
||||||
</ul>
|
- Sri Lanka
|
||||||
</td>
|
- Suriname
|
||||||
<td>
|
- Sweden
|
||||||
<ul>
|
- Switzerland
|
||||||
<li>Saint Lucia</li>
|
- Tanzania
|
||||||
<li>Saint Martin</li>
|
- Thailand
|
||||||
<li>Saint Vincent and the Grenadines</li>
|
- Timor-Leste
|
||||||
<li>San marino</li>
|
- Togo
|
||||||
<li>Saudi Arabia</li>
|
- Tonga
|
||||||
<li>Senegal</li>
|
- Trinidad and Tobago
|
||||||
<li>Serbia</li>
|
- Tunisia
|
||||||
<li>Seychelles</li>
|
- Turkey
|
||||||
<li>Singapore</li>
|
- Turks and Caicos Islands
|
||||||
<li>Sint Maarten</li>
|
- Uganda
|
||||||
<li>Slovakia</li>
|
- United Arab Emirates
|
||||||
<li>Slovenia</li>
|
- United Kingdom
|
||||||
<li>South Africa</li>
|
- United States
|
||||||
<li>Spain</li>
|
- Uruguay
|
||||||
<li>Sri Lanka</li>
|
- Vatican City
|
||||||
<li>Suriname</li>
|
- Viet Nam
|
||||||
<li>Sweden</li>
|
- Virgin Islands, U.S.
|
||||||
<li>Switzerland</li>
|
- Zambia
|
||||||
<li>Tanzania</li>
|
- Zimbabwe
|
||||||
<li>Thailand</li>
|
|
||||||
<li>Timor-Leste</li>
|
|
||||||
<li>Togo</li>
|
|
||||||
<li>Tonga</li>
|
|
||||||
<li>Trinidad and Tobago</li>
|
|
||||||
<li>Tunisia</li>
|
|
||||||
<li>Turkey</li>
|
|
||||||
<li>Turks and Caicos Islands</li>
|
|
||||||
<li>Uganda</li>
|
|
||||||
<li>United Arab Emirates</li>
|
|
||||||
<li>United Kingdom</li>
|
|
||||||
<li>United States</li>
|
|
||||||
<li>Uruguay</li>
|
|
||||||
<li>Vatican City</li>
|
|
||||||
<li>Viet Nam</li>
|
|
||||||
<li>Virgin Islands, U.S.</li>
|
|
||||||
<li>Zambia</li>
|
|
||||||
<li>Zimbabwe<br> </li><br/> </ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Support for free apps
|
### Support for free apps
|
||||||
Customers in these markets can use Microsoft Store for Business and Education to acquire free apps:
|
Customers in these markets can use Microsoft Store for Business and Education to acquire free apps:
|
||||||
|
|||||||
@ -24,56 +24,15 @@ Use the following procedure to configure the App-V for reporting.
|
|||||||
|
|
||||||
2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** cmdlet to configure appropriate Reporting Configuration settings:
|
2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** cmdlet to configure appropriate Reporting Configuration settings:
|
||||||
|
|
||||||
<table>
|
|Setting|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="30%" />
|
|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.|
|
||||||
<col width="70%" />
|
|ReportingServerURL|Specifies the location on the reporting server where client information is saved. For example, https://<reportingservername>:<reportingportnumber>.<br> **Note:** <br>This is the port number that was assigned during the Reporting Server setup|
|
||||||
</colgroup>
|
|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.|
|
||||||
<thead>
|
|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.|
|
||||||
<tr class="header">
|
|ReportingInterval|Specifies the retry interval that the client will use to resend data to the reporting server.|
|
||||||
<th align="left">Setting</th>
|
|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.|
|
||||||
<th align="left">Description</th>
|
|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.|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>ReportingEnabled</p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>ReportingServerURL</p></td>
|
|
||||||
<td align="left"><p>Specifies the location on the reporting server where client information is saved. For example, https://<reportingservername>:<reportingportnumber>.</p>
|
|
||||||
<div class="alert">
|
|
||||||
<strong>Note</strong><br/><p>This is the port number that was assigned during the Reporting Server setup</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
|
|
||||||
</div></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Reporting Start Time</p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>ReportingRandomDelay</p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>ReportingInterval</p></td>
|
|
||||||
<td align="left"><p>Specifies the retry interval that the client will use to resend data to the reporting server.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>ReportingDataCacheLimit</p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>ReportingDataBlockSize</p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. After the appropriate settings have been configured, the computer running the App-V client will automatically collect data and will send the data back to the reporting server.
|
3. After the appropriate settings have been configured, the computer running the App-V client will automatically collect data and will send the data back to the reporting server.
|
||||||
|
|
||||||
|
|||||||
@ -69,28 +69,10 @@ This topic explains the following procedures:
|
|||||||
|
|
||||||
2. Use the following cmdlets, and add the optional **–UserSID** parameter, where **-UserSID** represents the end user’s security identifier (SID):
|
2. Use the following cmdlets, and add the optional **–UserSID** parameter, where **-UserSID** represents the end user’s security identifier (SID):
|
||||||
|
|
||||||
<table>
|
|Cmdlet|Examples|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Enable-AppVClientConnectionGroup|Enable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345|
|
||||||
<col width="50%" />
|
|Disable-AppVClientConnectionGroup|Disable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Cmdlet</th>
|
|
||||||
<th align="left">Examples</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Enable-AppVClientConnectionGroup</p></td>
|
|
||||||
<td align="left"><p>Enable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Disable-AppVClientConnectionGroup</p></td>
|
|
||||||
<td align="left"><p>Disable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
## To allow only administrators to enable connection groups
|
## To allow only administrators to enable connection groups
|
||||||
|
|
||||||
@ -102,33 +84,9 @@ This topic explains the following procedures:
|
|||||||
|
|
||||||
2. Run the following cmdlet and parameter:
|
2. Run the following cmdlet and parameter:
|
||||||
|
|
||||||
<table>
|
|Cmdlet|Parameter and values|Example|
|
||||||
<colgroup>
|
|--- |--- |--- |
|
||||||
<col width="33%" />
|
|Set-AppvClientConfiguration|-RequirePublishAsAdmin<li>0 - False<li>1 - True|Set-AppvClientConfiguration -RequirePublishAsAdmin<br>1|
|
||||||
<col width="33%" />
|
|
||||||
<col width="33%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Cmdlet</th>
|
|
||||||
<th align="left">Parameter and values</th>
|
|
||||||
<th align="left">Example</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Set-AppvClientConfiguration</p></td>
|
|
||||||
<td align="left"><p>-RequirePublishAsAdmin</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>0 - False</p></li>
|
|
||||||
<li><p>1 - True</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>Set-AppvClientConfiguration -RequirePublishAsAdmin 1</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||||
|
|
||||||
|
|||||||
@ -24,50 +24,16 @@ In some previous versions of App-V, connection groups were referred to as Dynami
|
|||||||
|
|
||||||
**In this section:**
|
**In this section:**
|
||||||
|
|
||||||
<table>
|
|Links|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|[About the Connection Group Virtual Environment](appv-connection-group-virtual-environment.md)|Describes the connection group virtual environment.|
|
||||||
<col width="50%" />
|
|[About the Connection Group File](appv-connection-group-file.md)|Describes the connection group file.|
|
||||||
</colgroup>
|
|[How to Create a Connection Group](appv-create-a-connection-group.md)|Explains how to create a new connection group.|
|
||||||
<tbody>
|
|[How to Create a Connection Group with User-Published and Globally Published Packages](appv-create-a-connection-group-with-user-published-and-globally-published-packages.md)|Explains how to create a new connection group that contains a mix of packages that are published to the user and published globally.|
|
||||||
<tr class="odd">
|
|[How to Delete a Connection Group](appv-delete-a-connection-group.md)|Explains how to delete a connection group.|
|
||||||
<td align="left"><p><a href="appv-connection-group-virtual-environment.md" data-raw-source="[About the Connection Group Virtual Environment](appv-connection-group-virtual-environment.md)">About the Connection Group Virtual Environment</a></p></td>
|
|[How to Publish a Connection Group](appv-publish-a-connection-group.md)|Explains how to publish a connection group.|
|
||||||
<td align="left"><p>Describes the connection group virtual environment.</p></td>
|
|[How to Make a Connection Group Ignore the Package Version](appv-configure-connection-groups-to-ignore-the-package-version.md)|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.|
|
||||||
</tr>
|
[How to Allow Only Administrators to Enable Connection Groups](appv-allow-administrators-to-enable-connection-groups.md)|Explains how to configure the App-V client so that only administrators (not end users) can enable or disable connection groups.|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p><a href="appv-connection-group-file.md" data-raw-source="[About the Connection Group File](appv-connection-group-file.md)">About the Connection Group File</a></p></td>
|
|
||||||
<td align="left"><p>Describes the connection group file.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><a href="appv-create-a-connection-group.md" data-raw-source="[How to Create a Connection Group](appv-create-a-connection-group.md)">How to Create a Connection Group</a></p></td>
|
|
||||||
<td align="left"><p>Explains how to create a new connection group.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p><a href="appv-create-a-connection-group-with-user-published-and-globally-published-packages.md" data-raw-source="[How to Create a Connection Group with User-Published and Globally Published Packages](appv-create-a-connection-group-with-user-published-and-globally-published-packages.md)">How to Create a Connection Group with User-Published and Globally Published Packages</a></p></td>
|
|
||||||
<td align="left"><p>Explains how to create a new connection group that contains a mix of packages that are published to the user and published globally.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><a href="appv-delete-a-connection-group.md" data-raw-source="[How to Delete a Connection Group](appv-delete-a-connection-group.md)">How to Delete a Connection Group</a></p></td>
|
|
||||||
<td align="left"><p>Explains how to delete a connection group.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p><a href="appv-publish-a-connection-group.md" data-raw-source="[How to Publish a Connection Group](appv-publish-a-connection-group.md)">How to Publish a Connection Group</a></p></td>
|
|
||||||
<td align="left"><p>Explains how to publish a connection group.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p><a href="appv-configure-connection-groups-to-ignore-the-package-version.md" data-raw-source="[How to Make a Connection Group Ignore the Package Version](appv-configure-connection-groups-to-ignore-the-package-version.md)">How to Make a Connection Group Ignore the Package Version</a></p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p><a href="appv-allow-administrators-to-enable-connection-groups.md" data-raw-source="[How to Allow Only Administrators to Enable Connection Groups](appv-allow-administrators-to-enable-connection-groups.md)">How to Allow Only Administrators to Enable Connection Groups</a></p></td>
|
|
||||||
<td align="left"><p>Explains how to configure the App-V client so that only administrators (not end users) can enable or disable connection groups.</p></td>
|
|
||||||
</tr></tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||||
|
|
||||||
|
|||||||
@ -26,35 +26,9 @@ You can now use the package converter to convert App-V 4.6 packages that contain
|
|||||||
|
|
||||||
You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom-AppvLegacyPackage` cmdlet to specify which .osd files’ information is converted and placed within the new package.
|
You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom-AppvLegacyPackage` cmdlet to specify which .osd files’ information is converted and placed within the new package.
|
||||||
|
|
||||||
<table>
|
|New in App-V for Windows client|Prior to App-V for Windows 10|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|New .xml files are created corresponding to the .osd files associated with a package; these files include the following information:<li>environment variables<li>shortcuts<li>file type associations<li>registry information<li>scripts<br> <br>You can now choose to add information from a subset of the .osd files in the source directory to the package using the -OSDsToIncludeInPackage parameter.|Registry information and scripts included in .osd files associated with a package were not included in package converter output.<br> <br>The package converter would populate the new package with information from all of the .osd files in the source directory.|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">New in App-V for Windows client</th>
|
|
||||||
<th align="left">Prior to App-V for Windows 10</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>New .xml files are created corresponding to the .osd files associated with a package; these files include the following information:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>environment variables</p></li>
|
|
||||||
<li><p>shortcuts</p></li>
|
|
||||||
<li><p>file type associations</p></li>
|
|
||||||
<li><p>registry information</p></li>
|
|
||||||
<li><p>scripts</p></li>
|
|
||||||
</ul>
|
|
||||||
<p>You can now choose to add information from a subset of the .osd files in the source directory to the package using the <code>-OSDsToIncludeInPackage</code> parameter.</p></td>
|
|
||||||
<td align="left"><p>Registry information and scripts included in .osd files associated with a package were not included in package converter output.</p>
|
|
||||||
<p>The package converter would populate the new package with information from all of the .osd files in the source directory.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Example conversion statement
|
### Example conversion statement
|
||||||
|
|
||||||
@ -102,65 +76,10 @@ ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\
|
|||||||
|
|
||||||
**In the above example:**
|
**In the above example:**
|
||||||
|
|
||||||
<table>
|
|These Source directory files…|…are converted to these Destination directory files…|…and will contain these items|Description|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|<li>X.osd<li>Y.osd<li>Z.osd|<li>X_Config.xml<li>Y_Config.xml<li>Z_Config.xml|<li>Environment variables:<li>Shortcuts<li>File type associations<li>Registry information<li>Scripts|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.<br>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.|
|
||||||
<col width="25%" />
|
|<li>X.osd<li>Y.osd|<li>ContosoApp.appv <li>ContosoApp_DeploymentConfig.xml <li>ContosoApp_UserConfig.xml|<li>Environment variables<li>Shortcuts<li>File type associations|The information from the .osd files specified in the -OSDsToIncludeInPackage parameter are converted and placed inside the package. The converter then populates the deployment configuration file and the user configuration file with the contents of the package, just as App-V Sequencer does when sequencing a new package.<br>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 -OSDsToIncludeInPackage parameter. No information from Z.osd was included in the package, because it was not included as one of these arguments.|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">These Source directory files…</th>
|
|
||||||
<th align="left">…are converted to these Destination directory files…</th>
|
|
||||||
<th align="left">…and will contain these items</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>X.osd</p></li>
|
|
||||||
<li><p>Y.osd</p></li>
|
|
||||||
<li><p>Z.osd</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>X_Config.xml</p></li>
|
|
||||||
<li><p>Y_Config.xml</p></li>
|
|
||||||
<li><p>Z_Config.xml</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>Environment variables</p></li>
|
|
||||||
<li><p>Shortcuts</p></li>
|
|
||||||
<li><p>File type associations</p></li>
|
|
||||||
<li><p>Registry information</p></li>
|
|
||||||
<li><p>Scripts</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>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.</p>
|
|
||||||
<p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>X.osd</p></li>
|
|
||||||
<li><p>Y.osd</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>ContosoApp.appv</p></li>
|
|
||||||
<li><p>ContosoApp_DeploymentConfig.xml</p></li>
|
|
||||||
<li><p>ContosoApp_UserConfig.xml</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>Environment variables</p></li>
|
|
||||||
<li><p>Shortcuts</p></li>
|
|
||||||
<li><p>File type associations</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>The information from the .osd files specified in the <code>-OSDsToIncludeInPackage</code> parameter are converted and placed inside the package. The converter then populates the deployment configuration file and the user configuration file with the contents of the package, just as App-V Sequencer does when sequencing a new package.</p>
|
|
||||||
<p>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 <code>-OSDsToIncludeInPackage</code> parameter. No information from Z.osd was included in the package, because it was not included as one of these arguments.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Converting packages created using a prior version of App-V
|
## Converting packages created using a prior version of App-V
|
||||||
|
|
||||||
@ -175,34 +94,11 @@ After you convert an existing package you should test the package prior to deplo
|
|||||||
|
|
||||||
**What to know before you convert existing packages**
|
**What to know before you convert existing packages**
|
||||||
|
|
||||||
<table>
|
|Issue|Workaround|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Virtual packages using DSC are not linked after conversion.|Link the packages using connection groups. See [Managing Connection Groups](appv-managing-connection-groups.md).|
|
||||||
<col width="50%" />
|
|Environment variable conflicts are detected during conversion.|Resolve any conflicts in the associated **.osd** file.|
|
||||||
</colgroup>
|
|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.|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Issue</th>
|
|
||||||
<th align="left">Workaround</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Virtual packages using DSC are not linked after conversion.</p></td>
|
|
||||||
<td align="left"><p>Link the packages using connection groups. See <a href="appv-managing-connection-groups.md" data-raw-source="[Managing Connection Groups](appv-managing-connection-groups.md)">Managing Connection Groups</a>.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Environment variable conflicts are detected during conversion.</p></td>
|
|
||||||
<td align="left"><p>Resolve any conflicts in the associated <strong>.osd</strong> file.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Hard-coded paths are detected during conversion.</p></td>
|
|
||||||
<td align="left"><p>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.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
When converting a package check for failing files or shortcuts, locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
|
When converting a package check for failing files or shortcuts, locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
|
||||||
|
|
||||||
@ -218,39 +114,12 @@ If a converted package does not open after you convert it, it is also recommende
|
|||||||
|
|
||||||
There is no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server.
|
There is no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server.
|
||||||
|
|
||||||
<table>
|
|Task|More Information|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Review prerequisites.|[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software)|
|
||||||
<col width="50%" />
|
|Enable the App-V client.|[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)|
|
||||||
</colgroup>
|
|Install App-V Server.|[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)|
|
||||||
<thead>
|
|Migrate existing packages.|See [Converting packages created using a prior version of App-V](#converting-packages-created-using-a-prior-version-of-app-v) earlier in this topic.|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Task</th>
|
|
||||||
<th align="left">More Information</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Review prerequisites.</p></td>
|
|
||||||
<td align="left"><p><a href="appv-prerequisites.md#app-v-server-prerequisite-software" data-raw-source="[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software)">App-V Server prerequisite software</a>.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Enable the App-V client.</p></td>
|
|
||||||
<td align="left"><p><a href="appv-enable-the-app-v-desktop-client.md" data-raw-source="[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)">Enable the App-V desktop client</a>.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Install App-V Server.</p></td>
|
|
||||||
<td align="left"><p><a href="appv-deploy-the-appv-server.md" data-raw-source="[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)">How to Deploy the App-V Server</a>.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Migrate existing packages.</p></td>
|
|
||||||
<td align="left"><p>See <a href="#converting-packages-created-using-a-prior-version-of-app-v" data-raw-source="[Converting packages created using a prior version of App-V](#converting-packages-created-using-a-prior-version-of-app-v)">Converting packages created using a prior version of App-V</a> earlier in this topic.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||||
|
|
||||||
|
|||||||
@ -36,46 +36,13 @@ Windows 10 also introduces two additional scenarios that organizations should c
|
|||||||
|
|
||||||
So how do you choose? At a high level:
|
So how do you choose? At a high level:
|
||||||
|
|
||||||
<table>
|
| Consider ... | For these scenarios |
|
||||||
<colgroup>
|
|---|---|
|
||||||
<col width="50%" />
|
| In-place upgrade | - When you want to keep all (or at least most) existing applications<br/>- When you do not plan to significantly change the device configuration (for example, BIOS to UEFI) or operating system configuration (for example, x86 to x64, language changes, Administrators to non-Administrators, Active Directory domain consolidations)<br/>- To migrate from Windows 10 to a later Windows 10 release |
|
||||||
<col width="50%" />
|
| Traditional wipe-and-load | - When you upgrade significant numbers of applications along with the new Windows OS<br/>- When you make significant device or operating system configuration changes<br/>- When you “start clean”. For example, scenarios where it is not necessary to preserve existing apps or data (for example, call centers) or when you move from unmanaged to well-managed PCs<br/>- When you migrate from Windows Vista or other previous operating system versions |
|
||||||
</colgroup>
|
| Dynamic provisioning | - For new devices, especially in “choose your own device” scenarios when simple configuration (not reimaging) is all that is required. <br/>- When used in combination with a management tool (for example, an MDM service like Microsoft Intune) that enables self-service installation of user-specific or role-specific apps |
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Consider ...</th>
|
|
||||||
<th align="left">For these scenarios</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">In-place upgrade</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>When you want to keep all (or at least most) existing applications</p></li>
|
|
||||||
<li><p>When you do not plan to significantly change the device configuration (for example, BIOS to UEFI) or operating system configuration (for example, x86 to x64, language changes, Administrators to non-Administrators, Active Directory domain consolidations)</p></li>
|
|
||||||
<li><p>To migrate from Windows 10 to a later Windows 10 release</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left">Traditional wipe-and-load</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>When you upgrade significant numbers of applications along with the new Windows OS</p></li>
|
|
||||||
<li><p>When you make significant device or operating system configuration changes</p></li>
|
|
||||||
<li><p>When you “start clean”. For example, scenarios where it is not necessary to preserve existing apps or data (for example, call centers) or when you move from unmanaged to well-managed PCs</p></li>
|
|
||||||
<li><p>When you migrate from Windows Vista or other previous operating system versions</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left">Dynamic provisioning</td>
|
|
||||||
<td align="left"><ul>
|
|
||||||
<li><p>For new devices, especially in “choose your own device” scenarios when simple configuration (not reimaging) is all that is required</p></li>
|
|
||||||
<li><p>When used in combination with a management tool (for example, an MDM service like Microsoft Intune) that enables self-service installation of user-specific or role-specific apps</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
## Migration from previous Windows versions
|
## Migration from previous Windows versions
|
||||||
|
|
||||||
For existing PCs running Windows 7 or Windows 8.1, in-place upgrade is the recommended method for Windows 10 deployment and should be used whenever possible. Although wipe-and-load (OS refresh) deployments are still fully supported (and necessary in some scenarios, as mentioned previously), in-place upgrade is simpler and faster, and enables a faster Windows 10 deployment overall.
|
For existing PCs running Windows 7 or Windows 8.1, in-place upgrade is the recommended method for Windows 10 deployment and should be used whenever possible. Although wipe-and-load (OS refresh) deployments are still fully supported (and necessary in some scenarios, as mentioned previously), in-place upgrade is simpler and faster, and enables a faster Windows 10 deployment overall.
|
||||||
@ -105,7 +72,7 @@ In either of these scenarios, you can make a variety of configuration changes to
|
|||||||
|
|
||||||
## Stay up to date
|
## Stay up to date
|
||||||
|
|
||||||
For computers already running Windows 10 on the Semi-Annual Channel, new upgrades will be deployed two times per year. You can deploy these upgrades by using a variety of methods:
|
For computers using the [General Availability Channel](../update/waas-overview.md#general-availability-channel), you can deploy these upgrades by using a variety of methods:
|
||||||
|
|
||||||
- Windows Update or Windows Update for Business, for devices where you want to receive updates directly from the Internet.
|
- Windows Update or Windows Update for Business, for devices where you want to receive updates directly from the Internet.
|
||||||
- Windows Server Update Services (WSUS), for devices configured to pull updates from internal servers after they are approved (deploying like an update).
|
- Windows Server Update Services (WSUS), for devices configured to pull updates from internal servers after they are approved (deploying like an update).
|
||||||
|
|||||||
@ -103,7 +103,7 @@ sections:
|
|||||||
- question: |
|
- question: |
|
||||||
What are the servicing channels?
|
What are the servicing channels?
|
||||||
answer: |
|
answer: |
|
||||||
To align with the new method of delivering feature updates and quality updates in Windows 10, Microsoft introduced the concept of servicing channels to allow customers to designate how aggressively their individual devices are updated. For example, an organization may have test devices that the IT department can update with new features as soon as possible, and then specialized devices that require a longer feature update cycle to ensure continuity. With that in mind, Microsoft offers two servicing channels for Windows 10: Semi-Annual Channel, and Long-Term Servicing Channel (LTSC). For details about the versions in each servicing channel, see [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). For more information on each channel, see [servicing channels](../update/waas-overview.md#servicing-channels).
|
To align with the new method of delivering feature updates and quality updates in Windows 10, Microsoft introduced the concept of servicing channels to allow customers to designate how aggressively their individual devices are updated. For example, an organization may have test devices that the IT department can update with new features as soon as possible, and then specialized devices that require a longer feature update cycle to ensure continuity. With that in mind, Microsoft offers two servicing channels for Windows 10: General Availability Channel, and Long-Term Servicing Channel (LTSC). For details about the versions in each servicing channel, see [Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx). For more information on each channel, see [servicing channels](../update/waas-overview.md#servicing-channels).
|
||||||
|
|
||||||
- question: |
|
- question: |
|
||||||
What tools can I use to manage Windows as a service updates?
|
What tools can I use to manage Windows as a service updates?
|
||||||
|
|||||||
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Introduction to the Windows Insider Program for Business
|
title: Introduction to the Windows Insider Program for Business
|
||||||
description: In this article, you'll learn about the Windows Insider Program for Business and why IT Pros should join.
|
description: In this article, you'll learn about the Windows Insider Program for Business and why IT Pros should join.
|
||||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, WiP4Biz, enterprise, rings, flight
|
keywords: updates, servicing, current, deployment, General Availability Channel, semi-annual channel, feature, quality, rings, insider, WiP4Biz, enterprise, rings, flight
|
||||||
ms.custom: seo-marvel-apr2020
|
ms.custom: seo-marvel-apr2020
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
@ -22,7 +22,7 @@ ms.topic: article
|
|||||||
|
|
||||||
> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
> **Looking for information about Windows 10 for personal or home use?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||||
|
|
||||||
For many IT Pros, it's valuable to have visibility into feature updates early--before they’re available in the Semi-Annual Channel. With Windows 10, feature flighting enables participants in the Windows Insider Preview program can consume and deploy preproduction code to test devices, gaining early visibility into the next build. This is better for your organization because you can test the early builds of Windows 10 to discover possible issues with the code or with device and app compatibility in your organization before the update is ever publicly available. We at Microsoft also appreciate it because Insiders can report issues back to us in time for us to make improvements in a release before it is more generally available.
|
For many IT Pros, it's valuable to have visibility into feature updates early--before they’re available in the General Availability Channel. With Windows 10, feature flighting enables participants in the Windows Insider Preview program can consume and deploy preproduction code to test devices, gaining early visibility into the next build. This is better for your organization because you can test the early builds of Windows 10 to discover possible issues with the code or with device and app compatibility in your organization before the update is ever publicly available. We at Microsoft also appreciate it because Insiders can report issues back to us in time for us to make improvements in a release before it is more generally available.
|
||||||
|
|
||||||
The Windows Insider Program for Business gives you the opportunity to:
|
The Windows Insider Program for Business gives you the opportunity to:
|
||||||
|
|
||||||
@ -35,7 +35,7 @@ The Windows Insider Program for Business gives you the opportunity to:
|
|||||||
|
|
||||||
Microsoft recommends that all organizations have at least a few devices enrolled in the Windows Insider Program, to include the Windows Insider Program in their deployment plans, and to provide feedback on any issues they encounter to Microsoft via our Feedback Hub App.
|
Microsoft recommends that all organizations have at least a few devices enrolled in the Windows Insider Program, to include the Windows Insider Program in their deployment plans, and to provide feedback on any issues they encounter to Microsoft via our Feedback Hub App.
|
||||||
|
|
||||||
The Windows Insider Program doesn't replace Semi-Annual Channel deployments in an organization. Rather, it provides IT Pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft.
|
The Windows Insider Program doesn't replace General Availability Channel deployments in an organization. Rather, it provides IT Pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft.
|
||||||
|
|
||||||
[](images/WIP4Biz_deployment.png)<br>
|
[](images/WIP4Biz_deployment.png)<br>
|
||||||
Windows 10 Insider Preview builds enable organizations to prepare sooner for Windows Semi-Annual releases and reduce the overall validation effort required with traditional deployments.
|
Windows 10 Insider Preview builds enable organizations to prepare sooner for Windows Semi-Annual releases and reduce the overall validation effort required with traditional deployments.
|
||||||
@ -56,8 +56,8 @@ Along with exploring new features, you also have the option to validate your app
|
|||||||
- Get a head start on your Windows validation process
|
- Get a head start on your Windows validation process
|
||||||
- Identify issues sooner to accelerate your Windows deployment
|
- Identify issues sooner to accelerate your Windows deployment
|
||||||
- Engage Microsoft earlier for help with potential compatibility issues
|
- Engage Microsoft earlier for help with potential compatibility issues
|
||||||
- Deploy Windows 10 Semi-Annual releases faster and more confidently
|
- Deploy Windows 10 General Availability Channel releases faster and more confidently
|
||||||
- Maximize the 18-month support Window that comes with each Semi-Annual release.
|
- Maximize the support Window that comes with each General Availability Channel release.
|
||||||
|
|
||||||
|Objective |Feature exploration|
|
|Objective |Feature exploration|
|
||||||
|---------|---------|
|
|---------|---------|
|
||||||
|
|||||||
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Windows client updates, channels, and tools
|
title: Windows client updates, channels, and tools
|
||||||
description: Brief summary of the kinds of Windows updates, the channels they are served through, and the tools for managing them
|
description: Brief summary of the kinds of Windows updates, the channels they are served through, and the tools for managing them
|
||||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
keywords: updates, servicing, current, deployment, General Availability Channel, semi-annual channel, feature, quality, rings, insider, tools
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
author: jaimeo
|
author: jaimeo
|
||||||
@ -35,7 +35,7 @@ version of the software.
|
|||||||
|
|
||||||
We include information here about many different update types you'll hear about, but the two overarching types that you have the most direct control over are *feature updates* and *quality updates*.
|
We include information here about many different update types you'll hear about, but the two overarching types that you have the most direct control over are *feature updates* and *quality updates*.
|
||||||
|
|
||||||
- **Feature updates:** Released as soon as they become available. Feature updates add new features and functionality to Windows 10. Because they are delivered frequently (rather than every 3-5 years), they are easier to manage.
|
- **Feature updates:** Released annually. Feature updates add new features and functionality to Windows 10. Because they are delivered frequently (rather than every 3-5 years), they are easier to manage.
|
||||||
- **Quality updates:** Quality updates deliver both security and non-security fixes. Quality updates include security updates, critical updates, servicing stack updates, and driver updates. They are typically released on the second Tuesday of each month, though they can be released at any time. The second-Tuesday releases are the ones that focus on security updates. Quality updates are *cumulative*, so installing the latest quality update is sufficient to get all the available fixes for a specific feature update, including any out-of-band security fixes and any *servicing stack updates* that might have been released previously.
|
- **Quality updates:** Quality updates deliver both security and non-security fixes. Quality updates include security updates, critical updates, servicing stack updates, and driver updates. They are typically released on the second Tuesday of each month, though they can be released at any time. The second-Tuesday releases are the ones that focus on security updates. Quality updates are *cumulative*, so installing the latest quality update is sufficient to get all the available fixes for a specific feature update, including any out-of-band security fixes and any *servicing stack updates* that might have been released previously.
|
||||||
- **Servicing stack updates:** The "servicing stack" is the code component that actually installs Windows updates. From time to time, the servicing stack itself needs to be updated in order to function smoothly. If you don't install the latest servicing stack update, there's a risk that your device can't be updated with the latest Microsoft security fixes. Servicing stack updates are not necessarily included in *every* monthly quality update, and occasionally are released out of band to address a late-breaking issue. Always install the latest available quality update to catch any servicing stack updates that might have been released. The servicing stack also contains the "component-based servicing stack" (CBS), which is a key underlying component for several elements of Windows deployment, such as DISM, SFC, changing Windows features or roles, and repairing components. The CBS is a small component that typically does not have updates released every month. You can find a list of servicing stack updates at [Latest servicing stack updates](https://portal.msrc.microsoft.com/security-guidance/advisory/ADV990001). For more detail about servicing stack updates, see [Servicing stack updates](servicing-stack-updates.md).
|
- **Servicing stack updates:** The "servicing stack" is the code component that actually installs Windows updates. From time to time, the servicing stack itself needs to be updated in order to function smoothly. If you don't install the latest servicing stack update, there's a risk that your device can't be updated with the latest Microsoft security fixes. Servicing stack updates are not necessarily included in *every* monthly quality update, and occasionally are released out of band to address a late-breaking issue. Always install the latest available quality update to catch any servicing stack updates that might have been released. The servicing stack also contains the "component-based servicing stack" (CBS), which is a key underlying component for several elements of Windows deployment, such as DISM, SFC, changing Windows features or roles, and repairing components. The CBS is a small component that typically does not have updates released every month. You can find a list of servicing stack updates at [Latest servicing stack updates](https://portal.msrc.microsoft.com/security-guidance/advisory/ADV990001). For more detail about servicing stack updates, see [Servicing stack updates](servicing-stack-updates.md).
|
||||||
- **Driver updates**: These update drivers applicable to your devices. Driver updates are turned off by default in Windows Server Update Services (WSUS), but for cloud-based update methods, you can control whether they are installed or not.
|
- **Driver updates**: These update drivers applicable to your devices. Driver updates are turned off by default in Windows Server Update Services (WSUS), but for cloud-based update methods, you can control whether they are installed or not.
|
||||||
@ -51,7 +51,7 @@ The first step of controlling when and how devices install updates is assigning
|
|||||||
|
|
||||||
### General Availability Channel
|
### General Availability Channel
|
||||||
|
|
||||||
In the General Availability Channel, feature updates are available as soon as Microsoft releases them. As long as a device isn't set to defer feature updates, any device in this channel will install a feature update as soon as it's released. If you use Windows Update for Business, the channel provides three months of additional total deployment time before being required to update to the next release.
|
In the General Availability Channel, feature updates are released annually. As long as a device isn't set to defer feature updates, any device in this channel will install a feature update as soon as it's released. If you use Windows Update for Business, the channel provides three months of additional total deployment time before being required to update to the next release.
|
||||||
|
|
||||||
|
|
||||||
### Windows Insider Program for Business
|
### Windows Insider Program for Business
|
||||||
|
|||||||
@ -60,7 +60,7 @@ When using WSUS to manage updates on Windows client devices, start by configurin
|
|||||||
|
|
||||||
3. Right-click **Your_Domain**, and then select **Create a GPO in this domain, and Link it here**.
|
3. Right-click **Your_Domain**, and then select **Create a GPO in this domain, and Link it here**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>In this example, the **Configure Automatic Updates** and **Intranet Microsoft Update Service Location** Group Policy settings are specified for the entire domain. This is not a requirement; you can target these settings to any security group by using Security Filtering or a specific OU.
|
>In this example, the **Configure Automatic Updates** and **Intranet Microsoft Update Service Location** Group Policy settings are specified for the entire domain. This is not a requirement; you can target these settings to any security group by using Security Filtering or a specific OU.
|
||||||
@ -73,13 +73,13 @@ When using WSUS to manage updates on Windows client devices, start by configurin
|
|||||||
|
|
||||||
7. Right-click the **Configure Automatic Updates** setting, and then click **Edit**.
|
7. Right-click the **Configure Automatic Updates** setting, and then click **Edit**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
8. In the **Configure Automatic Updates** dialog box, select **Enable**.
|
8. In the **Configure Automatic Updates** dialog box, select **Enable**.
|
||||||
|
|
||||||
9. Under **Options**, from the **Configure automatic updating** list, select **3 - Auto download and notify for install**, and then click **OK**.
|
9. Under **Options**, from the **Configure automatic updating** list, select **3 - Auto download and notify for install**, and then click **OK**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
> Use Regedit.exe to check that the following key is not enabled, because it can break Windows Store connectivity: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\DoNotConnectToWindowsUpdateInternetLocations
|
> Use Regedit.exe to check that the following key is not enabled, because it can break Windows Store connectivity: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\DoNotConnectToWindowsUpdateInternetLocations
|
||||||
@ -91,12 +91,12 @@ When using WSUS to manage updates on Windows client devices, start by configurin
|
|||||||
|
|
||||||
11. In the **Specify intranet Microsoft update service location** dialog box, select **Enable**.
|
11. In the **Specify intranet Microsoft update service location** dialog box, select **Enable**.
|
||||||
|
|
||||||
12. Under **Options**, in the **Set the intranet update service for detecting updates** and **Set the intranet statistics server** options, type <strong>http://Your_WSUS_Server_FQDN:PortNumber</strong>, and then select **OK**.
|
12. Under **Options**, in the **Set the intranet update service for detecting updates** and **Set the intranet statistics server** options, type `http://Your_WSUS_Server_FQDN:PortNumber`, and then select **OK**.
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>The URL `http://CONTOSO-WSUS1.contoso.com:8530` in the following image is just an example. In your environment, be sure to use the server name and port number for your WSUS instance.
|
>The URL `http://CONTOSO-WSUS1.contoso.com:8530` in the following image is just an example. In your environment, be sure to use the server name and port number for your WSUS instance.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>The default HTTP port for WSUS is 8530, and the default HTTP over Secure Sockets Layer (HTTPS) port is 8531. (The other options are 80 and 443; no other ports are supported.)
|
>The default HTTP port for WSUS is 8530, and the default HTTP over Secure Sockets Layer (HTTPS) port is 8531. (The other options are 80 and 443; no other ports are supported.)
|
||||||
@ -116,7 +116,7 @@ You can use computer groups to target a subset of devices that have specific qua
|
|||||||
|
|
||||||
2. Go to *Server_Name*\Computers\All Computers, and then click **Add Computer Group**.
|
2. Go to *Server_Name*\Computers\All Computers, and then click **Add Computer Group**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. Type **Ring 2 Pilot Business Users** for the name, and then click **Add**.
|
3. Type **Ring 2 Pilot Business Users** for the name, and then click **Add**.
|
||||||
|
|
||||||
@ -144,7 +144,7 @@ When new computers communicate with WSUS, they appear in the **Unassigned Comput
|
|||||||
|
|
||||||
2. Select both computers, right-click the selection, and then click **Change Membership**.
|
2. Select both computers, right-click the selection, and then click **Change Membership**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. In the **Set Computer Group Membership** dialog box, select the **Ring 2 Pilot Business Users** deployment ring, and then click **OK**.
|
3. In the **Set Computer Group Membership** dialog box, select the **Ring 2 Pilot Business Users** deployment ring, and then click **OK**.
|
||||||
|
|
||||||
@ -162,7 +162,7 @@ Another way to add multiple computers to a deployment ring in the WSUS Administr
|
|||||||
|
|
||||||
3. In the search results, select the computers, right-click the selection, and then click **Change Membership**.
|
3. In the search results, select the computers, right-click the selection, and then click **Change Membership**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
4. Select the **Ring 3 Broad IT** deployment ring, and then click **OK**.
|
4. Select the **Ring 3 Broad IT** deployment ring, and then click **OK**.
|
||||||
|
|
||||||
@ -179,7 +179,7 @@ The WSUS Administration Console provides a friendly interface from which you can
|
|||||||
|
|
||||||
1. Open the WSUS Administration Console, and go to *Server_Name*\Options, and then click **Computers**.
|
1. Open the WSUS Administration Console, and go to *Server_Name*\Options, and then click **Computers**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
2. In the **Computers** dialog box, select **Use Group Policy or registry settings on computers**, and then click **OK**.
|
2. In the **Computers** dialog box, select **Use Group Policy or registry settings on computers**, and then click **OK**.
|
||||||
|
|
||||||
@ -203,7 +203,7 @@ Now that WSUS is ready for client-side targeting, complete the following steps t
|
|||||||
|
|
||||||
5. Right-click the **WSUS – Client Targeting – Ring 4 Broad Business Users** GPO, and then click **Edit**.
|
5. Right-click the **WSUS – Client Targeting – Ring 4 Broad Business Users** GPO, and then click **Edit**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
6. In the Group Policy Management Editor, go to Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update.
|
6. In the Group Policy Management Editor, go to Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update.
|
||||||
|
|
||||||
@ -213,7 +213,7 @@ Now that WSUS is ready for client-side targeting, complete the following steps t
|
|||||||
|
|
||||||
9. In the **Target group name for this computer** box, type *Ring 4 Broad Business Users*. This is the name of the deployment ring in WSUS to which these computers will be added.
|
9. In the **Target group name for this computer** box, type *Ring 4 Broad Business Users*. This is the name of the deployment ring in WSUS to which these computers will be added.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
> [!WARNING]
|
> [!WARNING]
|
||||||
> The target group name must match the computer group name.
|
> The target group name must match the computer group name.
|
||||||
@ -230,7 +230,7 @@ Now you’re ready to deploy this GPO to the correct computer security group for
|
|||||||
|
|
||||||
3. Under **Security Filtering**, remove the default **AUTHENTICATED USERS** security group, and then add the **Ring 4 Broad Business Users** group.
|
3. Under **Security Filtering**, remove the default **AUTHENTICATED USERS** security group, and then add the **Ring 4 Broad Business Users** group.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The next time the clients in the **Ring 4 Broad Business Users** security group receive their computer policy and contact WSUS, they will be added to the **Ring 4 Broad Business Users** deployment ring.
|
The next time the clients in the **Ring 4 Broad Business Users** security group receive their computer policy and contact WSUS, they will be added to the **Ring 4 Broad Business Users** deployment ring.
|
||||||
|
|
||||||
@ -239,7 +239,7 @@ The next time the clients in the **Ring 4 Broad Business Users** security group
|
|||||||
For clients that should have their feature updates approved as soon as they’re available, you can configure Automatic Approval rules in WSUS.
|
For clients that should have their feature updates approved as soon as they’re available, you can configure Automatic Approval rules in WSUS.
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>WSUS respects the client device's servicing branch. If you approve a feature update while it is still in one branch, such as Insider Preview, WSUS will install the update only on devices that are in that servicing branch. When Microsoft releases the build for Semi-Annual Channel (or General Availability Channel), the devices in that will install it. Windows Update for Business branch settings do not apply to feature updates through WSUS.
|
>WSUS respects the client device's servicing branch. If you approve a feature update while it is still in one branch, such as Insider Preview, WSUS will install the update only on devices that are in that servicing branch. When Microsoft releases the build for the [General Availability Channel](waas-overview.md#general-availability-channel), the devices in that will install it. Windows Update for Business branch settings do not apply to feature updates through WSUS.
|
||||||
|
|
||||||
|
|
||||||
**To configure an Automatic Approval rule for Windows client feature updates and approve them for the Ring 3 Broad IT deployment ring**
|
**To configure an Automatic Approval rule for Windows client feature updates and approve them for the Ring 3 Broad IT deployment ring**
|
||||||
@ -251,7 +251,7 @@ This example uses Windows 10, but the process is the same for Windows 11.
|
|||||||
|
|
||||||
3. In the **Add Rule** dialog box, select the **When an update is in a specific classification**, **When an update is in a specific product**, and **Set a deadline for the approval** check boxes.
|
3. In the **Add Rule** dialog box, select the **When an update is in a specific classification**, **When an update is in a specific product**, and **Set a deadline for the approval** check boxes.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
4. In the **Edit the properties** area, select **any classification**. Clear everything except **Upgrades**, and then click **OK**.
|
4. In the **Edit the properties** area, select **any classification**. Clear everything except **Upgrades**, and then click **OK**.
|
||||||
|
|
||||||
@ -265,7 +265,7 @@ This example uses Windows 10, but the process is the same for Windows 11.
|
|||||||
|
|
||||||
8. In the **Step 3: Specify a name** box, type **Windows 10 Upgrade Auto-approval for Ring 3 Broad IT**, and then click **OK**.
|
8. In the **Step 3: Specify a name** box, type **Windows 10 Upgrade Auto-approval for Ring 3 Broad IT**, and then click **OK**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
9. In the **Automatic Approvals** dialog box, click **OK**.
|
9. In the **Automatic Approvals** dialog box, click **OK**.
|
||||||
|
|
||||||
@ -300,7 +300,7 @@ To simplify the manual approval process, start by creating a software update vie
|
|||||||
|
|
||||||
5. In the **Step 3: Specify a name** box, type **All Windows 10 Upgrades**, and then click **OK**.
|
5. In the **Step 3: Specify a name** box, type **All Windows 10 Upgrades**, and then click **OK**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Now that you have the **All Windows 10 Upgrades** view, complete the following steps to manually approve an update for the **Ring 4 Broad Business Users** deployment ring:
|
Now that you have the **All Windows 10 Upgrades** view, complete the following steps to manually approve an update for the **Ring 4 Broad Business Users** deployment ring:
|
||||||
|
|
||||||
@ -308,21 +308,21 @@ Now that you have the **All Windows 10 Upgrades** view, complete the following s
|
|||||||
|
|
||||||
2. Right-click the feature update you want to deploy, and then click **Approve**.
|
2. Right-click the feature update you want to deploy, and then click **Approve**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. In the **Approve Updates** dialog box, from the **Ring 4 Broad Business Users** list, select **Approved for Install**.
|
3. In the **Approve Updates** dialog box, from the **Ring 4 Broad Business Users** list, select **Approved for Install**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
4. In the **Approve Updates** dialog box, from the **Ring 4 Broad Business Users** list, click **Deadline**, click **One Week**, and then click **OK**.
|
4. In the **Approve Updates** dialog box, from the **Ring 4 Broad Business Users** list, click **Deadline**, click **One Week**, and then click **OK**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
5. If the **Microsoft Software License Terms** dialog box opens, click **Accept**.
|
5. If the **Microsoft Software License Terms** dialog box opens, click **Accept**.
|
||||||
|
|
||||||
If the deployment is successful, you should receive a successful progress report.
|
If the deployment is successful, you should receive a successful progress report.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
6. In the **Approval Progress** dialog box, click **Close**.
|
6. In the **Approval Progress** dialog box, click **Close**.
|
||||||
|
|
||||||
|
|||||||
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Overview of Windows as a service
|
title: Overview of Windows as a service
|
||||||
description: Windows as a service is a way to build, deploy, and service Windows. Learn how Windows as a service works.
|
description: Windows as a service is a way to build, deploy, and service Windows. Learn how Windows as a service works.
|
||||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
keywords: updates, servicing, current, deployment, General Availability Channel, semi-annual channel, feature, quality, rings, insider, tools
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
author: jaimeo
|
author: jaimeo
|
||||||
@ -90,9 +90,9 @@ There are three servicing channels. The [Windows Insider Program](#windows-insid
|
|||||||
|
|
||||||
### General Availability Channel
|
### General Availability Channel
|
||||||
|
|
||||||
In the General Availability Channel, feature updates are available as soon as Microsoft releases them. This servicing model is ideal for pilot deployments and testing of feature updates and for users such as developers who need to work with the latest features immediately. Once the latest release has gone through pilot deployment and testing, you will be able to choose the timing at which it goes into broad deployment.
|
In the General Availability Channel, feature updates are available annually. This servicing model is ideal for pilot deployments and testing of feature updates and for users such as developers who need to work with the latest features. Once the latest release has gone through pilot deployment and testing, you will be able to choose the timing at which it goes into broad deployment.
|
||||||
|
|
||||||
When Microsoft officially releases a feature update, we make it available to any device not configured to defer feature updates so that those devices can immediately install it. Organizations that use Windows Server Update Services (WSUS), Microsoft Endpoint Configuration Manager, or Windows Update for Business, however, can defer feature updates to selective devices by withholding their approval and deployment. In this scenario, the content available for the Semi-Annual Channel will be available but not necessarily immediately mandatory, depending on the policy of the management system. For more details about servicing tools, see [Servicing tools](#servicing-tools).
|
When Microsoft officially releases a feature update, we make it available to any device not configured to defer feature updates so that those devices can immediately install it. Organizations that use Windows Server Update Services (WSUS), Microsoft Endpoint Configuration Manager, or Windows Update for Business, however, can defer feature updates to selective devices by withholding their approval and deployment. In this scenario, the content available for the General Availability Channel will be available but not necessarily immediately mandatory, depending on the policy of the management system. For more details about servicing tools, see [Servicing tools](#servicing-tools).
|
||||||
|
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
@ -120,7 +120,7 @@ The Long-term Servicing Channel is available only in the Windows 10 Enterprise L
|
|||||||
|
|
||||||
### Windows Insider
|
### Windows Insider
|
||||||
|
|
||||||
For many IT pros, gaining visibility into feature updates early--before they’re available to the Semi-Annual Channel — can be both intriguing and valuable for future end user communications as well as provide the means to test for any issues on the next General Availability release. Windows Insiders can consume and deploy preproduction code to their test machines, gaining early visibility into the next build. Testing the early builds helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft.
|
For many IT pros, gaining visibility into feature updates early--before they’re available to the General Availability Channel — can be both intriguing and valuable for future end user communications as well as provide the means to test for any issues on the next General Availability release. Windows Insiders can consume and deploy preproduction code to their test machines, gaining early visibility into the next build. Testing the early builds helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft.
|
||||||
|
|
||||||
Microsoft recommends that all organizations have at least a few devices enrolled in the Windows Insider Program and provide feedback on any issues they encounter. For information about the Windows Insider Program for Business, go to [Windows Insider Program for Business](/windows-insider/at-work-pro/wip-4-biz-get-started).
|
Microsoft recommends that all organizations have at least a few devices enrolled in the Windows Insider Program and provide feedback on any issues they encounter. For information about the Windows Insider Program for Business, go to [Windows Insider Program for Business](/windows-insider/at-work-pro/wip-4-biz-get-started).
|
||||||
|
|
||||||
@ -130,7 +130,7 @@ Microsoft recommends that all organizations have at least a few devices enrolled
|
|||||||
|
|
||||||
There are many tools you can use to service Windows as a service. Each option has its pros and cons, ranging from capabilities and control to simplicity and low administrative requirements. The following are examples of the servicing tools available to manage Windows as a service updates:
|
There are many tools you can use to service Windows as a service. Each option has its pros and cons, ranging from capabilities and control to simplicity and low administrative requirements. The following are examples of the servicing tools available to manage Windows as a service updates:
|
||||||
|
|
||||||
- **Windows Update (stand-alone)** provides limited control over feature updates, with IT pros manually configuring the device to be in the Semi-Annual Channel. Organizations can target which devices defer updates by selecting the **Defer upgrades** check box in **Start\Settings\Update & Security\Advanced Options** on a Windows client device.
|
- **Windows Update (stand-alone)** provides limited control over feature updates, with IT pros manually configuring the device to be in the General Availability Channel. Organizations can target which devices defer updates by selecting the **Defer upgrades** check box in **Start\Settings\Update & Security\Advanced Options** on a Windows client device.
|
||||||
- **Windows Update for Business** includes control over update deferment and provides centralized management using Group Policy or MDM. Windows Update for Business can be used to defer updates by up to 365 days, depending on the version. These deployment options are available to clients in the General Availability Channel. In addition to being able to use Group Policy to manage Windows Update for Business, either option can be configured without requiring any on-premises infrastructure by using Microsoft Intune.
|
- **Windows Update for Business** includes control over update deferment and provides centralized management using Group Policy or MDM. Windows Update for Business can be used to defer updates by up to 365 days, depending on the version. These deployment options are available to clients in the General Availability Channel. In addition to being able to use Group Policy to manage Windows Update for Business, either option can be configured without requiring any on-premises infrastructure by using Microsoft Intune.
|
||||||
- **Windows Server Update Services (WSUS)** provides extensive control over updates and is natively available in the Windows Server operating system. In addition to the ability to defer updates, organizations can add an approval layer for updates and choose to deploy them to specific computers or groups of computers whenever ready.
|
- **Windows Server Update Services (WSUS)** provides extensive control over updates and is natively available in the Windows Server operating system. In addition to the ability to defer updates, organizations can add an approval layer for updates and choose to deploy them to specific computers or groups of computers whenever ready.
|
||||||
- **Microsoft Endpoint Configuration Manager** provides the greatest control over servicing Windows as a service. IT pros can defer updates, approve them, and have multiple options for targeting deployments and managing bandwidth usage and deployment times.
|
- **Microsoft Endpoint Configuration Manager** provides the greatest control over servicing Windows as a service. IT pros can defer updates, approve them, and have multiple options for targeting deployments and managing bandwidth usage and deployment times.
|
||||||
|
|||||||
@ -1,14 +1,14 @@
|
|||||||
---
|
---
|
||||||
title: Quick guide to Windows as a service (Windows 10)
|
title: Quick guide to Windows as a service (Windows 10)
|
||||||
description: In Windows 10, Microsoft has streamlined servicing to make operating system updates simpler to test, manage, and deploy.
|
description: In Windows 10, Microsoft has streamlined servicing to make operating system updates simpler to test, manage, and deploy.
|
||||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
keywords: updates, servicing, current, deployment, General Availability Channel, semi-annual channel, feature, quality, rings, insider, tools
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
author: jaimeo
|
author: jaimeo
|
||||||
ms.localizationpriority: high
|
ms.localizationpriority: high
|
||||||
ms.author: jaimeo
|
ms.author: jaimeo
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: laurawi
|
manager: dougeby
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -25,12 +25,13 @@ Here is a quick guide to the most important concepts in Windows as a service. Fo
|
|||||||
## Definitions
|
## Definitions
|
||||||
|
|
||||||
Some new terms have been introduced as part of Windows as a service, so you should know what these terms mean.
|
Some new terms have been introduced as part of Windows as a service, so you should know what these terms mean.
|
||||||
- **Feature updates** are released twice per year, around March and September. As the name suggests, these updates add new features, delivered in bite-sized chunks compared to the previous practice of Windows releases every 3-5 years.
|
|
||||||
|
- **Feature updates** are released annually. As the name suggests, these updates add new features, delivered in bite-sized chunks compared to the previous practice of Windows releases every 3-5 years.
|
||||||
- **Quality updates** deliver both security and non-security fixes. They are typically released on the second Tuesday of each month, though they can be released at any time. Quality updates include security updates, critical updates, servicing stack updates, and driver updates. Quality updates are cumulative, so installing the latest quality update is sufficient to get all the available fixes for a specific Windows 10 feature update. The "servicing stack" is the code that installs other updates, so they are important to keep current. For more information, see [Servicing stack updates](servicing-stack-updates.md).
|
- **Quality updates** deliver both security and non-security fixes. They are typically released on the second Tuesday of each month, though they can be released at any time. Quality updates include security updates, critical updates, servicing stack updates, and driver updates. Quality updates are cumulative, so installing the latest quality update is sufficient to get all the available fixes for a specific Windows 10 feature update. The "servicing stack" is the code that installs other updates, so they are important to keep current. For more information, see [Servicing stack updates](servicing-stack-updates.md).
|
||||||
- **Insider Preview** builds are made available during the development of the features that will be shipped in the next feature update, enabling organizations to validate new features and confirm compatibility with existing apps and infrastructure, providing feedback to Microsoft on any issues encountered.
|
- **Insider Preview** builds are made available during the development of the features that will be shipped in the next feature update, enabling organizations to validate new features and confirm compatibility with existing apps and infrastructure, providing feedback to Microsoft on any issues encountered.
|
||||||
- **Servicing channels** allow organizations to choose when to deploy new features.
|
- **Servicing channels** allow organizations to choose when to deploy new features.
|
||||||
- The **General Availability Channel** receives feature updates as they become available.
|
- The **General Availability Channel** receives feature updates annually.
|
||||||
- The **Long-Term Servicing Channel**, which meant only for specialized devices (which typically don't run Office) such as those that control medical equipment or ATM machines, receives new feature releases every two to three years.
|
- The **Long-Term Servicing Channel**, which meant only for specialized devices (which typically don't run Office) such as those that control medical equipment or ATM machines, receives new feature releases every two to three years.
|
||||||
- **Deployment rings** are groups of devices used to initially pilot, and then to broadly deploy, each feature update in an organization.
|
- **Deployment rings** are groups of devices used to initially pilot, and then to broadly deploy, each feature update in an organization.
|
||||||
|
|
||||||
See [Overview of Windows as a service](waas-overview.md) for more information.
|
See [Overview of Windows as a service](waas-overview.md) for more information.
|
||||||
@ -51,6 +52,6 @@ To stay up to date, deploy feature updates at an appropriate time after their re
|
|||||||
|
|
||||||
Extensive advanced testing isn’t required. Instead, only business-critical apps need to be tested, with the remaining apps validated through a series of pilot deployment rings. Once these pilot deployments have validated most apps, broad deployment can begin.
|
Extensive advanced testing isn’t required. Instead, only business-critical apps need to be tested, with the remaining apps validated through a series of pilot deployment rings. Once these pilot deployments have validated most apps, broad deployment can begin.
|
||||||
|
|
||||||
This process repeats with each new feature update as they become available. These are small deployment projects, compared to the large projects that were necessary with the old three-to-five-year Windows release cycles.
|
This process repeats with each new feature update. These are small deployment projects, compared to the large projects that were necessary with the old three-to-five-year Windows release cycles.
|
||||||
|
|
||||||
Other technologies such as BranchCache and Delivery Optimization, both peer-to-peer distribution tools, can help with the distribution of the feature update installation files.
|
Other technologies such as BranchCache and Delivery Optimization, both peer-to-peer distribution tools, can help with the distribution of the feature update installation files.
|
||||||
|
|||||||
@ -43,7 +43,7 @@ The General Availability Channel is the default servicing channel for all Window
|
|||||||
>The LTSC edition is only available through the [Microsoft Volume Licensing Center](https://www.microsoft.com/Licensing/servicecenter/default.aspx).
|
>The LTSC edition is only available through the [Microsoft Volume Licensing Center](https://www.microsoft.com/Licensing/servicecenter/default.aspx).
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>Devices will automatically receive updates from the Semi-Annual Channel, unless they are configured to receive preview updates through the Windows Insider Program.
|
>Devices will automatically receive updates from the General Availability Channel, unless they are configured to receive preview updates through the Windows Insider Program.
|
||||||
|
|
||||||
|
|
||||||
## Enroll devices in the Windows Insider Program
|
## Enroll devices in the Windows Insider Program
|
||||||
|
|||||||
@ -15,6 +15,7 @@ ms.topic: article
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Windows 10 upgrade paths
|
# Windows 10 upgrade paths
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
|
||||||
- Windows 10
|
- Windows 10
|
||||||
@ -25,194 +26,73 @@ This topic provides a summary of available upgrade paths to Windows 10. You can
|
|||||||
|
|
||||||
If you are also migrating to a different edition of Windows, see [Windows 10 edition upgrade](windows-10-edition-upgrades.md). Methods and supported paths are described on this page to change the edition of Windows. These methods require that you input a license or product key for the new Windows edition prior to starting the upgrade process. Edition downgrade is also supported for some paths, but please note that applications and settings are not maintained when the Windows edition is downgraded.
|
If you are also migrating to a different edition of Windows, see [Windows 10 edition upgrade](windows-10-edition-upgrades.md). Methods and supported paths are described on this page to change the edition of Windows. These methods require that you input a license or product key for the new Windows edition prior to starting the upgrade process. Edition downgrade is also supported for some paths, but please note that applications and settings are not maintained when the Windows edition is downgraded.
|
||||||
|
|
||||||
> **Windows 10 version upgrade**: You can directly upgrade any semi-annual channel version of Windows 10 to a newer, supported semi-annual channel version of Windows 10, even if it involves skipping versions. Work with your account representative if your current version of Windows is out of support. See the [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet) for availability and service information.
|
- **Windows 10 version upgrade**: You can directly upgrade any General Availability Channel version of Windows 10 to a newer, supported General Availability Channel version of Windows 10, even if it involves skipping versions. Work with your account representative if your current version of Windows is out of support. See the [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet) for availability and service information.
|
||||||
>
|
|
||||||
> In-place upgrade from Windows 7, Windows 8.1, or [Windows 10 semi-annual channel](/windows/release-health/release-information) to Windows 10 LTSC is not supported. **Note**: Windows 10 LTSC 2015 did not block this upgrade path. This was corrected in the Windows 10 LTSC 2016 release, which will now only allow data-only and clean install options. You can upgrade from Windows 10 LTSC to Windows 10 semi-annual channel, provided that you upgrade to the same or a newer build version. For example, Windows 10 Enterprise 2016 LTSB can be upgraded to Windows 10 Enterprise version 1607 or later. Upgrade is supported using the in-place upgrade process (using Windows setup). You will need to use the Product Key switch if you want to keep your apps. If you don't use the switch the option 'Keep personal files and apps' will be grayed out. The command line would be **setup.exe /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx**, using your relevant Windows 10 SAC product key. For example, if using a KMS, the command line would be **setup.exe /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43**.
|
- **In-place upgrade from Windows 7, Windows 8.1, or [Windows 10 General Availability Channel](/windows/release-health/release-information)** to Windows 10 LTSC is not supported. Windows 10 LTSC 2015 did not block this in-place upgrade path. This issue was corrected in the Windows 10 LTSC 2016 release, which only allows data-only and clean install options.
|
||||||
>
|
|
||||||
> **Windows N/KN**: Windows "N" and "KN" SKUs (editions without media-related functionality) follow the same upgrade paths shown below. If the pre-upgrade and post-upgrade editions are not the same type (e.g. Windows 8.1 Pro N to Windows 10 Pro), personal data will be kept but applications and settings will be removed during the upgrade process.
|
You can upgrade from Windows 10 LTSC to Windows 10 General Availability Channel, provided that you upgrade to the same or a newer build version. For example, Windows 10 Enterprise 2016 LTSB can be upgraded to Windows 10 Enterprise version 1607 or later. Upgrade is supported using the in-place upgrade process (using Windows setup). You will need to use the Product Key switch if you want to keep your apps. If you don't use the switch, the option **Keep personal files and apps** option is grayed out. The command line would be `setup.exe /pkey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx`, using your relevant Windows 10 SAC product key. For example, if using a KMS, the command line would be `setup.exe /pkey NPPR9-FWDCX-D2C8J-H872K-2YT43`.
|
||||||
>
|
|
||||||
> **Windows 8.0**: You cannot upgrade directly from Windows 8.0 to Windows 10. To upgrade from Windows 8.0, you must first install the [Windows 8.1 update](https://support.microsoft.com/help/15356/windows-8-install-update-kb-2919355).
|
- **Windows N/KN**: Windows "N" and "KN" SKUs (editions without media-related functionality) follow the same upgrade paths shown below. If the pre-upgrade and post-upgrade editions are not the same type (e.g. Windows 8.1 Pro N to Windows 10 Pro), personal data will be kept but applications and settings will be removed during the upgrade process.
|
||||||
|
|
||||||
|
- **Windows 8.0**: You cannot upgrade directly from Windows 8.0 to Windows 10. To upgrade from Windows 8.0, you must first install the [Windows 8.1 update](https://support.microsoft.com/help/15356/windows-8-install-update-kb-2919355).
|
||||||
|
|
||||||
|
## Windows 10
|
||||||
|
|
||||||
|
✔ = Full upgrade is supported including personal data, settings, and applications.
|
||||||
|
|
||||||
✔ = Full upgrade is supported including personal data, settings, and applications.<br>
|
|
||||||
D = Edition downgrade; personal data is maintained, applications and settings are removed.
|
D = Edition downgrade; personal data is maintained, applications and settings are removed.
|
||||||
|
|
||||||
<br>
|
---
|
||||||
<table border="0" cellpadding="1">
|
| | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
|
||||||
<tr>
|
|---|---|---|---|---|---|
|
||||||
<td> </td>
|
| **Home** | | ✔ | ✔ | ✔ | |
|
||||||
<td> </td>
|
| **Pro** | D | | ✔ | ✔ | ✔ |
|
||||||
<th>Windows 10 Home</th>
|
| **Education** | | | | | D |
|
||||||
<th>Windows 10 Pro</th>
|
| **Enterprise** | | | | ✔ | |
|
||||||
<th>Windows 10 Pro Education</th>
|
|
||||||
<th>Windows 10 Education</th>
|
|
||||||
<th>Windows 10 Enterprise</th>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<th rowspan="7">Windows 7</th>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Starter</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Home Basic</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Home Premium</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Professional</td>
|
|
||||||
<td>D</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Ultimate</td>
|
|
||||||
<td>D</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Enterprise</td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<th rowspan="10">Windows 8.1</th>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>(Core)</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Connected</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Pro</td>
|
|
||||||
<td>D</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Pro Student</td>
|
|
||||||
<td>D</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Pro WMC</td>
|
|
||||||
<td>D</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Enterprise</td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Embedded Industry</td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Windows RT</td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Windows Phone 8.1</td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<th rowspan="8">Windows 10</th>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Home</td>
|
|
||||||
<td></td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Pro</td>
|
|
||||||
<td>D</td>
|
|
||||||
<td></td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td>✔</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Education</td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td>D</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Enterprise</td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td>✔</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Windows 8.1
|
||||||
|
|
||||||
|
✔ = Full upgrade is supported including personal data, settings, and applications.
|
||||||
|
|
||||||
|
D = Edition downgrade; personal data is maintained, applications and settings are removed.
|
||||||
|
|
||||||
|
---
|
||||||
|
| | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
|
||||||
|
|---|---|---|---|---|---|
|
||||||
|
| **(Core)** | ✔ | ✔ | ✔ | ✔ | |
|
||||||
|
| **Connected** | ✔ | ✔ | ✔ | ✔ | |
|
||||||
|
| **Pro** | D | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
| **Pro Student** | D | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
| **Pro WMC** | D | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
| **Enterprise** | | | | ✔ | ✔ |
|
||||||
|
| **Embedded Industry** | | | | | ✔ |
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Windows 7
|
||||||
|
|
||||||
|
✔ = Full upgrade is supported including personal data, settings, and applications.
|
||||||
|
|
||||||
|
D = Edition downgrade; personal data is maintained, applications and settings are removed.
|
||||||
|
|
||||||
|
---
|
||||||
|
| | Windows 10 Home | Windows 10 Pro | Windows 10 Pro Education | Windows 10 Education | Windows 10 Enterprise |
|
||||||
|
|---|---|---|---|---|---|
|
||||||
|
| **Starter** | ✔ | ✔ | ✔ | ✔ | |
|
||||||
|
| **Home Basic** | ✔ | ✔ | ✔ | ✔ | |
|
||||||
|
| **Home Premium** | ✔ | ✔ | ✔ | ✔ | |
|
||||||
|
| **Professional** | D | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
| **Ultimate** | D | ✔ | ✔ | ✔ | ✔ |
|
||||||
|
| **Enterprise** | | | | ✔ | ✔ |
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
## Related Topics
|
## Related Topics
|
||||||
|
|
||||||
[Windows 10 deployment scenarios](../windows-10-deployment-scenarios.md)<br>
|
[Windows 10 deployment scenarios](../windows-10-deployment-scenarios.md)
|
||||||
[Windows upgrade and migration considerations](windows-upgrade-and-migration-considerations.md)<br>
|
|
||||||
|
[Windows upgrade and migration considerations](windows-upgrade-and-migration-considerations.md)
|
||||||
|
|
||||||
[Windows 10 edition upgrade](windows-10-edition-upgrades.md)
|
[Windows 10 edition upgrade](windows-10-edition-upgrades.md)
|
||||||
@ -34,43 +34,12 @@ When you select a product, for example “Windows 10 Enterprise” or “Windows
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> If you do not see a Windows 10 release available in the list of downloads, verify the [release date](https://technet.microsoft.com/windows/release-info.aspx).
|
> If you do not see a Windows 10 release available in the list of downloads, verify the [release date](https://technet.microsoft.com/windows/release-info.aspx).
|
||||||
|
|
||||||
In Windows 10, version 1709 the packaging of volume licensing media and upgrade packages is different than it has been for previous releases. Instead of having separate media and packages for Windows 10 Pro (volume licensing version), Windows 10 Enterprise, and Windows 10 Education, all three are bundled together. The following section explains this change.
|
Instead of having separate media and packages for Windows 10 Pro (volume licensing version), Windows 10 Enterprise, and Windows 10 Education, all three are bundled together.
|
||||||
|
|
||||||
### Windows 10, version 1709
|
|
||||||
|
|
||||||
Windows 10, version 1709 is available starting on 10/17/2017 in all relevant distribution channels. Note: An updated [Windows ADK for Windows 10](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) is also available.
|
|
||||||
|
|
||||||
For ISOs that you download from the VLSC or Visual Studio Subscriptions, you can still search for the individual Windows editions. However, each of these editions (Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education) will point to the same ISO file, so you only need to download the ISO once. A single Windows image (WIM) file is included in the ISO that contains all the volume licensing images:
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
When using the contents of these ISOs with tools such as the Microsoft Deployment Toolkit or Microsoft Endpoint Configuration Manager, make sure you select the appropriate image index in any task sequences that you create or update.
|
|
||||||
|
|
||||||
For packages published to Windows Server Update Services (WSUS), you’ll also notice the change because, instead of having separate packages for each Windows edition, there will be just one package:
|
|
||||||
|
|
||||||
<br>
|
|
||||||
|
|
||||||
| Title | Classification | Description |
|
|
||||||
| --- | --- | --- |
|
|
||||||
| Feature update to Windows 10, version 1709, \<language\> | Upgrades | Package to upgrade Windows 10 Pro (VL), Windows 10 Enterprise, or Windows 10 Education to version 1709 |
|
|
||||||
| Windows 7 and 8.1 upgrade to Windows 10, version 1709, \<language\> | Upgrades | Package to upgrade Windows 7 Professional (VL), Windows 7 Enterprise, Windows 8.1 Professional (VL), or Windows 8.1 Enterprise to Windows 10 1709 |
|
|
||||||
|
|
||||||
<br>
|
|
||||||
|
|
||||||
When you approve one of these packages, it applies to all of the editions.
|
|
||||||
|
|
||||||
This Semi-Annual Channel release of Windows 10 continues the Windows as a service methodology. For more information about implementing Windows as a service in your organization in order to stay up to date with Windows, see [Update Windows 10 in the enterprise](./update/index.md).
|
|
||||||
|
|
||||||
|
|
||||||
### Language packs
|
### Language packs
|
||||||
|
|
||||||
- **Windows 10 versions 1507 and 1511**: you can select **Windows 10 Enterprise Language Pack**, click **Download** and then select **English** and **64-bit** to see these downloads.
|
|
||||||
- **Windows 10 1607 and later**: you must select **Multilanguage** from the drop-down list of languages.
|
- **Windows 10 1607 and later**: you must select **Multilanguage** from the drop-down list of languages.
|
||||||
|
|
||||||
See the following example for Windows 10, version 1709:
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Features on demand
|
### Features on demand
|
||||||
|
|
||||||
[Features on demand](/archive/blogs/mniehaus/adding-features-including-net-3-5-to-windows-10) can be downloaded by searching for "**Windows 10 Enterprise Features on Demand**" and then following the same download process that is described above.
|
[Features on demand](/archive/blogs/mniehaus/adding-features-including-net-3-5-to-windows-10) can be downloaded by searching for "**Windows 10 Enterprise Features on Demand**" and then following the same download process that is described above.
|
||||||
|
|||||||
@ -23,7 +23,7 @@ Applies to:
|
|||||||
- Windows 10
|
- Windows 10
|
||||||
- Windows 11
|
- Windows 11
|
||||||
|
|
||||||
Starting with Windows 10, version 1703, Windows 10 Pro supports the Subscription Activation feature, enabling users to “step-up” from Windows 10 Pro or Windows 11 Pro to **Windows 10 Enterprise** or **Windows 11 Enterprise**, respectively, if they are subscribed to Windows 10/11 Enterprise E3 or E5.
|
Windows 10 Pro supports the Subscription Activation feature, enabling users to “step-up” from Windows 10 Pro or Windows 11 Pro to **Windows 10 Enterprise** or **Windows 11 Enterprise**, respectively, if they are subscribed to Windows 10/11 Enterprise E3 or E5.
|
||||||
|
|
||||||
With Windows 10, version 1903 and later, the Subscription Activation feature also supports the ability to step-up from Windows 10 Pro Education or Windows 11 Pro Education to the Enterprise grade editions for educational institutions—**Windows 10 Education** or **Windows 11 Education**.
|
With Windows 10, version 1903 and later, the Subscription Activation feature also supports the ability to step-up from Windows 10 Pro Education or Windows 11 Pro Education to the Enterprise grade editions for educational institutions—**Windows 10 Education** or **Windows 11 Education**.
|
||||||
|
|
||||||
@ -44,9 +44,10 @@ For information on how to deploy Enterprise licenses, see [Deploy Windows 10/11
|
|||||||
|
|
||||||
## Subscription Activation for Windows 10/11 Enterprise
|
## Subscription Activation for Windows 10/11 Enterprise
|
||||||
|
|
||||||
With Windows 10, version 1703 and later both Windows 10/11 Enterprise E3 and Windows 10/11 Enterprise E5 are available as online services via subscription. Deploying Windows 10 Enterprise or Windows 11 Enterprise in your organization can now be accomplished with no keys and no reboots.
|
Windows 10/11 Enterprise E3 and Windows 10/11 Enterprise E5 are available as online services via subscription. Deploying Windows 10 Enterprise or Windows 11 Enterprise in your organization can now be accomplished with no keys and no reboots.
|
||||||
|
|
||||||
If you are running Windows 10, version 1703 or later:
|
If you are running Windows 10, version 1703 or later:
|
||||||
|
|
||||||
- Devices with a current Windows 10 Pro license or Windows 11 Pro license can be seamlessly upgraded to Windows 10 Enterprise or Windows 11 Enterprise, respectively.
|
- Devices with a current Windows 10 Pro license or Windows 11 Pro license can be seamlessly upgraded to Windows 10 Enterprise or Windows 11 Enterprise, respectively.
|
||||||
- Product key-based Windows 10 Enterprise or Windows 11 Enterprise software licenses can be transitioned to Windows 10 Enterprise and Windows 11 Enterprise subscriptions.
|
- Product key-based Windows 10 Enterprise or Windows 11 Enterprise software licenses can be transitioned to Windows 10 Enterprise and Windows 11 Enterprise subscriptions.
|
||||||
|
|
||||||
@ -109,8 +110,6 @@ An issue has been identified with Hybrid Azure AD joined devices that have enabl
|
|||||||
|
|
||||||
To resolve this issue:
|
To resolve this issue:
|
||||||
|
|
||||||
If the device is running Windows 10, version 1703, 1709, or 1803, the user must either sign in with an Azure AD account, or you must disable MFA for this user during the 30-day polling period and renewal.
|
|
||||||
|
|
||||||
If the device is running Windows 10, version 1809 or later:
|
If the device is running Windows 10, version 1809 or later:
|
||||||
|
|
||||||
- Windows 10, version 1809 must be updated with [KB4497934](https://support.microsoft.com/help/4497934/windows-10-update-kb4497934). Later versions of Windows 10 automatically include this patch.
|
- Windows 10, version 1809 must be updated with [KB4497934](https://support.microsoft.com/help/4497934/windows-10-update-kb4497934). Later versions of Windows 10 automatically include this patch.
|
||||||
@ -166,7 +165,7 @@ The IT administrator assigns Windows 10 Enterprise to a user. See the following
|
|||||||
|
|
||||||
When a licensed user signs in to a device that meets requirements using their Azure AD credentials, the operating system steps up from Windows 10 Pro to Windows 10 Enterprise (or Windows 10 Pro Education to Windows 10 Education) and all the appropriate Windows 10 Enterprise/Education features are unlocked. When a user’s subscription expires or is transferred to another user, the device reverts seamlessly to Windows 10 Pro / Windows 10 Pro Education edition, once current subscription validity expires.
|
When a licensed user signs in to a device that meets requirements using their Azure AD credentials, the operating system steps up from Windows 10 Pro to Windows 10 Enterprise (or Windows 10 Pro Education to Windows 10 Education) and all the appropriate Windows 10 Enterprise/Education features are unlocked. When a user’s subscription expires or is transferred to another user, the device reverts seamlessly to Windows 10 Pro / Windows 10 Pro Education edition, once current subscription validity expires.
|
||||||
|
|
||||||
Devices running Windows 10 Pro, version 1703 or Windows 10 Pro Education, version 1903 or later can get Windows 10 Enterprise or Education Semi-Annual Channel on up to five devices for each user covered by the license. This benefit does not include Long Term Servicing Channel.
|
Devices running Windows 10 Pro Education, version 1903 or later can get Windows 10 Enterprise or Education General Availability Channel on up to five devices for each user covered by the license. This benefit does not include Long Term Servicing Channel.
|
||||||
|
|
||||||
The following figures summarize how the Subscription Activation model works:
|
The following figures summarize how the Subscription Activation model works:
|
||||||
|
|
||||||
@ -192,18 +191,6 @@ All of your Windows 10 Pro devices will step-up to Windows 10 Enterprise, and de
|
|||||||
|
|
||||||
#### Scenario #2
|
#### Scenario #2
|
||||||
|
|
||||||
You are using Windows 10, version 1607, 1703, or 1709 with KMS for activation, and just purchased Windows 10 Enterprise E3 or E5 subscriptions (or have had an E3 or E5 subscription for a while but haven’t yet deployed Windows 10 Enterprise).
|
|
||||||
|
|
||||||
To change all of your Windows 10 Pro devices to Windows 10 Enterprise, run the following command on each computer:
|
|
||||||
|
|
||||||
```console
|
|
||||||
cscript.exe c:\windows\system32\slmgr.vbs /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
|
|
||||||
```
|
|
||||||
|
|
||||||
The command causes the OS to change to Windows 10 Enterprise and then seek out the KMS server to reactivate. This key comes from [Appendix A: KMS Client Setup Keys](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612867(v=ws.11)) in the Volume Activation guide. It is also possible to inject the Windows 10 Pro key from this article if you wish to step back down from Enterprise to Pro.
|
|
||||||
|
|
||||||
#### Scenario #3
|
|
||||||
|
|
||||||
Using Azure AD-joined devices or Active Directory-joined devices running Windows 10 1709 or later, and with Azure AD synchronization configured, just follow the steps in [Deploy Windows 10 Enterprise licenses](deploy-enterprise-licenses.md) to acquire a $0 SKU and get a new Windows 10 Enterprise E3 or E5 license in Azure AD. Then, assign that license to all of your Azure AD users. These can be AD-synced accounts. The device will automatically change from Windows 10 Pro to Windows 10 Enterprise when that user signs in.
|
Using Azure AD-joined devices or Active Directory-joined devices running Windows 10 1709 or later, and with Azure AD synchronization configured, just follow the steps in [Deploy Windows 10 Enterprise licenses](deploy-enterprise-licenses.md) to acquire a $0 SKU and get a new Windows 10 Enterprise E3 or E5 license in Azure AD. Then, assign that license to all of your Azure AD users. These can be AD-synced accounts. The device will automatically change from Windows 10 Pro to Windows 10 Enterprise when that user signs in.
|
||||||
|
|
||||||
In summary, if you have a Windows 10 Enterprise E3 or E5 subscription, but are still running Windows 10 Pro, it’s really simple (and quick) to move to Windows 10 Enterprise using one of the scenarios above.
|
In summary, if you have a Windows 10 Enterprise E3 or E5 subscription, but are still running Windows 10 Pro, it’s really simple (and quick) to move to Windows 10 Enterprise using one of the scenarios above.
|
||||||
|
|||||||
@ -47,7 +47,7 @@ These are the things you'll need to complete this lab:
|
|||||||
|
|
||||||
| | Description |
|
| | Description |
|
||||||
|:---|:---|
|
|:---|:---|
|
||||||
|**Windows 10 installation media**|Windows 10 Professional or Enterprise (ISO file) for a supported version of Windows 10, semi-annual channel. If you don't already have an ISO to use, a link is provided to download an <a href="https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise" data-raw-source="[evaluation version of Windows 10 Enterprise](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise)">evaluation version of Windows 10 Enterprise</a>.|
|
|**Windows 10 installation media**|Windows 10 Professional or Enterprise (ISO file) for a supported version of Windows 10, General Availability Channel. If you don't already have an ISO to use, a link is provided to download an <a href="https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise" data-raw-source="[evaluation version of Windows 10 Enterprise](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise)">evaluation version of Windows 10 Enterprise</a>.|
|
||||||
|**Internet access**|If you're behind a firewall, see the detailed <a href="/mem/autopilot/software-requirements#networking-requirements" data-raw-source="[networking requirements](/mem/autopilot/software-requirements#networking-requirements)">networking requirements</a>. Otherwise, just ensure that you have a connection to the internet.|
|
|**Internet access**|If you're behind a firewall, see the detailed <a href="/mem/autopilot/software-requirements#networking-requirements" data-raw-source="[networking requirements](/mem/autopilot/software-requirements#networking-requirements)">networking requirements</a>. Otherwise, just ensure that you have a connection to the internet.|
|
||||||
|**Hyper-V or a physical device running Windows 10**|The guide assumes that you'll use a Hyper-V VM, and provides instructions to install and configure Hyper-V if needed. To use a physical device, skip the steps to install and configure Hyper-V.|
|
|**Hyper-V or a physical device running Windows 10**|The guide assumes that you'll use a Hyper-V VM, and provides instructions to install and configure Hyper-V if needed. To use a physical device, skip the steps to install and configure Hyper-V.|
|
||||||
|**An account with Azure Active Directory (AD) Premium license**|This guide will describe how to obtain a free 30-day trial Azure AD Premium subscription that can be used to complete the lab.|
|
|**An account with Azure Active Directory (AD) Premium license**|This guide will describe how to obtain a free 30-day trial Azure AD Premium subscription that can be used to complete the lab.|
|
||||||
|
|||||||
@ -13,7 +13,7 @@ manager: dansimp
|
|||||||
ms.collection: M365-security-compliance
|
ms.collection: M365-security-compliance
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
audience: ITPro
|
audience: ITPro
|
||||||
ms.date: 09/08/2021
|
ms.date:
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -34,7 +34,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
||||||
- [Windows 10, version 20H2 and Windows 10, version 2004 basic diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
- [Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||||
- [Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
- [Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
||||||
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||||
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||||
|
|||||||
@ -13,7 +13,7 @@ manager: dansimp
|
|||||||
ms.collection: M365-security-compliance
|
ms.collection: M365-security-compliance
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
audience: ITPro
|
audience: ITPro
|
||||||
ms.date: 09/08/2021
|
ms.date:
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -34,7 +34,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
||||||
- [Windows 10, version 20H2 and Windows 10, version 2004 basic diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
- [Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||||
- [Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
- [Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
||||||
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||||
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||||
@ -3029,22 +3029,6 @@ The following fields are available:
|
|||||||
|
|
||||||
- **winInetError** The HResult of the operation.
|
- **winInetError** The HResult of the operation.
|
||||||
|
|
||||||
|
|
||||||
## Other events
|
|
||||||
|
|
||||||
### Microsoft.ServerManagementExperience.Gateway.Service.ManagedNodeProperties
|
|
||||||
|
|
||||||
This is a periodic rundown event that contains more detailed information about the nodes added to this Windows Admin Center gateway for management.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **nodeId** The nodeTypeId concatenated with the hostname or IP address that gateway uses to connect to this node.
|
|
||||||
- **nodeOperatingSystem** A user friendly description of the node's OS version.
|
|
||||||
- **nodeOSVersion** A major or minor build version string for the node's OS.
|
|
||||||
- **nodeTypeId** A string that distinguishes between a connection target, whether it is a client, server, cluster or a hyper-converged cluster.
|
|
||||||
- **otherProperties** Contains a JSON object with variable content and may contain: "nodes": a list of host names or IP addresses of the servers belonging to a cluster, "aliases": the alias if it is set for this connection, "lastUpdatedTime": the number of milliseconds since Unix epoch when this connection was last updated, "ncUri", "caption", "version", "productType", "networkName", "operatingSystem", "computerManufacturer", "computerModel", "isS2dEnabled". This JSON object is formatted as an quotes-escaped string.
|
|
||||||
|
|
||||||
|
|
||||||
## Privacy logging notification events
|
## Privacy logging notification events
|
||||||
|
|
||||||
### Microsoft.Windows.Shell.PrivacyNotifierLogging.PrivacyNotifierCompleted
|
### Microsoft.Windows.Shell.PrivacyNotifierLogging.PrivacyNotifierCompleted
|
||||||
|
|||||||
@ -13,7 +13,7 @@ manager: dansimp
|
|||||||
ms.collection: M365-security-compliance
|
ms.collection: M365-security-compliance
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
audience: ITPro
|
audience: ITPro
|
||||||
ms.date: 09/08/2021
|
ms.date:
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -34,7 +34,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
||||||
- [Windows 10, version 20H2 and Windows 10, version 2004 basic diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
- [Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||||
- [Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
- [Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
||||||
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||||
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
||||||
@ -44,7 +44,6 @@ You can learn more about Windows functional and diagnostic data through these ar
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Appraiser events
|
## Appraiser events
|
||||||
|
|
||||||
### Microsoft.Windows.Appraiser.General.ChecksumTotalPictureCount
|
### Microsoft.Windows.Appraiser.General.ChecksumTotalPictureCount
|
||||||
@ -4370,14 +4369,6 @@ The following fields are available:
|
|||||||
|
|
||||||
## Other events
|
## Other events
|
||||||
|
|
||||||
### Microsoft.Surface.Battery.Prod.BatteryInfoEvent
|
|
||||||
|
|
||||||
This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **pszBatteryDataXml** Battery performance data.
|
|
||||||
- **szBatteryInfo** Battery performance data.
|
|
||||||
|
|
||||||
|
|
||||||
## Privacy consent logging events
|
## Privacy consent logging events
|
||||||
@ -5473,6 +5464,17 @@ The following fields are available:
|
|||||||
- **UpdateId** The update ID for a specific piece of content.
|
- **UpdateId** The update ID for a specific piece of content.
|
||||||
- **ValidityWindowInDays** The validity window that's in effect when verifying the timestamp.
|
- **ValidityWindowInDays** The validity window that's in effect when verifying the timestamp.
|
||||||
|
|
||||||
|
## Surface events
|
||||||
|
|
||||||
|
### Microsoft.Surface.Battery.Prod.BatteryInfoEvent
|
||||||
|
|
||||||
|
This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **pszBatteryDataXml** Battery performance data.
|
||||||
|
- **szBatteryInfo** Battery performance data.
|
||||||
|
|
||||||
|
|
||||||
## Update Assistant events
|
## Update Assistant events
|
||||||
|
|
||||||
|
|||||||
@ -13,7 +13,7 @@ manager: dansimp
|
|||||||
ms.collection: M365-security-compliance
|
ms.collection: M365-security-compliance
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
audience: ITPro
|
audience: ITPro
|
||||||
ms.date: 09/08/2021
|
ms.date:
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -24,7 +24,6 @@ ms.reviewer:
|
|||||||
|
|
||||||
- Windows 10, version 1809
|
- Windows 10, version 1809
|
||||||
|
|
||||||
|
|
||||||
The Basic level gathers a limited set of information that is critical for understanding the device and its configuration including: basic device information, quality-related information, app compatibility, and Microsoft Store. When the level is set to Basic, it also includes the Security level information.
|
The Basic level gathers a limited set of information that is critical for understanding the device and its configuration including: basic device information, quality-related information, app compatibility, and Microsoft Store. When the level is set to Basic, it also includes the Security level information.
|
||||||
|
|
||||||
The Basic level helps to identify problems that can occur on a particular device hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a particular driver version. This helps Microsoft fix operating system or app problems.
|
The Basic level helps to identify problems that can occur on a particular device hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a particular driver version. This helps Microsoft fix operating system or app problems.
|
||||||
@ -34,7 +33,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
||||||
- [Windows 10, version 20H2 and Windows 10, version 2004 basic diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
- [Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||||
- [Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
- [Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
||||||
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||||
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
||||||
@ -5790,36 +5789,6 @@ The following fields are available:
|
|||||||
- **totalRunDuration** Total running/evaluation time from last time.
|
- **totalRunDuration** Total running/evaluation time from last time.
|
||||||
- **totalRuns** Total number of running/evaluation from last time.
|
- **totalRuns** Total number of running/evaluation from last time.
|
||||||
|
|
||||||
|
|
||||||
## Other events
|
|
||||||
|
|
||||||
### Microsoft.ServerManagementExperience.Gateway.Service.ManagedNodeProperties
|
|
||||||
|
|
||||||
This is a periodic rundown event that contains more detailed information about the nodes added to this Windows Admin Center gateway for management.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **nodeId** The nodeTypeId concatenated with the hostname or IP address that gateway uses to connect to this node.
|
|
||||||
- **nodeOperatingSystem** A user friendly description of the node's OS version.
|
|
||||||
- **nodeOSVersion** A major or minor build version string for the node's OS.
|
|
||||||
- **nodeTypeId** A string that distinguishes between a connection target, whether it is a client, server, cluster or a hyper-converged cluster.
|
|
||||||
- **otherProperties** Contains a JSON object with variable content and may contain: "nodes": a list of host names or IP addresses of the servers belonging to a cluster, "aliases": the alias if it is set for this connection, "lastUpdatedTime": the number of milliseconds since Unix epoch when this connection was last updated, "ncUri", "caption", "version", "productType", "networkName", "operatingSystem", "computerManufacturer", "computerModel", "isS2dEnabled". This JSON object is formatted as an quotes-escaped string.
|
|
||||||
|
|
||||||
|
|
||||||
### Microsoft.Surface.Battery.Prod.BatteryInfoEvent
|
|
||||||
|
|
||||||
This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **batteryData.data()** Battery performance data.
|
|
||||||
- **BatteryDataSize:** Size of the battery performance data.
|
|
||||||
- **batteryInfo.data()** Battery performance data.
|
|
||||||
- **BatteryInfoSize:** Size of the battery performance data.
|
|
||||||
- **pszBatteryDataXml** Battery performance data.
|
|
||||||
- **szBatteryInfo** Battery performance data.
|
|
||||||
|
|
||||||
|
|
||||||
## Privacy consent logging events
|
## Privacy consent logging events
|
||||||
|
|
||||||
### Microsoft.Windows.Shell.PrivacyConsentLogging.PrivacyConsentCompleted
|
### Microsoft.Windows.Shell.PrivacyConsentLogging.PrivacyConsentCompleted
|
||||||
@ -7029,6 +6998,22 @@ The following fields are available:
|
|||||||
- **UpdateId** The update ID for a specific piece of content.
|
- **UpdateId** The update ID for a specific piece of content.
|
||||||
- **ValidityWindowInDays** The validity window that's in effect when verifying the timestamp.
|
- **ValidityWindowInDays** The validity window that's in effect when verifying the timestamp.
|
||||||
|
|
||||||
|
## Surface events
|
||||||
|
|
||||||
|
### Microsoft.Surface.Battery.Prod.BatteryInfoEvent
|
||||||
|
|
||||||
|
This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **batteryData.data()** Battery performance data.
|
||||||
|
- **BatteryDataSize:** Size of the battery performance data.
|
||||||
|
- **batteryInfo.data()** Battery performance data.
|
||||||
|
- **BatteryInfoSize:** Size of the battery performance data.
|
||||||
|
- **pszBatteryDataXml** Battery performance data.
|
||||||
|
- **szBatteryInfo** Battery performance data.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## System Resource Usage Monitor events
|
## System Resource Usage Monitor events
|
||||||
|
|
||||||
|
|||||||
@ -13,7 +13,7 @@ manager: dansimp
|
|||||||
ms.collection: M365-security-compliance
|
ms.collection: M365-security-compliance
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
audience: ITPro
|
audience: ITPro
|
||||||
ms.date: 09/08/2021
|
ms.date:
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
||||||
@ -39,7 +39,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
- [Required Windows 11 diagnostic events and fields](required-windows-11-diagnostic-events-and-fields.md)
|
||||||
- [Windows 10, version 20H2 and Windows 10, version 2004 basic diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
- [Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||||
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||||
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||||
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
||||||
@ -277,6 +277,8 @@ The following fields are available:
|
|||||||
- **DatasourceApplicationFile_20H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_21H1** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_21H1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_21H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceApplicationFile_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceApplicationFile_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_RS1** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_RS1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_RS2** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_RS2** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_RS3** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_RS3** The total number of objects of this type present on this device.
|
||||||
@ -290,6 +292,8 @@ The following fields are available:
|
|||||||
- **DatasourceDevicePnp_20H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_21H1** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_21H1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_21H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceDevicePnp_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceDevicePnp_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_RS1** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_RS1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_RS2** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_RS2** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_RS3** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_RS3** The total number of objects of this type present on this device.
|
||||||
@ -306,6 +310,8 @@ The following fields are available:
|
|||||||
- **DatasourceDriverPackage_20H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_21H1** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_21H1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_21H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceDriverPackage_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceDriverPackage_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_RS1** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_RS1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_RS2** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_RS2** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_RS3** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_RS3** The total number of objects of this type present on this device.
|
||||||
@ -322,6 +328,8 @@ The following fields are available:
|
|||||||
- **DataSourceMatchingInfoBlock_20H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_21H1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_21H1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_21H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoBlock_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoBlock_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_RS1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_RS1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_RS2** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_RS2** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_RS3** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_RS3** The total number of objects of this type present on this device.
|
||||||
@ -335,6 +343,8 @@ The following fields are available:
|
|||||||
- **DataSourceMatchingInfoPassive_20H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_21H1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_21H1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_21H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoPassive_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoPassive_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_RS1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_RS1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_RS2** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_RS2** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_RS3** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_RS3** The total number of objects of this type present on this device.
|
||||||
@ -348,6 +358,8 @@ The following fields are available:
|
|||||||
- **DataSourceMatchingInfoPostUpgrade_20H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_21H1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_21H1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_21H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoPostUpgrade_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoPostUpgrade_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_RS1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_RS1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_RS2** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_RS2** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_RS3** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_RS3** The total number of objects of this type present on this device.
|
||||||
@ -362,6 +374,8 @@ The following fields are available:
|
|||||||
- **DatasourceSystemBios_20H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_21H1** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_21H1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_21H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceSystemBios_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceSystemBios_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_RS1** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_RS1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_RS2** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_RS2** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_RS3** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_RS3** The total number of objects of this type present on this device.
|
||||||
@ -378,6 +392,8 @@ The following fields are available:
|
|||||||
- **DecisionApplicationFile_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_21H1** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionApplicationFile_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionApplicationFile_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_RS1** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_RS2** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_RS3** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_RS3** The total number of objects of this type present on this device.
|
||||||
@ -391,6 +407,8 @@ The following fields are available:
|
|||||||
- **DecisionDevicePnp_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_21H1** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionDevicePnp_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionDevicePnp_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_RS1** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_RS2** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_RS3** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_RS3** The total number of objects of this type present on this device.
|
||||||
@ -407,6 +425,8 @@ The following fields are available:
|
|||||||
- **DecisionDriverPackage_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_21H1** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionDriverPackage_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionDriverPackage_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_RS1** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_RS2** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_RS3** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_RS3** The total number of objects of this type present on this device.
|
||||||
@ -423,6 +443,8 @@ The following fields are available:
|
|||||||
- **DecisionMatchingInfoBlock_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_21H1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoBlock_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoBlock_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_RS1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_RS2** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_RS3** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_RS3** The total number of objects of this type present on this device.
|
||||||
@ -436,6 +458,8 @@ The following fields are available:
|
|||||||
- **DecisionMatchingInfoPassive_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_21H1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoPassive_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoPassive_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_RS1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_RS2** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_RS3** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_RS3** The total number of objects of this type present on this device.
|
||||||
@ -449,6 +473,8 @@ The following fields are available:
|
|||||||
- **DecisionMatchingInfoPostUpgrade_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_21H1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoPostUpgrade_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoPostUpgrade_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_RS1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_RS2** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_RS3** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_RS3** The total number of objects of this type present on this device.
|
||||||
@ -462,6 +488,8 @@ The following fields are available:
|
|||||||
- **DecisionMediaCenter_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_21H1** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMediaCenter_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMediaCenter_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_RS1** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_RS2** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_RS3** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_RS3** The total number of objects of this type present on this device.
|
||||||
@ -469,17 +497,19 @@ The following fields are available:
|
|||||||
- **DecisionMediaCenter_RS5** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_RS5** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_TH1** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_TH1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_TH2** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_TH2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_19H1** The total number of objects of this type present on this device.
|
- **DecisionSModeState_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_20H1** The total number of objects of this type present on this device.
|
- **DecisionSModeState_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSModeState_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_21H1** The total number of objects of this type present on this device.
|
- **DecisionSModeState_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_RS1** The total number of objects of this type present on this device.
|
- **DecisionSModeState_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_RS2** The total number of objects of this type present on this device.
|
- **DecisionSModeState_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_RS3** The total number of objects of this type present on this device.
|
- **DecisionSModeState_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_RS4** The total number of objects of this type present on this device.
|
- **DecisionSModeState_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_RS5** The total number of objects of this type present on this device.
|
- **DecisionSModeState_RS3** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_TH1** The total number of objects of this type present on this device.
|
- **DecisionSModeState_RS4** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_TH2** The total number of objects of this type present on this device.
|
- **DecisionSModeState_RS5** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSModeState_TH1** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSModeState_TH2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_19ASetup** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_19ASetup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_19H1** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_19H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_19H1Setup** The total number of objects of this type present on this device.
|
||||||
@ -487,6 +517,8 @@ The following fields are available:
|
|||||||
- **DecisionSystemBios_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemBios_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemBios_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_RS3** The total number of objects of this type present on this device.
|
||||||
@ -497,67 +529,79 @@ The following fields are available:
|
|||||||
- **DecisionSystemBios_RS5Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_RS5Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_TH1** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_TH1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_TH2** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_TH2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_19H1** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_20H1** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_RS4** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_RS5** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_RS3** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_TH1** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_RS4** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_TH2** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_RS5** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_19H1** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_TH1** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemDiskSize_TH2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemMemory_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_20H1** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_RS4** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_RS5** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_RS3** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_TH1** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_RS4** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_TH2** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_RS5** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemMemory_TH1** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemMemory_TH2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessor_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessor_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_19H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_20H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_RS4** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_RS5** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_RS3** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_TH1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_RS4** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_TH2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_RS5** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_19H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_TH1** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuCores_TH2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuModel_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_20H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_RS4** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_RS5** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_RS3** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_TH1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_RS4** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_TH2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_RS5** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_19H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_TH1** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuModel_TH2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuSpeed_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_20H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_RS4** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_RS5** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_RS3** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_TH1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_RS4** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_TH2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_RS5** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuSpeed_TH1** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuSpeed_TH2** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_19H1** The total number of objects of this type present on this device.
|
- **DecisionTest_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_20H1** The total number of objects of this type present on this device.
|
- **DecisionTest_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionTest_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_21H1** The total number of objects of this type present on this device.
|
- **DecisionTest_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionTest_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionTest_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionTest_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_RS1** The total number of objects of this type present on this device.
|
- **DecisionTest_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_RS2** The total number of objects of this type present on this device.
|
- **DecisionTest_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_RS3** The total number of objects of this type present on this device.
|
- **DecisionTest_RS3** The total number of objects of this type present on this device.
|
||||||
@ -565,28 +609,32 @@ The following fields are available:
|
|||||||
- **DecisionTest_RS5** The total number of objects of this type present on this device.
|
- **DecisionTest_RS5** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_TH1** The total number of objects of this type present on this device.
|
- **DecisionTest_TH1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_TH2** The total number of objects of this type present on this device.
|
- **DecisionTest_TH2** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_19H1** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_20H1** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_21H1** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_RS1** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_RS2** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_RS3** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_RS4** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_RS5** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_RS3** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_TH1** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_RS4** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_TH2** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_RS5** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_19H1** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_TH1** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionTpmVersion_TH2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionUefiSecureBoot_19H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_20H1** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_20H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_21H1** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_RS1** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_RS2** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_RS3** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_RS4** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_RS5** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_RS3** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_TH1** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_RS4** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_TH2** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_RS5** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionUefiSecureBoot_TH1** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionUefiSecureBoot_TH2** The total number of objects of this type present on this device.
|
||||||
- **InventoryApplicationFile** The total number of objects of this type present on this device.
|
- **InventoryApplicationFile** The total number of objects of this type present on this device.
|
||||||
- **InventoryDeviceContainer** The total number of objects of this type present on this device.
|
- **InventoryDeviceContainer** The total number of objects of this type present on this device.
|
||||||
- **InventoryDevicePnp** The total number of objects of this type present on this device.
|
- **InventoryDevicePnp** The total number of objects of this type present on this device.
|
||||||
@ -616,6 +664,8 @@ The following fields are available:
|
|||||||
- **Wmdrm_20H1Setup** The total number of objects of this type present on this device.
|
- **Wmdrm_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_21H1** The total number of objects of this type present on this device.
|
- **Wmdrm_21H1** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_21H1Setup** The total number of objects of this type present on this device.
|
- **Wmdrm_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **Wmdrm_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **Wmdrm_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_RS1** The total number of objects of this type present on this device.
|
- **Wmdrm_RS1** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_RS2** The total number of objects of this type present on this device.
|
- **Wmdrm_RS2** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_RS3** The total number of objects of this type present on this device.
|
- **Wmdrm_RS3** The total number of objects of this type present on this device.
|
||||||
@ -4237,6 +4287,7 @@ The following fields are available:
|
|||||||
- **DriverInfSectionName** Name of the DDInstall section within the driver INF file.
|
- **DriverInfSectionName** Name of the DDInstall section within the driver INF file.
|
||||||
- **DriverPackageId** The ID of the driver package that is staged to the driver store.
|
- **DriverPackageId** The ID of the driver package that is staged to the driver store.
|
||||||
- **DriverProvider** The driver manufacturer or provider.
|
- **DriverProvider** The driver manufacturer or provider.
|
||||||
|
- **DriverShimIds** List of driver shim IDs.
|
||||||
- **DriverUpdated** Indicates whether the driver is replacing an old driver.
|
- **DriverUpdated** Indicates whether the driver is replacing an old driver.
|
||||||
- **DriverVersion** The version of the driver file.
|
- **DriverVersion** The version of the driver file.
|
||||||
- **EndTime** The time the installation completed.
|
- **EndTime** The time the installation completed.
|
||||||
@ -4614,13 +4665,13 @@ The following fields are available:
|
|||||||
- **Generic** A count of generic objects in cache.
|
- **Generic** A count of generic objects in cache.
|
||||||
- **HwItem** A count of hwitem objects in cache.
|
- **HwItem** A count of hwitem objects in cache.
|
||||||
- **InventoryAcpiPhatHealthRecord** A count of ACPI PHAT health records in cache.
|
- **InventoryAcpiPhatHealthRecord** A count of ACPI PHAT health records in cache.
|
||||||
- **InventoryAcpiPhatVersionElement** A count of ACPI PHAT version elements in cache
|
- **InventoryAcpiPhatVersionElement** A count of ACPI PHAT version elements in cache.
|
||||||
- **InventoryApplication** A count of application objects in cache.
|
- **InventoryApplication** A count of application objects in cache.
|
||||||
- **InventoryApplicationAppV** A count of application AppV objects in cache.
|
- **InventoryApplicationAppV** A count of application AppV objects in cache.
|
||||||
- **InventoryApplicationDriver** A count of application driver objects in cache
|
- **InventoryApplicationDriver** A count of application driver objects in cache.
|
||||||
- **InventoryApplicationFile** A count of application file objects in cache.
|
- **InventoryApplicationFile** A count of application file objects in cache.
|
||||||
- **InventoryApplicationFramework** A count of application framework objects in cache
|
- **InventoryApplicationFramework** A count of application framework objects in cache.
|
||||||
- **InventoryApplicationShortcut** A count of application shortcut objects in cache
|
- **InventoryApplicationShortcut** A count of application shortcut objects in cache.
|
||||||
- **InventoryDeviceContainer** A count of device container objects in cache.
|
- **InventoryDeviceContainer** A count of device container objects in cache.
|
||||||
- **InventoryDeviceInterface** A count of Plug and Play device interface objects in cache.
|
- **InventoryDeviceInterface** A count of Plug and Play device interface objects in cache.
|
||||||
- **InventoryDeviceMediaClass** A count of device media objects in cache.
|
- **InventoryDeviceMediaClass** A count of device media objects in cache.
|
||||||
@ -4631,14 +4682,14 @@ The following fields are available:
|
|||||||
- **InventoryDriverPackage** A count of device objects in cache.
|
- **InventoryDriverPackage** A count of device objects in cache.
|
||||||
- **InventoryMiscellaneousOfficeAddIn** A count of office add-in objects in cache
|
- **InventoryMiscellaneousOfficeAddIn** A count of office add-in objects in cache
|
||||||
- **InventoryMiscellaneousOfficeAddInUsage** A count of office add-in usage objects in cache.
|
- **InventoryMiscellaneousOfficeAddInUsage** A count of office add-in usage objects in cache.
|
||||||
- **InventoryMiscellaneousOfficeIdentifiers** A count of office identifier objects in cache
|
- **InventoryMiscellaneousOfficeIdentifiers** A count of office identifier objects in cache.
|
||||||
- **InventoryMiscellaneousOfficeIESettings** A count of office ie settings objects in cache
|
- **InventoryMiscellaneousOfficeIESettings** A count of office ie settings objects in cache.
|
||||||
- **InventoryMiscellaneousOfficeInsights** A count of office insights objects in cache
|
- **InventoryMiscellaneousOfficeInsights** A count of office insights objects in cache.
|
||||||
- **InventoryMiscellaneousOfficeProducts** A count of office products objects in cache
|
- **InventoryMiscellaneousOfficeProducts** A count of office products objects in cache.
|
||||||
- **InventoryMiscellaneousOfficeSettings** A count of office settings objects in cache
|
- **InventoryMiscellaneousOfficeSettings** A count of office settings objects in cache.
|
||||||
- **InventoryMiscellaneousOfficeVBA** A count of office vba objects in cache
|
- **InventoryMiscellaneousOfficeVBA** A count of office vba objects in cache.
|
||||||
- **InventoryMiscellaneousOfficeVBARuleViolations** A count of office vba rule violations objects in cache
|
- **InventoryMiscellaneousOfficeVBARuleViolations** A count of office vba rule violations objects in cache.
|
||||||
- **InventoryMiscellaneousUUPInfo** A count of uup info objects in cache
|
- **InventoryMiscellaneousUUPInfo** A count of uup info objects in cache.
|
||||||
- **InventoryVersion** The version of the inventory binary generating the events.
|
- **InventoryVersion** The version of the inventory binary generating the events.
|
||||||
- **Metadata** A count of metadata objects in cache.
|
- **Metadata** A count of metadata objects in cache.
|
||||||
- **Orphan** A count of orphan file objects in cache.
|
- **Orphan** A count of orphan file objects in cache.
|
||||||
@ -5896,27 +5947,6 @@ The following fields are available:
|
|||||||
- **ModelName** Windows Mixed Reality device model name.
|
- **ModelName** Windows Mixed Reality device model name.
|
||||||
- **SerialNumber** Windows Mixed Reality device serial number.
|
- **SerialNumber** Windows Mixed Reality device serial number.
|
||||||
|
|
||||||
|
|
||||||
## OneDrive events
|
|
||||||
|
|
||||||
### Microsoft.OneDrive.Sync.Setup.OSUpgradeInstallationOperation
|
|
||||||
|
|
||||||
This event is related to the OS version when the OS is upgraded with OneDrive installed. The data collected with this event is used to help keep Windows up to date, secure, and performing properly.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **CurrentOneDriveVersion** The current version of OneDrive.
|
|
||||||
- **CurrentOSBuildBranch** The current branch of the operating system.
|
|
||||||
- **CurrentOSBuildNumber** The current build number of the operating system.
|
|
||||||
- **CurrentOSVersion** The current version of the operating system.
|
|
||||||
- **HResult** The HResult of the operation.
|
|
||||||
- **SourceOSBuildBranch** The source branch of the operating system.
|
|
||||||
- **SourceOSBuildNumber** The source build number of the operating system.
|
|
||||||
- **SourceOSVersion** The source version of the operating system.
|
|
||||||
|
|
||||||
|
|
||||||
## Other events
|
|
||||||
|
|
||||||
### Microsoft.ML.ONNXRuntime.ProcessInfo
|
### Microsoft.ML.ONNXRuntime.ProcessInfo
|
||||||
|
|
||||||
This event collects information when an application loads ONNXRuntime.dll. The data collected with this event is used to keep Windows product and service performing properly.
|
This event collects information when an application loads ONNXRuntime.dll. The data collected with this event is used to keep Windows product and service performing properly.
|
||||||
@ -5941,21 +5971,52 @@ The following fields are available:
|
|||||||
- **totalRunDuration** Total running/evaluation time from last time.
|
- **totalRunDuration** Total running/evaluation time from last time.
|
||||||
- **totalRuns** Total number of running/evaluation from last time.
|
- **totalRuns** Total number of running/evaluation from last time.
|
||||||
|
|
||||||
|
## OneDrive events
|
||||||
|
|
||||||
### Microsoft.Surface.Battery.Prod.BatteryInfoEvent
|
### Microsoft.OneDrive.Sync.Setup.OSUpgradeInstallationOperation
|
||||||
|
|
||||||
This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly.
|
This event is related to the OS version when the OS is upgraded with OneDrive installed. The data collected with this event is used to help keep Windows up to date, secure, and performing properly.
|
||||||
|
|
||||||
The following fields are available:
|
The following fields are available:
|
||||||
|
|
||||||
- **batteryData** Hardware level data about battery performance.
|
- **CurrentOneDriveVersion** The current version of OneDrive.
|
||||||
- **batteryData.data()** Battery performance data.
|
- **CurrentOSBuildBranch** The current branch of the operating system.
|
||||||
- **BatteryDataSize:** Size of the battery performance data.
|
- **CurrentOSBuildNumber** The current build number of the operating system.
|
||||||
- **batteryInfo.data()** Battery performance data.
|
- **CurrentOSVersion** The current version of the operating system.
|
||||||
- **BatteryInfoSize:** Battery performance data.
|
- **HResult** The HResult of the operation.
|
||||||
- **pszBatteryDataXml** Battery performance data.
|
- **SourceOSBuildBranch** The source branch of the operating system.
|
||||||
- **szBatteryInfo** Battery performance data.
|
- **SourceOSBuildNumber** The source build number of the operating system.
|
||||||
|
- **SourceOSVersion** The source version of the operating system.
|
||||||
|
|
||||||
|
## Privacy consent logging events
|
||||||
|
|
||||||
|
### Microsoft.Windows.Shell.PrivacyConsentLogging.PrivacyConsentCompleted
|
||||||
|
|
||||||
|
This event is used to determine whether the user successfully completed the privacy consent experience. The data collected with this event is used to help keep Windows up to date.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **presentationVersion** Which display version of the privacy consent experience the user completed
|
||||||
|
- **privacyConsentState** The current state of the privacy consent experience
|
||||||
|
- **settingsVersion** Which setting version of the privacy consent experience the user completed
|
||||||
|
- **userOobeExitReason** The exit reason of the privacy consent experience
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Windows.Shell.PrivacyConsentLogging.PrivacyConsentStatus
|
||||||
|
|
||||||
|
This event provides the effectiveness of new privacy experience. The data collected with this event is used to help keep Windows up to date.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **isAdmin** whether the person who is logging in is an admin
|
||||||
|
- **isExistingUser** whether the account existed in a downlevel OS
|
||||||
|
- **isLaunching** Whether or not the privacy consent experience will be launched
|
||||||
|
- **isSilentElevation** whether the user has most restrictive UAC controls
|
||||||
|
- **privacyConsentState** whether the user has completed privacy experience
|
||||||
|
- **userRegionCode** The current user's region setting
|
||||||
|
|
||||||
|
|
||||||
|
## Update Assistant events
|
||||||
|
|
||||||
### Microsoft.Windows.UpdateHealthTools.ExpediteBlocked
|
### Microsoft.Windows.UpdateHealthTools.ExpediteBlocked
|
||||||
|
|
||||||
@ -6336,37 +6397,6 @@ The following fields are available:
|
|||||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
||||||
- **PackageVersion** Current package version of remediation.
|
- **PackageVersion** Current package version of remediation.
|
||||||
|
|
||||||
|
|
||||||
## Privacy consent logging events
|
|
||||||
|
|
||||||
### Microsoft.Windows.Shell.PrivacyConsentLogging.PrivacyConsentCompleted
|
|
||||||
|
|
||||||
This event is used to determine whether the user successfully completed the privacy consent experience. The data collected with this event is used to help keep Windows up to date.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **presentationVersion** Which display version of the privacy consent experience the user completed
|
|
||||||
- **privacyConsentState** The current state of the privacy consent experience
|
|
||||||
- **settingsVersion** Which setting version of the privacy consent experience the user completed
|
|
||||||
- **userOobeExitReason** The exit reason of the privacy consent experience
|
|
||||||
|
|
||||||
|
|
||||||
### Microsoft.Windows.Shell.PrivacyConsentLogging.PrivacyConsentStatus
|
|
||||||
|
|
||||||
This event provides the effectiveness of new privacy experience. The data collected with this event is used to help keep Windows up to date.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **isAdmin** whether the person who is logging in is an admin
|
|
||||||
- **isExistingUser** whether the account existed in a downlevel OS
|
|
||||||
- **isLaunching** Whether or not the privacy consent experience will be launched
|
|
||||||
- **isSilentElevation** whether the user has most restrictive UAC controls
|
|
||||||
- **privacyConsentState** whether the user has completed privacy experience
|
|
||||||
- **userRegionCode** The current user's region setting
|
|
||||||
|
|
||||||
|
|
||||||
## Quality Update Assistant events
|
|
||||||
|
|
||||||
### Microsoft.Windows.QualityUpdateAssistant.Applicability
|
### Microsoft.Windows.QualityUpdateAssistant.Applicability
|
||||||
|
|
||||||
This event sends basic info on whether the device should be updated to the latest cumulative update. The data collected with this event is used to help keep Windows up to date and secure.
|
This event sends basic info on whether the device should be updated to the latest cumulative update. The data collected with this event is used to help keep Windows up to date and secure.
|
||||||
@ -7037,6 +7067,19 @@ The following fields are available:
|
|||||||
- **healthLogSize** 4KB.
|
- **healthLogSize** 4KB.
|
||||||
- **productId** Identifier for product model.
|
- **productId** Identifier for product model.
|
||||||
|
|
||||||
|
### Microsoft.Surface.Battery.Prod.BatteryInfoEvent
|
||||||
|
|
||||||
|
This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **batteryData** Hardware level data about battery performance.
|
||||||
|
- **batteryData.data()** Battery performance data.
|
||||||
|
- **BatteryDataSize:** Size of the battery performance data.
|
||||||
|
- **batteryInfo.data()** Battery performance data.
|
||||||
|
- **BatteryInfoSize:** Battery performance data.
|
||||||
|
- **pszBatteryDataXml** Battery performance data.
|
||||||
|
- **szBatteryInfo** Battery performance data.
|
||||||
|
|
||||||
## System reset events
|
## System reset events
|
||||||
|
|
||||||
|
|||||||
@ -36,7 +36,7 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
|||||||
|
|
||||||
You can learn more about Windows functional and diagnostic data through these articles:
|
You can learn more about Windows functional and diagnostic data through these articles:
|
||||||
|
|
||||||
- [Windows 10, version 20H2 and Windows 10, version 2004 basic diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
- [Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic events and fields](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||||
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||||
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
- [Windows 10, version 1803 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||||
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
- [Windows 10, version 1709 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
||||||
|
|||||||
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
description: Use this article to learn more about what required Windows diagnostic data is gathered.
|
description: Use this article to learn more about what required Windows diagnostic data is gathered.
|
||||||
title: Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required diagnostic events and fields (Windows 10)
|
title: Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required diagnostic events and fields (Windows 10)
|
||||||
keywords: privacy, telemetry
|
keywords: privacy, telemetry
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: manage
|
ms.mktglfcycl: manage
|
||||||
@ -13,11 +13,11 @@ manager: dansimp
|
|||||||
ms.collection: M365-security-compliance
|
ms.collection: M365-security-compliance
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
audience: ITPro
|
audience: ITPro
|
||||||
ms.date: 10/04/2021
|
ms.date:
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
||||||
# Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic events and fields
|
# Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic events and fields
|
||||||
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
@ -26,10 +26,12 @@ ms.date: 10/04/2021
|
|||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 10, version 21H2
|
||||||
- Windows 10, version 21H1
|
- Windows 10, version 21H1
|
||||||
- Windows 10, version 20H2
|
- Windows 10, version 20H2
|
||||||
- Windows 10, version 2004
|
- Windows 10, version 2004
|
||||||
|
|
||||||
|
|
||||||
Required diagnostic data gathers a limited set of information that is critical for understanding the device and its configuration including: basic device information, quality-related information, app compatibility, and Microsoft Store.
|
Required diagnostic data gathers a limited set of information that is critical for understanding the device and its configuration including: basic device information, quality-related information, app compatibility, and Microsoft Store.
|
||||||
|
|
||||||
Required diagnostic data helps to identify problems that can occur on a particular device hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a particular driver version. This helps Microsoft fix operating system or app problems.
|
Required diagnostic data helps to identify problems that can occur on a particular device hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a particular driver version. This helps Microsoft fix operating system or app problems.
|
||||||
@ -63,6 +65,8 @@ The following fields are available:
|
|||||||
- **DatasourceApplicationFile_20H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_21H1** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_21H1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_21H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceApplicationFile_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceApplicationFile_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_RS1** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_RS1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_RS2** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_RS2** The total number of objects of this type present on this device.
|
||||||
- **DatasourceApplicationFile_RS3** The total number of objects of this type present on this device.
|
- **DatasourceApplicationFile_RS3** The total number of objects of this type present on this device.
|
||||||
@ -76,6 +80,8 @@ The following fields are available:
|
|||||||
- **DatasourceDevicePnp_20H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_21H1** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_21H1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_21H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceDevicePnp_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceDevicePnp_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_RS1** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_RS1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_RS2** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_RS2** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDevicePnp_RS3** The total number of objects of this type present on this device.
|
- **DatasourceDevicePnp_RS3** The total number of objects of this type present on this device.
|
||||||
@ -91,6 +97,8 @@ The following fields are available:
|
|||||||
- **DatasourceDriverPackage_20H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_21H1** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_21H1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_21H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceDriverPackage_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceDriverPackage_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_RS1** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_RS1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_RS2** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_RS2** The total number of objects of this type present on this device.
|
||||||
- **DatasourceDriverPackage_RS3** The total number of objects of this type present on this device.
|
- **DatasourceDriverPackage_RS3** The total number of objects of this type present on this device.
|
||||||
@ -106,6 +114,8 @@ The following fields are available:
|
|||||||
- **DataSourceMatchingInfoBlock_20H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_21H1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_21H1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_21H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoBlock_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoBlock_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_RS1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_RS1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_RS2** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_RS2** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoBlock_RS3** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoBlock_RS3** The total number of objects of this type present on this device.
|
||||||
@ -119,6 +129,8 @@ The following fields are available:
|
|||||||
- **DataSourceMatchingInfoPassive_20H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_21H1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_21H1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_21H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoPassive_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoPassive_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_RS1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_RS1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_RS2** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_RS2** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPassive_RS3** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPassive_RS3** The total number of objects of this type present on this device.
|
||||||
@ -132,6 +144,8 @@ The following fields are available:
|
|||||||
- **DataSourceMatchingInfoPostUpgrade_20H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_21H1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_21H1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_21H1Setup** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoPostUpgrade_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DataSourceMatchingInfoPostUpgrade_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_RS1** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_RS1** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_RS2** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_RS2** The total number of objects of this type present on this device.
|
||||||
- **DataSourceMatchingInfoPostUpgrade_RS3** The total number of objects of this type present on this device.
|
- **DataSourceMatchingInfoPostUpgrade_RS3** The total number of objects of this type present on this device.
|
||||||
@ -145,6 +159,8 @@ The following fields are available:
|
|||||||
- **DatasourceSystemBios_20H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_21H1** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_21H1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_21H1Setup** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceSystemBios_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DatasourceSystemBios_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_RS1** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_RS1** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_RS2** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_RS2** The total number of objects of this type present on this device.
|
||||||
- **DatasourceSystemBios_RS3** The total number of objects of this type present on this device.
|
- **DatasourceSystemBios_RS3** The total number of objects of this type present on this device.
|
||||||
@ -160,6 +176,8 @@ The following fields are available:
|
|||||||
- **DecisionApplicationFile_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_21H1** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionApplicationFile_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionApplicationFile_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_RS1** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_RS2** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionApplicationFile_RS3** The total number of objects of this type present on this device.
|
- **DecisionApplicationFile_RS3** The total number of objects of this type present on this device.
|
||||||
@ -173,6 +191,8 @@ The following fields are available:
|
|||||||
- **DecisionDevicePnp_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_21H1** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionDevicePnp_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionDevicePnp_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_RS1** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_RS2** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionDevicePnp_RS3** The total number of objects of this type present on this device.
|
- **DecisionDevicePnp_RS3** The total number of objects of this type present on this device.
|
||||||
@ -188,6 +208,8 @@ The following fields are available:
|
|||||||
- **DecisionDriverPackage_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_21H1** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionDriverPackage_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionDriverPackage_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_RS1** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_RS2** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionDriverPackage_RS3** The total number of objects of this type present on this device.
|
- **DecisionDriverPackage_RS3** The total number of objects of this type present on this device.
|
||||||
@ -203,6 +225,8 @@ The following fields are available:
|
|||||||
- **DecisionMatchingInfoBlock_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_21H1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoBlock_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoBlock_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_RS1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_RS2** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoBlock_RS3** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoBlock_RS3** The total number of objects of this type present on this device.
|
||||||
@ -216,6 +240,8 @@ The following fields are available:
|
|||||||
- **DecisionMatchingInfoPassive_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_21H1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoPassive_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoPassive_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_RS1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_RS2** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPassive_RS3** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPassive_RS3** The total number of objects of this type present on this device.
|
||||||
@ -229,6 +255,8 @@ The following fields are available:
|
|||||||
- **DecisionMatchingInfoPostUpgrade_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_21H1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoPostUpgrade_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMatchingInfoPostUpgrade_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_RS1** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_RS2** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionMatchingInfoPostUpgrade_RS3** The total number of objects of this type present on this device.
|
- **DecisionMatchingInfoPostUpgrade_RS3** The total number of objects of this type present on this device.
|
||||||
@ -242,6 +270,8 @@ The following fields are available:
|
|||||||
- **DecisionMediaCenter_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_21H1** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMediaCenter_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionMediaCenter_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_RS1** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_RS2** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionMediaCenter_RS3** The total number of objects of this type present on this device.
|
- **DecisionMediaCenter_RS3** The total number of objects of this type present on this device.
|
||||||
@ -254,6 +284,8 @@ The following fields are available:
|
|||||||
- **DecisionSModeState_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSModeState_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_21H1** The total number of objects of this type present on this device.
|
- **DecisionSModeState_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSModeState_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSModeState_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSModeState_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_RS1** The total number of objects of this type present on this device.
|
- **DecisionSModeState_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_RS2** The total number of objects of this type present on this device.
|
- **DecisionSModeState_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSModeState_RS3** The total number of objects of this type present on this device.
|
- **DecisionSModeState_RS3** The total number of objects of this type present on this device.
|
||||||
@ -267,6 +299,8 @@ The following fields are available:
|
|||||||
- **DecisionSystemBios_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemBios_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemBios_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemBios_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemBios_RS3** The total number of objects of this type present on this device.
|
||||||
@ -281,6 +315,8 @@ The following fields are available:
|
|||||||
- **DecisionSystemDiskSize_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemDiskSize_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemDiskSize_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemDiskSize_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemDiskSize_RS3** The total number of objects of this type present on this device.
|
||||||
@ -293,6 +329,8 @@ The following fields are available:
|
|||||||
- **DecisionSystemMemory_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemMemory_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemMemory_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemMemory_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemMemory_RS3** The total number of objects of this type present on this device.
|
||||||
@ -305,6 +343,8 @@ The following fields are available:
|
|||||||
- **DecisionSystemProcessorCpuCores_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuCores_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuCores_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuCores_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuCores_RS3** The total number of objects of this type present on this device.
|
||||||
@ -317,6 +357,7 @@ The following fields are available:
|
|||||||
- **DecisionSystemProcessorCpuModel_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuModel_21H2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuModel_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuModel_RS3** The total number of objects of this type present on this device.
|
||||||
@ -329,6 +370,8 @@ The following fields are available:
|
|||||||
- **DecisionSystemProcessorCpuSpeed_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_21H1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuSpeed_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionSystemProcessorCpuSpeed_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_RS1** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_RS2** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionSystemProcessorCpuSpeed_RS3** The total number of objects of this type present on this device.
|
- **DecisionSystemProcessorCpuSpeed_RS3** The total number of objects of this type present on this device.
|
||||||
@ -341,6 +384,8 @@ The following fields are available:
|
|||||||
- **DecisionTest_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionTest_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_21H1** The total number of objects of this type present on this device.
|
- **DecisionTest_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionTest_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionTest_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionTest_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_RS1** The total number of objects of this type present on this device.
|
- **DecisionTest_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_RS2** The total number of objects of this type present on this device.
|
- **DecisionTest_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionTest_RS3** The total number of objects of this type present on this device.
|
- **DecisionTest_RS3** The total number of objects of this type present on this device.
|
||||||
@ -353,6 +398,8 @@ The following fields are available:
|
|||||||
- **DecisionTpmVersion_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_21H1** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionTpmVersion_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionTpmVersion_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_RS1** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_RS2** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionTpmVersion_RS3** The total number of objects of this type present on this device.
|
- **DecisionTpmVersion_RS3** The total number of objects of this type present on this device.
|
||||||
@ -365,6 +412,8 @@ The following fields are available:
|
|||||||
- **DecisionUefiSecureBoot_20H1Setup** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_21H1** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_21H1** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_21H1Setup** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionUefiSecureBoot_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **DecisionUefiSecureBoot_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_RS1** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_RS1** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_RS2** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_RS2** The total number of objects of this type present on this device.
|
||||||
- **DecisionUefiSecureBoot_RS3** The total number of objects of this type present on this device.
|
- **DecisionUefiSecureBoot_RS3** The total number of objects of this type present on this device.
|
||||||
@ -395,6 +444,8 @@ The following fields are available:
|
|||||||
- **Wmdrm_20H1Setup** The total number of objects of this type present on this device.
|
- **Wmdrm_20H1Setup** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_21H1** The total number of objects of this type present on this device.
|
- **Wmdrm_21H1** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_21H1Setup** The total number of objects of this type present on this device.
|
- **Wmdrm_21H1Setup** The total number of objects of this type present on this device.
|
||||||
|
- **Wmdrm_21H2** The total number of objects of this type present on this device.
|
||||||
|
- **Wmdrm_21H2Setup** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_RS1** The total number of objects of this type present on this device.
|
- **Wmdrm_RS1** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_RS2** The total number of objects of this type present on this device.
|
- **Wmdrm_RS2** The total number of objects of this type present on this device.
|
||||||
- **Wmdrm_RS3** The total number of objects of this type present on this device.
|
- **Wmdrm_RS3** The total number of objects of this type present on this device.
|
||||||
@ -2446,6 +2497,7 @@ The following fields are available:
|
|||||||
- **objectType** Indicates the object type that the event applies to.
|
- **objectType** Indicates the object type that the event applies to.
|
||||||
- **syncId** A string used to group StartSync, EndSync, Add, and Remove operations that belong together. This field is unique by Sync period and is used to disambiguate in situations where multiple agents perform overlapping inventories for the same object.
|
- **syncId** A string used to group StartSync, EndSync, Add, and Remove operations that belong together. This field is unique by Sync period and is used to disambiguate in situations where multiple agents perform overlapping inventories for the same object.
|
||||||
|
|
||||||
|
|
||||||
## Component-based servicing events
|
## Component-based servicing events
|
||||||
|
|
||||||
### CbsServicingProvider.CbsCapabilityEnumeration
|
### CbsServicingProvider.CbsCapabilityEnumeration
|
||||||
@ -2978,6 +3030,7 @@ The following fields are available:
|
|||||||
- **DriverInfSectionName** Name of the DDInstall section within the driver INF file.
|
- **DriverInfSectionName** Name of the DDInstall section within the driver INF file.
|
||||||
- **DriverPackageId** The ID of the driver package that is staged to the driver store.
|
- **DriverPackageId** The ID of the driver package that is staged to the driver store.
|
||||||
- **DriverProvider** The driver manufacturer or provider.
|
- **DriverProvider** The driver manufacturer or provider.
|
||||||
|
- **DriverShimIds** List of driver shim IDs.
|
||||||
- **DriverUpdated** Indicates whether the driver is replacing an old driver.
|
- **DriverUpdated** Indicates whether the driver is replacing an old driver.
|
||||||
- **DriverVersion** The version of the driver file.
|
- **DriverVersion** The version of the driver file.
|
||||||
- **EndTime** The time the installation completed.
|
- **EndTime** The time the installation completed.
|
||||||
@ -4375,7 +4428,7 @@ The following fields are available:
|
|||||||
- **device_sample_rate** A number representing how often the device sends telemetry, expressed as a percentage. Low values indicate that device sends more events and high values indicate that device sends fewer events. The value is rounded to 5 significant figures for privacy reasons and if an error is hit in getting the device sample number value from the registry then this will be -1; and if client is not on a UTC-enabled platform, then this value will not be set.
|
- **device_sample_rate** A number representing how often the device sends telemetry, expressed as a percentage. Low values indicate that device sends more events and high values indicate that device sends fewer events. The value is rounded to 5 significant figures for privacy reasons and if an error is hit in getting the device sample number value from the registry then this will be -1; and if client is not on a UTC-enabled platform, then this value will not be set.
|
||||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||||
- **experimentation_mode** A number representing the value set for the ExperimentationAndConfigurationServiceControl group policy. See [Microsoft Edge - Policies](/DeployEdge/microsoft-edge-policies#experimentationandconfigurationservicecontrol) for more details on this policy.
|
- **experimentation_mode** A number representing the value set for the ExperimentationAndConfigurationServiceControl group policy. See [Microsoft Edge - Policies](/DeployEdge/microsoft-edge-policies#experimentationandconfigurationservicecontrol) for more details on this policy.
|
||||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||||
- **installSourceName** A string representation of the installation source.
|
- **installSourceName** A string representation of the installation source.
|
||||||
@ -4618,195 +4671,16 @@ The following fields are available:
|
|||||||
- **totalRunDuration** Total running/evaluation time from last time.
|
- **totalRunDuration** Total running/evaluation time from last time.
|
||||||
- **totalRuns** Total number of running/evaluation from last time.
|
- **totalRuns** Total number of running/evaluation from last time.
|
||||||
|
|
||||||
|
## Settings events
|
||||||
|
|
||||||
## Other events
|
### Microsoft.Windows.Shell.SystemSettings.SettingsAppActivity.ProtocolActivation
|
||||||
|
|
||||||
### Microsoft.Surface.Battery.Prod.BatteryInfoEvent
|
This event tracks protocol launching for Setting's URIs. The data collected with this event is used to help keep Windows up to date.
|
||||||
|
|
||||||
This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly.
|
|
||||||
|
|
||||||
The following fields are available:
|
The following fields are available:
|
||||||
|
|
||||||
- **batteryData** Battery Performance data.
|
- **activationSource** Where activation is initiated.
|
||||||
- **batteryData.data()** Battery performance data.
|
- **uriString** URI of the launching protocol.
|
||||||
- **BatteryDataSize:** Size of the battery performance data.
|
|
||||||
- **batteryInfo.data()** Battery performance data.
|
|
||||||
- **BatteryInfoSize:** Size of the battery performance data.
|
|
||||||
- **pszBatteryDataXml** Battery performance data.
|
|
||||||
- **szBatteryInfo** Battery performance data.
|
|
||||||
|
|
||||||
|
|
||||||
### Microsoft.Surface.Battery.Prod.BatteryInfoEventV2_BPM
|
|
||||||
|
|
||||||
This event includes the hardware level data about battery performance. The data The data collected with this event is used to keep Windows performing properly.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **BPMCurrentlyEngaged** Instantaneous snapshot if BPM is engaged on device.
|
|
||||||
- **BPMExitCriteria** What is the BPM exit criteria - 20%SOC or 50%SOC?
|
|
||||||
- **BPMHvtCountA** Current HVT count for BPM counter A.
|
|
||||||
- **BPMHvtCountB** Current HVT count for BPM counter B.
|
|
||||||
- **bpmOptOutLifetimeCount** BPM OptOut Lifetime Count.
|
|
||||||
- **BPMRsocBucketsHighTemp_Values** Time in temperature range 46°C -60°C and in the following true RSOC ranges: 0%-49%; 50%-79%; 80%-89%; 90%-94%; 95%-100%.
|
|
||||||
- **BPMRsocBucketsLowTemp_Values** Time in temperature range 0°C -20°C and in the following true RSOC ranges: 0%-49%; 50%-79%; 80%-89%; 90%-94%; 95%-100%.
|
|
||||||
- **BPMRsocBucketsMediumHighTemp_Values** Time in temperature range 36°C -45°C and in the following true RSOC ranges: 0%-49%; 50%-79%; 80%-89%; 90%-94%; 95%-100%.
|
|
||||||
- **BPMRsocBucketsMediumLowTemp_Values** Time in temperature range 21°C-35°C and in the following true RSOC ranges: 0%-49%; 50%-79%; 80%-89%; 90%-94%; 95%-100%.
|
|
||||||
- **BPMTotalEngagedMinutes** Total time that BPM was engaged.
|
|
||||||
- **BPMTotalEntryEvents** Total number of times entering BPM.
|
|
||||||
- **ComponentId** Component ID.
|
|
||||||
- **FwVersion** FW version that created this log.
|
|
||||||
- **LogClass** Log Class.
|
|
||||||
- **LogInstance** Log instance within class (1..n).
|
|
||||||
- **LogVersion** Log MGR version.
|
|
||||||
- **MCUInstance** Instance id used to identify multiple MCU's in a product.
|
|
||||||
- **ProductId** Product ID.
|
|
||||||
- **SeqNum** Sequence Number.
|
|
||||||
- **TimeStamp** UTC seconds when log was created.
|
|
||||||
- **Ver** Schema version.
|
|
||||||
|
|
||||||
|
|
||||||
### Microsoft.Surface.Battery.Prod.BatteryInfoEventV2_GG
|
|
||||||
|
|
||||||
This event includes the hardware level data about battery performance. The data The data collected with this event is used to keep Windows performing properly.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **cbTimeCell_Values** cb time for different cells.
|
|
||||||
- **ComponentId** Component ID.
|
|
||||||
- **cycleCount** Cycle Count.
|
|
||||||
- **deltaVoltage** Delta voltage.
|
|
||||||
- **eocChargeVoltage_Values** EOC Charge voltage values.
|
|
||||||
- **fullChargeCapacity** Full Charge Capacity.
|
|
||||||
- **FwVersion** FW version that created this log.
|
|
||||||
- **lastCovEvent** Last Cov event.
|
|
||||||
- **lastCuvEvent** Last Cuv event.
|
|
||||||
- **LogClass** LOG_CLASS.
|
|
||||||
- **LogInstance** Log instance within class (1..n).
|
|
||||||
- **LogVersion** LOG_MGR_VERSION.
|
|
||||||
- **manufacturerName** Manufacturer name.
|
|
||||||
- **maxChargeCurrent** Max charge current.
|
|
||||||
- **maxDeltaCellVoltage** Max delta cell voltage.
|
|
||||||
- **maxDischargeCurrent** Max discharge current.
|
|
||||||
- **maxTempCell** Max temp cell.
|
|
||||||
- **maxVoltage_Values** Max voltage values.
|
|
||||||
- **MCUInstance** Instance id used to identify multiple MCU's in a product.
|
|
||||||
- **minTempCell** Min temp cell.
|
|
||||||
- **minVoltage_Values** Min voltage values.
|
|
||||||
- **numberOfCovEvents** Number of Cov events.
|
|
||||||
- **numberOfCuvEvents** Number of Cuv events.
|
|
||||||
- **numberOfOCD1Events** Number of OCD1 events.
|
|
||||||
- **numberOfOCD2Events** Number of OCD2 events.
|
|
||||||
- **numberOfQmaxUpdates** Number of Qmax updates.
|
|
||||||
- **numberOfRaUpdates** Number of Ra updates.
|
|
||||||
- **numberOfShutdowns** Number of shutdowns.
|
|
||||||
- **pfStatus_Values** pf status values.
|
|
||||||
- **ProductId** Product ID.
|
|
||||||
- **qmax_Values** Qmax values for different cells.
|
|
||||||
- **SeqNum** Sequence Number.
|
|
||||||
- **TimeStamp** UTC seconds when log was created.
|
|
||||||
- **Ver** Schema version.
|
|
||||||
|
|
||||||
|
|
||||||
### Microsoft.Surface.Battery.Prod.BatteryInfoEventV2_GGExt
|
|
||||||
|
|
||||||
This event includes the hardware level data about battery performance. The data The data collected with this event is used to keep Windows performing properly.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **avgCurrLastRun** Average current last run.
|
|
||||||
- **avgPowLastRun** Average power last run.
|
|
||||||
- **batteryMSPN** BatteryMSPN
|
|
||||||
- **batteryMSSN** BatteryMSSN.
|
|
||||||
- **cell0Ra3** Cell0Ra3.
|
|
||||||
- **cell1Ra3** Cell1Ra3.
|
|
||||||
- **cell2Ra3** Cell2Ra3.
|
|
||||||
- **cell3Ra3** Cell3Ra3.
|
|
||||||
- **ComponentId** Component ID.
|
|
||||||
- **currentAtEoc** Current at Eoc.
|
|
||||||
- **firstPFstatusA** First PF status-A.
|
|
||||||
- **firstPFstatusB** First PF status-B.
|
|
||||||
- **firstPFstatusC** First PF status-C.
|
|
||||||
- **firstPFstatusD** First PF status-D.
|
|
||||||
- **FwVersion** FW version that created this log.
|
|
||||||
- **lastQmaxUpdate** Last Qmax update.
|
|
||||||
- **lastRaDisable** Last Ra disable.
|
|
||||||
- **lastRaUpdate** Last Ra update.
|
|
||||||
- **lastValidChargeTerm** Last valid charge term.
|
|
||||||
- **LogClass** LOG CLASS.
|
|
||||||
- **LogInstance** Log instance within class (1..n).
|
|
||||||
- **LogVersion** LOG MGR VERSION.
|
|
||||||
- **maxAvgCurrLastRun** Max average current last run.
|
|
||||||
- **maxAvgPowLastRun** Max average power last run.
|
|
||||||
- **MCUInstance** Instance id used to identify multiple MCU's in a product.
|
|
||||||
- **mfgInfoBlockB01** MFG info Block B01.
|
|
||||||
- **mfgInfoBlockB02** MFG info Block B02.
|
|
||||||
- **mfgInfoBlockB03** MFG info Block B03.
|
|
||||||
- **mfgInfoBlockB04** MFG info Block B04.
|
|
||||||
- **numOfRaDisable** Number of Ra disable.
|
|
||||||
- **numOfValidChargeTerm** Number of valid charge term.
|
|
||||||
- **ProductId** Product ID.
|
|
||||||
- **qmaxCycleCount** Qmax cycle count.
|
|
||||||
- **SeqNum** Sequence Number.
|
|
||||||
- **stateOfHealthEnergy** State of health energy.
|
|
||||||
- **stateOfHealthFcc** State of health Fcc.
|
|
||||||
- **stateOfHealthPercent** State of health percent.
|
|
||||||
- **TimeStamp** UTC seconds when log was created.
|
|
||||||
- **totalFwRuntime** Total FW runtime.
|
|
||||||
- **updateStatus** Update status.
|
|
||||||
- **Ver** Schema version.
|
|
||||||
|
|
||||||
|
|
||||||
### Microsoft.Surface.SystemReset.Prod.ResetCauseEventV2
|
|
||||||
|
|
||||||
This event sends reason for SAM, PCH and SoC reset. The data collected with this event is used to keep Windows performing properly.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **HostResetCause** Host reset cause.
|
|
||||||
- **PchResetCause** PCH reset cause.
|
|
||||||
- **SamResetCause** SAM reset cause.
|
|
||||||
|
|
||||||
|
|
||||||
### Microsoft.Windows.UpdateAssistantApp.UpdateAssistantDeviceInformation
|
|
||||||
|
|
||||||
This event provides basic information about the device where update assistant was run. The data collected with this event is used to help keep Windows up to date.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **CV** The correlation vector.
|
|
||||||
- **GlobalEventCounter** The global event counter for all telemetry on the device.
|
|
||||||
- **UpdateAssistantAppFilePath** Path to Update Assistant app.
|
|
||||||
- **UpdateAssistantDeviceId** Device Id of the Update Assistant Candidate Device.
|
|
||||||
- **UpdateAssistantExeName** Exe name running as Update Assistant.
|
|
||||||
- **UpdateAssistantExternalId** External Id of the Update Assistant Candidate Device.
|
|
||||||
- **UpdateAssistantIsDeviceCloverTrail** True/False is the device clovertrail.
|
|
||||||
- **UpdateAssistantIsPushing** True if the update is pushing to the device.
|
|
||||||
- **UpdateAssistantMachineId** Machine Id of the Update Assistant Candidate Device.
|
|
||||||
- **UpdateAssistantOsVersion** Update Assistant OS Version.
|
|
||||||
- **UpdateAssistantPartnerId** Partner Id for Assistant application.
|
|
||||||
- **UpdateAssistantReportPath** Path to report for Update Assistant.
|
|
||||||
- **UpdateAssistantStartTime** Start time for UpdateAssistant.
|
|
||||||
- **UpdateAssistantUiType** The type of UI whether default or OOBE.
|
|
||||||
- **UpdateAssistantVersion** Current package version of UpdateAssistant.
|
|
||||||
- **UpdateAssistantVersionInfo** Information about Update Assistant application.
|
|
||||||
|
|
||||||
|
|
||||||
### Microsoft.Windows.UpdateAssistantApp.UpdateAssistantStartState
|
|
||||||
|
|
||||||
This event marks the start of an Update Assistant State. The data collected with this event is used to help keep Windows up to date.
|
|
||||||
|
|
||||||
The following fields are available:
|
|
||||||
|
|
||||||
- **CV** The correlation vector.
|
|
||||||
- **GlobalEventCounter** The global event counter for all telemetry on the device.
|
|
||||||
- **UpdateAssistantStateAcceptEULA** True at the start of AcceptEULA.
|
|
||||||
- **UpdateAssistantStateCheckingCompat** True at the start of Checking Compat
|
|
||||||
- **UpdateAssistantStateCheckingUpgrade** True at the start of CheckingUpgrade.
|
|
||||||
- **UpdateAssistantStateDownloading** True at the start Downloading.
|
|
||||||
- **UpdateAssistantStateInitializingApplication** True at the start of the state InitializingApplication.
|
|
||||||
- **UpdateAssistantStateInitializingStates** True at the start of InitializingStates.
|
|
||||||
- **UpdateAssistantStateInstalling** True at the start of Installing.
|
|
||||||
- **UpdateAssistantVersion** Current package version of UpdateAssistant.
|
|
||||||
|
|
||||||
|
|
||||||
## Privacy consent logging events
|
## Privacy consent logging events
|
||||||
@ -5411,6 +5285,182 @@ The following fields are available:
|
|||||||
- **healthLogSize** 4KB.
|
- **healthLogSize** 4KB.
|
||||||
- **productId** Identifier for product model.
|
- **productId** Identifier for product model.
|
||||||
|
|
||||||
|
### Microsoft.Surface.Battery.Prod.BatteryInfoEvent
|
||||||
|
|
||||||
|
This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **batteryData** Battery Performance data.
|
||||||
|
- **batteryData.data()** Battery performance data.
|
||||||
|
- **BatteryDataSize:** Size of the battery performance data.
|
||||||
|
- **batteryInfo.data()** Battery performance data.
|
||||||
|
- **BatteryInfoSize:** Size of the battery performance data.
|
||||||
|
- **pszBatteryDataXml** Battery performance data.
|
||||||
|
- **szBatteryInfo** Battery performance data.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Surface.Battery.Prod.BatteryInfoEventV2_BPM
|
||||||
|
|
||||||
|
This event includes the hardware level data about battery performance. The data The data collected with this event is used to keep Windows performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **BPMCurrentlyEngaged** Instantaneous snapshot if BPM is engaged on device.
|
||||||
|
- **BPMExitCriteria** What is the BPM exit criteria - 20%SOC or 50%SOC?
|
||||||
|
- **BPMHvtCountA** Current HVT count for BPM counter A.
|
||||||
|
- **BPMHvtCountB** Current HVT count for BPM counter B.
|
||||||
|
- **bpmOptOutLifetimeCount** BPM OptOut Lifetime Count.
|
||||||
|
- **BPMRsocBucketsHighTemp_Values** Time in temperature range 46°C -60°C and in the following true RSOC ranges: 0%-49%; 50%-79%; 80%-89%; 90%-94%; 95%-100%.
|
||||||
|
- **BPMRsocBucketsLowTemp_Values** Time in temperature range 0°C -20°C and in the following true RSOC ranges: 0%-49%; 50%-79%; 80%-89%; 90%-94%; 95%-100%.
|
||||||
|
- **BPMRsocBucketsMediumHighTemp_Values** Time in temperature range 36°C -45°C and in the following true RSOC ranges: 0%-49%; 50%-79%; 80%-89%; 90%-94%; 95%-100%.
|
||||||
|
- **BPMRsocBucketsMediumLowTemp_Values** Time in temperature range 21°C-35°C and in the following true RSOC ranges: 0%-49%; 50%-79%; 80%-89%; 90%-94%; 95%-100%.
|
||||||
|
- **BPMTotalEngagedMinutes** Total time that BPM was engaged.
|
||||||
|
- **BPMTotalEntryEvents** Total number of times entering BPM.
|
||||||
|
- **ComponentId** Component ID.
|
||||||
|
- **FwVersion** FW version that created this log.
|
||||||
|
- **LogClass** Log Class.
|
||||||
|
- **LogInstance** Log instance within class (1..n).
|
||||||
|
- **LogVersion** Log MGR version.
|
||||||
|
- **MCUInstance** Instance id used to identify multiple MCU's in a product.
|
||||||
|
- **ProductId** Product ID.
|
||||||
|
- **SeqNum** Sequence Number.
|
||||||
|
- **TimeStamp** UTC seconds when log was created.
|
||||||
|
- **Ver** Schema version.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Surface.Battery.Prod.BatteryInfoEventV2_CTT
|
||||||
|
|
||||||
|
This event includes the hardware level data about battery performance. The data The data collected with this event is used to keep Windows performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **BPMKioskModeStartDateInSeconds** First time Battery Limit was turned on.
|
||||||
|
- **BPMKioskModeTotalEngagedMinutes** Total time Battery Limit was on (SOC value at 50%).
|
||||||
|
- **ComponentId** Component ID.
|
||||||
|
- **CTTEqvTimeat35C** Poll time every minute. Add to lifetime counter based on temperature. Only count time above 80% SOC.
|
||||||
|
- **CTTEqvTimeat35CinBPM** Poll time every minute. Add to lifetime counter based on temperature. Only count time above 55% SOC and when device is in BPM. Round up.
|
||||||
|
- **CTTMinSOC1day** Rolling 1 day minimum SOC. Value set to 0 initially.
|
||||||
|
- **CTTMinSOC28day** Rolling 28 day minimum SOC. Value set to 0 initially.
|
||||||
|
- **CTTMinSOC3day** Rolling 3 day minimum SOC. Value set to 0 initially.
|
||||||
|
- **CTTMinSOC7day** Rolling 7 day minimum SOC. Value set to 0 initially.
|
||||||
|
- **CTTStartDateInSeconds** Start date from when device was starting to be used.
|
||||||
|
- **currentAuthenticationState** Current Authentication State.
|
||||||
|
- **FwVersion** FW version that created this log.
|
||||||
|
- **LogClass** Log Class.
|
||||||
|
- **LogInstance** Log instance within class (1..n).
|
||||||
|
- **LogVersion** Log MGR version.
|
||||||
|
- **MCUInstance** Instance id used to identify multiple MCU's in a product.
|
||||||
|
- **newSnFruUpdateCount** New Sn FRU Update Count.
|
||||||
|
- **newSnUpdateCount** New Sn Update Count.
|
||||||
|
- **ProductId** Product ID.
|
||||||
|
- **ProtectionPolicy** Battery limit engaged. True (0 False).
|
||||||
|
- **SeqNum** Sequence Number.
|
||||||
|
- **TimeStamp** UTC seconds when log was created.
|
||||||
|
- **Ver** Schema version.
|
||||||
|
- **VoltageOptimization** Current CTT reduction in mV.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Surface.Battery.Prod.BatteryInfoEventV2_GG
|
||||||
|
|
||||||
|
This event includes the hardware level data about battery performance. The data The data collected with this event is used to keep Windows performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **cbTimeCell_Values** cb time for different cells.
|
||||||
|
- **ComponentId** Component ID.
|
||||||
|
- **cycleCount** Cycle Count.
|
||||||
|
- **deltaVoltage** Delta voltage.
|
||||||
|
- **eocChargeVoltage_Values** EOC Charge voltage values.
|
||||||
|
- **fullChargeCapacity** Full Charge Capacity.
|
||||||
|
- **FwVersion** FW version that created this log.
|
||||||
|
- **lastCovEvent** Last Cov event.
|
||||||
|
- **lastCuvEvent** Last Cuv event.
|
||||||
|
- **LogClass** LOG_CLASS.
|
||||||
|
- **LogInstance** Log instance within class (1..n).
|
||||||
|
- **LogVersion** LOG_MGR_VERSION.
|
||||||
|
- **manufacturerName** Manufacturer name.
|
||||||
|
- **maxChargeCurrent** Max charge current.
|
||||||
|
- **maxDeltaCellVoltage** Max delta cell voltage.
|
||||||
|
- **maxDischargeCurrent** Max discharge current.
|
||||||
|
- **maxTempCell** Max temp cell.
|
||||||
|
- **maxVoltage_Values** Max voltage values.
|
||||||
|
- **MCUInstance** Instance id used to identify multiple MCU's in a product.
|
||||||
|
- **minTempCell** Min temp cell.
|
||||||
|
- **minVoltage_Values** Min voltage values.
|
||||||
|
- **numberOfCovEvents** Number of Cov events.
|
||||||
|
- **numberOfCuvEvents** Number of Cuv events.
|
||||||
|
- **numberOfOCD1Events** Number of OCD1 events.
|
||||||
|
- **numberOfOCD2Events** Number of OCD2 events.
|
||||||
|
- **numberOfQmaxUpdates** Number of Qmax updates.
|
||||||
|
- **numberOfRaUpdates** Number of Ra updates.
|
||||||
|
- **numberOfShutdowns** Number of shutdowns.
|
||||||
|
- **pfStatus_Values** pf status values.
|
||||||
|
- **ProductId** Product ID.
|
||||||
|
- **qmax_Values** Qmax values for different cells.
|
||||||
|
- **SeqNum** Sequence Number.
|
||||||
|
- **TimeStamp** UTC seconds when log was created.
|
||||||
|
- **Ver** Schema version.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Surface.Battery.Prod.BatteryInfoEventV2_GGExt
|
||||||
|
|
||||||
|
This event includes the hardware level data about battery performance. The data The data collected with this event is used to keep Windows performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **avgCurrLastRun** Average current last run.
|
||||||
|
- **avgPowLastRun** Average power last run.
|
||||||
|
- **batteryMSPN** BatteryMSPN
|
||||||
|
- **batteryMSSN** BatteryMSSN.
|
||||||
|
- **cell0Ra3** Cell0Ra3.
|
||||||
|
- **cell1Ra3** Cell1Ra3.
|
||||||
|
- **cell2Ra3** Cell2Ra3.
|
||||||
|
- **cell3Ra3** Cell3Ra3.
|
||||||
|
- **ComponentId** Component ID.
|
||||||
|
- **currentAtEoc** Current at Eoc.
|
||||||
|
- **firstPFstatusA** First PF status-A.
|
||||||
|
- **firstPFstatusB** First PF status-B.
|
||||||
|
- **firstPFstatusC** First PF status-C.
|
||||||
|
- **firstPFstatusD** First PF status-D.
|
||||||
|
- **FwVersion** FW version that created this log.
|
||||||
|
- **lastQmaxUpdate** Last Qmax update.
|
||||||
|
- **lastRaDisable** Last Ra disable.
|
||||||
|
- **lastRaUpdate** Last Ra update.
|
||||||
|
- **lastValidChargeTerm** Last valid charge term.
|
||||||
|
- **LogClass** LOG CLASS.
|
||||||
|
- **LogInstance** Log instance within class (1..n).
|
||||||
|
- **LogVersion** LOG MGR VERSION.
|
||||||
|
- **maxAvgCurrLastRun** Max average current last run.
|
||||||
|
- **maxAvgPowLastRun** Max average power last run.
|
||||||
|
- **MCUInstance** Instance id used to identify multiple MCU's in a product.
|
||||||
|
- **mfgInfoBlockB01** MFG info Block B01.
|
||||||
|
- **mfgInfoBlockB02** MFG info Block B02.
|
||||||
|
- **mfgInfoBlockB03** MFG info Block B03.
|
||||||
|
- **mfgInfoBlockB04** MFG info Block B04.
|
||||||
|
- **numOfRaDisable** Number of Ra disable.
|
||||||
|
- **numOfValidChargeTerm** Number of valid charge term.
|
||||||
|
- **ProductId** Product ID.
|
||||||
|
- **qmaxCycleCount** Qmax cycle count.
|
||||||
|
- **SeqNum** Sequence Number.
|
||||||
|
- **stateOfHealthEnergy** State of health energy.
|
||||||
|
- **stateOfHealthFcc** State of health Fcc.
|
||||||
|
- **stateOfHealthPercent** State of health percent.
|
||||||
|
- **TimeStamp** UTC seconds when log was created.
|
||||||
|
- **totalFwRuntime** Total FW runtime.
|
||||||
|
- **updateStatus** Update status.
|
||||||
|
- **Ver** Schema version.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Surface.SystemReset.Prod.ResetCauseEventV2
|
||||||
|
|
||||||
|
This event sends reason for SAM, PCH and SoC reset. The data collected with this event is used to keep Windows performing properly.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **HostResetCause** Host reset cause.
|
||||||
|
- **PchResetCause** PCH reset cause.
|
||||||
|
- **SamResetCause** SAM reset cause.
|
||||||
|
|
||||||
## Update Assistant events
|
## Update Assistant events
|
||||||
|
|
||||||
@ -5888,6 +5938,90 @@ The following fields are available:
|
|||||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
||||||
- **PackageVersion** Current package version of remediation.
|
- **PackageVersion** Current package version of remediation.
|
||||||
|
|
||||||
|
### Microsoft.Windows.UpdateAssistantApp.UpdateAssistantCompatCheckResult
|
||||||
|
|
||||||
|
This event provides the result of running the compatibility check for update assistant. The data collected with this event is used to help keep Windows up to date.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **CV** The correlation vector.
|
||||||
|
- **GlobalEventCounter** The global event counter for all telemetry on the device.
|
||||||
|
- **UpdateAssistantCompatCheckResultOutput** Output of compatibility check for update assistant.
|
||||||
|
- **UpdateAssistantVersion** Current package version of UpdateAssistant.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Windows.UpdateAssistantApp.UpdateAssistantDeviceInformation
|
||||||
|
|
||||||
|
This event provides basic information about the device where update assistant was run. The data collected with this event is used to help keep Windows up to date.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **CV** The correlation vector.
|
||||||
|
- **GlobalEventCounter** The global event counter for all telemetry on the device.
|
||||||
|
- **UpdateAssistantAppFilePath** Path to Update Assistant app.
|
||||||
|
- **UpdateAssistantDeviceId** Device Id of the Update Assistant Candidate Device.
|
||||||
|
- **UpdateAssistantExeName** Exe name running as Update Assistant.
|
||||||
|
- **UpdateAssistantExternalId** External Id of the Update Assistant Candidate Device.
|
||||||
|
- **UpdateAssistantIsDeviceCloverTrail** True/False is the device clovertrail.
|
||||||
|
- **UpdateAssistantIsPushing** True if the update is pushing to the device.
|
||||||
|
- **UpdateAssistantMachineId** Machine Id of the Update Assistant Candidate Device.
|
||||||
|
- **UpdateAssistantOsVersion** Update Assistant OS Version.
|
||||||
|
- **UpdateAssistantPartnerId** Partner Id for Assistant application.
|
||||||
|
- **UpdateAssistantReportPath** Path to report for Update Assistant.
|
||||||
|
- **UpdateAssistantStartTime** Start time for UpdateAssistant.
|
||||||
|
- **UpdateAssistantTargetOSVersion** Update Assistant Target OS Version.
|
||||||
|
- **UpdateAssistantUiType** The type of UI whether default or OOBE.
|
||||||
|
- **UpdateAssistantVersion** Current package version of UpdateAssistant.
|
||||||
|
- **UpdateAssistantVersionInfo** Information about Update Assistant application.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Windows.UpdateAssistantApp.UpdateAssistantEULAProperty
|
||||||
|
|
||||||
|
This event is set to true at the start of AcceptEULA. The data collected with this event is used to help keep Windows up to date.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **CV** The correlation vector.
|
||||||
|
- **GlobalEventCounter** The global event counter for all telemetry on the device.
|
||||||
|
- **UpdateAssistantEULAPropertyGeoId** Geo Id used to show EULA.
|
||||||
|
- **UpdateAssistantEULAPropertyRegion** Region used to show EULA.
|
||||||
|
- **UpdateAssistantVersion** Current package version of UpdateAssistant.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Windows.UpdateAssistantApp.UpdateAssistantStartState
|
||||||
|
|
||||||
|
This event marks the start of an Update Assistant State. The data collected with this event is used to help keep Windows up to date.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **CV** The correlation vector.
|
||||||
|
- **GlobalEventCounter** The global event counter for all telemetry on the device.
|
||||||
|
- **UpdateAssistantStateAcceptEULA** True at the start of AcceptEULA.
|
||||||
|
- **UpdateAssistantStateCheckingCompat** True at the start of Checking Compat
|
||||||
|
- **UpdateAssistantStateCheckingUpgrade** True at the start of CheckingUpgrade.
|
||||||
|
- **UpdateAssistantStateDownloading** True at the start Downloading.
|
||||||
|
- **UpdateAssistantStateInitializingApplication** True at the start of the state InitializingApplication.
|
||||||
|
- **UpdateAssistantStateInitializingStates** True at the start of InitializingStates.
|
||||||
|
- **UpdateAssistantStateInstalling** True at the start of Installing.
|
||||||
|
- **UpdateAssistantStatePerformRestart** True at the start of PerformRestart.
|
||||||
|
- **UpdateAssistantStatePostInstall** True at the start of PostInstall.
|
||||||
|
- **UpdateAssistantStateShowingUpdate** True at the start of Showing Update.
|
||||||
|
- **UpdateAssistantStateWelcomeToNewOS** True at the start of WelcomeToNewOS.
|
||||||
|
- **UpdateAssistantVersion** Current package version of UpdateAssistant.
|
||||||
|
|
||||||
|
|
||||||
|
### Microsoft.Windows.UpdateAssistantApp.UpdateAssistantUserActionDetails
|
||||||
|
|
||||||
|
This event provides details about user action. The data collected with this event is used to help keep Windows up to date.
|
||||||
|
|
||||||
|
The following fields are available:
|
||||||
|
|
||||||
|
- **CV** The correlation vector.
|
||||||
|
- **GlobalEventCounter** The global event counter for all telemetry on the device.
|
||||||
|
- **UpdateAssistantUserActionExitingState** Exiting state name user performed action on.
|
||||||
|
- **UpdateAssistantUserActionHResult** HRESULT of user action.
|
||||||
|
- **UpdateAssistantUserActionState** State name user performed action on.
|
||||||
|
- **UpdateAssistantVersion** Current package version of UpdateAssistant.
|
||||||
|
|
||||||
## Update events
|
## Update events
|
||||||
|
|
||||||
|
|||||||
@ -17,7 +17,7 @@
|
|||||||
items:
|
items:
|
||||||
- name: Required Windows 11 diagnostic data events and fields
|
- name: Required Windows 11 diagnostic data events and fields
|
||||||
href: required-windows-11-diagnostic-events-and-fields.md
|
href: required-windows-11-diagnostic-events-and-fields.md
|
||||||
- name: Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic data events and fields
|
- name: Windows 10, version 21H2, Windows 10, version 21H1, Windows 10, version 20H2 and Windows 10, version 2004 required Windows diagnostic data events and fields
|
||||||
href: required-windows-diagnostic-data-events-and-fields-2004.md
|
href: required-windows-diagnostic-data-events-and-fields-2004.md
|
||||||
- name: Windows 10, version 1909 and Windows 10, version 1903 required level Windows diagnostic events and fields
|
- name: Windows 10, version 1909 and Windows 10, version 1903 required level Windows diagnostic events and fields
|
||||||
href: basic-level-windows-diagnostic-events-and-fields-1903.md
|
href: basic-level-windows-diagnostic-events-and-fields-1903.md
|
||||||
|
|||||||
@ -19,6 +19,8 @@ ms.reviewer:
|
|||||||
|
|
||||||
Applies to:
|
Applies to:
|
||||||
- Windows 11
|
- Windows 11
|
||||||
|
- Windows 10, version 21H2
|
||||||
|
- Windows 10, version 21H1
|
||||||
- Windows 10, version 20H2
|
- Windows 10, version 20H2
|
||||||
- Windows 10, version 2004
|
- Windows 10, version 2004
|
||||||
- Windows 10, version 1909
|
- Windows 10, version 1909
|
||||||
|
|||||||
@ -14,6 +14,8 @@
|
|||||||
- name: Windows 10
|
- name: Windows 10
|
||||||
expanded: true
|
expanded: true
|
||||||
items:
|
items:
|
||||||
|
- name: What's new in Windows 10, version 21H2
|
||||||
|
href: whats-new-windows-10-version-21H2.md
|
||||||
- name: What's new in Windows 10, version 21H1
|
- name: What's new in Windows 10, version 21H1
|
||||||
href: whats-new-windows-10-version-21H1.md
|
href: whats-new-windows-10-version-21H1.md
|
||||||
- name: What's new in Windows 10, version 20H2
|
- name: What's new in Windows 10, version 20H2
|
||||||
|
|||||||
@ -1,6 +1,8 @@
|
|||||||
- name: Windows 10 Enterprise LTSC
|
- name: Windows 10 Enterprise LTSC
|
||||||
href: index.md
|
href: index.md
|
||||||
items:
|
items:
|
||||||
|
- name: What's new in Windows 10 Enterprise LTSC 2021
|
||||||
|
href: whats-new-windows-10-2021.md
|
||||||
- name: What's new in Windows 10 Enterprise LTSC 2019
|
- name: What's new in Windows 10 Enterprise LTSC 2019
|
||||||
href: whats-new-windows-10-2019.md
|
href: whats-new-windows-10-2019.md
|
||||||
- name: What's new in Windows 10 Enterprise LTSC 2016
|
- name: What's new in Windows 10 Enterprise LTSC 2016
|
||||||
|
|||||||
@ -8,7 +8,7 @@ ms.sitesec: library
|
|||||||
audience: itpro
|
audience: itpro
|
||||||
author: greg-lindsay
|
author: greg-lindsay
|
||||||
ms.author: greglin
|
ms.author: greglin
|
||||||
manager: laurawi
|
manager: dougeby
|
||||||
ms.localizationpriority: low
|
ms.localizationpriority: low
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
@ -22,6 +22,7 @@ ms.topic: article
|
|||||||
|
|
||||||
This topic provides links to articles with information about what's new in each release of Windows 10 Enterprise LTSC, and includes a short description of this servicing channel.
|
This topic provides links to articles with information about what's new in each release of Windows 10 Enterprise LTSC, and includes a short description of this servicing channel.
|
||||||
|
|
||||||
|
[What's New in Windows 10 Enterprise LTSC 2021](whats-new-windows-10-2021.md)<br>
|
||||||
[What's New in Windows 10 Enterprise LTSC 2019](whats-new-windows-10-2019.md)<br>
|
[What's New in Windows 10 Enterprise LTSC 2019](whats-new-windows-10-2019.md)<br>
|
||||||
[What's New in Windows 10 Enterprise LTSC 2016](whats-new-windows-10-2016.md)<br>
|
[What's New in Windows 10 Enterprise LTSC 2016](whats-new-windows-10-2016.md)<br>
|
||||||
[What's New in Windows 10 Enterprise LTSC 2015](whats-new-windows-10-2015.md)
|
[What's New in Windows 10 Enterprise LTSC 2015](whats-new-windows-10-2015.md)
|
||||||
@ -35,14 +36,15 @@ The following table summarizes equivalent feature update versions of Windows 10
|
|||||||
| Windows 10 Enterprise LTSC 2015 | Windows 10, Version 1507 | 7/29/2015 |
|
| Windows 10 Enterprise LTSC 2015 | Windows 10, Version 1507 | 7/29/2015 |
|
||||||
| Windows 10 Enterprise LTSC 2016 | Windows 10, Version 1607 | 8/2/2016 |
|
| Windows 10 Enterprise LTSC 2016 | Windows 10, Version 1607 | 8/2/2016 |
|
||||||
| Windows 10 Enterprise LTSC 2019 | Windows 10, Version 1809 | 11/13/2018 |
|
| Windows 10 Enterprise LTSC 2019 | Windows 10, Version 1809 | 11/13/2018 |
|
||||||
|
| Windows 10 Enterprise LTSC 2019 | Windows 10, Version 21H2 | 11/16/2021 |
|
||||||
|
|
||||||
>[!NOTE]
|
> [!NOTE]
|
||||||
>The Long-Term Servicing Channel was previously called the Long-Term Servicing Branch (LTSB). All references to LTSB are changed in this article to LTSC for consistency, even though the name of previous versions might still be displayed as LTSB.
|
> The Long-Term Servicing Channel was previously called the Long-Term Servicing Branch (LTSB). All references to LTSB are changed in this article to LTSC for consistency, even though the name of previous versions might still be displayed as LTSB.
|
||||||
|
|
||||||
With the LTSC servicing model, customers can delay receiving feature updates and instead only receive monthly quality updates on devices. Features from Windows 10 that could be updated with new functionality, including Cortana, Edge, and all in-box Universal Windows apps, are also not included. Feature updates are offered in new LTSC releases every 2–3 years instead of every 6 months, and organizations can choose to install them as in-place upgrades or even skip releases over a 10-year life cycle. Microsoft is committed to providing bug fixes and security patches for each LTSC release during this 10 year period.
|
With the LTSC servicing model, customers can delay receiving feature updates and instead only receive monthly quality updates on devices. Features from Windows 10 that could be updated with new functionality, including Cortana, Edge, and all in-box Universal Windows apps, are also not included. Feature updates are offered in new LTSC releases every 2–3 years instead of every 6 months, and organizations can choose to install them as in-place upgrades or even skip releases over a 10-year life cycle. Microsoft is committed to providing bug fixes and security patches for each LTSC release during this 10 year period.
|
||||||
|
|
||||||
>[!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
>The Long-Term Servicing Channel is not intended for deployment on most or all the PCs in an organization. The LTSC edition of Windows 10 provides customers with access to a deployment option for their special-purpose devices and environments. These devices typically perform a single important task and don’t need feature updates as frequently as other devices in the organization. These devices are also typically not heavily dependent on support from external apps and tools. Since the feature set for LTSC does not change for the lifetime of the release, over time there might be some external tools that do not continue to provide legacy support. See [LTSC: What is it, and when it should be used](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181).
|
> The Long-Term Servicing Channel is not intended for deployment on most or all the PCs in an organization. The LTSC edition of Windows 10 provides customers with access to a deployment option for their special-purpose devices and environments. These devices typically perform a single important task and don’t need feature updates as frequently as other devices in the organization. These devices are also typically not heavily dependent on support from external apps and tools. Since the feature set for LTSC does not change for the lifetime of the release, over time there might be some external tools that do not continue to provide legacy support. See [LTSC: What is it, and when it should be used](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181).
|
||||||
|
|
||||||
For detailed information about Windows 10 servicing, see [Overview of Windows as a service](/windows/deployment/update/waas-overview).
|
For detailed information about Windows 10 servicing, see [Overview of Windows as a service](/windows/deployment/update/waas-overview).
|
||||||
|
|
||||||
|
|||||||
@ -36,7 +36,7 @@ The Windows 10 Enterprise LTSC 2019 release is an important release for LTSC use
|
|||||||
|
|
||||||
## Microsoft Intune
|
## Microsoft Intune
|
||||||
|
|
||||||
Microsoft Intune supports Windows 10 Enterprise LTSC 2019 and later. This includes support for features such as [Windows Autopilot](#windows-autopilot). However, note that Windows 10 Update Rings Device profiles do not support LTSC releases, therefore you should use [Policy configuration service provider](/windows/client-management/mdm/policy-csp-update), WSUS, or Configuration Manager for patching.
|
Microsoft Intune supports Windows 10 Enterprise LTSC 2019 and later. However, note that Windows 10 Update Rings Device profiles do not support LTSC releases, therefore you should use [Policy configuration service provider](/windows/client-management/mdm/policy-csp-update), WSUS, or Configuration Manager for patching.
|
||||||
|
|
||||||
## Security
|
## Security
|
||||||
|
|
||||||
@ -48,7 +48,7 @@ This version of Window 10 includes security improvements for threat protection,
|
|||||||
|
|
||||||
The [Microsoft Defender for Endpoint](/windows/security/threat-protection/index) platform includes the security pillars shown in the following diagram. In this version of Windows, Defender for Endpoint includes powerful analytics, security stack integration, and centralized management for better detection, prevention, investigation, response, and management.
|
The [Microsoft Defender for Endpoint](/windows/security/threat-protection/index) platform includes the security pillars shown in the following diagram. In this version of Windows, Defender for Endpoint includes powerful analytics, security stack integration, and centralized management for better detection, prevention, investigation, response, and management.
|
||||||
|
|
||||||
|
[  ](../images/wdatp.png#lightbox)
|
||||||
|
|
||||||
##### Attack surface reduction
|
##### Attack surface reduction
|
||||||
|
|
||||||
@ -188,26 +188,6 @@ This is an update to the [BitLocker CSP](/windows/client-management/mdm/bitlocke
|
|||||||
|
|
||||||
This feature will soon be enabled on Olympia Corp as an optional feature.
|
This feature will soon be enabled on Olympia Corp as an optional feature.
|
||||||
|
|
||||||
#### Delivering BitLocker policy to AutoPilot devices during OOBE
|
|
||||||
|
|
||||||
You can choose which encryption algorithm to apply to BitLocker encryption capable devices, rather than automatically having those devices encrypt themselves with the default algorithm. This allows the encryption algorithm (and other BitLocker policies that must be applied prior to encryption), to be delivered before BitLocker encryption begins.
|
|
||||||
|
|
||||||
For example, you can choose the XTS-AES 256 encryption algorithm, and have it applied to devices that would normally encrypt themselves automatically with the default XTS-AES 128 algorithm during OOBE.
|
|
||||||
|
|
||||||
To achieve this:
|
|
||||||
|
|
||||||
1. Configure the [encryption method settings](/intune/endpoint-protection-windows-10#windows-encryption) in the Windows 10 Endpoint Protection profile to the desired encryption algorithm.
|
|
||||||
|
|
||||||
2. [Assign the policy](/intune/device-profile-assign) to your Autopilot device group.
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> The encryption policy must be assigned to **devices** in the group, not users.
|
|
||||||
|
|
||||||
3. Enable the Autopilot [Enrollment Status Page](/windows/deployment/windows-autopilot/enrollment-status) (ESP) for these devices.
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> If the ESP is not enabled, the policy will not apply before encryption starts.
|
|
||||||
|
|
||||||
### Identity protection
|
### Identity protection
|
||||||
|
|
||||||
Improvements have been added are to Windows Hello for Business and Credential Guard.
|
Improvements have been added are to Windows Hello for Business and Credential Guard.
|
||||||
@ -288,24 +268,11 @@ A new security policy setting
|
|||||||
|
|
||||||
We’ve continued to work on the **Current threats** area in [Virus & threat protection](/windows/security/threat-protection/windows-defender-security-center/wdsc-virus-threat-protection), which now displays all threats that need action. You can quickly take action on threats from this screen:
|
We’ve continued to work on the **Current threats** area in [Virus & threat protection](/windows/security/threat-protection/windows-defender-security-center/wdsc-virus-threat-protection), which now displays all threats that need action. You can quickly take action on threats from this screen:
|
||||||
|
|
||||||
|
> [!div class="mx-imgBorder"]
|
||||||
|
> 
|
||||||
|
|
||||||
## Deployment
|
## Deployment
|
||||||
|
|
||||||
### Windows Autopilot
|
|
||||||
|
|
||||||
[Windows Autopilot](/windows/deployment/windows-autopilot/windows-autopilot) is a deployment tool introduced with Windows 10, version 1709 and is also available for Windows 10 Enterprise LTSC 2019 (and later versions). Windows Autopilot provides a modern device lifecycle management service powered by the cloud to deliver a zero touch experience for deploying Windows 10.
|
|
||||||
|
|
||||||
Windows Autopilot is currently available with Surface, Dell, HP, and Lenovo. Other OEM partners such as Panasonic, and Acer will support Autopilot soon. Check the [Windows IT Pro Blog](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows10Blog) or this article for updated information.
|
|
||||||
|
|
||||||
Using Intune, Autopilot now enables locking the device during provisioning during the Windows Out Of Box Experience (OOBE) until policies and settings for the device get provisioned, thereby ensuring that by the time the user gets to the desktop, the device is secured and configured correctly.
|
|
||||||
|
|
||||||
You can also apply an Autopilot deployment profile to your devices using Microsoft Store for Business. When people in your organization run the out-of-box experience on the device, the profile configures Windows based on the Autopilot deployment profile you applied to the device. For more information, see [Manage Windows device deployment with Windows Autopilot Deployment](/microsoft-store/add-profile-to-devices).
|
|
||||||
|
|
||||||
#### Autopilot Reset
|
|
||||||
|
|
||||||
IT Pros can use Autopilot Reset to quickly remove personal files, apps, and settings. A custom login screen is available from the lock screen that enables you to apply original settings and management enrollment (Azure Active Directory and device management) so that devices are returned to a fully configured, known, IT-approved state and ready to use. For more information, see [Reset devices with Autopilot Reset](/education/windows/autopilot-reset).
|
|
||||||
|
|
||||||
### MBR2GPT.EXE
|
### MBR2GPT.EXE
|
||||||
|
|
||||||
MBR2GPT.EXE is a new command-line tool introduced with Windows 10, version 1703 and also available in Windows 10 Enterprise LTSC 2019 (and later versions). MBR2GPT converts a disk from Master Boot Record (MBR) to GUID Partition Table (GPT) partition style without modifying or deleting data on the disk. The tool is designed to be run from a Windows Preinstallation Environment (Windows PE) command prompt, but can also be run from the full Windows 10 operating system (OS).
|
MBR2GPT.EXE is a new command-line tool introduced with Windows 10, version 1703 and also available in Windows 10 Enterprise LTSC 2019 (and later versions). MBR2GPT converts a disk from Master Boot Record (MBR) to GUID Partition Table (GPT) partition style without modifying or deleting data on the disk. The tool is designed to be run from a Windows Preinstallation Environment (Windows PE) command prompt, but can also be run from the full Windows 10 operating system (OS).
|
||||||
|
|||||||
248
windows/whats-new/ltsc/whats-new-windows-10-2021.md
Normal file
248
windows/whats-new/ltsc/whats-new-windows-10-2021.md
Normal file
@ -0,0 +1,248 @@
|
|||||||
|
---
|
||||||
|
title: What's new in Windows 10 Enterprise LTSC 2021
|
||||||
|
ms.reviewer:
|
||||||
|
manager: dougeby
|
||||||
|
ms.author: greglin
|
||||||
|
description: New and updated IT Pro content about new features in Windows 10 Enterprise LTSC 2021.
|
||||||
|
keywords: ["What's new in Windows 10", "Windows 10", "Windows 10 Enterprise LTSC 2021"]
|
||||||
|
ms.prod: w10
|
||||||
|
ms.mktglfcycl: deploy
|
||||||
|
ms.sitesec: library
|
||||||
|
author: greg-lindsay
|
||||||
|
ms.localizationpriority: low
|
||||||
|
ms.topic: article
|
||||||
|
---
|
||||||
|
|
||||||
|
# What's new in Windows 10 Enterprise LTSC 2021
|
||||||
|
|
||||||
|
**Applies to**
|
||||||
|
- Windows 10 Enterprise LTSC 2021
|
||||||
|
|
||||||
|
This article lists new and updated features and content that is of interest to IT Pros for Windows 10 Enterprise LTSC 2021, compared to Windows 10 Enterprise LTSC 2019 (LTSB). For a brief description of the LTSC servicing channel and associated support, see [Windows 10 Enterprise LTSC](index.md).
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> Features in Windows 10 Enterprise LTSC 2021 are equivalent to Windows 10, version 21H2.<br>
|
||||||
|
> The LTSC release is [intended for special use devices](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181). Support for LTSC by apps and tools that are designed for the semi-annual channel release of Windows 10 might be limited.
|
||||||
|
|
||||||
|
Windows 10 Enterprise LTSC 2021 builds on Windows 10 Enterprise LTSC 2019, adding premium features such as advanced protection against modern security threats and comprehensive device management, app management, and control capabilities.
|
||||||
|
|
||||||
|
The Windows 10 Enterprise LTSC 2021 release includes the cumulative enhancements provided in Windows 10 versions 1903, 1909, 2004, 21H1, and 21H2. Details about these enhancements are provided below.
|
||||||
|
|
||||||
|
## Lifecycle
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> Windows 10 Enterprise LTSC 2021 has a 5 year lifecycle ([IoT](/windows/iot/product-family/what's-new-in-windows-10-iot-enterprise-21h2) continues to have a [10 year lifecycle](/windows/iot/product-family/product-lifecycle?tabs=2021)). Thus, the LTSC 2021 release is not a direct replacement for LTSC 2019, which has a 10 year lifecycle.
|
||||||
|
|
||||||
|
For more information about the lifecycle for this release, see [The next Windows 10 Long Term Servicing Channel (LTSC) release](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/the-next-windows-10-long-term-servicing-channel-ltsc-release/ba-p/2147232).
|
||||||
|
|
||||||
|
## Hardware security
|
||||||
|
|
||||||
|
### System Guard
|
||||||
|
|
||||||
|
[System Guard](/windows/security/threat-protection/windows-defender-system-guard/how-hardware-based-root-of-trust-helps-protect-windows) has improved a feature in this version of Windows called **SMM Firmware Protection**. This feature is built on top of [System Guard Secure Launch](/windows/security/threat-protection/windows-defender-system-guard/system-guard-secure-launch-and-smm-protection) to reduce the firmware attack surface and ensure that the System Management Mode (SMM) firmware on the device is operating in a healthy manner - specifically, SMM code cannot access the OS memory and secrets.
|
||||||
|
|
||||||
|
In this release, [Windows Defender System Guard](/windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows) enables an even *higher* level of [System Management Mode](/windows/security/threat-protection/windows-defender-system-guard/how-hardware-based-root-of-trust-helps-protect-windows#system-management-mode-smm-protection) (SMM) Firmware Protection that goes beyond checking the OS memory and secrets to other resources like registers and IO.
|
||||||
|
|
||||||
|
With this improvement, the OS can detect a higher level of SMM compliance, enabling devices to be even more hardened against SMM exploits and vulnerabilities. Based on the platform, the underlying hardware and firmware, there are three versions of SMM Firmware Protection (one, two and three), with each subsequent versions offering stronger protections than the preceding ones.
|
||||||
|
|
||||||
|
There are already devices in the market today that offer SMM Firmware Protection versions one and two. SMM Firmware Protection version three This feature is currently forward-looking and requires new hardware that will be made available soon.
|
||||||
|
|
||||||
|
## Operating system security
|
||||||
|
|
||||||
|
### System security
|
||||||
|
|
||||||
|
[Windows Security app](/windows/security/threat-protection/windows-defender-security-center/windows-defender-security-center) improvements now include Protection history, including detailed and easier to understand information about threats and available actions, Controlled Folder Access blocks are now in the Protection history, Windows Defender Offline Scanning tool actions, and any pending recommendations.
|
||||||
|
|
||||||
|
### Encryption and data protection
|
||||||
|
|
||||||
|
BitLocker and Mobile Device Management (MDM) with Azure Active Directory work together to protect your devices from accidental password disclosure. Now, a new key-rolling feature securely rotates recovery passwords on MDM-managed devices. The feature is activated whenever Microsoft Intune/MDM tools or a recovery password is used to unlock a BitLocker protected drive. As a result, the recovery password will be better protected when users manually unlock a BitLocker drive.
|
||||||
|
|
||||||
|
### Network security
|
||||||
|
|
||||||
|
#### Windows Defender Firewall
|
||||||
|
|
||||||
|
Windows Defender Firewall now offers the following benefits:
|
||||||
|
|
||||||
|
**Reduce risk**: Windows Defender Firewall reduces the attack surface of a device with rules to restrict or allow traffic by many properties, such as IP addresses, ports, or program paths. Reducing the attack surface of a device increases manageability and decreases the likelihood of a successful attack.
|
||||||
|
|
||||||
|
**Safeguard data**: With integrated Internet Protocol Security (IPsec), Windows Defender Firewall provides a simple way to enforce authenticated, end-to-end network communications. It provides scalable, tiered access to trusted network resources, helping to enforce integrity of the data, and optionally helping to protect the confidentiality of the data.
|
||||||
|
|
||||||
|
**Extend value**: Windows Defender Firewall is a host-based firewall that is included with the operating system, so there is no additional hardware or software required. Windows Defender Firewall is also designed to complement existing non-Microsoft network security solutions through a documented application programming interface (API).
|
||||||
|
|
||||||
|
The Windows Defender Firewall is also now easier to analyze and debug. IPsec behavior has been integrated with Packet Monitor (pktmon), an in-box cross-component network diagnostic tool for Windows.
|
||||||
|
|
||||||
|
Additionally, the Windows Defender Firewall event logs have been enhanced to ensure an audit can identify the specific filter that was responsible for any given event. This enables analysis of firewall behavior and rich packet capture without relying on other tools.
|
||||||
|
|
||||||
|
Windows Defender Firewall also now supports [Windows Subsystem for Linux (WSL)](/windows/wsl/); You can add rules for WSL process, just like for Windows processes. For more information, see [Windows Defender Firewall now supports Windows Subsystem for Linux (WSL)](https://blogs.windows.com/windowsexperience/2018/04/19/announcing-windows-10-insider-preview-build-17650-for-skip-ahead/#II14f7VlSBcZ0Gs4.97).
|
||||||
|
|
||||||
|
### Virus and threat protection
|
||||||
|
|
||||||
|
[Attack surface area reduction](/windows/security/threat-protection/windows-defender-atp/overview-attack-surface-reduction) – IT admins can configure devices with advanced web protection that enables them to define allow and deny lists for specific URL’s and IP addresses.
|
||||||
|
[Next generation protection](/microsoft-365/security/defender-endpoint/microsoft-defender-antivirus-in-windows-10) – Controls have been extended to protection from ransomware, credential misuse, and attacks that are transmitted through removable storage.
|
||||||
|
- Integrity enforcement capabilities – Enable remote runtime attestation of Windows 10 platform.
|
||||||
|
- [Tamper-proofing](/microsoft-365/security/defender-endpoint/prevent-changes-to-security-settings-with-tamper-protection) capabilities – Uses virtualization-based security to isolate critical Microsoft Defender for Endpoint security capabilities away from the OS and attackers.
|
||||||
|
[Platform support](https://techcommunity.microsoft.com/t5/Windows-Defender-ATP/Protecting-Windows-Server-with-Windows-Defender-ATP/ba-p/267114) – In addition to Windows 10, Microsoft Defender for Endpoint’s functionality has been extended to support Windows 7 and Windows 8.1 clients, as well as macOS, Linux, and Windows Server with both its Endpoint Detection (EDR) and Endpoint Protection Platform (EPP) capabilities.
|
||||||
|
|
||||||
|
**Advanced machine learning**: Improved with advanced machine learning and AI models that enable it to protect against apex attackers using innovative vulnerability exploit techniques, tools and malware.
|
||||||
|
|
||||||
|
**Emergency outbreak protection**: Provides emergency outbreak protection which will automatically update devices with new intelligence when a new outbreak has been detected.
|
||||||
|
|
||||||
|
**Certified ISO 27001 compliance**: Ensures that the cloud service has analyzed for threats, vulnerabilities and impacts, and that risk management and security controls are in place.
|
||||||
|
|
||||||
|
**Geolocation support**: Support geolocation and sovereignty of sample data as well as configurable retention policies.
|
||||||
|
|
||||||
|
**Improved support for non-ASCII file paths** for Microsoft Defender Advanced Threat Protection (ATP) Auto Incident Response (IR).
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> The [DisableAntiSpyware](/windows-hardware/customize/desktop/unattend/security-malware-windows-defender-disableantispyware) parameter is deprecated in this release.
|
||||||
|
|
||||||
|
## Application security
|
||||||
|
|
||||||
|
### App isolation
|
||||||
|
|
||||||
|
[Windows Sandbox](https://techcommunity.microsoft.com/t5/Windows-Kernel-Internals/Windows-Sandbox/ba-p/301849): Isolated desktop environment where you can run untrusted software without the fear of lasting impact to your device.
|
||||||
|
|
||||||
|
#### Microsoft Defender Application Guard
|
||||||
|
|
||||||
|
[Microsoft Defender Application Guard](/windows/security/threat-protection/windows-defender-application-guard/wd-app-guard-overview) enhancements include:
|
||||||
|
- Standalone users can install and configure their Windows Defender Application Guard settings without needing to change registry key settings. Enterprise users can check their settings to see what their administrators have configured for their machines to better understand the behavior.
|
||||||
|
- Application Guard is now an extension in Google Chrome and Mozilla Firefox. Many users are in a hybrid browser environment, and would like to extend Application Guard’s browser isolation technology beyond Microsoft Edge. In the latest release, users can install the Application Guard extension in their Chrome or Firefox browsers. This extension will redirect untrusted navigation to the Application Guard Edge browser. There is also a companion app to enable this feature in the Microsoft Store. Users can quickly launch Application Guard from their desktop using this app. This feature is also available in Windows 10, version 1803 or later with the latest updates.
|
||||||
|
|
||||||
|
To try this extension:
|
||||||
|
1. Configure Application Guard policies on your device.
|
||||||
|
2. Go to the Chrome Web Store or Firefox Add-ons and search for Application Guard. Install the extension.
|
||||||
|
3. Follow any additional configuration steps on the extension setup page.
|
||||||
|
4. Reboot the device.
|
||||||
|
5. Navigate to an untrusted site in Chrome and Firefox.
|
||||||
|
|
||||||
|
**Dynamic navigation**: Application Guard now allows users to navigate back to their default host browser from the Application Guard Microsoft Edge. Previously, users browsing in Application Guard Edge would see an error page when they try to go to a trusted site within the container browser. With this new feature, users will automatically be redirected to their host default browser when they enter or click on a trusted site in Application Guard Edge. This feature is also available in Windows 10, version 1803 or later with the latest updates.
|
||||||
|
|
||||||
|
Application Guard performance is improved with optimized document opening times:
|
||||||
|
- An issue is fixed that could cause a one minute or more delay when you open a Microsoft Defender Application Guard (Application Guard) Office document. This can occur when you try to open a file using a Universal Naming Convention (UNC) path or Server Message Block (SMB) share link.
|
||||||
|
- A memory issue is fixed that could cause an Application Guard container to use almost 1 GB of working set memory when the container is idle.
|
||||||
|
- The performance of Robocopy is improved when copying files over 400 MB in size.
|
||||||
|
|
||||||
|
[Edge support for Microsoft Defender Application Guard](/deployedge/microsoft-edge-security-windows-defender-application-guard) has been available for Chromium-based Edge since early 2020.
|
||||||
|
|
||||||
|
**Application Guard now supports Office**: With [Microsoft Defender Application Guard for Office](/microsoft-365/security/office-365-security/install-app-guard), you can launch untrusted Office documents (from outside the Enterprise) in an isolated container to prevent potentially malicious content from compromising your device.
|
||||||
|
|
||||||
|
### Application Control
|
||||||
|
|
||||||
|
[Application Control for Windows](/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control): In Windows 10, version 1903 WDAC added a number of new features that light up key scenarios and provide feature parity with AppLocker.
|
||||||
|
- [Multiple Policies](/windows/security/threat-protection/windows-defender-application-control/deploy-multiple-windows-defender-application-control-policies): WDAC now supports multiple simultaneous code integrity policies for one device in order to enable the following scenarios: 1) enforce and audit side by side, 2) simpler targeting for policies with different scope/intent, 3) expanding a policy using a new ‘supplemental’ policy.
|
||||||
|
- [Path-Based Rules](/windows/security/threat-protection/windows-defender-application-control/create-path-based-rules): The path condition identifies an app by its location in the file system of the computer or on the network instead of a signer or hash identifier. Additionally, WDAC has an option that allows admins to enforce at runtime that only code from paths that are not user-writeable is executed. When code tries to execute at runtime, the directory is scanned and files will be checked for write permissions for non-known admins. If a file is found to be user writeable, the executable is blocked from running unless it is authorized by something other than a path rule like a signer or hash rule.<br>
|
||||||
|
This brings WDAC to functionality parity with AppLocker in terms of support for file path rules. WDAC improves upon the security of policies based on file path rules with the availability of the user-writability permission checks at runtime time, which is a capability that is not available with AppLocker.
|
||||||
|
- [Allow COM Object Registration](/windows/security/threat-protection/windows-defender-application-control/allow-com-object-registration-in-windows-defender-application-control-policy): Previously, WDAC enforced a built-in allow list for COM object registration. While this mechanism works for most common application usage scenarios, customers have provided feedback that there are cases where additional COM objects need to be allowed. The 1903 update to Windows 10 introduces the ability to specify allowed COM objects via their GUID in the WDAC policy.
|
||||||
|
|
||||||
|
## Identity and privacy
|
||||||
|
|
||||||
|
### Secured identity
|
||||||
|
|
||||||
|
Windows Hello enhancements include:
|
||||||
|
- Windows Hello is now supported as Fast Identity Online 2 (FIDO2) authenticator across all major browsers including Chrome and Firefox.
|
||||||
|
- You can now enable passwordless sign-in for Microsoft accounts on your Windows 10 device by going to **Settings > Accounts > Sign-in options**, and selecting **On** under **Make your device passwordless**. Enabling passwordless sign in will switch all Microsoft accounts on your Windows 10 device to modern authentication with Windows Hello Face, Fingerprint, or PIN.
|
||||||
|
- Windows Hello PIN sign-in support is [added to Safe mode](/windows-insider/archive/new-in-20H1#windows-hello-pin-in-safe-mode-build-18995).
|
||||||
|
- Windows Hello for Business now has Hybrid Azure Active Directory support and phone number sign-in (MSA). FIDO2 security key support is expanded to Azure Active Directory hybrid environments, enabling enterprises with hybrid environments to take advantage of [passwordless authentication](/azure/active-directory/authentication/howto-authentication-passwordless-security-key-on-premises). For more information, see [Expanding Azure Active Directory support for FIDO2 preview to hybrid environments](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/expanding-azure-active-directory-support-for-fido2-preview-to/ba-p/981894).
|
||||||
|
- With specialized hardware and software components available on devices shipping with Windows 10, version 20H2 configured out of factory, Windows Hello now offers added support for virtualization-based security with supporting fingerprint and face sensors. This feature isolates and secures a user's biometric authentication data.
|
||||||
|
- Windows Hello multi-camera support is added, allowing users to choose an external camera priority when both external and internal Windows Hello-capable cameras are present.
|
||||||
|
- [Windows Hello FIDO2 certification](https://fidoalliance.org/microsoft-achieves-fido2-certification-for-windows-hello/): Windows Hello is now a FIDO2 Certified authenticator and enables password-less login for websites supporting FIDO2 authentication, such as Microsoft account and Azure AD.
|
||||||
|
- [Streamlined Windows Hello PIN reset experience](/windows/security/identity-protection/hello-for-business/hello-videos#windows-hello-for-business-forgotten-pin-user-experience): Microsoft account users have a revamped Windows Hello PIN reset experience with the same look and feel as signing in on the web.
|
||||||
|
- [Remote Desktop with Biometrics](/windows/security/identity-protection/hello-for-business/hello-feature-remote-desktop#remote-desktop-with-biometrics): Azure Active Directory and Active Directory users using Windows Hello for Business can use biometrics to authenticate to a remote desktop session.
|
||||||
|
|
||||||
|
### Credential protection
|
||||||
|
|
||||||
|
#### Windows Defender Credential Guard
|
||||||
|
|
||||||
|
[Windows Defender Credential Guard](/windows/security/identity-protection/credential-guard/credential-guard) is now available for ARM64 devices, for additional protection against credential theft for enterprises deploying ARM64 devices in their organizations, such as Surface Pro X.
|
||||||
|
|
||||||
|
### Privacy controls
|
||||||
|
|
||||||
|
[Microphone privacy settings](https://support.microsoft.com/en-us/help/4468232/windows-10-camera-microphone-and-privacy-microsoft-privacy): A microphone icon appears in the notification area letting you see which apps are using your microphone.
|
||||||
|
|
||||||
|
## Cloud Services
|
||||||
|
|
||||||
|
### Microsoft Endpoint Manager
|
||||||
|
|
||||||
|
Configuration Manager, Intune, Desktop Analytics, Co-Management, and Device Management Admin Console are now [Microsoft Endpoint Manager](/configmgr/). See the Nov. 4 2019 [announcement](https://www.microsoft.com/microsoft-365/blog/2019/11/04/use-the-power-of-cloud-intelligence-to-simplify-and-accelerate-it-and-the-move-to-a-modern-workplace/). Also see [Modern management and security principles driving our Microsoft Endpoint Manager vision](https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/Modern-management-and-security-principles-driving-our-Microsoft/ba-p/946797).
|
||||||
|
|
||||||
|
### Configuration Manager
|
||||||
|
|
||||||
|
An in-place upgrade wizard is available in Configuration Manager. For more information, see [Simplifying Windows 10 deployment with Configuration Manager](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/simplifying-windows-10-deployment-with-configuration-manager/ba-p/1214364).
|
||||||
|
|
||||||
|
#### Microsoft Intune
|
||||||
|
|
||||||
|
Microsoft Intune supports Windows 10 Enterprise LTSC 2021, except for [Windows Update Rings](/mem/intune/configuration/device-profile-create#create-the-profile) in device profiles.
|
||||||
|
|
||||||
|
A new Intune remote action: **Collect diagnostics**, lets you collect the logs from corporate devices without interrupting or waiting for the end user. For more information, see [Collect diagnostics remote action](/mem/intune/fundamentals/whats-new#collect-diagnostics-remote-action).
|
||||||
|
|
||||||
|
Intune has also added capabilities to [Role-based access control](/mem/intune/fundamentals/whats-new#role-based-access-control) (RBAC) that can be used to further define profile settings for the Enrollment Status Page (ESP). For more information see [Create Enrollment Status Page profile and assign to a group](/mem/intune/enrollment/windows-enrollment-status#create-enrollment-status-page-profile-and-assign-to-a-group).
|
||||||
|
|
||||||
|
For a full list of what's new in Microsoft Intune, see [What's new in Microsoft Intune](/mem/intune/fundamentals/whats-new).
|
||||||
|
|
||||||
|
### Mobile Device Management
|
||||||
|
|
||||||
|
Mobile Device Management (MDM) policy is extended with new [Local Users and Groups settings](/windows/client-management/mdm/policy-csp-localusersandgroups) that match the options available for devices managed through Group Policy.
|
||||||
|
|
||||||
|
For more information about what's new in MDM, see [What's new in mobile device enrollment and management](/windows/client-management/mdm/new-in-windows-mdm-enrollment-management)
|
||||||
|
|
||||||
|
Windows Management Instrumentation (WMI) Group Policy Service (GPSVC) has a performance improvement to support remote work scenarios:
|
||||||
|
- An issue is fixed that caused changes by an Active Directory (AD) administrator to user or computer group memberships to propagate slowly. Although the access token eventually updates, these changes might not appear when the administrator uses gpresult /r or gpresult /h to create a report.
|
||||||
|
|
||||||
|
#### Key-rolling and Key-rotation
|
||||||
|
|
||||||
|
This release also includes two new features called Key-rolling and Key-rotation enables secure rolling of Recovery passwords on MDM-managed AAD devices on demand from Microsoft Intune/MDM tools or when a recovery password is used to unlock the BitLocker protected drive. This feature will help prevent accidental recovery password disclosure as part of manual BitLocker drive unlock by users.
|
||||||
|
|
||||||
|
## Deployment
|
||||||
|
|
||||||
|
### SetupDiag
|
||||||
|
|
||||||
|
[SetupDiag](/windows/deployment/upgrade/setupdiag) is a command-line tool that can help diagnose why a Windows 10 update failed. SetupDiag works by searching Windows Setup log files. When searching log files, SetupDiag uses a set of rules to match known issues. In the current version of SetupDiag there are 53 rules contained in the rules.xml file, which is extracted when SetupDiag is run. The rules.xml file will be updated as new versions of SetupDiag are made available.
|
||||||
|
|
||||||
|
### Reserved storage
|
||||||
|
|
||||||
|
[**Reserved storage**](https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Windows-10-and-reserved-storage/ba-p/428327): Reserved storage sets aside disk space to be used by updates, apps, temporary files, and system caches. It improves the day-to-day function of your PC by ensuring critical OS functions always have access to disk space. Reserved storage will be enabled automatically on new PCs with Windows 10, version 1903 pre-installed, and for clean installs. It will not be enabled when updating from a previous version of Windows 10.
|
||||||
|
|
||||||
|
### Windows Assessment and Deployment Toolkit (ADK)
|
||||||
|
|
||||||
|
A new [Windows ADK](/windows-hardware/get-started/adk-install) is available for Windows 11 that also supports Windows 10, version 21H2.
|
||||||
|
|
||||||
|
### Microsoft Deployment Toolkit (MDT)
|
||||||
|
|
||||||
|
For the latest information about MDT, see the [MDT release notes](/mem/configmgr/mdt/release-notes).
|
||||||
|
|
||||||
|
### Windows Setup
|
||||||
|
|
||||||
|
Windows Setup [answer files](/windows-hardware/manufacture/desktop/update-windows-settings-and-scripts-create-your-own-answer-file-sxs) (unattend.xml) have improved language handling.
|
||||||
|
|
||||||
|
Improvements in Windows Setup with this release also include:
|
||||||
|
- Reduced offline time during feature updates
|
||||||
|
- Improved controls for reserved storage
|
||||||
|
- Improved controls and diagnostics
|
||||||
|
- New recovery options
|
||||||
|
|
||||||
|
For more information, see Windows Setup enhancements in the [Windows IT Pro Blog](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/pilot-new-features-with-the-windows-insider-program-for-business/ba-p/1220464).
|
||||||
|
|
||||||
|
## Microsoft Edge
|
||||||
|
|
||||||
|
Microsoft Edge Browser support is now included in-box.
|
||||||
|
|
||||||
|
### Microsoft Edge kiosk mode
|
||||||
|
|
||||||
|
Microsoft Edge kiosk mode is available for LTSC releases starting in Windows 10 Enterprise 2021 LTSC and [Windows 10 IoT Enterprise 2021 LTSC](/windows/iot/product-family/what's-new-in-windows-10-iot-enterprise-21h2).
|
||||||
|
|
||||||
|
Microsoft Edge kiosk mode offers two lockdown experiences of the browser so organizations can create, manage, and provide the best experience for their customers. The following lockdown experiences are available:
|
||||||
|
- Digital/Interactive Signage experience - Displays a specific site in full-screen mode.
|
||||||
|
- Public-Browsing experience - Runs a limited multi-tab version of Microsoft Edge.
|
||||||
|
- Both experiences are running a Microsoft Edge InPrivate session, which protects user data.
|
||||||
|
|
||||||
|
## Windows Subsystem for Linux
|
||||||
|
|
||||||
|
Windows Subsystem for Linux (WSL) is be available in-box.
|
||||||
|
|
||||||
|
## Networking
|
||||||
|
|
||||||
|
WPA3 H2E standards are supported for enhanced Wi-Fi security.
|
||||||
|
|
||||||
|
## See Also
|
||||||
|
|
||||||
|
[Windows 10 Enterprise LTSC](index.md): A short description of the LTSC servicing channel with links to information about each release.
|
||||||
@ -35,21 +35,13 @@ This article lists new and updated features and content that are of interest to
|
|||||||
- Windows Autopilot is self-updating during OOBE. Starting with the Windows 10, version 1903 Autopilot functional and critical updates will begin downloading automatically during OOBE.
|
- Windows Autopilot is self-updating during OOBE. Starting with the Windows 10, version 1903 Autopilot functional and critical updates will begin downloading automatically during OOBE.
|
||||||
- Windows Autopilot will set the [diagnostics data](/windows/privacy/windows-diagnostic-data) level to Full on Windows 10 version 1903 and later during OOBE.
|
- Windows Autopilot will set the [diagnostics data](/windows/privacy/windows-diagnostic-data) level to Full on Windows 10 version 1903 and later during OOBE.
|
||||||
|
|
||||||
### Windows 10 Subscription Activation
|
|
||||||
|
|
||||||
Windows 10 Education support has been added to Windows 10 Subscription Activation.
|
|
||||||
|
|
||||||
With Windows 10, version 1903, you can step-up from Windows 10 Pro Education to the enterprise-grade edition for educational institutions – Windows 10 Education. For more information, see [Windows 10 Subscription Activation](/windows/deployment/windows-10-subscription-activation).
|
|
||||||
|
|
||||||
### SetupDiag
|
### SetupDiag
|
||||||
|
|
||||||
[SetupDiag](/windows/deployment/upgrade/setupdiag) version 1.4.1 is available.
|
[SetupDiag](/windows/deployment/upgrade/setupdiag) is a command-line tool that can help diagnose why a Windows 10 update failed. SetupDiag works by searching Windows Setup log files. When searching log files, SetupDiag uses a set of rules to match known issues. In the current version of SetupDiag there are 53 rules contained in the rules.xml file, which is extracted when SetupDiag is run. The rules.xml file will be updated as new versions of SetupDiag are made available.
|
||||||
|
|
||||||
SetupDiag is a command-line tool that can help diagnose why a Windows 10 update failed. SetupDiag works by searching Windows Setup log files. When searching log files, SetupDiag uses a set of rules to match known issues. In the current version of SetupDiag there are 53 rules contained in the rules.xml file, which is extracted when SetupDiag is run. The rules.xml file will be updated as new versions of SetupDiag are made available.
|
|
||||||
|
|
||||||
### Reserved storage
|
### Reserved storage
|
||||||
|
|
||||||
[**Reserved storage**](https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Windows-10-and-reserved-storage/ba-p/428327): Reserved storage sets aside disk space to be used by updates, apps, temporary files, and system caches. It improves the day-to-day function of your PC by ensuring critical OS functions always have access to disk space. Reserved storage will be enabled automatically on new PCs with Windows 10, version 1903 pre-installed, and for clean installs. It will not be enabled when updating from a previous version of Windows 10.
|
[**Reserved storage**](https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Windows-10-and-reserved-storage/ba-p/428327): Reserved storage sets aside disk space to be used by updates, apps, temporary files, and system caches. It improves the day-to-day function of your PC by ensuring critical OS functions always have access to disk space. Reserved storage will be enabled automatically on new PCs with Windows 10, version 1903 or later pre-installed, and for clean installs. It will not be enabled when updating from a previous version of Windows 10.
|
||||||
|
|
||||||
## Servicing
|
## Servicing
|
||||||
|
|
||||||
@ -102,7 +94,7 @@ The draft release of the [security configuration baseline settings](/archive/blo
|
|||||||
|
|
||||||
- [Windows Defender Application Guard](/windows/security/threat-protection/windows-defender-application-guard/wd-app-guard-overview) enhancements:
|
- [Windows Defender Application Guard](/windows/security/threat-protection/windows-defender-application-guard/wd-app-guard-overview) enhancements:
|
||||||
- Standalone users can install and configure their Windows Defender Application Guard settings without needing to change Registry key settings. Enterprise users can check their settings to see what their administrators have configured for their machines to better understand the behavior.
|
- Standalone users can install and configure their Windows Defender Application Guard settings without needing to change Registry key settings. Enterprise users can check their settings to see what their administrators have configured for their machines to better understand the behavior.
|
||||||
- WDAG is now an extension in Google Chrome and Mozilla Firefox. Many users are in a hybrid browser environment, and would like to extend WDAG’s browser isolation technology beyond Microsoft Edge. In the latest release, users can install the WDAG extension in their Chrome or Firefox browsers. This extension will redirect untrusted navigations to the WDAG Edge browser. There is also a companion app to enable this feature in the Microsoft Store. Users can quickly launch WDAG from their desktop using this app. This feature is also available in Windows 10, version 1803 or later with the latest updates.
|
- WDAG is now an extension in Google Chrome and Mozilla Firefox. Many users are in a hybrid browser environment, and would like to extend WDAG’s browser isolation technology beyond Microsoft Edge. In the latest release, users can install the WDAG extension in their Chrome or Firefox browsers. This extension will redirect untrusted navigation to the WDAG Edge browser. There is also a companion app to enable this feature in the Microsoft Store. Users can quickly launch WDAG from their desktop using this app. This feature is also available in Windows 10, version 1803 or later with the latest updates.
|
||||||
|
|
||||||
To try this extension:
|
To try this extension:
|
||||||
1. Configure WDAG policies on your device.
|
1. Configure WDAG policies on your device.
|
||||||
|
|||||||
78
windows/whats-new/whats-new-windows-10-version-21H2.md
Normal file
78
windows/whats-new/whats-new-windows-10-version-21H2.md
Normal file
@ -0,0 +1,78 @@
|
|||||||
|
---
|
||||||
|
title: What's new in Windows 10, version 21H2 for IT pros
|
||||||
|
description: Learn more about what's new in Windows 10 version 21H2, including servicing updates, Windows Subsystem for Linux, the latest CSPs, and more.
|
||||||
|
ms.reviewer:
|
||||||
|
manager: dougeby
|
||||||
|
ms.prod: w10
|
||||||
|
ms.mktglfcycl: deploy
|
||||||
|
ms.sitesec: library
|
||||||
|
ms.pagetype: mobile
|
||||||
|
ms.author: mandia
|
||||||
|
author: MandiOhlinger
|
||||||
|
ms.localizationpriority: medium
|
||||||
|
ms.topic: article
|
||||||
|
---
|
||||||
|
|
||||||
|
# What's new in Windows 10, version 21H2
|
||||||
|
|
||||||
|
**Applies to**:
|
||||||
|
|
||||||
|
- Windows 10, version 21H2
|
||||||
|
|
||||||
|
Windows 10, version 21H2 is the next feature update. This article lists the new and updated features IT Pros should know. Windows 10, version 21H2 is also known as the Windows 10 November 2021 Update. It includes all features and fixes in previous cumulative updates to Windows 10, version 21H1.
|
||||||
|
|
||||||
|
Windows 10, version 21H2 is an [H2-targeted release](/lifecycle/faq/windows#what-is-the-servicing-timeline-for-a-version--feature-update--of-windows-10-), and has the following servicing schedule:
|
||||||
|
|
||||||
|
- **Windows 10 Professional**: Serviced for 24 months from the release date.
|
||||||
|
- **Windows 10 Enterprise**: Serviced for 36 months from the release date.
|
||||||
|
|
||||||
|
Windows 10, version 21H2 is available through Windows Server Update Services (including Configuration Manager), Windows Update for Business, and the Volume Licensing Service Center (VLSC). For more information, see [How to get the Windows 10 November 2021 Update](https://blogs.windows.com/windowsexperience/2021/11/16/how-to-get-the-windows-10-november-2021-update/) and [IT tools to support Windows 10, version 21H2 blog](https://aka.ms/tools-for-21h2).
|
||||||
|
|
||||||
|
Devices running Windows 10, versions 2004, 20H2, and 21H1 can update quickly to version 21H2 using an enablement package. For more information, see [Feature Update through Windows 10, version 21H2 Enablement Package](https://support.microsoft.com/help/5003791).
|
||||||
|
|
||||||
|
To learn more about the status of the November 2021 Update rollout, known issues, and new information, see [Windows release health](/windows/release-health/).
|
||||||
|
|
||||||
|
## Updates and servicing
|
||||||
|
|
||||||
|
Windows 10, version 21H2 feature updates are installed annually using the General Availability Channel. Previous feature updates were installed using the Semi-Annual Channel. For more information on this change, see the [How to get the Windows 10 November 2021 Update](https://blogs.windows.com/windowsexperience/?p=176473).
|
||||||
|
|
||||||
|
Quality updates are still installed monthly on patch Tuesday.
|
||||||
|
|
||||||
|
For more information, see:
|
||||||
|
|
||||||
|
- [Feature and quality update definitions](/windows/deployment/update/waas-quick-start#definitions)
|
||||||
|
- [Windows servicing channels](/windows/deployment/update/waas-overview#servicing-channels)
|
||||||
|
|
||||||
|
## GPU compute support for the Windows Subsystem for Linux
|
||||||
|
|
||||||
|
Starting with Windows 10 version 21H2, the Windows Subsystem for Linux has full graphics processing unit (GPU) compute support. It was available to Windows Insiders, and is now available to everyone. The Linux binaries can use your Windows GPU, and run different workloads, including artificial intelligence (AI) and machine learning (ML) development workflows.
|
||||||
|
|
||||||
|
For more information, and what GPU compute support means for you, see the [GPU accelerated ML training inside the Windows Subsystem for Linux blog post](https://blogs.windows.com/windowsdeveloper/2020/06/17/gpu-accelerated-ml-training-inside-the-windows-subsystem-for-linux/).
|
||||||
|
|
||||||
|
## Get the latest CSPs
|
||||||
|
|
||||||
|
The [KB5005101 September 1, 2021 update](https://support.microsoft.com/topic/september-1-2021-kb5005101-os-builds-19041-1202-19042-1202-and-19043-1202-preview-82a50f27-a56f-4212-96ce-1554e8058dc1) includes about 1400 CSPs that were made available to MDM providers.
|
||||||
|
|
||||||
|
These CSPs are built in to Windows 10, version 21H2. These settings are available in Endpoint Manager in the [Settings Catalog](/mem/intune/configuration/settings-catalog). [Group Policy analytics](/mem/intune/configuration/group-policy-analytics) also includes these GPOs in its analysis.
|
||||||
|
|
||||||
|
For more information on the CSPs, see the [Configuration service provider reference](/windows/client-management/mdm/configuration-service-provider-reference).
|
||||||
|
|
||||||
|
## Apps appear local with Azure Virtual Desktop
|
||||||
|
|
||||||
|
Azure virtual desktop is a Windows client OS hosted in the cloud, and runs virtual apps. You use the cloud to deliver virtual apps in real time, and as-needed. Users use the apps as if they're installed locally.
|
||||||
|
|
||||||
|
You can create Azure virtual desktops that run Windows 10 version 21H2.
|
||||||
|
|
||||||
|
For more information, see:
|
||||||
|
|
||||||
|
- [What is Azure Virtual Desktop?](/azure/virtual-desktop/overview)
|
||||||
|
- [What's new in Azure Virtual Desktop?](/azure/virtual-desktop/whats-new)
|
||||||
|
- [Set up MSIX app attach with the Azure portal](/azure/virtual-desktop/app-attach-azure-portal)
|
||||||
|
|
||||||
|
## Wi-Fi 6E support
|
||||||
|
|
||||||
|
Also known as 802.11ax, Wi-Fi 6E support is built in to Windows 10, version 21H2. Wi-Fi 6E has new channel frequencies that are dedicated to 6E devices, and is more performant for apps that use more bandwidth.
|
||||||
|
|
||||||
|
## Related articles
|
||||||
|
|
||||||
|
- [Release notes for Microsoft Edge Stable Channel](/deployedge/microsoft-edge-relnote-stable-channel)
|
||||||
@ -149,7 +149,7 @@ For more information on the security features you can configure, manage, and enf
|
|||||||
|
|
||||||
- Your Windows 10 apps will also work on Windows 11. **[App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure)** is also available if there are some issues.
|
- Your Windows 10 apps will also work on Windows 11. **[App Assure](https://www.microsoft.com/fasttrack/microsoft-365/app-assure)** is also available if there are some issues.
|
||||||
|
|
||||||
You can continue to use **MSIX packages** for your UWP, Win32, WPF, and WinForm desktop application files. Continue to use **Windows Package Manager** to install Windows apps. Use **Azure Virtual desktop with MSIX app attach** to virtualize desktops and apps. For more information on these features, see [Overview of apps on Windows client devices](/windows/application-management/apps-in-windows-10).
|
You can continue to use **MSIX packages** for your UWP, Win32, WPF, and WinForm desktop application files. Continue to use **Windows Package Manager** to install Windows apps. You can create **Azure virtual desktops** that run Windows 11. Use **Azure Virtual desktop with MSIX app attach** to virtualize desktops and apps. For more information on these features, see [Overview of apps on Windows client devices](/windows/application-management/apps-in-windows-10).
|
||||||
|
|
||||||
In the **Settings** app > **Apps**, users can manage some of the app settings. For example, they can get apps anywhere, but let the user know if there's a comparable app in the Microsoft Store. They can also choose which apps start when they sign in.
|
In the **Settings** app > **Apps**, users can manage some of the app settings. For example, they can get apps anywhere, but let the user know if there's a comparable app in the Microsoft Store. They can also choose which apps start when they sign in.
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user