deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

HTMLTableConversionToMD-batch 04

Browse Source
This commit is contained in:
Alekhya Jupudi 2021-11-11 10:06:53 +05:30
parent 4c78cd460f
commit 6fe235e54a
15 changed files with 308 additions and 1581 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

118
windows/client-management/mdm/get-seats.md
View File

@ -1,6 +1,6 @@
--- ---
title: Get seats title: Get seats
description: The Get seats operation retrieves the information about active seats in the Micorsoft Store for Business. description: The Get seats operation retrieves the information about active seats in the Microsoft Store for Business.
ms.assetid: 32945788-47AC-4259-B616-F359D48F4F2F ms.assetid: 32945788-47AC-4259-B616-F359D48F4F2F
ms.reviewer: ms.reviewer:
manager: dansimp manager: dansimp
@ -18,118 +18,34 @@ The **Get seats** operation retrieves the information about active seats in the
## Request ## Request
<table> **GET:**
<colgroup>
<col width="50%" /> ```http
<col width="50%" /> https://bspmts.mp.microsoft.com/V1/Inventory/{productId}/{skuId}/Seats?continuationToken={ContinuationToken}&amp;maxResults={MaxResults}
</colgroup> ```
<thead>
<tr class="header">
<th>Method</th>
<th>Request URI</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>GET</p></td>
<td><p>https://bspmts.mp.microsoft.com/V1/Inventory/{productId}/{skuId}/Seats?continuationToken={ContinuationToken}&amp;maxResults={MaxResults}</p></td>
</tr>
</tbody>
</table>
 
### URI parameters ### URI parameters
The following parameters may be specified in the request URI. The following parameters may be specified in the request URI.
<table> |Parameter|Type|Description|
<colgroup> |--- |--- |--- |
<col width="33%" /> |productId|string|Required. Product identifier for an application that is used by the Store for Business.|
<col width="33%" /> |skuId|string|Required. Product identifier that specifies a specific SKU of an application.|
<col width="33%" /> |continuationToken|string|Optional.|
</colgroup> |maxResults|int32|Optional. Default = 25, Maximum = 100|
<thead>
<tr class="header">
<th>Parameter</th>
<th>Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>productId</p></td>
<td><p>string</p></td>
<td><p>Required. Product identifier for an application that is used by the Store for Business.</p></td>
</tr>
<tr class="even">
<td><p>skuId</p></td>
<td><p>string</p></td>
<td><p>Required. Product identifier that specifies a specific SKU of an application.</p></td>
</tr>
<tr class="odd">
<td><p>continuationToken</p></td>
<td><p>string</p></td>
<td><p>Optional.</p></td>
</tr>
<tr class="even">
<td><p>maxResults</p></td>
<td><p>int32</p></td>
<td><p>Optional. Default = 25, Maximum = 100</p></td>
</tr>
</tbody>
</table>
 
## Response ## Response
### Response body ### Response body
The response body contains [SeatDetailsResultSet](data-structures-windows-store-for-business.md#seatdetailsresultset). The response body contains [SeatDetailsResultSet](data-structures-windows-store-for-business.md#seatdetailsresultset).
<table> |Error code|Description|Retry|Data field|
<colgroup> |--- |--- |--- |--- |
<col width="25%" /> |400|Invalid parameters|No|Parameter name <br> Reason: Missing parameter or invalid parameter <br> Details: String|
<col width="25%" /> |404|Not found|||
<col width="25%" /> |409|Conflict||Reason: Not online|
<col width="25%" />
</colgroup>
<thead>
<tr class="header">
<th>Error code</th>
<th>Description</th>
<th>Retry</th>
<th>Data field</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>400</p></td>
<td><p>Invalid parameters</p></td>
<td><p>No</p></td>
<td><p>Parameter name</p>
<p>Reason: Missing parameter or invalid parameter</p>
<p>Details: String</p></td>
</tr>
<tr class="even">
<td><p>404</p></td>
<td><p>Not found</p></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><p>409</p></td>
<td><p>Conflict</p></td>
<td></td>
<td><p>Reason: Not online</p></td>
</tr>
</tbody>
</table>
 
 

323
windows/client-management/mdm/healthattestation-csp.md
View File

@ -551,77 +551,16 @@ More information about TPM attestation can be found here: [Microsoft Azure Attes
![healthattestation service diagram.](images/healthattestation_2.png) ![healthattestation service diagram.](images/healthattestation_2.png)
<table> |DHA-Service type|Description|Operation cost|
<col width="20%" /> |--- |--- |--- |
<col width="60%" /> |Device Health Attestation – Cloud (DHA-Cloud)|DHA-Cloud is a Microsoft owned and operated DHA-Service that is:<li>Available in Windows for free<li>Running on a high-availability and geo-balanced cloud infrastructure <li>Supported by most DHA-Enabled device management solutions as the default device attestation service provider<li>Accessible to all enterprise-managed devices via following:<ul><li>FQDN = has.spserv.microsoft.com port<li>Port = 443<li>Protocol = TCP|No cost</ul></li>|
<col width="20%" /> |Device Health Attestation – On Premise(DHA-OnPrem)|DHA-OnPrem refers to DHA-Service that is running on premises:<li>Offered to Windows Server 2016 customer (no added licensing cost for enabling/running DHA-Service) <li>Hosted on an enterprise owned and managed server device/hardware<li>Supported by 1st and 3rd party DHA-Enabled device management solution providers that support on-premises and hybrid (Cloud + OnPrem) hardware attestation scenarios<li>Accessible to all enterprise-managed devices via following:<ul><li>FQDN = (enterprise assigned)<li>Port = (enterprise assigned)<li>Protocol = TCP|The operation cost of running one or more instances of Server 2016 on-premises.</ul></li>|
</colgroup> |Device Health Attestation - Enterprise-Managed Cloud(DHA-EMC)|DHA-EMC refers to an enterprise-managed DHA-Service that is running as a virtual host/service on a Windows Server 2016 compatible - enterprise-managed cloud service, such as Microsoft Azure.<li>Offered to Windows Server 2016 customers with no additional licensing cost (no added licensing cost for enabling/running DHA-Service)<li>Supported by 1st and 3rd party DHA-Enabled device management solution providers that support on-premises and hybrid (Cloud + OnPrem) hardware attestation scenarios <li>Accessible to all enterprise-managed devices via following:<ul> <li>FQDN = (enterprise assigned)<li>Port = (enterprise assigned)<li>Protocol = TCP|The operation cost of running Server 2016 on a compatible cloud service, such as Microsoft Azure.</ul></li>|
<thead>
<tr class="header">
<th>DHA-Service type</th>
<th>Description</th>
<th>Operation cost</th>
</tr>
</thead>
<tbody>
<tr class="even">
<td>Device Health Attestation – Cloud <p>(DHA-Cloud)</p></td>
<td><p>DHA-Cloud is a Microsoft owned and operated DHA-Service that is:</p>
<ul>
<li>Available in Windows for free</li>
<li>Running on a high-availability and geo-balanced cloud infrastructure </li>
<li>Supported by most DHA-Enabled device management solutions as the default device attestation service provider</li>
<li>Accessible to all enterprise-managed devices via following:
<ul>
<li>FQDN = has.spserv.microsoft.com) port</li>
<li>Port = 443</li>
<li>Protocol = TCP</li>
</ul>
</li>
</ul>
<td>No cost</td>
</td>
</tr>
<tr class="even">
<td>Device Health Attestation – On Premise<p>(DHA-OnPrem)</p></td>
<td><p>DHA-OnPrem refers to DHA-Service that is running on premises:</p>
<ul>
<li>Offered to Windows Server 2016 customer (no added licensing cost for enabling/running DHA-Service) </li>
<li>Hosted on an enterprise owned and managed server device/hardware</li>
<li>Supported by 1st and 3rd party DHA-Enabled device management solution providers that support on-premises and hybrid (Cloud + OnPrem) hardware attestation scenarios</li>
<li><p>Accessible to all enterprise-managed devices via following:</p>
<ul>
<li>FQDN = (enterprise assigned)</li>
<li>Port = (enterprise assigned)</li>
<li>Protocol = TCP</li>
</ul>
</li>
</ul></td>
<td>The operation cost of running one or more instances of Server 2016 on-premises.</td>
</tr>
<tr class="even">
<td>Device Health Attestation - Enterprise-Managed Cloud<p>(DHA-EMC)</p></td>
<td><p>DHA-EMC refers to an enterprise-managed DHA-Service that is running as a virtual host/service on a Windows Server 2016 compatible - enterprise-managed cloud service, such as Microsoft Azure.</p>
<ul>
<li>Offered to Windows Server 2016 customers with no additional licensing cost (no added licensing cost for enabling/running DHA-Service)</li>
<li>Supported by 1st and 3rd party DHA-Enabled device management solution providers that support on-premises and hybrid (Cloud + OnPrem) hardware attestation scenarios </li>
<li><p>Accessible to all enterprise-managed devices via following:</p>
<ul>
<li>FQDN = (enterprise assigned)</li>
<li>Port = (enterprise assigned)</li>
<li>Protocol = TCP</li>
</ul>
</li>
</ul></td>
<td>The operation cost of running Server 2016 on a compatible cloud service, such as Microsoft Azure.</td>
</tr>
</tbody>
</table>
### CSP diagram and node descriptions ### CSP diagram and node descriptions
The following shows the Device HealthAttestation configuration service provider in tree format. The following shows the Device HealthAttestation configuration service provider in tree format.
``` ```
./Vendor/MSFT ./Vendor/MSFT
HealthAttestation HealthAttestation
@ -1263,214 +1202,48 @@ Each of these are described in further detail in the following sections, along w
### **Device HealthAttestation CSP status and error codes** ### **Device HealthAttestation CSP status and error codes**
<table> |Error code|Error name|Description|
<tr> |--- |--- |--- |
<th>Error code</th> |0|HEALTHATTESTATION_CERT_RETRIEVAL_UNINITIALIZED|This is the initial state for devices that have never participated in a DHA-Session.|
<th>Error name</th> |1|HEALTHATTESTATION_CERT_RETRIEVAL_REQUESTED|This state signifies that MDM client’s Exec call on the node VerifyHealth has been triggered and now the OS is trying to retrieve DHA-EncBlob from DHA-Server.|
<th>Description</th> |2|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED|This state signifies that the device failed to retrieve DHA-EncBlob from DHA-Server.|
</tr> |3|HEALTHATTESTATION_CERT_RETRIEVAL_COMPLETE|This state signifies that the device has successfully retrieved DHA-EncBlob from the DHA-Server.|
<tr> |4|HEALTHATTESTATION_CERT_RETRIEVAL_PCR_FAIL|Deprecated in Windows 10, version 1607.|
<td>0</td> |5|HEALTHATTESTATION_CERT_RETRIEVAL_GETQUOTE_FAIL|DHA-CSP failed to get a claim quote.|
<td>HEALTHATTESTATION_CERT_RETRIEVAL_UNINITIALIZED</td> |6|HEALTHATTESTATION_CERT_RETRIEVAL_DEVICE_NOT_READY|DHA-CSP failed in opening a handle to Microsoft Platform Crypto Provider.|
<td>This is the initial state for devices that have never participated in a DHA-Session. </td> |7|HEALTHATTESTATION_CERT_RETRIEVAL_WINDOWS_AIK_FAIL|DHA-CSP failed in retrieving Windows AIK|
</tr> |8|HEALTHATTESTATION_CERT_RETRIEVAL_FROM_WEB_FAIL|Deprecated in Windows 10, version 1607.|
<tr> |9|HEALTHATTESTATION_CERT_RETRIEVAL_INVALID_TPM_VERSION|Invalid TPM version (TPM version is not 1.2 or 2.0)|
<td>1</td> |10|HEALTHATTESTATION_CERT_RETRIEVAL_GETNONCE_FAIL|Nonce was not found in the registry.|
<td>HEALTHATTESTATION_CERT_RETRIEVAL_REQUESTED</td> |11|HEALTHATTESTATION_CERT_RETRIEVAL_GETCORRELATIONID_FAIL|Correlation ID was not found in the registry.|
<td>This state signifies that MDM client’s Exec call on the node VerifyHealth has been triggered and now the OS is trying to retrieve DHA-EncBlob from DHA-Server.</td> |12|HEALTHATTESTATION_CERT_RETRIEVAL_GETCERT_FAIL|Deprecated in Windows 10, version 1607.|
</tr> |13|HEALTHATTESTATION_CERT_RETRIEVAL_GETCLAIM_FAIL|Deprecated in Windows 10, version 1607.|
<tr> |14|HEALTHATTESTATION_CERT_RETRIEVAL_ENCODING_FAIL|Failure in Encoding functions. (Extremely unlikely scenario)|
<td>2</td> |15|HEALTHATTESTATION_CERT_RETRIEVAL_ENDPOINTOVERRIDE_FAIL|Deprecated in Windows 10, version 1607.|
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED</td> |16|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_LOAD_XML|DHA-CSP failed to load the payload it received from DHA-Service|
<td>This state signifies that the device failed to retrieve DHA-EncBlob from DHA-Server.</td> |17|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CORRUPT_XML|DHA-CSP received a corrupted response from DHA-Service.|
</tr> |18|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EMPTY_XML|DHA-CSP received an empty response from DHA-Service.|
<tr> |19|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_DECRYPT_AES_EK|DHA-CSP failed in decrypting the AES key from the EK challenge.|
<td>3</td> |20|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_DECRYPT_CERT_AES_EK|DHA-CSP failed in decrypting the health cert with the AES key.|
<td>HEALTHATTESTATION_CERT_RETRIEVAL_COMPLETE</td> |21|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EXPORT_AIKPUB|DHA-CSP failed in exporting the AIK Public Key.|
<td>This state signifies that the device has successfully retrieved DHA-EncBlob from the DHA-Server.</td> |22|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CREATE_CLAIMAUTHORITYONLY|DHA-CSP failed in trying to create a claim with AIK attestation data.|
</tr> |23|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_APPEND_AIKPUB|DHA-CSP failed in appending the AIK Pub to the request blob.|
<tr> |24|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_APPEND_AIKCERT|DHA-CSP failed in appending the AIK Cert to the request blob.|
<td>4</td> |25|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_INIT_HTTPHANDLE|DHA-CSP failed to obtain a Session handle.|
<td>HEALTHATTESTATION_CERT_RETRIEVAL_PCR_FAIL</td> |26|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_GETTARGET_HTTPHANDLE|DHA-CSP failed to connect to the DHA-Service.|
<td>Deprecated in Windows 10, version 1607.</td> |27|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CREATE_HTTPHANDLE|DHA-CSP failed to create an HTTP request handle.|
</tr> |28|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_SET_INTERNETOPTION|DHA-CSP failed to set options.|
<tr> |29|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_ADD_REQUESTHEADERS|DHA-CSP failed to add request headers.|
<td>5</td> |30|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_SEND_REQUEST|DHA-CSP failed to send the HTTP request.|
<td>HEALTHATTESTATION_CERT_RETRIEVAL_GETQUOTE_FAIL</td> |31|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_RECEIVE_RESPONSE|DHA-CSP failed to receive a response from the DHA-Service.|
<td>DHA-CSP failed to get a claim quote.</td> |32|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_QUERY_HEADERS|DHA-CSP failed to query headers when trying to get HTTP status code.|
</tr> |33|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EMPTY_RESPONSE|DHA-CSP received an empty response from DHA-Service even though HTTP status was OK.|
<tr> |34|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_MISSING_RESPONSE|DHA-CSP received an empty response along with an HTTP error code from DHA-Service.|
<td>6</td> |35|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_IMPERSONATE_USER|DHA-CSP failed to impersonate user.|
<td>HEALTHATTESTATION_CERT_RETRIEVAL_DEVICE_NOT_READY</td> |36|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_ACQUIRE_PDCNETWORKACTIVATOR|DHA-CSP failed to acquire the PDC activators that are needed for network communication when the device is in Connected standby mode.|
<td>DHA-CSP failed in opening a handle to Microsoft Platform Crypto Provider.</td> |0xFFFF|HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_UNKNOWN|DHA-CSP failed due to an unknown reason, this error is highly unlikely to occur.|
</tr> |400|Bad_Request_From_Client|DHA-CSP has received a bad (malformed) attestation request.|
<tr> |404|Endpoint_Not_Reachable|DHA-Service is not reachable by DHA-CSP|
<td>7</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_WINDOWS_AIK_FAIL</td>
<td>DHA-CSP failed in retrieving Windows AIK</td>
</tr>
<tr>
<td>8</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FROM_WEB_FAIL</td>
<td>Deprecated in Windows 10, version 1607.</td>
</tr>
<tr>
<td>9</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_INVALID_TPM_VERSION</td>
<td>Invalid TPM version (TPM version is not 1.2 or 2.0)</td>
</tr>
<tr>
<td>10</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_GETNONCE_FAIL</td>
<td>Nonce was not found in the registry.</td>
</tr>
<tr>
<td>11</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_GETCORRELATIONID_FAIL</td>
<td>Correlation ID was not found in the registry.</td>
</tr>
<tr>
<td>12</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_GETCERT_FAIL</td>
<td>Deprecated in Windows 10, version 1607.</td>
</tr>
<tr>
<td>13</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_GETCLAIM_FAIL</td>
<td>Deprecated in Windows 10, version 1607.</td>
</tr>
<tr>
<td>14</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_ENCODING_FAIL</td>
<td>Failure in Encoding functions. (Extremely unlikely scenario)</td>
</tr>
<tr>
<td>15</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_ENDPOINTOVERRIDE_FAIL</td>
<td>Deprecated in Windows 10, version 1607.</td>
</tr>
<tr>
<td>16</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_LOAD_XML</td>
<td>DHA-CSP failed to load the payload it received from DHA-Service </td>
</tr>
<tr>
<td>17</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CORRUPT_XML</td>
<td>DHA-CSP received a corrupted response from DHA-Service.</td>
</tr>
<tr>
<td>18</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EMPTY_XML</td>
<td>DHA-CSP received an empty response from DHA-Service.</td>
</tr>
<tr>
<td>19</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_DECRYPT_AES_EK</td>
<td>DHA-CSP failed in decrypting the AES key from the EK challenge.</td>
</tr>
<tr>
<td>20</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_DECRYPT_CERT_AES_EK</td>
<td>DHA-CSP failed in decrypting the health cert with the AES key.</td>
</tr>
<tr>
<td>21</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EXPORT_AIKPUB</td>
<td>DHA-CSP failed in exporting the AIK Public Key.</td>
</tr>
<tr>
<td>22</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CREATE_CLAIMAUTHORITYONLY</td>
<td>DHA-CSP failed in trying to create a claim with AIK attestation data.</td>
</tr>
<tr>
<td>23</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_APPEND_AIKPUB</td>
<td>DHA-CSP failed in appending the AIK Pub to the request blob.</td>
</tr>
<tr>
<td>24</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_APPEND_AIKCERT</td>
<td>DHA-CSP failed in appending the AIK Cert to the request blob.</td>
</tr>
<tr>
<td>25</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_INIT_HTTPHANDLE</td>
<td>DHA-CSP failed to obtain a Session handle.</td>
</tr>
<tr>
<td>26</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_GETTARGET_HTTPHANDLE</td>
<td>DHA-CSP failed to connect to the DHA-Service.</td>
</tr>
<tr>
<td>27</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CREATE_HTTPHANDLE</td>
<td>DHA-CSP failed to create an HTTP request handle.</td>
</tr>
<tr>
<td>28</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_SET_INTERNETOPTION</td>
<td>DHA-CSP failed to set options.</td>
</tr>
<tr>
<td>29</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_ADD_REQUESTHEADERS</td>
<td>DHA-CSP failed to add request headers.</td>
</tr>
<tr>
<td>30</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_SEND_REQUEST</td>
<td>DHA-CSP failed to send the HTTP request.</td>
</tr>
<tr>
<td>31</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_RECEIVE_RESPONSE</td>
<td>DHA-CSP failed to receive a response from the DHA-Service.</td>
</tr>
<tr>
<td>32</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_QUERY_HEADERS</td>
<td>DHA-CSP failed to query headers when trying to get HTTP status code.</td>
</tr>
<tr>
<td>33</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EMPTY_RESPONSE</td>
<td>DHA-CSP received an empty response from DHA-Service even though HTTP status was OK.</td>
</tr>
<tr>
<td>34</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_MISSING_RESPONSE</td>
<td>DHA-CSP received an empty response along with an HTTP error code from DHA-Service.</td>
</tr>
<tr>
<td>35</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_IMPERSONATE_USER</td>
<td>DHA-CSP failed to impersonate user.</td>
</tr>
<tr>
<td>36</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_ACQUIRE_PDCNETWORKACTIVATOR</td>
<td>DHA-CSP failed to acquire the PDC activators that are needed for network communication when the device is in Connected standby mode.</td>
</tr>
<tr>
<td>0xFFFF</td>
<td>HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_UNKNOWN</td>
<td>DHA-CSP failed due to an unknown reason, this error is highly unlikely to occur.</td>
</tr>
<tr>
<td>400</td>
<td>Bad_Request_From_Client</td>
<td>DHA-CSP has received a bad (malformed) attestation request.</td>
</tr>
<tr>
<td>404</td>
<td>Endpoint_Not_Reachable</td>
<td>DHA-Service is not reachable by DHA-CSP</td>
</tr>
</table>
### DHA-Report V3 schema ### DHA-Report V3 schema

33
windows/client-management/mdm/hotspot-csp.md
View File

@ -186,34 +186,11 @@ The DLL must be code signed in a specific way, see [Sign binaries and packages](
During an entitlement check the Internet Sharing service loads the specified DLL and then call the `IsEntitled` function. The function must connect to the server to perform any required validation, then return one of the following **ICS\_ENTITLEMENT\_RESULT** enumeration values. During an entitlement check the Internet Sharing service loads the specified DLL and then call the `IsEntitled` function. The function must connect to the server to perform any required validation, then return one of the following **ICS\_ENTITLEMENT\_RESULT** enumeration values.
<table> |Value|Description|
<colgroup> |--- |--- |
<col width="50%" /> |**ENTITLEMENT_SUCCESS**|The device is allowed to connect to the server.|
<col width="50%" /> |**ENTITLEMENT_FAILED**|The device is not allowed to connect to the server|
</colgroup> |**ENTITLEMENT_UNAVAILABLE**|The entitlement check failed because the device could not contact the server or acquire a connection to verify entitlement.|
<thead>
<tr class="header">
<th>Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p><strong>ENTITLEMENT_SUCCESS</strong></p></td>
<td><p>The device is allowed to connect to the server.</p></td>
</tr>
<tr class="even">
<td><p><strong>ENTITLEMENT_FAILED</strong></p></td>
<td><p>The device is not allowed to connect to the server</p></td>
</tr>
<tr class="odd">
<td><p><strong>ENTITLEMENT_UNAVAILABLE</strong></p></td>
<td><p>The entitlement check failed because the device could not contact the server or acquire a connection to verify entitlement.</p></td>
</tr>
</tbody>
</table>
The definition for the **ICS\_ENTITLEMENT\_RESULT** is in the header file `IcsEntitlementh`, which ships with the Windows Adaptation Kit. The definition for the **ICS\_ENTITLEMENT\_RESULT** is in the header file `IcsEntitlementh`, which ships with the Windows Adaptation Kit.

42
windows/client-management/mdm/implement-server-side-mobile-application-management.md
View File

@ -129,40 +129,8 @@ If the MAM device is properly configured for MDM enrollment, then the Enroll onl
We have updated Skype for Business to work with MAM. The following table explains Office release channels and release dates for Skype for Business compliance with the MAM feature. We have updated Skype for Business to work with MAM. The following table explains Office release channels and release dates for Skype for Business compliance with the MAM feature.
<table> |Update channel|Primary purpose|LOB Tattoo availability|Default update channel for the products|
<colgroup> |--- |--- |--- |--- |
<col width="15%" /> |[Current channel](/deployoffice/overview-update-channels#BKMK_CB)|Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel.|March 9 2017|Visio Pro for Office 365<br>Project Desktop Client<br>Microsoft 365 Apps for business (the version of Office that comes with some Microsoft 365 plans, such as Business Premium.)|
<col width="35%" /> |[Deferred channel](/deployoffice/overview-update-channels#BKMK_CBB)|Provide users with new features of Office only a few times a year.|October 10 2017|Microsoft 365 Apps for enterprise|
<col width="15%" /> |[First release for deferred channel](/deployoffice/overview-update-channels#BKMK_FRCBB)|Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel.|June 13 2017||
<col width="35%" />
</colgroup>
<thead>
<tr class="header">
<th>Update channel</th>
<th>Primary purpose</th>
<th>LOB Tattoo availability</th>
<th>Default update channel for the products</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="/deployoffice/overview-update-channels#BKMK_CB" data-raw-source="[Current channel](/deployoffice/overview-update-channels#BKMK_CB)">Current channel</a></td>
<td>Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel. </td>
<td>March 9 2017</td>
<td><p>Visio Pro for Office 365</p>
<p>Project Desktop Client</p>
<p>Microsoft 365 Apps for business (the version of Office that comes with some Microsoft 365 plans, such as Business Premium.)</p></td>
</tr>
<tr>
<td><a href="/deployoffice/overview-update-channels#BKMK_CBB" data-raw-source="[Deferred channel](/deployoffice/overview-update-channels#BKMK_CBB)">Deferred channel</a></td>
<td>Provide users with new features of Office only a few times a year.</td>
<td>October 10 2017</td>
<td>Microsoft 365 Apps for enterprise</td>
</tr><tr>
<td><a href="/deployoffice/overview-update-channels#BKMK_FRCBB" data-raw-source="[First release for deferred channel](/deployoffice/overview-update-channels#BKMK_FRCBB)">First release for Deferred channel</a></td>
<td>Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel. </td>
<td>June 13 2017</td>
<td></td>
</tr>
</tbody>
</table>

23
windows/client-management/mdm/management-tool-for-windows-store-for-business.md
View File

@ -34,26 +34,11 @@ For additional information about Store for Business, see the TechNet topics in [
The Store for Business provides services that enable a management tool to synchronize new and updated applications on behalf of an organization. Once synchronized, you can distribute new and updated applications using the Windows Management framework. The services provides several capabilities including providing application data, the ability to assign and reclaim applications, and the ability to download offline-licensed application packages. The Store for Business provides services that enable a management tool to synchronize new and updated applications on behalf of an organization. Once synchronized, you can distribute new and updated applications using the Windows Management framework. The services provides several capabilities including providing application data, the ability to assign and reclaim applications, and the ability to download offline-licensed application packages.
<table> - **Application data**:The Store for Business service provides metadata for the applications that have been acquired via the Store for Business. This includes the application identifier that is used to deploy online license applications, artwork for an application that is used to create a company portal, and localized descriptions for applications.
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td><p>Application data</p></td>
<td><p>The Store for Business service provides metadata for the applications that have been acquired via the Store for Business. This includes the application identifier that is used to deploy online license applications, artwork for an application that is used to create a company portal, and localized descriptions for applications.</p></td>
</tr>
<tr class="even">
<td><p>Licensing models</p></td>
<td><p><strong>Offline vs. Online</strong></p>
<p>Online-licensed applications require connectivity to the Microsoft Store. Users require an Azure Active Directory identity and rely on the store services on the device to be able to acquire an application from the store. It is similar to how applications are acquired from the Microsoft Store using a Microsoft account. Assigning or reclaiming seats for an application require a call to the Store for Business services.</p>
<p>Offline-licensed applications enable an organization to use the application for imaging and for devices that may not have connectivity to the store or may not have Azure Active Directory. Offline-licensed application do not require connectivity to the store, however it can be updated directly from the store if the device has connectivity and the app update policies allow updates to be distributed via the store.</p></td>
</tr>
</tbody>
</table>
- **Licensing models**:
- **Online-licensed** applications require connectivity to the Microsoft Store. Users require an Azure Active Directory identity and rely on the store services on the device to be able to acquire an application from the store. It is similar to how applications are acquired from the Microsoft Store using a Microsoft account. Assigning or reclaiming seats for an application require a call to the Store for Business services.
- **Offline-licensed** applications enable an organization to use the application for imaging and for devices that may not have connectivity to the store or may not have Azure Active Directory. Offline-licensed application do not require connectivity to the store, however it can be updated directly from the store if the device has connectivity and the app update policies allow updates to be distributed via the store.
### Offline-licensed application distribution ### Offline-licensed application distribution

147
windows/client-management/mdm/mobile-device-enrollment.md
View File

@ -110,75 +110,15 @@ The enrollment server can decline enrollment messages using the SOAP Fault forma
</s:envelope> </s:envelope>
``` ```
<table> |Namespace|Subcode|Error|Description|HRESULT|
<colgroup> |--- |--- |--- |--- |--- |
<col width="20%" /> |s:|MessageFormat|MENROLL_E_DEVICE_MESSAGE_FORMAT_ERROR|Invalid message from the Mobile Device Management (MDM) server.|80180001|
<col width="20%" /> |s:|Authentication|MENROLL_E_DEVICE_AUTHENTICATION_ERROR|The Mobile Device Management (MDM) server failed to authenticate the user. Try again or contact your system administrator.|80180002|
<col width="20%" /> |s:|Authorization|MENROLL_E_DEVICE_AUTHORIZATION_ERROR|The user is not authorized to enroll to Mobile Device Management (MDM). Try again or contact your system administrator.|80180003|
<col width="20%" /> |s:|CertificateRequest|MENROLL_E_DEVICE_CERTIFICATEREQUEST_ERROR|The user has no permission for the certificate template or the certificate authority is unreachable. Try again or contact your system administrator.|80180004|
<col width="20%" /> |s:|EnrollmentServer|MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR|The Mobile Device Management (MDM) server encountered an error. Try again or contact your system administrator.|80180005|
</colgroup> |a:|InternalServiceFault|MENROLL_E_DEVICE_INTERNALSERVICE_ERROR|There was an unhandled exception on the Mobile Device Management (MDM) server. Try again or contact your system administrator.|80180006|
<thead> |a:|InvalidSecurity|MENROLL_E_DEVICE_INVALIDSECURITY_ERROR|The Mobile Device Management (MDM) server was not able to validate your account. Try again or contact your system administrator.|80180007|
<tr class="header">
<th>Namespace</th>
<th>Subcode</th>
<th>Error</th>
<th>Description</th>
<th>HRESULT</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>s:</p></td>
<td><p>MessageFormat</p></td>
<td><p>MENROLL_E_DEVICE_MESSAGE_FORMAT_ERROR</p></td>
<td><p>Invalid message from the Mobile Device Management (MDM) server.</p></td>
<td><p>80180001</p></td>
</tr>
<tr class="even">
<td><p>s:</p></td>
<td><p>Authentication</p></td>
<td><p>MENROLL_E_DEVICE_AUTHENTICATION_ERROR</p></td>
<td><p>The Mobile Device Management (MDM) server failed to authenticate the user. Try again or contact your system administrator.</p></td>
<td><p>80180002</p></td>
</tr>
<tr class="odd">
<td><p>s:</p></td>
<td><p>Authorization</p></td>
<td><p>MENROLL_E_DEVICE_AUTHORIZATION_ERROR</p></td>
<td><p>The user is not authorized to enroll to Mobile Device Management (MDM). Try again or contact your system administrator.</p></td>
<td><p>80180003</p></td>
</tr>
<tr class="even">
<td><p>s:</p></td>
<td><p>CertificateRequest</p></td>
<td><p>MENROLL_E_DEVICE_CERTIFICATEREQUEST_ERROR</p></td>
<td><p>The user has no permission for the certificate template or the certificate authority is unreachable. Try again or contact your system administrator.</p></td>
<td><p>80180004</p></td>
</tr>
<tr class="odd">
<td><p>s:</p></td>
<td><p>EnrollmentServer</p></td>
<td><p>MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR</p></td>
<td>The Mobile Device Management (MDM) server encountered an error. Try again or contact your system administrator.</td>
<td><p>80180005</p></td>
</tr>
<tr class="even">
<td><p>a:</p></td>
<td><p>InternalServiceFault</p></td>
<td><p>MENROLL_E_DEVICE_INTERNALSERVICE_ERROR</p></td>
<td><p> There was an unhandled exception on the Mobile Device Management (MDM) server. Try again or contact your system administrator.</p></td>
<td><p>80180006</p></td>
</tr>
<tr class="odd">
<td><p>a:</p></td>
<td><p>InvalidSecurity</p></td>
<td><p>MENROLL_E_DEVICE_INVALIDSECURITY_ERROR</p></td>
<td><p>The Mobile Device Management (MDM) server was not able to validate your account. Try again or contact your system administrator.</p></td>
<td><p>80180007</p></td>
</tr>
</tbody>
</table>
In Windows 10, version 1507, we added the deviceenrollmentserviceerror element. Here is an example: In Windows 10, version 1507, we added the deviceenrollmentserviceerror element. Here is an example:
@ -212,66 +152,15 @@ In Windows 10, version 1507, we added the deviceenrollmentserviceerror element.
</s:envelope> </s:envelope>
``` ```
<table> |Subcode|Error|Description|HRESULT|
<colgroup> |--- |--- |--- |--- |
<col width="25%" /> |DeviceCapReached|MENROLL_E_DEVICECAPREACHED|The account has too many devices enrolled to Mobile Device Management (MDM). Delete or unenroll old devices to fix this error.|80180013|
<col width="25%" /> |DeviceNotSupported|MENROLL_E_DEVICENOTSUPPORTED|The Mobile Device Management (MDM) server doesn't support this platform or version, consider upgrading your device.|80180014|
<col width="25%" /> |NotSupported|MENROLL_E_NOT_SUPPORTED|Mobile Device Management (MDM) is generally not supported for this device.|80180015|
<col width="25%" /> |NotEligibleToRenew|MENROLL_E_NOTELIGIBLETORENEW|The device is attempting to renew the Mobile Device Management (MDM) certificate, but the server rejected the request. Check renew schedule on the device.|80180016|
</colgroup> |InMaintenance|MENROLL_E_INMAINTENANCE|The Mobile Device Management (MDM) server states your account is in maintenance, try again later.|80180017|
<thead> |UserLicense|MENROLL_E_USER_LICENSE|There was an error with your Mobile Device Management (MDM) user license. Contact your system administrator.|80180018|
<tr class="header"> |InvalidEnrollmentData|MENROLL_E_ENROLLMENTDATAINVALID|The Mobile Device Management (MDM) server rejected the enrollment data. The server may not be configured correctly.|80180019|
<th>Subcode</th>
<th>Error</th>
<th>Description</th>
<th>HRESULT</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>DeviceCapReached</p></td>
<td><p>MENROLL_E_DEVICECAPREACHED</p></td>
<td><p>The account has too many devices enrolled to Mobile Device Management (MDM). Delete or unenroll old devices to fix this error.</p></td>
<td><p>80180013</p></td>
</tr>
<tr class="even">
<td><p>DeviceNotSupported</p></td>
<td><p>MENROLL_E_DEVICENOTSUPPORTED</p></td>
<td><p>The Mobile Device Management (MDM) server doesn't support this platform or version, consider upgrading your device.</p></td>
<td><p>80180014</p></td>
</tr>
<tr class="odd">
<td><p>NotSupported</p></td>
<td><p>MENROLL_E_NOT_SUPPORTED</p></td>
<td><p>Mobile Device Management (MDM) is generally not supported for this device.</p></td>
<td><p>80180015</p></td>
</tr>
<tr class="even">
<td><p>NotEligibleToRenew</p></td>
<td><p>MENROLL_E_NOTELIGIBLETORENEW</p></td>
<td><p>The device is attempting to renew the Mobile Device Management (MDM) certificate, but the server rejected the request. Check renew schedule on the device.</p></td>
<td><p>80180016</p></td>
</tr>
<tr class="odd">
<td><p>InMaintenance</p></td>
<td><p>MENROLL_E_INMAINTENANCE</p></td>
<td><p>The Mobile Device Management (MDM) server states your account is in maintenance, try again later.</p></td>
<td><p>80180017</p></td>
</tr>
<tr class="even">
<td><p>UserLicense</p></td>
<td><p>MENROLL_E_USER_LICENSE</p></td>
<td><p>There was an error with your Mobile Device Management (MDM) user license. Contact your system administrator.</p></td>
<td><p>80180018</p></td>
</tr>
<tr class="odd">
<td><p>InvalidEnrollmentData</p></td>
<td><p>MENROLL_E_ENROLLMENTDATAINVALID</p></td>
<td><p>The Mobile Device Management (MDM) server rejected the enrollment data. The server may not be configured correctly.</p></td>
<td><p>80180019</p></td>
</tr>
</tbody>
</table>
TraceID is a freeform text node which is logged. It should identify the server side state for this enrollment attempt. This information may be used by support to look up why the server declined the enrollment. TraceID is a freeform text node which is logged. It should identify the server side state for this enrollment attempt. This information may be used by support to look up why the server declined the enrollment.

33
windows/client-management/mdm/nap-csp.md
View File

@ -87,34 +87,11 @@ Required. Specifies the type of address used to identify the destination network
The following table shows some commonly used ADDRTYPE values and the types of connection that corresponds with each value. The following table shows some commonly used ADDRTYPE values and the types of connection that corresponds with each value.
<table> |ADDRTYPE Value|Connection Type|
<colgroup> |--- |--- |
<col width="50%" /> |E164|RAS connections|
<col width="50%" /> |APN|GPRS connections|
</colgroup> |ALPHA|Wi-Fi-based connections|
<thead>
<tr class="header">
<th>ADDRTYPE Value</th>
<th>Connection Type</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>E164</p></td>
<td><p>RAS connections</p></td>
</tr>
<tr class="even">
<td><p>APN</p></td>
<td><p>GPRS connections</p></td>
</tr>
<tr class="odd">
<td><p>ALPHA</p></td>
<td><p>Wi-Fi-based connections</p></td>
</tr>
</tbody>
</table>
 
<a href="" id="napx-authinfo"></a>***NAPX*/AuthInfo** <a href="" id="napx-authinfo"></a>***NAPX*/AuthInfo**
Optional node. Specifies the authentication information, including the protocol, user name, and password. Optional node. Specifies the authentication information, including the protocol, user name, and password.

39
windows/client-management/mdm/napdef-csp.md
View File

@ -127,39 +127,12 @@ The name of the *NAPID* element is the same as the value passed during initial b
The following table shows the Microsoft custom elements that this configuration service provider supports for OMA Client Provisioning. The following table shows the Microsoft custom elements that this configuration service provider supports for OMA Client Provisioning.
<table> |Elements|Available|
<colgroup> |--- |--- |
<col width="20%" /> |Parm-query|Yes <br>Note that some GPRS parameters will not necessarily contain the exact same value as was set.|
<col width="80%" /> |Noparm|Yes|
</colgroup> |Nocharacteristic|Yes|
<thead> |Characteristic-query|Yes|
<tr class="header">
<th>Elements</th>
<th>Available</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>Parm-query</p></td>
<td><p>Yes</p>
<p>Note that some GPRS parameters will not necessarily contain the exact same value as was set.</p></td>
</tr>
<tr class="even">
<td><p>Noparm</p></td>
<td><p>Yes</p></td>
</tr>
<tr class="odd">
<td><p>Nocharacteristic</p></td>
<td><p>Yes</p></td>
</tr>
<tr class="even">
<td><p>Characteristic-query</p></td>
<td><p>Yes</p></td>
</tr>
</tbody>
</table>
## Related topics ## Related topics

158
windows/client-management/mdm/office-csp.md
View File

@ -151,140 +151,24 @@ To get the current status of Office 365 on the device.
## Status code ## Status code
<table> |Status|Description|Comment|
<colgroup> |--- |--- |--- |
<col width="30%" /> |0|Installation succeeded|OK|
<col width="50%" /> |997|Installation in progress||
<col width="20%" /> |13|ERROR_INVALID_DATA <br>Cannot verify signature of the downloaded Office Deployment Tool (ODT)|Failure|
|1460|ERROR_TIMEOUT <br>Failed to download ODT|Failure|
</colgroup> |1602|ERROR_INSTALL_USEREXIT <br>User cancelled the installation|Failure|
<thead> |1603|ERROR_INSTALL_FAILURE<br>Failed any pre-req check.<li>SxS (Tried to install when 2016 MSI is installed)<li>Bit mismatch between the currently installed Office and the Office that was attempting to be installed (such as when you try to install a 32-bit version while 64-bit version is currently installed.)|Failure|
<tr class="header"> |17000|ERROR_PROCESSPOOL_INITIALIZATION
<th>Status</th> Failed to start C2RClient|Failure|
<th>Description</th> |17001|ERROR_QUEUE_SCENARIO
<th>Comment</th> Failed to queue installation scenario in C2RClient|Failure|
</tr> |17002|ERROR_COMPLETING_SCENARIO <br>Failed to complete the process. Possible reasons:<li>Installation cancelled by user<li>Installation cancelled by another installation<li>Out of disk space during installation <li>Unknown language ID|Failure|
</thead> |17003|ERROR_ANOTHER_RUNNING_SCENARIO <br>Another scenario is running|Failure|
<tbody> |17004|ERROR_COMPLETING_SCENARIO_NEED_CLEAN_UP<br>Possible reasons:<li>Unknown SKUs<li>Content does't exist on CDN<ul><li>such as trying to install an unsupported LAP, like zh-sg<li>CDN issue that content is not available</li></ul><li>Signature check issue, such as failed the signature check for Office content<li>User cancelled|Failure|
<tr> |17005|ERROR_SCENARIO_CANCELLED_AS_PLANNED|Failure|
<td>0</td> |17006|ERROR_SCENARIO_CANCELLED<br>Blocked update by running apps|Failure|
<td>Installation succeeded</td> |17007|ERROR_REMOVE_INSTALLATION_NEEDED<br>The client is requesting client clean up in a "Remove Installation" scenario|Failure|
<td>OK</td> |17100|ERROR_HANDLING_COMMAND_LINE<br>C2RClient command line error|Failure|
</tr> |0x80004005|E_FAIL <br>ODT cannot be used to install Volume license|Failure|
<tr> |0x8000ffff|E_UNEXPECTED<br>Tried to uninstall when there is no C2R Office on the machine.|Failure|
<td>997</td>
<td>Installation in progress</td>
<td></td>
</tr>
<tr>
<td>13</td>
<td>ERROR_INVALID_DATA
<p>Cannot verify signature of the downloaded Office Deployment Tool (ODT)<p></td>
<td>Failure</td>
</tr>
<tr>
<td>1460</td>
<td>ERROR_TIMEOUT
<p>Failed to download ODT</p></td>
<td>Failure</td>
</tr>
<tr>
<td>1602 </td>
<td>ERROR_INSTALL_USEREXIT
<p>User cancelled the installation </p></td>
<td>Failure</td>
</tr>
<tr>
<td>1603</td>
<td>ERROR_INSTALL_FAILURE
<p>Failed any pre-req check.</p>
<ul>
<li>SxS (Tried to install when 2016 MSI is installed)</li>
<li>Bit mismatch between the currently installed Office and the Office that was attempting to be installed (such as when you try to install a 32-bit version while 64-bit version is currently installed.)</li>
</ul>
</td>
<td>Failure</td>
</tr>
<tr>
<td>17000</td>
<td>ERROR_PROCESSPOOL_INITIALIZATION
<p>Failed to start C2RClient </p></td>
<td>Failure</td>
</tr>
<tr>
<td>17001</td>
<td>ERROR_QUEUE_SCENARIO
<p>Failed to queue installation scenario in C2RClient</p></td>
<td>Failure</td>
</tr>
<tr>
<td>17002</td>
<td>ERROR_COMPLETING_SCENARIO
<p>Failed to complete the process. Possible reasons:</p>
<ul>
<li>Installation cancelled by user</li>
<li>Installation cancelled by another installation</li>
<li>Out of disk space during installation </li>
<li>Unknown language ID</li>
</ul></td>
<td>Failure</td>
</tr>
<tr>
<td>17003</td>
<td>ERROR_ANOTHER_RUNNING_SCENARIO
<p>Another scenario is running</p></td>
<td>Failure</td>
</tr>
<tr>
<td>17004</td>
<td>ERROR_COMPLETING_SCENARIO_NEED_CLEAN_UP
<p>Possible reasons:</p>
<ul>
<li>Unknown SKUs</li>
<li>Content does't exist on CDN
<ul><li>such as trying to install an unsupported LAP, like zh-sg</li>
<li>CDN issue that content is not available</li></ul>
</li>
<li>Signature check issue, such as failed the signature check for Office content</li>
<li>User cancelled
</ul>
</td>
<td>Failure</td>
</tr>
<tr>
<td>17005</td>
<td>ERROR_SCENARIO_CANCELLED_AS_PLANNED</td>
<td>Failure</td>
</tr>
<tr>
<td>17006</td>
<td>ERROR_SCENARIO_CANCELLED
<p>Blocked update by running apps</p></td>
<td>Failure</td>
</tr>
<tr>
<td>17007</td>
<td>ERROR_REMOVE_INSTALLATION_NEEDED
<p>The client is requesting client clean up in a "Remove Installation" scenario</p></td>
<td>Failure</td>
</tr>
<tr>
<td>17100</td>
<td>ERROR_HANDLING_COMMAND_LINE
<p>C2RClient command line error </p></td>
<td>Failure</td>
</tr>
<tr>
<td>0x80004005</td>
<td>E_FAIL
<p>ODT cannot be used to install Volume license</p></td>
<td>Failure</td>
</tr>
<tr>
<td>0x8000ffff </td>
<td>E_UNEXPECTED
<p>Tried to uninstall when there is no C2R Office on the machine.</p></td>
<td>Failure</td>
</tr>
</tbody>
</table>

284
windows/client-management/mdm/oma-dm-protocol-support.md
View File

@ -35,113 +35,17 @@ The OMA DM client communicates with the server over HTTPS and uses DM Sync (OMA
The following table shows the OMA DM standards that Windows uses. The following table shows the OMA DM standards that Windows uses.
<table> |General area|OMA DM standard that is supported|
<colgroup> |--- |--- |
<col width="50%" /> |Data transport and session|<li>Client-initiated remote HTTPS DM session over SSL.<li>Remote HTTPS DM session over SSL.<li>Remote DM server initiation notification using WAP Push over Short Message Service (SMS). Not used by enterprise management.<li>Remote bootstrap by using WAP Push over SMS. Not used by enterprise management.|
<col width="50%" /> |Bootstrap XML|OMA Client Provisioning XML.|
</colgroup> |DM protocol commands|The following list shows the commands that are used by the device. For further information about the OMA DM command elements, see "[OMA website](https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/)" available from the OMA website.<li>Add (Implicit Add supported)<li>Alert (DM alert): Generic alert (1226) is used by enterprise management client when the user triggers an MDM unenrollment action from the device or when a CSP finishes some asynchronous actions. Device alert (1224) is used to notify the server some device triggered event.<li>Atomic: Note that performing an Add command followed by Replace on the same node within an atomic element is not supported. Nested Atomic and Get commands are not allowed and will generate error code 500.<li>Delete: Removes a node from the DM tree, and the entire subtree beneath that node if one exists<li>Exec: Invokes an executable on the client device<li>Get: Retrieves data from the client device; for interior nodes, the child node names in the Data element are returned in URI-encoded format<li>Replace: Overwrites data on the client device<li>Result: Returns the data results of a Get command to the DM server<li>Sequence: Specifies the order in which a group of commands must be processed<li>Status: Indicates the completion status (success or failure) of an operation<br>If an XML element that is not a valid OMA DM command is under one of the following elements, the status code 400 is returned for that element:<li>SyncBody<li>Atomic<li>Sequence<br>If no CmdID is provided in the DM command, the client returns blank in the status element and the status code 400.<br>If Atomic elements are nested, the following status codes are returned:<li>The nested Atomic command returns 500.<li>The parent Atomic command returns 507.<br>For more information about the Atomic command, see OMA DM protocol common elements.<br>Performing an Add command followed by Replace on the same node within an Atomic element is not supported.<br>LocURI cannot start with "/".<br>Meta XML tag in SyncHdr is ignored by the device.|
<thead> |OMA DM standard objects|DevInfo<li>DevDetail<li>OMA DM DMS account objects (OMA DM version 1.2)|
<tr class="header"> |Security|<li>Authenticate DM server initiation notification SMS message (not used by enterprise management)<li>Application layer Basic and MD5 client authentication<li>Authenticate server with MD5 credential at application level<li>Data integrity and authentication with HMAC at application level<li>SSL level certificate based client/server authentication, encryption, and data integrity check|
<th>General area</th> |Nodes|In the OMA DM tree, the following rules apply for the node name:<li>"" can be part of the node name.<li>The node name cannot be empty.<li>The node name cannot be only the asterisk (*) character.|
<th>OMA DM standard that is supported</th> |Provisioning Files|Provisioning XML must be well formed and follow the definition in SyncML Representation Protocol](https://go.microsoft.com/fwlink/p/?LinkId=526905).<br>If an XML element that is not a valid OMA DM command is under SyncBody, the status code 400 is returned for that element.<div class="alert">**Note**<br>To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding.</div>|
</tr> |WBXML support|Windows supports sending and receiving SyncML in both XML format and encoded WBXML format. This is configurable by using the DEFAULTENCODING node under the w7 APPLICATION characteristic during enrollment. For more information about WBXML encoding, see section 8 of the [SyncML Representation Protocol](https://go.microsoft.com/fwlink/p/?LinkId=526905) specification.|
</thead> |Handling of large objects|In Windows 10, version 1511, client support for uploading large objects to the server was added.|
<tbody>
<tr class="odd">
<td><p>Data transport and session</p></td>
<td><ul>
<li><p>Client-initiated remote HTTPS DM session over SSL.</p></li>
<li><p>Remote HTTPS DM session over SSL.</p></li>
<li><p>Remote DM server initiation notification using WAP Push over Short Message Service (SMS). Not used by enterprise management.</p></li>
<li><p>Remote bootstrap by using WAP Push over SMS. Not used by enterprise management.</p></li>
</ul></td>
</tr>
<tr class="even">
<td><p>Bootstrap XML</p></td>
<td><ul>
<li><p>OMA Client Provisioning XML.</p></li>
</ul></td>
</tr>
<tr class="odd">
<td><p>DM protocol commands</p></td>
<td><p>The following list shows the commands that are used by the device. For further information about the OMA DM command elements, see &quot;SyncML Representation Protocol Device Management Usage (OMA-SyncML-DMRepPro-V1_1_2-20030613-A)&quot; available from the <a href="https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/" data-raw-source="[OMA website](https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/)">OMA website</a>.</p>
<ul>
<li><p>Add (Implicit Add supported)</p></li>
<li><p>Alert (DM alert): Generic alert (1226) is used by enterprise management client when the user triggers an MDM unenrollment action from the device or when a CSP finishes some asynchronous actions. Device alert (1224) is used to notify the server some device triggered event.</p></li>
<li><p>Atomic: Note that performing an Add command followed by Replace on the same node within an atomic element is not supported. Nested Atomic and Get commands are not allowed and will generate error code 500.</p></li>
<li><p>Delete: Removes a node from the DM tree, and the entire subtree beneath that node if one exists</p></li>
<li><p>Exec: Invokes an executable on the client device</p></li>
<li><p>Get: Retrieves data from the client device; for interior nodes, the child node names in the Data element are returned in URI-encoded format</p></li>
<li><p>Replace: Overwrites data on the client device</p></li>
<li><p>Result: Returns the data results of a Get command to the DM server</p></li>
<li><p>Sequence: Specifies the order in which a group of commands must be processed</p></li>
<li><p>Status: Indicates the completion status (success or failure) of an operation</p></li>
</ul>
<p>If an XML element that is not a valid OMA DM command is under one of the following elements, the status code 400 is returned for that element:</p>
<ul>
<li><p>SyncBody</p></li>
<li><p>Atomic</p></li>
<li><p>Sequence</p></li>
</ul>
<p>If no CmdID is provided in the DM command, the client returns blank in the status element and the status code 400.</p>
<p>If Atomic elements are nested, the following status codes are returned:</p>
<ul>
<li><p>The nested Atomic command returns 500.</p></li>
<li><p>The parent Atomic command returns 507.</p></li>
</ul>
<p>For more information about the Atomic command, see OMA DM protocol common elements.</p>
<p>Performing an Add command followed by Replace on the same node within an Atomic element is not supported.</p>
<p>LocURI cannot start with &quot;/&quot;.</p>
<p>Meta XML tag in SyncHdr is ignored by the device.</p></td>
</tr>
<tr class="even">
<td><p>OMA DM standard objects</p></td>
<td><ul>
<li><p>DevInfo</p></li>
<li><p>DevDetail</p></li>
<li><p>OMA DM DMS account objects (OMA DM version 1.2)</p></li>
</ul></td>
</tr>
<tr class="odd">
<td><p>Security</p></td>
<td><ul>
<li><p>Authenticate DM server initiation notification SMS message (not used by enterprise management)</p></li>
<li><p>Application layer Basic and MD5 client authentication</p></li>
<li><p>Authenticate server with MD5 credential at application level</p></li>
<li><p>Data integrity and authentication with HMAC at application level</p></li>
<li><p>SSL level certificate based client/server authentication, encryption, and data integrity check</p></li>
</ul></td>
</tr>
<tr class="even">
<td><p>Nodes</p></td>
<td><p>In the OMA DM tree, the following rules apply for the node name:</p>
<ul>
<li><p>&quot;.&quot; can be part of the node name.</p></li>
<li><p>The node name cannot be empty.</p></li>
<li><p>The node name cannot be only the asterisk (*) character.</p></li>
</ul></td>
</tr>
<tr class="odd">
<td><p>Provisioning Files</p></td>
<td><p>Provisioning XML must be well formed and follow the definition in <a href="https://go.microsoft.com/fwlink/p/?LinkId=526905" data-raw-source="[SyncML Representation Protocol](https://go.microsoft.com/fwlink/p/?LinkId=526905)">SyncML Representation Protocol</a> specification.</p>
<p>If an XML element that is not a valid OMA DM command is under SyncBody, the status code 400 is returned for that element.</p>
<div class="alert">
<strong>Note</strong><br/><p>To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding.</p>
</div>
<div>
</div></td>
</tr>
<tr class="even">
<td><p>WBXML support</p></td>
<td><p>Windows supports sending and receiving SyncML in both XML format and encoded WBXML format. This is configurable by using the DEFAULTENCODING node under the w7 APPLICATION characteristic during enrollment. For more information about WBXML encoding, see section 8 of the <a href="https://go.microsoft.com/fwlink/p/?LinkId=526905" data-raw-source="[SyncML Representation Protocol](https://go.microsoft.com/fwlink/p/?LinkId=526905)">SyncML Representation Protocol</a> specification.</p></td>
</tr>
<tr class="odd">
<td><p>Handling of large objects</p></td>
<td><p>In Windows 10, version 1511, client support for uploading large objects to the server was added.</p></td>
</tr>
</tbody>
</table>
<a href="" id="protocol-common-elements"></a> <a href="" id="protocol-common-elements"></a>
@ -149,99 +53,26 @@ The following table shows the OMA DM standards that Windows uses.
Common elements are used by other OMA DM element types. The following table lists the OMA DM common elements used to configure the devices. For more information about OMA DM common elements, see "SyncML Representation Protocol Device Management Usage" (OMA-SyncML-DMRepPro-V1_1_2-20030613-A) available from the [OMA website](https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/). Common elements are used by other OMA DM element types. The following table lists the OMA DM common elements used to configure the devices. For more information about OMA DM common elements, see "SyncML Representation Protocol Device Management Usage" (OMA-SyncML-DMRepPro-V1_1_2-20030613-A) available from the [OMA website](https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/).
<table> |Element|Description|
<colgroup> |--- |--- |
<col width="50%" /> |Chal|Specifies an authentication challenge. The server or client can send a challenge to the other if no credentials or inadequate credentials were given in the original request message.|
<col width="50%" /> |Cmd|Specifies the name of an OMA DM command referenced in a Status element.|
</colgroup> |CmdID|Specifies the unique identifier for an OMA DM command.|
<thead> |CmdRef|Specifies the ID of the command for which status or results information is being returned. This element takes the value of the CmdID element of the corresponding request message.|
<tr class="header"> |Cred|Specifies the authentication credential for the originator of the message.|
<th>Element</th> |Final|Indicates that the current message is the last message in the package.|
<th>Description</th> |LocName|Specifies the display name in the Target and Source elements, used for sending a user ID for MD5 authentication.|
</tr> |LocURI|Specifies the address of the target or source location. If the address contains a non-alphanumeric character, it must be properly escaped according to the URL encoding standard.|
</thead> |MsgID|Specifies a unique identifier for an OMA DM session message.|
<tbody> |MsgRef|Specifies the ID of the corresponding request message. This element takes the value of the request message MsgID element.|
<tr class="odd"> |RespURI|Specifies the URI that the recipient must use when sending a response to this message.|
<td><p>Chal</p></td> |SessionID|Specifies the identifier of the OMA DM session associated with the containing message.<div class="alert">**Note**<br> If the server does not notify the device that it supports a new version (through SyncApplicationVersion node in the DMClient CSP), the desktop client returns the SessionID in integer in decimal format and the mobile device client returns 2 bytes as a string. If the server supports DM session sync version 2.0, which is used in Windows 10, the desktop and mobile device client returns 2 bytes.</div>|
<td><p>Specifies an authentication challenge. The server or client can send a challenge to the other if no credentials or inadequate credentials were given in the original request message.</p></td> |Source|Specifies the message source address.|
</tr> |SourceRef|Specifies the source of the corresponding request message. This element takes the value of the request message Source element and is returned in the Status or Results element.|
<tr class="even"> |Target|Specifies the address of the node, in the DM Tree, that is the target of the OMA DM command.|
<td><p>Cmd</p></td> |TargetRef|Specifies the target address in the corresponding request message. This element takes the value of the request message Target element and is returned in the Status or Results element.|
<td><p>Specifies the name of an OMA DM command referenced in a Status element.</p></td> |VerDTD|Specifies the major and minor version identifier of the OMA DM representation protocol specification used to represent the message.|
</tr> |VerProto|Specifies the major and minor version identifier of the OMA DM protocol specification used with the message.|
<tr class="odd">
<td><p>CmdID</p></td>
<td><p>Specifies the unique identifier for an OMA DM command.</p></td>
</tr>
<tr class="even">
<td><p>CmdRef</p></td>
<td><p>Specifies the ID of the command for which status or results information is being returned. This element takes the value of the CmdID element of the corresponding request message.</p></td>
</tr>
<tr class="odd">
<td><p>Cred</p></td>
<td><p>Specifies the authentication credential for the originator of the message.</p></td>
</tr>
<tr class="even">
<td><p>Final</p></td>
<td><p>Indicates that the current message is the last message in the package.</p></td>
</tr>
<tr class="odd">
<td><p>LocName</p></td>
<td><p>Specifies the display name in the Target and Source elements, used for sending a user ID for MD5 authentication.</p></td>
</tr>
<tr class="even">
<td><p>LocURI</p></td>
<td><p>Specifies the address of the target or source location. If the address contains a non-alphanumeric character, it must be properly escaped according to the URL encoding standard.</p></td>
</tr>
<tr class="odd">
<td><p>MsgID</p></td>
<td><p>Specifies a unique identifier for an OMA DM session message.</p></td>
</tr>
<tr class="even">
<td><p>MsgRef</p></td>
<td><p>Specifies the ID of the corresponding request message. This element takes the value of the request message MsgID element.</p></td>
</tr>
<tr class="odd">
<td><p>RespURI</p></td>
<td><p>Specifies the URI that the recipient must use when sending a response to this message.</p></td>
</tr>
<tr class="even">
<td><p>SessionID</p></td>
<td><p>Specifies the identifier of the OMA DM session associated with the containing message.</p>
<div class="alert">
<strong>Note</strong> If the server does not notify the device that it supports a new version (through SyncApplicationVersion node in the DMClient CSP), the desktop client returns the SessionID in integer in decimal format and the mobile device client returns 2 bytes as a string. If the server supports DM session sync version 2.0, which is used in Windows 10, the desktop and mobile device client returns 2 bytes.
</div>
<div>
</div></td>
</tr>
<tr class="odd">
<td><p>Source</p></td>
<td><p>Specifies the message source address.</p></td>
</tr>
<tr class="even">
<td><p>SourceRef</p></td>
<td><p>Specifies the source of the corresponding request message. This element takes the value of the request message Source element and is returned in the Status or Results element.</p></td>
</tr>
<tr class="odd">
<td><p>Target</p></td>
<td><p>Specifies the address of the node, in the DM Tree, that is the target of the OMA DM command.</p></td>
</tr>
<tr class="even">
<td><p>TargetRef</p></td>
<td><p>Specifies the target address in the corresponding request message. This element takes the value of the request message Target element and is returned in the Status or Results element.</p></td>
</tr>
<tr class="odd">
<td><p>VerDTD</p></td>
<td><p>Specifies the major and minor version identifier of the OMA DM representation protocol specification used to represent the message.</p></td>
</tr>
<tr class="even">
<td><p>VerProto</p></td>
<td><p>Specifies the major and minor version identifier of the OMA DM protocol specification used with the message.</p></td>
</tr>
</tbody>
</table>
## Device management session ## Device management session
@ -257,52 +88,13 @@ A DM session can be divided into two phases:
The following table shows the sequence of events during a typical DM session. The following table shows the sequence of events during a typical DM session.
<table> |Step|Action|Description|
<colgroup> |--- |--- |--- |
<col width="33%" /> |1|DM client is invoked to call back to the management server<br><br>Enterprise scenario – The device task schedule invokes the DM client.|The MO server sends a server trigger message to invoke the DM client.<br><br>The trigger message includes the server ID and tells the client device to initiate a session with the server. The client device authenticates the trigger message and verifies that the server is authorized to communicate with it.<br><br>Enterprise scenario - At the scheduled time, the DM client is invoked periodically to call back to the enterprise management server over HTTPS.|
<col width="33%" /> |2|The device sends a message, over an IP connection, to initiate the session.|This message includes device information and credentials. The client and server do mutual authentication over an SSL channel or at the DM application level.|
<col width="33%" /> |3|The DM server responds, over an IP connection (HTTPS).|The server sends initial device management commands, if any.|
</colgroup> |4|The device responds to server management commands.|This message includes the results of performing the specified device management operations.|
<thead> |5|The DM server terminates the session or sends another command.|The DM session ends, or Step 4 is repeated.|
<tr class="header">
<th>Step</th>
<th>Action</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>1</p></td>
<td><p>DM client is invoked to call back to the management server</p>
<p>Enterprise scenario – The device task schedule invokes the DM client.</p></td>
<td><p>The MO server sends a server trigger message to invoke the DM client.</p>
<p>The trigger message includes the server ID and tells the client device to initiate a session with the server. The client device authenticates the trigger message and verifies that the server is authorized to communicate with it.</p>
<p>Enterprise scenario - At the scheduled time, the DM client is invoked periodically to call back to the enterprise management server over HTTPS.</p></td>
</tr>
<tr class="even">
<td><p>2</p></td>
<td><p>The device sends a message, over an IP connection, to initiate the session.</p></td>
<td><p>This message includes device information and credentials. The client and server do mutual authentication over an SSL channel or at the DM application level.</p></td>
</tr>
<tr class="odd">
<td><p>3</p></td>
<td><p>The DM server responds, over an IP connection (HTTPS).</p></td>
<td><p>The server sends initial device management commands, if any.</p></td>
</tr>
<tr class="even">
<td><p>4</p></td>
<td><p>The device responds to server management commands.</p></td>
<td><p>This message includes the results of performing the specified device management operations.</p></td>
</tr>
<tr class="odd">
<td><p>5</p></td>
<td><p>The DM server terminates the session or sends another command.</p></td>
<td><p>The DM session ends, or Step 4 is repeated.</p></td>
</tr>
</tbody>
</table>
The step numbers in the table do not represent message identification numbers (MsgID). All messages from the server must have a MsgID that is unique within the session, starting at 1 for the first message, and increasing by an increment of 1 for each additional message. For more information about MsgID and OMA SyncML protocol, see "OMA Device Management Representation Protocol" (DM_RepPro-V1_2-20070209-A) available from the [OMA website](https://www.openmobilealliance.org/release/DM/V1_2-20070209-A/). The step numbers in the table do not represent message identification numbers (MsgID). All messages from the server must have a MsgID that is unique within the session, starting at 1 for the first message, and increasing by an increment of 1 for each additional message. For more information about MsgID and OMA SyncML protocol, see "OMA Device Management Representation Protocol" (DM_RepPro-V1_2-20070209-A) available from the [OMA website](https://www.openmobilealliance.org/release/DM/V1_2-20070209-A/).

61
windows/client-management/mdm/policy-csp-abovelock.md
View File

@ -38,33 +38,13 @@ manager: dansimp
<a href="" id="abovelock-allowcortanaabovelock"></a>**AboveLock/AllowCortanaAboveLock** <a href="" id="abovelock-allowcortanaabovelock"></a>**AboveLock/AllowCortanaAboveLock**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr>
<th>Edition</th>
<th>Windows 10</th>
<th>Windows 11</th>
</tr>
<tr>
<td>Home</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</table> |Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -105,28 +85,13 @@ The following list shows the supported values:
<a href="" id="abovelock-allowtoasts"></a>**AboveLock/AllowToasts** <a href="" id="abovelock-allowtoasts"></a>**AboveLock/AllowToasts**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|Yes, starting in Windows 10, version 1607|Yes|
</tr> |Enterprise|Yes, starting in Windows 10, version 1607|Yes|
<tr> |Education|Yes, starting in Windows 10, version 1607|Yes|
<td>Home</td>
<td>No</td><td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>Yes, starting in Windows 10, version 1607</td><td>Yes</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes, starting in Windows 10, version 1607</td><td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes, starting in Windows 10, version 1607</td><td>Yes</td>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>

150
windows/client-management/mdm/policy-csp-accounts.md
View File

@ -40,43 +40,15 @@ manager: dansimp
<a href="" id="accounts-allowaddingnonmicrosoftaccountsmanually"></a>**Accounts/AllowAddingNonMicrosoftAccountsManually** <a href="" id="accounts-allowaddingnonmicrosoftaccountsmanually"></a>**Accounts/AllowAddingNonMicrosoftAccountsManually**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|Yes|Yes|
</tr> |Enterprise|Yes|Yes|
<tr> |Education|Yes|Yes|
<td>Home</td> |Mobile|Yes|Yes|
<td>No</td> |Mobile Enterprise|Yes|Yes|
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Mobile</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Mobile Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -114,48 +86,16 @@ The following list shows the supported values:
<a href="" id="accounts-allowmicrosoftaccountconnection"></a>**Accounts/AllowMicrosoftAccountConnection** <a href="" id="accounts-allowmicrosoftaccountconnection"></a>**Accounts/AllowMicrosoftAccountConnection**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|Yes|Yes|
</tr> |Business|Yes|Yes|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td> |Mobile|Yes|Yes|
<td>No</td> |Mobile Enterprise|Yes|Yes|
</tr>
<tr>
<td>Pro</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Business</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Mobile</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Mobile Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -190,48 +130,16 @@ The following list shows the supported values:
<a href="" id="accounts-allowmicrosoftaccountsigninassistant"></a>**Accounts/AllowMicrosoftAccountSignInAssistant** <a href="" id="accounts-allowmicrosoftaccountsigninassistant"></a>**Accounts/AllowMicrosoftAccountSignInAssistant**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|Yes|Yes|
</tr> |Business|Yes|Yes|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td> |Mobile|Yes|Yes|
<td>No</td> |Mobile Enterprise|Yes|Yes|
</tr>
<tr>
<td>Pro</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Business</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Mobile</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Mobile Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>

32
windows/client-management/mdm/policy-csp-activexcontrols.md
View File

@ -40,31 +40,13 @@ manager: dansimp
<a href="" id="activexcontrols-approvedinstallationsites"></a>**ActiveXControls/ApprovedInstallationSites** <a href="" id="activexcontrols-approvedinstallationsites"></a>**ActiveXControls/ApprovedInstallationSites**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|Yes|Yes|
</tr> |Enterprise|Yes|Yes|
<tr> |Education|Yes|Yes|
<td>Home</td>
<td>No</td><td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>

33
windows/client-management/mdm/policy-csp-admx-activexinstallservice.md
View File

@ -40,31 +40,14 @@ manager: dansimp
<a href="" id="admx-activexinstallservice-axisurlzonepolicies"></a>**ADMX_ActiveXInstallService/AxISURLZonePolicies** <a href="" id="admx-activexinstallservice-axisurlzonepolicies"></a>**ADMX_ActiveXInstallService/AxISURLZonePolicies**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|Yes|Yes|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>

411
windows/client-management/mdm/policy-csp-admx-addremoveprograms.md
View File

@ -70,20 +70,10 @@ manager: dansimp
<a href="" id="admx-addremoveprograms-defaultcategory"></a>**ADMX_AddRemovePrograms/DefaultCategory** <a href="" id="admx-addremoveprograms-defaultcategory"></a>**ADMX_AddRemovePrograms/DefaultCategory**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr>
<th>Edition</th>
<th>Windows 10</th>
<th>Windows 11</th>
</tr>
<tr>
<td>Home</td>
<td>No</td>
<td>No</td>
</tr>
</tr> |Edition|Windows 10|Windows 11|
</table> |--- |--- |--- |
|Home|No|No|
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -135,34 +125,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-noaddfromcdorfloppy"></a>**ADMX_AddRemovePrograms/NoAddFromCDorFloppy** <a href="" id="admx-addremoveprograms-noaddfromcdorfloppy"></a>**ADMX_AddRemovePrograms/NoAddFromCDorFloppy**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|||
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|||
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -212,38 +182,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-noaddfrominternet"></a>**ADMX_AddRemovePrograms/NoAddFromInternet** <a href="" id="admx-addremoveprograms-noaddfrominternet"></a>**ADMX_AddRemovePrograms/NoAddFromInternet**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -294,38 +240,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-noaddfromnetwork"></a>**ADMX_AddRemovePrograms/NoAddFromNetwork** <a href="" id="admx-addremoveprograms-noaddfromnetwork"></a>**ADMX_AddRemovePrograms/NoAddFromNetwork**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -377,38 +299,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-noaddpage"></a>**ADMX_AddRemovePrograms/NoAddPage** <a href="" id="admx-addremoveprograms-noaddpage"></a>**ADMX_AddRemovePrograms/NoAddPage**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -456,38 +354,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-noaddremoveprograms"></a>**ADMX_AddRemovePrograms/NoAddRemovePrograms** <a href="" id="admx-addremoveprograms-noaddremoveprograms"></a>**ADMX_AddRemovePrograms/NoAddRemovePrograms**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -535,38 +409,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-nochooseprogramspage"></a>**ADMX_AddRemovePrograms/NoChooseProgramsPage** <a href="" id="admx-addremoveprograms-nochooseprogramspage"></a>**ADMX_AddRemovePrograms/NoChooseProgramsPage**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -615,37 +465,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-noremovepage"></a>**ADMX_AddRemovePrograms/NoRemovePage** <a href="" id="admx-addremoveprograms-noremovepage"></a>**ADMX_AddRemovePrograms/NoRemovePage**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -693,38 +520,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-noservices"></a>**ADMX_AddRemovePrograms/NoServices** <a href="" id="admx-addremoveprograms-noservices"></a>**ADMX_AddRemovePrograms/NoServices**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -775,38 +578,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-nosupportinfo"></a>**ADMX_AddRemovePrograms/NoSupportInfo** <a href="" id="admx-addremoveprograms-nosupportinfo"></a>**ADMX_AddRemovePrograms/NoSupportInfo**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>
@ -856,38 +635,14 @@ ADMX Info:
<a href="" id="admx-addremoveprograms-nowindowssetuppage"></a>**ADMX_AddRemovePrograms/NoWindowsSetupPage** <a href="" id="admx-addremoveprograms-nowindowssetuppage"></a>**ADMX_AddRemovePrograms/NoWindowsSetupPage**
<!--SupportedSKUs--> <!--SupportedSKUs-->
<table>
<tr> |Edition|Windows 10|Windows 11|
<th>Edition</th> |--- |--- |--- |
<th>Windows 10</th> |Home|No|No|
<th>Windows 11</th> |Pro|No|No|
</tr> |Business|No|No|
<tr> |Enterprise|Yes|Yes|
<td>Home</td> |Education|Yes|Yes|
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Pro</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Business</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Enterprise</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Education</td>
<td>Yes</td>
<td>Yes</td>
</tr>
</table>
<!--/SupportedSKUs--> <!--/SupportedSKUs-->
<hr/> <hr/>