mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge branch 'master' into v-smandalika-5494946-B3
This commit is contained in:
commit
941dc0e7ea
@ -35,16 +35,16 @@ You should read and understand the following information before reading this doc
|
|||||||
|
|
||||||
- [App-V Sequencing Guide](https://www.microsoft.com/download/details.aspx?id=27760)
|
- [App-V Sequencing Guide](https://www.microsoft.com/download/details.aspx?id=27760)
|
||||||
|
|
||||||
**Note**
|
> [!Note]
|
||||||
Some terms used in this document may have different meanings depending on external source and context. For more information about terms used in this document followed by an asterisk <strong>*</strong> review the [Application Virtualization Performance Guidance Terminology](#bkmk-terms1) section of this document.
|
> Some terms used in this document may have different meanings depending on external source and context. For more information about terms used in this document followed by an asterisk `*`, review the [Application Virtualization Performance Guidance Terminology](#bkmk-terms1) section of this document.
|
||||||
|
|
||||||
Finally, this document will provide you with the information to configure the computer running App-V client and the environment for optimal performance. Optimize your virtual application packages for performance using the sequencer, and to understand how to use User Experience Virtualization (UE-V) or other user environment management technologies to provide the optimal user experience with App-V in both Remote Desktop Services (RDS) and non-persistent virtual desktop infrastructure (VDI).
|
Finally, this document will provide you with the information to configure the computer running App-V client and the environment for optimal performance. Optimize your virtual application packages for performance using the sequencer, and to understand how to use User Experience Virtualization (UE-V) or other user environment management technologies to provide the optimal user experience with App-V in both Remote Desktop Services (RDS) and non-persistent virtual desktop infrastructure (VDI).
|
||||||
|
|
||||||
To help determine what information is relevant to your environment you should review each section’s brief overview and applicability checklist.
|
To help determine what information is relevant to your environment, you should review each section’s brief overview and applicability checklist.
|
||||||
|
|
||||||
## <a href="" id="---------app-v-5-1-in-stateful--non-persistent-deployments"></a> App-V in stateful\* non-persistent deployments
|
## <a href="" id="---------app-v-5-1-in-stateful--non-persistent-deployments"></a> App-V in stateful\* non-persistent deployments
|
||||||
|
|
||||||
This section provides information about an approach that helps ensure a user will have access to all virtual applications within seconds after logging in. This is achieved by uniquely addressing the often long-running App-V publishing refresh. As you will discover the basis of the approach, the fastest publishing refresh, is one that doesn’t have to actually do anything. A number of conditions must be met and steps followed to provide the optimal user experience.
|
This section provides information about an approach that helps ensure a user will have access to all virtual applications within seconds after logging in. This is achieved by uniquely addressing the often long-running App-V publishing refresh. As you will discover the basis of the approach, the fastest publishing refresh, is one that doesn’t have to actually do anything. Many conditions must be met and steps followed to provide the optimal user experience.
|
||||||
|
|
||||||
Use the information in the following section for more information:
|
Use the information in the following section for more information:
|
||||||
|
|
||||||
@ -72,199 +72,97 @@ Use the information in the following section for more information:
|
|||||||
|
|
||||||
### <a href="" id="applicability-checklist-"></a>Applicability Checklist
|
### <a href="" id="applicability-checklist-"></a>Applicability Checklist
|
||||||
|
|
||||||
Deployment Environment
|
|Checklist|Deployment Environment|
|
||||||
|
|--- |--- |
|
||||||
|
||Non-Persistent VDI or RDSH.|
|
||||||
|
||User Experience Virtualization (UE-V), other UPM solutions or User Profile Disks (UPD).|
|
||||||
|
|
||||||
<table>
|
|Checklist|Expected Configuration|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
||User Experience Virtualization (UE-V) with the App-V user state template enabled or User Profile Management (UPM) software. Non-UE-V UPM software must be capable of triggering on Login or Process/Application Start and Logoff.|
|
||||||
<col width="50%" />
|
||App-V Shared Content Store (SCS) is configured or can be configured.|
|
||||||
</colgroup>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
|
||||||
<td align="left"><p>Non-Persistent VDI or RDSH.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
|
||||||
<td align="left"><p>User Experience Virtualization (UE-V), other UPM solutions or User Profile Disks (UPD).</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Expected Configuration
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
|
||||||
<td align="left"><p>User Experience Virtualization (UE-V) with the App-V user state template enabled or User Profile Management (UPM) software. Non-UE-V UPM software must be capable of triggering on Login or Process/Application Start and Logoff.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
|
||||||
<td align="left"><p>App-V Shared Content Store (SCS) is configured or can be configured.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
IT Administration
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
|
|
||||||
<td align="left"><p>Admin may need to update the VM base image regularly to ensure optimal performance or Admin may need to manage multiple images for different user groups.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|Checklist|IT Administration|
|
||||||
|
|--- |--- |
|
||||||
|
||Admin may need to update the VM base image regularly to ensure optimal performance or Admin may need to manage multiple images for different user groups.|
|
||||||
|
|
||||||
### <a href="" id="bkmk-us"></a>Usage Scenarios
|
### <a href="" id="bkmk-us"></a>Usage Scenarios
|
||||||
|
|
||||||
As you review the two scenarios, keep in mind that these approach the extremes. Based on your usage requirements, you may choose to apply these steps to a subset of users, virtual application packages, or both.
|
As you review the two scenarios, keep in mind that these approach the extremes. Based on your usage requirements, you may choose to apply these steps to a subset of users, virtual application packages, or both.
|
||||||
|
|
||||||
<table>
|
- **Performance**: To provide the most optimal user experience, this approach uses the capabilities of a UPM solution and requires extra image preparation and can incur some more image management overhead.
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Optimized for Performance</th>
|
|
||||||
<th align="left">Optimized for Storage</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>To provide the most optimal user experience, this approach leverages the capabilities of a UPM solution and requires additional image preparation and can incur some additional image management overhead.</p>
|
|
||||||
<p>The following describes many performance improvements in stateful non-persistent deployments. For more information, see <a href="#sequencing-steps-to-optimize-packages-for-publishing-performance" data-raw-source="[Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance)">Sequencing Steps to Optimize Packages for Publishing Performance</a> later in this topic.</p></td>
|
|
||||||
<td align="left"><p>The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in very costly arrays; a slight alteration has been made to the approach. Do not pre-configure user-targeted virtual application packages in the base image.</p>
|
|
||||||
<p>The impact of this alteration is detailed in the <a href="#bkmk-uewt" data-raw-source="[User Experience Walk-through](#bkmk-uewt)">User Experience Walk-through</a> section of this document.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
The following describes many performance improvements in stateful non-persistent deployments. For more information, see [Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance) (in this article).
|
||||||
|
|
||||||
|
- **Storage**: The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in costly arrays; a slight alteration has been made to the approach. Do not pre-configure user-targeted virtual application packages in the base image.
|
||||||
|
|
||||||
|
The impact of this alteration is detailed in the [User Experience Walk-through](#bkmk-uewt) (in this article).
|
||||||
|
|
||||||
### <a href="" id="bkmk-pe"></a>Preparing your Environment
|
### <a href="" id="bkmk-pe"></a>Preparing your Environment
|
||||||
|
|
||||||
The following table displays the required steps to prepare the base image and the UE-V or another UPM solution for the approach.
|
The following information displays the required steps to prepare the base image and the UE-V or another UPM solution for the approach.
|
||||||
|
|
||||||
**Prepare the Base Image**
|
#### Prepare the Base Image
|
||||||
|
|
||||||
<table>
|
- **Performance**:
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Optimized for Performance</th>
|
|
||||||
<th align="left">Optimized for Storage</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Enable the App-V client as described in <a href="appv-enable-the-app-v-desktop-client.md" data-raw-source="[Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md)">Enable the App-V in-box client</a>.</p></li>
|
|
||||||
<li><p>Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
|
|
||||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see <a href="appv-deploying-the-appv-sequencer-and-client.md" data-raw-source="[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)">Deploying the App-V Sequencer and Configuring the Client</a>.</p></li>
|
|
||||||
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
|
|
||||||
<li><p>Pre-configure all user- and global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
|
|
||||||
<li><p>Pre-configure all user- and global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
|
|
||||||
<li><p>Pre-publish all global-targeted packages.</p>
|
|
||||||
<p></p>
|
|
||||||
<p>Alternatively,</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Perform a global publishing/refresh.</p></li>
|
|
||||||
<li><p>Perform a user publishing/refresh.</p></li>
|
|
||||||
<li><p>Un-publish all user-targeted packages.</p></li>
|
|
||||||
<li><p>Delete the following user-Virtual File System (VFS) entries.</p></li>
|
|
||||||
</ul>
|
|
||||||
<p><code>AppData\Local\Microsoft\AppV\Client\VFS</code></p>
|
|
||||||
<p><code>AppData\Roaming\Microsoft\AppV\Client\VFS</code></p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Enable the App-V client as described in <a href="appv-enable-the-app-v-desktop-client.md" data-raw-source="[Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md)">Enable the App-V in-box client</a>.</p></li>
|
|
||||||
<li><p>Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
|
|
||||||
<li><p>Configure for Shared Content Store (SCS) mode. For more information see <a href="appv-deploying-the-appv-sequencer-and-client.md" data-raw-source="[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)">Deploying the App-V Sequencer and Configuring the Client</a>.</p></li>
|
|
||||||
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
|
|
||||||
<li><p>Pre-configure all global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
|
|
||||||
<li><p>Pre-configure all global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
|
|
||||||
<li><p>Pre-publish all global-targeted packages.</p>
|
|
||||||
<p></p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
- Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).
|
||||||
|
- Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.
|
||||||
|
- Configure for Shared Content Store (SCS) mode. For more information, see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
|
||||||
|
- Configure Preserve User Integrations on Login Registry DWORD.
|
||||||
|
- Pre-configure all user and global-targeted packages, for example, **Add-AppvClientPackage**.
|
||||||
|
- Pre-configure all user- and global-targeted connection groups, for example, **Add-AppvClientConnectionGroup**.
|
||||||
|
- Pre-publish all global-targeted packages. Or:
|
||||||
|
- Perform a global publishing/refresh.
|
||||||
|
- Perform a user publishing/refresh.
|
||||||
|
- Unpublish all user-targeted packages.
|
||||||
|
- Delete the following user-Virtual File System (VFS) entries:
|
||||||
|
|
||||||
|
- `AppData\Local\Microsoft\AppV\Client\VFS`
|
||||||
|
- `AppData\Roaming\Microsoft\AppV\Client\VFS`
|
||||||
|
|
||||||
**Configurations** - For critical App-V Client configurations and for a little more context and how-to, review the following information:
|
- **Storage**:
|
||||||
|
|
||||||
<table>
|
- Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).
|
||||||
<colgroup>
|
- Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.
|
||||||
<col width="33%" />
|
- Configure for Shared Content Store (SCS) mode. For more information, see [Deploying the
|
||||||
<col width="33%" />
|
App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
|
||||||
<col width="33%" />
|
- Configure Preserve User Integrations on Login Registry DWORD.
|
||||||
</colgroup>
|
- Pre-configure all global-targeted packages, for example, **Add-AppvClientPackage**.
|
||||||
<thead>
|
- Pre-configure all global-targeted connection groups, for example, **Add-AppvClientConnectionGroup**.
|
||||||
<tr class="header">
|
- Pre-publish all global-targeted packages.
|
||||||
<th align="left">Configuration Setting</th>
|
|
||||||
<th align="left">What does this do?</th>
|
|
||||||
<th align="left">How should I use it?</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Shared Content Store (SCS) Mode</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Configurable in Windows PowerShell with <code>Set-AppvClientConfiguration -SharedContentStoreMode 1</code><br>or configurable with Group Policy, as described in <a href="appv-deploying-the-appv-sequencer-and-client.md" data-raw-source="[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)">Deploying the App-V Sequencer and Configuring the Client</a>.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM).</p>
|
|
||||||
<p>This helps to conserve local storage and minimize disk I/O per second (IOPS).</p></td>
|
|
||||||
<td align="left"><p>This is recommended when low-latency connections are available between the App-V Client endpoint and the SCS content server, SAN.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>PreserveUserIntegrationsOnLogin</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Configure in the Registry under <strong>HKEY_LOCAL_MACHINE</strong> \ <strong>Software</strong> \ <strong>Microsoft</strong> \ <strong>AppV</strong> \ <strong>Client</strong> \ <strong>Integration</strong>.</p></li>
|
|
||||||
<li><p>Create the DWORD value <strong>PreserveUserIntegrationsOnLogin</strong> with a value of <strong>1</strong>.</p></li>
|
|
||||||
<li><p>Restart the App-V client service or restart the computer running the App-V Client.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>If you have not pre-configured (<strong>Add-AppvClientPackage</strong>) a specific package and this setting is not configured, the App-V Client will de-integrate* the persisted user integrations, then re-integrate*.</p>
|
|
||||||
<p>For every package that meets the above conditions, effectively twice the work will be done during publishing/refresh.</p></td>
|
|
||||||
<td align="left"><p>If you don’t plan to pre-configure every available user package in the base image, use this setting.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>MaxConcurrentPublishingRefresh</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Configure in the Registry under <strong>HKEY_LOCAL_MACHINE</strong> \ <strong>Software</strong> \ <strong>Microsoft</strong> \ <strong>AppV</strong> \ <strong>Client</strong> \ <strong>Publishing</strong>.</p></li>
|
|
||||||
<li><p>Create the DWORD value <strong>MaxConcurrentPublishingrefresh</strong> with the desired maximum number of concurrent publishing refreshes.</p></li>
|
|
||||||
<li><p>The App-V client service and computer do not need to be restarted.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>This setting determines the number of users that can perform a publishing refresh/sync at the same time. The default setting is no limit.</p></td>
|
|
||||||
<td align="left"><p>Limiting the number of concurrent publishing refreshes prevents excessive CPU usage that could impact computer performance. This limit is recommended in an RDS environment, where multiple users can log in to the same computer at the same time and perform a publishing refresh sync.</p>
|
|
||||||
<p>If the concurrent publishing refresh threshold is reached, the time required to publish new applications and make them available to end users after they log in could take an indeterminate amount of time.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
#### Configurations
|
||||||
|
|
||||||
|
For critical App-V Client configurations and for a little more context and how-to, review the following configuration settings:
|
||||||
|
|
||||||
|
- **Shared Content Store (SCS) Mode**: When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM). This helps to conserve local storage and minimize disk I/O per second (IOPS).
|
||||||
|
|
||||||
|
This setting is recommended when low-latency connections are available between the App-V Client endpoint and the SCS content server, SAN.
|
||||||
|
|
||||||
|
- Configurable in Windows PowerShell: `Set-AppvClientConfiguration -SharedContentStoreMode 1`
|
||||||
|
- Configurable with Group Policy: See [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
|
||||||
|
|
||||||
|
- **PreserveUserIntegrationsOnLogin**: If you have not pre-configured (**Add-AppvClientPackage**) a specific package and this setting is not configured, the App-V Client will de-integrate* the persisted user integrations, then reintegrate*.
|
||||||
|
|
||||||
|
For every package that meets the above conditions, effectively twice the work will be done during publishing/refresh.
|
||||||
|
|
||||||
|
If you don’t plan to pre-configure every available user package in the base image, use this setting.
|
||||||
|
|
||||||
|
- Configure in the Registry under `HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Integration`.
|
||||||
|
- Create the DWORD value **PreserveUserIntegrationsOnLogin** with a value of 1.
|
||||||
|
- Restart the App-V client service or restart the computer running the App-V Client.
|
||||||
|
|
||||||
|
- **MaxConcurrentPublishingRefresh**: This setting determines the number of users that can perform a publishing refresh/sync at the same time. The default setting is no limit.
|
||||||
|
|
||||||
|
Limiting the number of concurrent publishing refreshes prevents excessive CPU usage that could impact computer performance. This limit is recommended in an RDS environment, where multiple users can log in to the same computer at the same time and perform a publishing refresh sync.
|
||||||
|
|
||||||
|
If the concurrent publishing refresh threshold is reached, the time required to publish new applications and make them available to end users after they log in could take an indeterminate amount of time.
|
||||||
|
|
||||||
|
- Configure in the Registry under `HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Publishing`.
|
||||||
|
- Create the DWORD value **MaxConcurrentPublishingrefresh** with the desired maximum number of concurrent publishing refreshes.
|
||||||
|
- The App-V client service and computer do not need to be restarted.
|
||||||
|
|
||||||
### Configure UE-V solution for App-V Approach
|
### Configure UE-V solution for App-V Approach
|
||||||
|
|
||||||
@ -278,8 +176,8 @@ For more information, see:
|
|||||||
|
|
||||||
In essence all that is required is to enable the UE-V service and download the following Microsoft authored App-V settings template from the [Microsoft User Experience Virtualization (UE-V) template gallery](https://gallery.technet.microsoft.com/Authored-UE-V-Settings-bb442a33). Register the template. For more information about UE-V templates, see [User Experience Virtualization (UE-V) for Windows client overview](/windows/configuration/ue-v/uev-for-windows).
|
In essence all that is required is to enable the UE-V service and download the following Microsoft authored App-V settings template from the [Microsoft User Experience Virtualization (UE-V) template gallery](https://gallery.technet.microsoft.com/Authored-UE-V-Settings-bb442a33). Register the template. For more information about UE-V templates, see [User Experience Virtualization (UE-V) for Windows client overview](/windows/configuration/ue-v/uev-for-windows).
|
||||||
|
|
||||||
**Note**
|
> [!Note]
|
||||||
Without performing an additional configuration step, User Environment Virtualization (UE-V) will not be able to synchronize the Start menu shortcuts (.lnk files) on the target computer. The .lnk file type is excluded by default.
|
> Without performing an additional configuration step, User Environment Virtualization (UE-V) will not be able to synchronize the Start menu shortcuts (.lnk files) on the target computer. The .lnk file type is excluded by default.
|
||||||
|
|
||||||
UE-V will only support removing the .lnk file type from the exclusion list in the RDS and VDI scenarios, where every user’s device will have the same set of applications installed to the same location and every .lnk file is valid for all the users’ devices. For example, UE-V would not currently support the following two scenarios, because the net result will be that the shortcut will be valid on one but not all devices.
|
UE-V will only support removing the .lnk file type from the exclusion list in the RDS and VDI scenarios, where every user’s device will have the same set of applications installed to the same location and every .lnk file is valid for all the users’ devices. For example, UE-V would not currently support the following two scenarios, because the net result will be that the shortcut will be valid on one but not all devices.
|
||||||
|
|
||||||
@ -287,12 +185,10 @@ UE-V will only support removing the .lnk file type from the exclusion list in th
|
|||||||
|
|
||||||
- If a user has an application installed on one device but not another with .lnk files enabled.
|
- If a user has an application installed on one device but not another with .lnk files enabled.
|
||||||
|
|
||||||
**Important**
|
> [!Important]
|
||||||
This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
|
> This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
|
||||||
|
|
||||||
|
Using the Microsoft Registry Editor (regedit.exe), navigate to `HKEY\_LOCAL\_MACHINE\Software\Microsoft\UEV\Agent\Configuration\ExcludedFileTypes` and remove `.lnk` from the excluded file types.
|
||||||
|
|
||||||
Using the Microsoft Registry Editor (regedit.exe), navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **UEV** \\ **Agent** \\ **Configuration** \\ **ExcludedFileTypes** and remove **.lnk** from the excluded file types.
|
|
||||||
|
|
||||||
## Configure other User Profile Management (UPM) solutions for App-V Approach
|
## Configure other User Profile Management (UPM) solutions for App-V Approach
|
||||||
|
|
||||||
@ -308,12 +204,11 @@ To enable an optimized login experience, for example the App-V approach for the
|
|||||||
|
|
||||||
- Attaching and detaching a user profile disk (UPD) or similar technology that contains the user integrations.
|
- Attaching and detaching a user profile disk (UPD) or similar technology that contains the user integrations.
|
||||||
|
|
||||||
**Note**
|
> [!Note]
|
||||||
App-V is supported when using UPD only when the entire profile is stored on the user profile disk.
|
>
|
||||||
|
> App-V is supported when using UPD only when the entire profile is stored on the user profile disk.
|
||||||
App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver does not handle UPD selected folders.
|
>
|
||||||
|
> App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver does not handle UPD selected folders.
|
||||||
|
|
||||||
|
|
||||||
- Capturing changes to the locations, which constitute the user integrations, prior to session logoff.
|
- Capturing changes to the locations, which constitute the user integrations, prior to session logoff.
|
||||||
|
|
||||||
@ -355,83 +250,61 @@ Registry – HKEY\_CURRENT\_USER
|
|||||||
|
|
||||||
This following is a step-by-step walk-through of the App-V and UPM operations and the expectations users should expect.
|
This following is a step-by-step walk-through of the App-V and UPM operations and the expectations users should expect.
|
||||||
|
|
||||||
<table>
|
- **Performance**: After implementing this approach in the VDI/RDSH environment, on first login,
|
||||||
<colgroup>
|
- (Operation) A user-publishing/refresh is initiated.
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Optimized for Performance</th>
|
|
||||||
<th align="left">Optimized for Storage</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>After implementing this approach in the VDI/RDSH environment, on first login,</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>(Operation) A user-publishing/refresh is initiated. (Expectation) If this is the first time a user has published virtual applications (e.g. non-persistent), this will take the usual duration of a publishing/refresh.</p></li>
|
|
||||||
<li><p>(Operation) After the publishing/refresh, the UPM solution captures the user integrations. (Expectation) Depending on how the UPM solution is configured, this may occur as part of the logoff process. This will incur the same/similar overhead as persisting the user state.</p></li>
|
|
||||||
</ul>
|
|
||||||
<p>On subsequent logins:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>(Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.</p>
|
|
||||||
<p>(Expectation) There will be shortcuts present on the desktop, or in the start menu, which work immediately. When the publishing/refresh completes (i.e., package entitlements change), some may go away.</p></li>
|
|
||||||
<li><p>(Operation) Publishing/refresh will process un-publish and publish operations for changes in user package entitlements. (Expectation) If there are no entitlement changes, publishing1 will complete in seconds. Otherwise, the publishing/refresh will increase relative to the number and complexity* of virtual applications</p></li>
|
|
||||||
<li><p>(Operation) UPM solution will capture user integrations again at logoff. (Expectation) Same as previous.</p></li>
|
|
||||||
</ul>
|
|
||||||
<p>¹ The publishing operation (<strong>Publish-AppVClientPackage</strong>) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps.</p></td>
|
|
||||||
<td align="left"><p>After implementing this approach in the VDI/RDSH environment, on first login,</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>(Operation) A user-publishing/refresh is initiated. (Expectation)</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>If this is the first time a user has published virtual applications (e.g., non-persistent), this will take the usual duration of a publishing/refresh.</p></li>
|
|
||||||
<li><p>First and subsequent logins will be impacted by pre-configuring of packages (add/refresh).</p>
|
|
||||||
<p></p></li>
|
|
||||||
</ul></li>
|
|
||||||
<li><p>(Operation) After the publishing/refresh, the UPM solution captures the user integrations. (Expectation) Depending on how the UPM solution is configured, this may occur as part of the logoff process. This will incur the same/similar overhead as persisting the user state</p></li>
|
|
||||||
</ul>
|
|
||||||
<p>On subsequent logins:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>(Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.</p></li>
|
|
||||||
<li><p>(Operation) Add/refresh must pre-configure all user targeted applications. (Expectation)</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>This may increase the time to application availability significantly (on the order of 10’s of seconds).</p></li>
|
|
||||||
<li><p>This will increase the publishing refresh time relative to the number and complexity* of virtual applications.</p>
|
|
||||||
<p></p></li>
|
|
||||||
</ul></li>
|
|
||||||
<li><p>(Operation) Publishing/refresh will process un-publish and publish operations for changes to user package entitlements.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
(Expectation) If this is the first time a user has published virtual applications (e.g. non-persistent), this will take the usual duration of a publishing/refresh.
|
||||||
|
|
||||||
|
- (Operation) After the publishing/refresh, the UPM solution captures the user integrations.
|
||||||
|
|
||||||
<table>
|
(Expectation) Depending on how the UPM solution is configured, this may occur as part of the logoff process. This will incur the same/similar overhead as persisting the user state.
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Outcome</th>
|
|
||||||
<th align="left">Outcome</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Because the user integrations are entirely preserved, there will be no work for example, integration for the publishing/refresh to complete. All virtual applications will be available within seconds of login.</p></li>
|
|
||||||
<li><p>The publishing/refresh will process changes to the users entitled virtual applications which impacts the experience.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>Because the add/refresh must re-configure all the virtual applications to the VM, the publishing refresh time on every login will be extended.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
**On subsequent logins**:
|
||||||
|
|
||||||
|
- (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.
|
||||||
|
|
||||||
|
(Expectation) There will be shortcuts present on the desktop, or in the start menu, which work immediately. When the publishing/refresh completes (i.e., package entitlements change), some may go away.
|
||||||
|
|
||||||
|
- (Operation) Publishing/refresh will process un-publish and publish operations for changes in user package entitlements.
|
||||||
|
|
||||||
|
(Expectation) If there are no entitlement changes, publishing will complete in seconds. Otherwise, the publishing/refresh will increase relative to the number and complexity of virtual applications
|
||||||
|
|
||||||
|
The publishing operation (**Publish-AppVClientPackage**) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps.
|
||||||
|
|
||||||
|
- (Operation) UPM solution will capture user integrations again at logoff.
|
||||||
|
|
||||||
|
(Expectation) Same as previous.
|
||||||
|
|
||||||
|
**Outcome**:
|
||||||
|
|
||||||
|
- Because the user integrations are entirely preserved, there will be no work for example, integration for the publishing/refresh to complete. All virtual applications will be available within seconds of login.
|
||||||
|
- The publishing/refresh will process changes to the users entitled virtual applications which impacts the experience.
|
||||||
|
|
||||||
|
- **Storage**: After implementing this approach in the VDI/RDSH environment, on first login
|
||||||
|
|
||||||
|
- (Operation) A user-publishing/refresh is initiated.
|
||||||
|
|
||||||
|
(Expectation):
|
||||||
|
|
||||||
|
- If this is the first time a user has published virtual applications (e.g., non-persistent), this will take the usual duration of a publishing/refresh.
|
||||||
|
- First and subsequent logins will be impacted by pre-configuring of packages (add/refresh).
|
||||||
|
|
||||||
|
- (Operation) After the publishing/refresh, the UPM solution captures the user integrations.
|
||||||
|
|
||||||
|
(Expectation) Depending on how the UPM solution is configured, this may occur as part of the logoff process. This will incur the same/similar overhead as persisting the user state.
|
||||||
|
|
||||||
|
**On subsequent logins**:
|
||||||
|
|
||||||
|
- (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.
|
||||||
|
- (Operation) Add/refresh must pre-configure all user targeted applications.
|
||||||
|
|
||||||
|
- (Expectation):
|
||||||
|
- This may increase the time to application availability significantly (on the order of 10’s of seconds).
|
||||||
|
- This will increase the publishing refresh time relative to the number and complexity* of virtual applications.
|
||||||
|
|
||||||
|
- (Operation) Publishing/refresh will process un-publish and publish operations for changes to user package entitlements.
|
||||||
|
|
||||||
|
**Outcome**: Because the add/refresh must re-configure all the virtual applications to the VM, the publishing refresh time on every login will be extended.
|
||||||
|
|
||||||
### <a href="" id="bkmk-plc"></a>Impact to Package Life Cycle
|
### <a href="" id="bkmk-plc"></a>Impact to Package Life Cycle
|
||||||
|
|
||||||
@ -489,36 +362,9 @@ Server Performance Tuning Guidelines for
|
|||||||
|
|
||||||
Several App-V features facilitate new scenarios or enable new customer deployment scenarios. These following features can impact the performance of the publishing and launch operations.
|
Several App-V features facilitate new scenarios or enable new customer deployment scenarios. These following features can impact the performance of the publishing and launch operations.
|
||||||
|
|
||||||
<table>
|
|Step|Consideration|Benefits|Tradeoffs|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|No Feature Block 1 (FB1, also known as Primary FB)|No FB1 means the application will launch immediately and stream fault (application requires file, DLL and must pull down over the network) during launch. If there are network limitations, FB1 will:<br><li>Reduce the number of stream faults and network bandwidth used when you launch an application for the first time.<li>Delay launch until the entire FB1 has been streamed.|Stream faulting decreases the launch time.|Virtual application packages with FB1 configured will need to be re-sequenced.|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Consideration</th>
|
|
||||||
<th align="left">Benefits</th>
|
|
||||||
<th align="left">Tradeoffs</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>No Feature Block 1 (FB1, also known as Primary FB)</p></td>
|
|
||||||
<td align="left"><p>No FB1 means the application will launch immediately and stream fault (application requires file, DLL and must pull down over the network) during launch. If there are network limitations, FB1 will:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Reduce the number of stream faults and network bandwidth used when you launch an application for the first time.</p></li>
|
|
||||||
<li><p>Delay launch until the entire FB1 has been streamed.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>Stream faulting decreases the launch time.</p></td>
|
|
||||||
<td align="left"><p>Virtual application packages with FB1 configured will need to be re-sequenced.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Removing FB1
|
### Removing FB1
|
||||||
|
|
||||||
@ -554,36 +400,12 @@ Removing FB1 does not require the original application installer. After completi
|
|||||||
|
|
||||||
"C:\\UpgradedPackages"
|
"C:\\UpgradedPackages"
|
||||||
|
|
||||||
**Note**
|
> [!Note]
|
||||||
This cmdlet requires an executable (.exe) or batch file (.bat). You must provide an empty (does nothing) executable or batch file.
|
> This cmdlet requires an executable (.exe) or batch file (.bat). You must provide an empty (does nothing) executable or batch file.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Considerations</th>
|
|
||||||
<th align="left">Benefits</th>
|
|
||||||
<th align="left">Tradeoffs</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>No SXS Install at Publish (Pre-Install SxS assemblies)</p></td>
|
|
||||||
<td align="left"><p>Virtual Application packages do not need to be re-sequenced. SxS Assemblies can remain in the virtual application package.</p></td>
|
|
||||||
<td align="left"><p>The SxS Assembly dependencies will not install at publishing time.</p></td>
|
|
||||||
<td align="left"><p>SxS Assembly dependencies must be pre-installed.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|Step|Considerations|Benefits|Tradeoffs|
|
||||||
|
|--- |--- |--- |--- |
|
||||||
|
|No SXS Install at Publish (Pre-Install SxS assemblies)|Virtual Application packages do not need to be re-sequenced. SxS Assemblies can remain in the virtual application package.|The SxS Assembly dependencies will not install at publishing time.|SxS Assembly dependencies must be pre-installed.|
|
||||||
|
|
||||||
|
|
||||||
### Creating a new virtual application package on the sequencer
|
### Creating a new virtual application package on the sequencer
|
||||||
@ -594,33 +416,9 @@ If, during sequencer monitoring, an SxS Assembly (such as a VC++ Runtime) is ins
|
|||||||
|
|
||||||
When publishing a virtual application package, the App-V Client will detect if a required SxS dependency is already installed. If the dependency is unavailable on the computer and it is included in the package, a traditional Windows Installer (.**msi**) installation of the SxS assembly will be initiated. As previously documented, simply install the dependency on the computer running the client to ensure that the Windows Installer (.msi) installation will not occur.
|
When publishing a virtual application package, the App-V Client will detect if a required SxS dependency is already installed. If the dependency is unavailable on the computer and it is included in the package, a traditional Windows Installer (.**msi**) installation of the SxS assembly will be initiated. As previously documented, simply install the dependency on the computer running the client to ensure that the Windows Installer (.msi) installation will not occur.
|
||||||
|
|
||||||
<table>
|
|Step|Considerations|Benefits|Tradeoffs|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|Selectively Employ Dynamic Configuration files|The App-V client must parse and process these Dynamic Configuration files. <br> <br>Be conscious of size and complexity (script execution, VREG inclusions/exclusions) of the file.<br> <br>Numerous virtual application packages may already have User- or computer–specific dynamic configurations files.|Publishing times will improve if these files are used selectively or not at all.|Virtual application packages would need to be reconfigured individually or via the App-V server management console to remove associated Dynamic Configuration files.|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Considerations</th>
|
|
||||||
<th align="left">Benefits</th>
|
|
||||||
<th align="left">Tradeoffs</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Selectively Employ Dynamic Configuration files</p></td>
|
|
||||||
<td align="left"><p>The App-V client must parse and process these Dynamic Configuration files.</p>
|
|
||||||
<p>Be conscious of size and complexity (script execution, VREG inclusions/exclusions) of the file.</p>
|
|
||||||
<p>Numerous virtual application packages may already have User- or computer–specific dynamic configurations files.</p></td>
|
|
||||||
<td align="left"><p>Publishing times will improve if these files are used selectively or not at all.</p></td>
|
|
||||||
<td align="left"><p>Virtual application packages would need to be reconfigured individually or via the App-V server management console to remove associated Dynamic Configuration files.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Disabling a Dynamic Configuration by using Windows PowerShell
|
### Disabling a Dynamic Configuration by using Windows PowerShell
|
||||||
@ -639,39 +437,10 @@ For documentation on How to Apply a Dynamic Configuration, see:
|
|||||||
|
|
||||||
- [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
- [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||||
|
|
||||||
<table>
|
|Step|Considerations|Benefits|Tradeoffs|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|Account for Synchronous Script Execution during Package Lifecycle.|If script collateral is embedded in the package, Add cmdlets may be significantly slower.<br>Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations.|Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently.|This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously.|
|
||||||
<col width="25%" />
|
|Remove Extraneous Virtual Fonts from Package.|The majority of applications investigated by the App-V product team contained a small number of fonts, typically fewer than 20.|Virtual Fonts impact publishing refresh performance.|Desired fonts will need to be enabled/installed natively. For instructions, see Install or uninstall fonts.|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Step</th>
|
|
||||||
<th align="left">Considerations</th>
|
|
||||||
<th align="left">Benefits</th>
|
|
||||||
<th align="left">Tradeoffs</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Account for Synchronous Script Execution during Package Lifecycle.</p></td>
|
|
||||||
<td align="left"><p>If script collateral is embedded in the package, Add cmdlets may be significantly slower.</p>
|
|
||||||
<p>Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations.</p></td>
|
|
||||||
<td align="left"><p>Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently.</p></td>
|
|
||||||
<td align="left"><p>This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Remove Extraneous Virtual Fonts from Package.</p></td>
|
|
||||||
<td align="left"><p>The majority of applications investigated by the App-V product team contained a small number of fonts, typically fewer than 20.</p></td>
|
|
||||||
<td align="left"><p>Virtual Fonts impact publishing refresh performance.</p></td>
|
|
||||||
<td align="left"><p>Desired fonts will need to be enabled/installed natively. For instructions, see Install or uninstall fonts.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Determining what virtual fonts exist in the package
|
### Determining what virtual fonts exist in the package
|
||||||
|
|
||||||
@ -681,15 +450,15 @@ For documentation on How to Apply a Dynamic Configuration, see:
|
|||||||
|
|
||||||
- Open AppxManifest.xml and locate the following:
|
- Open AppxManifest.xml and locate the following:
|
||||||
|
|
||||||
```
|
```xml
|
||||||
<appv:Extension Category="AppV.Fonts">
|
<appv:Extension Category="AppV.Fonts">
|
||||||
<appv:Fonts>
|
<appv:Fonts>
|
||||||
<appv:Font Path="[{Fonts}]\private\CalibriL.ttf" DelayLoad="true"></appv:Font>
|
<appv:Font Path="[{Fonts}]\private\CalibriL.ttf" DelayLoad="true"></appv:Font>
|
||||||
</appv:Fonts>
|
</appv:Fonts>
|
||||||
```
|
```
|
||||||
|
|
||||||
**Note** If there are fonts marked as **DelayLoad**, those will not impact first launch.
|
> [!Note]
|
||||||
|
> If there are fonts marked as **DelayLoad**, those will not impact first launch.
|
||||||
|
|
||||||
### Excluding virtual fonts from the package
|
### Excluding virtual fonts from the package
|
||||||
|
|
||||||
@ -699,7 +468,7 @@ Use the dynamic configuration file that best suits the user scope – deployment
|
|||||||
|
|
||||||
Fonts
|
Fonts
|
||||||
|
|
||||||
```
|
```xml
|
||||||
-->
|
-->
|
||||||
<Fonts Enabled="false" />
|
<Fonts Enabled="false" />
|
||||||
<!--
|
<!--
|
||||||
|
@ -54,56 +54,35 @@ Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages glo
|
|||||||
|
|
||||||
1. Using the information in the following table, create a new registry key using the name of the executable file, for example, **MyApp.exe**.
|
1. Using the information in the following table, create a new registry key using the name of the executable file, for example, **MyApp.exe**.
|
||||||
|
|
||||||
<table>
|
- **Published globally**: Create the `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual` registry key.
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Package publishing method</th>
|
|
||||||
<th align="left">Where to create the registry key</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Published globally</p></td>
|
|
||||||
<td align="left"><p>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual</p>
|
|
||||||
<p><strong>Example</strong>: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Published to the user</p></td>
|
|
||||||
<td align="left"><p>HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual</p>
|
|
||||||
<p><strong>Example</strong>: HKEY_CURRENT_USER \SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Connection group can contain:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Packages that are published just globally or just to the user</p></li>
|
|
||||||
<li><p>Packages that are published globally and to the user</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p>Either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER key, but all of the following must be true:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>If you want to include multiple packages in the virtual environment, you must include them in an enabled connection group.</p></li>
|
|
||||||
<li><p>Create only one subkey for one of the packages in the connection group. If, for example, you have one package that is published globally, and another package that is published to the user, you create a subkey for either of these packages, but not both. Although you create a subkey for only one of the packages, all of the packages in the connection group, plus the local application, will be available in the virtual environment.</p></li>
|
|
||||||
<li><p>The key under which you create the subkey must match the publishing method you used for the package.</p>
|
|
||||||
<p>For example, if you published the package to the user, you must create the subkey under <code>HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual</code>. Do not add a key for the same application under both hives.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
For example, create `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe`.
|
||||||
|
|
||||||
|
- **Published to the user**: Create the `HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual` registry key.
|
||||||
|
|
||||||
|
For example, create `HKEY_CURRENT_USER \SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe`.
|
||||||
|
|
||||||
|
- Connection group can be:
|
||||||
|
- Packages that are published just globally or just to the user
|
||||||
|
- Packages that are published globally and to the user
|
||||||
|
|
||||||
|
Use the `HKEY_LOCAL_MACHINE` or `HKEY_CURRENT_USER` key. But, all of the following must be true:
|
||||||
|
|
||||||
|
- If you want to include multiple packages in the virtual environment, you must include them in an enabled connection group.
|
||||||
|
- Create only one subkey for one of the packages in the connection group. If, for example, you have one package that is published globally, and another package that is published to the user, you create a subkey for either of these packages, but not both. Although you create a subkey for only one of the packages, all of the packages in the connection group, plus the local application, will be available in the virtual environment.
|
||||||
|
- The key under which you create the subkey must match the publishing method you used for the package.
|
||||||
|
|
||||||
|
For example, if you published the package to the user, you must create the subkey under `HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual`. Do not add a key for the same application under both hives.
|
||||||
|
|
||||||
2. Set the new registry subkey’s value to the PackageId and VersionId of the package, separating the values with an underscore.
|
2. Set the new registry subkey’s value to the PackageId and VersionId of the package, separating the values with an underscore.
|
||||||
|
|
||||||
**Syntax**: <PackageId>\_<VersionId>
|
**Syntax**: `<PackageId>_<VersionId>`
|
||||||
|
|
||||||
**Example**: 4c909996-afc9-4352-b606-0b74542a09c1\_be463724-Oct1-48f1-8604-c4bd7ca92fa
|
**Example**: 4c909996-afc9-4352-b606-0b74542a09c1\_be463724-Oct1-48f1-8604-c4bd7ca92fa
|
||||||
|
|
||||||
The application in the previous example would produce a registry export file (.reg file) like the following:
|
The application in the previous example would produce a registry export file (.reg file) like the following:
|
||||||
|
|
||||||
``` syntax
|
```registry
|
||||||
Windows Registry Editor Version 5.00
|
Windows Registry Editor Version 5.00
|
||||||
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual]
|
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual]
|
||||||
@=""
|
@=""
|
||||||
@ -116,24 +95,24 @@ Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages glo
|
|||||||
|
|
||||||
You can use the **Start-AppVVirtualProcess** cmdlet to retrieve the package name and then start a process within the specified package's virtual environment. This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
|
You can use the **Start-AppVVirtualProcess** cmdlet to retrieve the package name and then start a process within the specified package's virtual environment. This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
|
||||||
|
|
||||||
Use the following example syntax, and substitute the name of your package for **<Package>**:
|
Use the following example syntax, and substitute the name of your package for `<Package>`:
|
||||||
|
|
||||||
`$AppVName = Get-AppvClientPackage <Package>`
|
`$AppVName = Get-AppvClientPackage <Package>`
|
||||||
|
|
||||||
`Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe`
|
`Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe`
|
||||||
|
|
||||||
If you don’t know the exact name of your package, you can use the command line <strong>Get-AppvClientPackage \*executable\*</strong>, where **executable** is the name of the application, for example:<br>Get-AppvClientPackage \*Word\*
|
If you don’t know the exact name of your package, you can use the command line `Get-AppvClientPackage YourExecutable`, where `YourExecutable` is the name of the application. For example, enter `Get-AppvClientPackage Word`.
|
||||||
|
|
||||||
## <a href="" id="bkmk-cl-switch-appvpid"></a>Command line switch /appvpid:<PID>
|
## <a href="" id="bkmk-cl-switch-appvpid"></a>Command line switch `/appvpid:<PID>`
|
||||||
|
|
||||||
|
|
||||||
You can apply the **/appvpid:<PID>** switch to any command, which enables that command to run within a virtual process that you select by specifying its process ID (PID). Using this method launches the new executable in the same App-V environment as an executable that is already running.
|
You can apply the `/appvpid:<PID>` switch to any command, which enables that command to run within a virtual process that you select by specifying its process ID (PID). Using this method launches the new executable in the same App-V environment as an executable that is already running.
|
||||||
|
|
||||||
Example: `cmd.exe /appvpid:8108`
|
Example: `cmd.exe /appvpid:8108`
|
||||||
|
|
||||||
To find the process ID (PID) of your App-V process, run the command **tasklist.exe** from an elevated command prompt.
|
To find the process ID (PID) of your App-V process, run the command **tasklist.exe** from an elevated command prompt.
|
||||||
|
|
||||||
## <a href="" id="bkmk-cl-hook-switch-appvve"></a>Command line hook switch /appvve:<GUID>
|
## <a href="" id="bkmk-cl-hook-switch-appvve"></a>Command line hook switch `/appvve:<GUID>`
|
||||||
|
|
||||||
|
|
||||||
This switch lets you run a local command within the virtual environment of an App-V package. Unlike the **/appvid** switch, where the virtual environment must already be running, this switch enables you to start the virtual environment.
|
This switch lets you run a local command within the virtual environment of an App-V package. Unlike the **/appvid** switch, where the virtual environment must already be running, this switch enables you to start the virtual environment.
|
||||||
@ -152,25 +131,11 @@ To get the package GUID and version GUID of your application, run the **Get-Appv
|
|||||||
|
|
||||||
- Version ID of the desired package
|
- Version ID of the desired package
|
||||||
|
|
||||||
If you don’t know the exact name of your package, use the command line <strong>Get-AppvClientPackage \*executable\*</strong>, where **executable** is the name of the application, for example:<br>Get-AppvClientPackage \*Word\*
|
If you don’t know the exact name of your package, use the command line `Get-AppvClientPackage YourExecutable`, where `YourExecutable` is the name of the application. For example, enter `Get-AppvClientPackage Word`.
|
||||||
|
|
||||||
This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
|
This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
|
||||||
[Technical Reference for App-V](appv-technical-reference.md)
|
[Technical Reference for App-V](appv-technical-reference.md)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -42,49 +42,30 @@ You can obtain information about the App-V client or perform specific tasks by u
|
|||||||
|
|
||||||
The client management console contains the following described main tabs.
|
The client management console contains the following described main tabs.
|
||||||
|
|
||||||
<table>
|
- **Overview**: The **Overview** tab contains the following elements:
|
||||||
<colgroup>
|
|
||||||
<col width="20%" />
|
|
||||||
<col width="80%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Tab</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Overview</p></td>
|
|
||||||
<td align="left"><p>The <strong>Overview</strong> tab contains the following elements:</p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Update – Use the <strong>Update</strong> tile to refresh a virtualized application or to receive a new virtualized package.</p>
|
|
||||||
<p>The <strong>Last Refresh</strong> displays the current version of the virtualized package.</p></li>
|
|
||||||
<li><p>Download all virtual applications – Use the <strong>Download</strong> tile to download all of the packages provisioned to the current user.</p>
|
|
||||||
<p>(Associated Windows PowerShell cmdlet: <strong>Mount-AppvClientPackage</strong>)</p>
|
|
||||||
<p></p></li>
|
|
||||||
<li><p>Work Offline – Use this tile to disallow all automatic and manual virtual application updates.</p>
|
|
||||||
<p>(Associated Windows PowerShell cmdlet: <strong>Set-AppvPublishServer –UserRefreshEnabled –GlobalRefreshEnabled</strong>)</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Virtual Apps</p></td>
|
|
||||||
<td align="left"><p>The <strong>VIRTUAL APPS</strong> tab displays all of the packages that have been published to the user. You can also click a specific package and see all of the applications that are part of that package. This displays information about packages that are currently in use and how much of each package has been downloaded to the computer. You can also start and stop package downloads. Additionally, you can repair the user state. A repair will delete all user data that is associated with a package.</p>
|
|
||||||
<p></p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>App Connection Groups</p></td>
|
|
||||||
<td align="left"><p>The <strong>APP CONNECTION GROUPS</strong> tab displays all of the connection groups that are available to the current user. Click a specific connection group to see all of the packages that are part of the selected group. This displays information about connection groups that are already in use and how much of the connection group contents have been downloaded to the computer. Additionally, you can start and stop connection group downloads. You can use this section to initiate a repair. A repair will remove all of the user state that is associated a connection group.</p>
|
|
||||||
<p>(Associated Windows PowerShell cmdlets: Download - <strong>Mount-AppvClientConnectionGroup</strong>. Repair -<strong>AppvClientConnectionGroup</strong>.)</p>
|
|
||||||
<p></p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
- **Update**: Refreshes a virtualized application or to receive a new virtualized package.
|
||||||
|
- **Last Refresh**: Displays the current version of the virtualized package.
|
||||||
|
- **Download all virtual applications**: Use the Download tile to download all of the packages provisioned to the current user.
|
||||||
|
|
||||||
|
Associated Windows PowerShell cmdlet: `Mount-AppvClientPackage`
|
||||||
|
|
||||||
|
- **Work Offline**: Disallows all automatic and manual virtual application updates.
|
||||||
|
|
||||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
Associated Windows PowerShell cmdlet: `-AppvPublishServer –UserRefreshEnabled –GlobalRefreshEnabled`
|
||||||
|
|
||||||
|
- **VIRTUAL APPS**: Displays all of the packages that have been published to the user.
|
||||||
|
|
||||||
|
You can also click a specific package and see all of the applications that are part of that package. This option displays information about packages that are currently in use and how much of each package has been downloaded to the computer. You can also start and stop package downloads, and repair the user state. A repair will delete all user data that is associated with a package.
|
||||||
|
|
||||||
|
- **APP CONNECTION GROUPS**: Displays all of the connection groups that are available to the current user. Click a specific connection group to see all of the packages that are part of the selected group. This displays information about connection groups that are already in use and how much of the connection group contents have been downloaded to the computer. Additionally, you can start and stop connection group downloads. You can use this section to initiate a repair. A repair will remove all of the user state that is associated a connection group.
|
||||||
|
|
||||||
|
Associated Windows PowerShell cmdlets:
|
||||||
|
|
||||||
|
- Download: `Mount-AppvClientConnectionGroup`
|
||||||
|
- Repair: `AppvClientConnectionGroup`
|
||||||
|
|
||||||
|
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
@ -77,84 +77,20 @@ To get the name of the Publishing server and the port number (`http://<PubServer
|
|||||||
|
|
||||||
In your publishing metadata query, enter the string values that correspond to the client operating system that you’re using.
|
In your publishing metadata query, enter the string values that correspond to the client operating system that you’re using.
|
||||||
|
|
||||||
<table>
|
|Operating system|Architecture|String value|
|
||||||
<colgroup>
|
|--- |--- |--- |
|
||||||
<col width="33%" />
|
|Windows 10/11|64-bit|WindowsClient_10.0_x64|
|
||||||
<col width="33%" />
|
|Windows 10/11|32-bit|WindowsClient_10.0_x86|
|
||||||
<col width="33%" />
|
|Windows 8.1|64-bit|WindowsClient_6.2_x64|
|
||||||
</colgroup>
|
|Windows 8.1|32-bit|WindowsClient_6.2_x86|
|
||||||
<thead>
|
|Windows 8|64-bit|WindowsClient_6.2_x64|
|
||||||
<tr class="header">
|
|Windows 8|32-bit|WindowsClient_6.2_x86|
|
||||||
<th align="left">Operating system</th>
|
|Windows Server 2012 R2|64-bit|WindowsServer_6.2_x64|
|
||||||
<th align="left">Architecture</th>
|
|Windows Server 2012 R2|32-bit|WindowsServer_6.2_x86|
|
||||||
<th align="left">String value</th>
|
|Windows Server 2012|64-bit|WindowsServer_6.2_x64|
|
||||||
</tr>
|
|Windows Server 2012|32-bit|WindowsServer_6.2_x86|
|
||||||
</thead>
|
|Windows Server 2008 R2|64-bit|WindowsServer_6.1_x64|
|
||||||
<tbody>
|
|Windows Server 2008 R2|32-bit|WindowsServer_6.1_x86|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Windows 10/11</p></td>
|
|
||||||
<td align="left"><p>64-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsClient_10.0_x64</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Windows 10/11</p></td>
|
|
||||||
<td align="left"><p>32-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsClient_10.0_x86</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Windows 8.1</p></td>
|
|
||||||
<td align="left"><p>64-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsClient_6.2_x64</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Windows 8.1</p></td>
|
|
||||||
<td align="left"><p>32-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsClient_6.2_x86</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Windows 8</p></td>
|
|
||||||
<td align="left"><p>64-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsClient_6.2_x64</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Windows 8</p></td>
|
|
||||||
<td align="left"><p>32-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsClient_6.2_x86</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Windows Server 2012 R2</p></td>
|
|
||||||
<td align="left"><p>64-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsServer_6.2_x64</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Windows Server 2012 R2</p></td>
|
|
||||||
<td align="left"><p>32-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsServer_6.2_x86</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Windows Server 2012</p></td>
|
|
||||||
<td align="left"><p>64-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsServer_6.2_x64</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Windows Server 2012</p></td>
|
|
||||||
<td align="left"><p>32-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsServer_6.2_x86</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Windows Server 2008 R2</p></td>
|
|
||||||
<td align="left"><p>64-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsServer_6.1_x64</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Windows Server 2008 R2</p></td>
|
|
||||||
<td align="left"><p>32-bit</p></td>
|
|
||||||
<td align="left"><p>WindowsServer_6.1_x86</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).
|
||||||
|
@ -60,7 +60,7 @@ Make sure that you install the latest Windows updates, cumulative updates, and r
|
|||||||
|
|
||||||
1. Network Capture with ETW. Enter the following at an elevated command prompt:
|
1. Network Capture with ETW. Enter the following at an elevated command prompt:
|
||||||
|
|
||||||
```
|
```cmd
|
||||||
netsh trace start wireless_dbg capture=yes overwrite=yes maxsize=4096 tracefile=c:\tmp\wireless.etl
|
netsh trace start wireless_dbg capture=yes overwrite=yes maxsize=4096 tracefile=c:\tmp\wireless.etl
|
||||||
```
|
```
|
||||||
2. Reproduce the issue.
|
2. Reproduce the issue.
|
||||||
@ -70,12 +70,12 @@ Make sure that you install the latest Windows updates, cumulative updates, and r
|
|||||||
- If intermittent connection drops trigger stop command on a script (ping or test network constantly until fail, then netsh trace stop).
|
- If intermittent connection drops trigger stop command on a script (ping or test network constantly until fail, then netsh trace stop).
|
||||||
3. Stop the trace by entering the following command:
|
3. Stop the trace by entering the following command:
|
||||||
|
|
||||||
```
|
```cmd
|
||||||
netsh trace stop
|
netsh trace stop
|
||||||
```
|
```
|
||||||
4. To convert the output file to text format:
|
4. To convert the output file to text format:
|
||||||
|
|
||||||
```
|
```cmd
|
||||||
netsh trace convert c:\tmp\wireless.etl
|
netsh trace convert c:\tmp\wireless.etl
|
||||||
```
|
```
|
||||||
|
|
||||||
@ -85,17 +85,13 @@ See the [example ETW capture](#example-etw-capture) at the bottom of this articl
|
|||||||
|
|
||||||
The following is a high-level view of the main wifi components in Windows.
|
The following is a high-level view of the main wifi components in Windows.
|
||||||
|
|
||||||
<table>
|
|Wi-fi Components|Description|
|
||||||
<tr><td><img src="images/wcm.png" alt="Windows Connection Manager"></td><td>The <b>Windows Connection Manager</b> (Wcmsvc) is closely associated with the UI controls (taskbar icon) to connect to various networks, including wireless networks. It accepts and processes input from the user and feeds it to the core wireless service. </td></tr>
|
|--- |--- |
|
||||||
<tr><td><img src="images/wlan.png" alt="WLAN Autoconfig Service"></td><td>The <b>WLAN Autoconfig Service</b> (WlanSvc) handles the following core functions of wireless networks in windows:
|
||The Windows Connection Manager (Wcmsvc) is closely associated with the UI controls (taskbar icon) to connect to various networks, including wireless networks. It accepts and processes input from the user and feeds it to the core wireless service.|
|
||||||
|
||The WLAN Autoconfig Service (WlanSvc) handles the following core functions of wireless networks in windows:<li> Scanning for wireless networks in range<li>Managing connectivity of wireless networks|
|
||||||
- Scanning for wireless networks in range
|
||The Media Specific Module (MSM) handles security aspects of connection being established.|
|
||||||
- Managing connectivity of wireless networks</td></tr>
|
||The Native WiFi stack consists of drivers and wireless APIs to interact with wireless miniports and the supporting user-mode Wlansvc.|
|
||||||
<tr><td><img src="images/msm.png" alt="Media Specific Module"></td><td>The <b>Media Specific Module</b> (MSM) handles security aspects of connection being established.</td></tr>
|
||Third-party wireless miniport drivers interface with the upper wireless stack to provide notifications to and receive commands from Windows.|
|
||||||
<tr><td><img src="images/wifi-stack.png" alt="Native WiFi stack"></td><td>The <b>Native WiFi stack</b> consists of drivers and wireless APIs to interact with wireless miniports and the supporting user-mode Wlansvc.</td></tr>
|
|
||||||
<tr><td><img src="images/miniport.png" alt="Wireless miniport"></td><td>Third-party <b>wireless miniport</b> drivers interface with the upper wireless stack to provide notifications to and receive commands from Windows.</td></tr>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
The wifi connection state machine has the following states:
|
The wifi connection state machine has the following states:
|
||||||
- Reset
|
- Reset
|
||||||
@ -289,7 +285,7 @@ C:\tmp>dir
|
|||||||
|
|
||||||
Copy and paste all the lines below and save them into a text file named "wifi.tat." Load the filter file into the TextAnalysisTool by clicking **File > Load Filters**.
|
Copy and paste all the lines below and save them into a text file named "wifi.tat." Load the filter file into the TextAnalysisTool by clicking **File > Load Filters**.
|
||||||
|
|
||||||
```
|
```xml
|
||||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||||||
<TextAnalysisTool.NET version="2018-01-03" showOnlyFilteredLines="False">
|
<TextAnalysisTool.NET version="2018-01-03" showOnlyFilteredLines="False">
|
||||||
<filters>
|
<filters>
|
||||||
|
@ -18,7 +18,8 @@ ms.date: 11/19/2019
|
|||||||
The AppLocker configuration service provider is used to specify which applications are allowed or disallowed. There is no user interface shown for apps that are blocked.
|
The AppLocker configuration service provider is used to specify which applications are allowed or disallowed. There is no user interface shown for apps that are blocked.
|
||||||
|
|
||||||
The following shows the AppLocker configuration service provider in tree format.
|
The following shows the AppLocker configuration service provider in tree format.
|
||||||
```
|
|
||||||
|
```console
|
||||||
./Vendor/MSFT
|
./Vendor/MSFT
|
||||||
AppLocker
|
AppLocker
|
||||||
----ApplicationLaunchRestrictions
|
----ApplicationLaunchRestrictions
|
||||||
@ -258,54 +259,29 @@ Data type is string.
|
|||||||
|
|
||||||
Supported operations are Get, Add, Delete, and Replace.
|
Supported operations are Get, Add, Delete, and Replace.
|
||||||
|
|
||||||
6. On your phone under **Device discovery**, tap **Pair**. You will get a code (case sensitive).
|
1. On your phone under **Device discovery**, tap **Pair**. You will get a code (case sensitive).
|
||||||
7. On the browser on the **Set up access page**, enter the code (case sensitive) into the text box and click **Submit**.
|
2. On the browser on the **Set up access page**, enter the code (case sensitive) into the text box and click **Submit**.
|
||||||
|
|
||||||
The **Device Portal** page opens on your browser.
|
The **Device Portal** page opens on your browser.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
8. On the desktop **Device Portal** page, click **Apps** to open the **App Manager**.
|
3. On the desktop **Device Portal** page, click **Apps** to open the **App Manager**.
|
||||||
9. On the **App Manager** page under **Running apps**, you will see the **Publisher** and **PackageFullName** of apps.
|
4. On the **App Manager** page under **Running apps**, you will see the **Publisher** and **PackageFullName** of apps.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
10. If you do not see the app that you want, look under **Installed apps**. Using the drop- down menu, click on the application and you get the Version, Publisher, and PackageFullName displayed.
|
5. If you do not see the app that you want, look under **Installed apps**. Using the drop- down menu, click on the application and you get the Version, Publisher, and PackageFullName displayed.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
The following table shows the mapping of information to the AppLocker publisher rule field.
|
The following table shows the mapping of information to the AppLocker publisher rule field.
|
||||||
|
|
||||||
<table>
|
|Device portal data|AppLocker publisher rule field|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|PackageFullName|ProductName<br><br> The product name is first part of the PackageFullName followed by the version number. In the Windows Camera example, the ProductName is Microsoft.WindowsCamera.|
|
||||||
<col width="80%" />
|
|Publisher|Publisher|
|
||||||
</colgroup>
|
|Version|Version<br> <br>This can be used either in the HighSection or LowSection of the BinaryVersionRange.<br> <br>HighSection defines the highest version number and LowSection defines the lowest version number that should be trusted. You can use a wildcard for both versions to make a version- independent rule. Using a wildcard for one of the values will provide higher than or lower than a specific version semantics.|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Device portal data</th>
|
|
||||||
<th>AppLocker publisher rule field</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>PackageFullName</p></td>
|
|
||||||
<td><p>ProductName</p>
|
|
||||||
<p>The product name is first part of the PackageFullName followed by the version number. In the Windows Camera example, the ProductName is Microsoft.WindowsCamera.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Publisher</p></td>
|
|
||||||
<td><p>Publisher</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Version</p></td>
|
|
||||||
<td><p>Version</p>
|
|
||||||
<p>This can be used either in the HighSection or LowSection of the BinaryVersionRange.</p>
|
|
||||||
<p>HighSection defines the highest version number and LowSection defines the lowest version number that should be trusted. You can use a wildcard for both versions to make a version- independent rule. Using a wildcard for one of the values will provide higher than or lower than a specific version semantics.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
Here is an example AppLocker publisher rule:
|
Here is an example AppLocker publisher rule:
|
||||||
|
|
||||||
@ -325,21 +301,11 @@ You can get the publisher name and product name of apps using a web API.
|
|||||||
|
|
||||||
3. In your browser, run the Store for Business portal web API, to return a JavaScript Object Notation (JSON) file that includes the publisher and product name values.
|
3. In your browser, run the Store for Business portal web API, to return a JavaScript Object Notation (JSON) file that includes the publisher and product name values.
|
||||||
|
|
||||||
<table>
|
Request URI:
|
||||||
<colgroup>
|
|
||||||
<col width="100%" />
|
```http
|
||||||
</colgroup>
|
https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/{app ID}/applockerdata
|
||||||
<thead>
|
```
|
||||||
<tr class="header">
|
|
||||||
<th>Request URI</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><code>https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/{app ID}/applockerdata</code></p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
Here is the example for Microsoft OneNote:
|
Here is the example for Microsoft OneNote:
|
||||||
|
|
||||||
@ -360,35 +326,11 @@ Result
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
<table>
|
|Result data|AppLocker publisher rule field|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|packageIdentityName|ProductName|
|
||||||
<col width="80%" />
|
|publisherCertificateName|Publisher|
|
||||||
</colgroup>
|
|windowsPhoneLegacyId|Same value maps to the ProductName and Publisher name. <br> <br> This value will only be present if there is a XAP package associated with the app in the Store. <br> <br>If this value is populated then the simple thing to do to cover both the AppX and XAP package would be to create two rules for the app. One rule for AppX using the packageIdentityName and publisherCertificateName value and another one using the windowsPhoneLegacyId value.|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Result data</th>
|
|
||||||
<th>AppLocker publisher rule field</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>packageIdentityName</p></td>
|
|
||||||
<td><p>ProductName</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>publisherCertificateName</p></td>
|
|
||||||
<td><p>Publisher</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>windowsPhoneLegacyId</p></td>
|
|
||||||
<td><p>Same value maps to the ProductName and Publisher name</p>
|
|
||||||
<p>This value will only be present if there is a XAP package associated with the app in the Store.</p>
|
|
||||||
<p>If this value is populated then the simple thing to do to cover both the AppX and XAP package would be to create two rules for the app. One rule for AppX using the packageIdentityName and publisherCertificateName value and another one using the windowsPhoneLegacyId value.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## <a href="" id="settingssplashapps"></a>Settings apps that rely on splash apps
|
## <a href="" id="settingssplashapps"></a>Settings apps that rely on splash apps
|
||||||
@ -428,464 +370,96 @@ The following list shows the apps that may be included in the inbox.
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|App|Product ID|Product name|
|
||||||
<colgroup>
|
|--- |--- |--- |
|
||||||
<col width="33%" />
|
|3D Viewer|f41647c9-d567-4378-b2ab-7924e5a152f3|Microsoft.Microsoft3DViewer (Added in Windows 10, version 1703)|
|
||||||
<col width="33%" />
|
|Advanced info|b6e3e590-9fa5-40c0-86ac-ef475de98e88|b6e3e590-9fa5-40c0-86ac-ef475de98e88|
|
||||||
<col width="33%" />
|
|Age out worker|09296e27-c9f3-4ab9-aa76-ecc4497d94bb||
|
||||||
</colgroup>
|
|Alarms and clock|44f7d2b4-553d-4bec-a8b7-634ce897ed5f|Microsoft.WindowsAlarms|
|
||||||
<thead>
|
|App downloads|20bf77a0-19c7-4daa-8db5-bc3dfdfa44ac||
|
||||||
<tr class="header">
|
|Assigned access lock app|b84f4722-313e-4f85-8f41-cf5417c9c5cb||
|
||||||
<th>App</th>
|
|Bing lock images|5f28c179-2780-41df-b966-27807b8de02c||
|
||||||
<th>Product ID</th>
|
|Block and filter|59553c14-5701-49a2-9909-264d034deb3d||
|
||||||
<th>Product name</th>
|
|Broker plug-in (same as Work or school account)||Microsoft.AAD.BrokerPlugin|
|
||||||
</tr>
|
|Calculator|b58171c6-c70c-4266-a2e8-8f9c994f4456|Microsoft.WindowsCalculator|
|
||||||
</thead>
|
|Camera|f0d8fefd-31cd-43a1-a45a-d0276db069f1|Microsoft.WindowsCamera|
|
||||||
<tbody>
|
|CertInstaller|4c4ad968-7100-49de-8cd1-402e198d869e||
|
||||||
<tr class="even">
|
|Color profile|b08997ca-60ab-4dce-b088-f92e9c7994f3||
|
||||||
<td>3D Viewer</td>
|
|Connect|af7d2801-56c0-4eb1-824b-dd91cdf7ece5|Microsoft.DevicesFlow|
|
||||||
<td>f41647c9-d567-4378-b2ab-7924e5a152f3</td>
|
|Contact Support|0db5fcff-4544-458a-b320-e352dfd9ca2b|Windows.ContactSupport|
|
||||||
<td>Microsoft.Microsoft3DViewer <p>(Added in Windows 10, version 1703)</p></td>
|
|Cortana|fd68dcf4-166f-4c55-a4ca-348020f71b94|Microsoft.Windows.Cortana|
|
||||||
</tr>
|
|Cortana Listen UI||CortanaListenUI|
|
||||||
<tr class="odd">
|
|Credentials Dialog Host||Microsoft.CredDialogHost|
|
||||||
<td>Advanced info</td>
|
|Device Portal PIN UX||holopairingapp|
|
||||||
<td>b6e3e590-9fa5-40c0-86ac-ef475de98e88</td>
|
|Email and accounts|39cf127b-8c67-c149-539a-c02271d07060|Microsoft.AccountsControl|
|
||||||
<td>b6e3e590-9fa5-40c0-86ac-ef475de98e88</td>
|
|Enterprise installs app|da52fa01-ac0f-479d-957f-bfe4595941cb||
|
||||||
</tr>
|
|Equalizer|373cb76e-7f6c-45aa-8633-b00e85c73261||
|
||||||
<tr class="even">
|
|Excel|ead3e7c0-fae6-4603-8699-6a448138f4dc|Microsoft.Office.Excel|
|
||||||
<td>Age out worker</td>
|
|Facebook|82a23635-5bd9-df11-a844-00237de2db9e|Microsoft.MSFacebook|
|
||||||
<td>09296e27-c9f3-4ab9-aa76-ecc4497d94bb</td>
|
|Field Medic|73c58570-d5a7-46f8-b1b2-2a90024fc29c||
|
||||||
<td></td>
|
|File Explorer|c5e2524a-ea46-4f67-841f-6a9465d9d515|c5e2524a-ea46-4f67-841f-6a9465d9d515|
|
||||||
</tr>
|
|FM Radio|f725010e-455d-4c09-ac48-bcdef0d4b626|f725010e-455d-4c09-ac48-bcdef0d4b626|
|
||||||
<tr class="odd">
|
|Get Started|b3726308-3d74-4a14-a84c-867c8c735c3c|Microsoft.Getstarted|
|
||||||
<td>Alarms and clock</td>
|
|Glance|106e0a97-8b19-42cf-8879-a8ed2598fcbb||
|
||||||
<td>44f7d2b4-553d-4bec-a8b7-634ce897ed5f</td>
|
|Groove Music|d2b6a184-da39-4c9a-9e0a-8b589b03dec0|Microsoft.ZuneMusic|
|
||||||
<td>Microsoft.WindowsAlarms</td>
|
|Hands-Free Activation|df6c9621-e873-4e86-bb56-93e9f21b1d6f||
|
||||||
</tr>
|
|Hands-Free Activation|72803bd5-4f36-41a4-a349-e83e027c4722||
|
||||||
<tr class="even">
|
|HAP update background worker|73c73cdd-4dea-462c-bd83-fa983056a4ef||
|
||||||
<td>App downloads</td>
|
|Holographic Shell||HoloShell|
|
||||||
<td>20bf77a0-19c7-4daa-8db5-bc3dfdfa44ac</td>
|
|Lumia motion data|8fc25fd2-4e2e-4873-be44-20e57f6ec52b||
|
||||||
<td></td>
|
|Maps|ed27a07e-af57-416b-bc0c-2596b622ef7d|Microsoft.WindowsMaps|
|
||||||
</tr>
|
|Messaging|27e26f40-e031-48a6-b130-d1f20388991a|Microsoft.Messaging|
|
||||||
<tr class="odd">
|
|Microsoft account|3a4fae89-7b7e-44b4-867b-f7e2772b8253|Microsoft.CloudExperienceHost|
|
||||||
<td>Assigned access lock app</td>
|
|Microsoft Edge|395589fb-5884-4709-b9df-f7d558663ffd|Microsoft.MicrosoftEdge|
|
||||||
<td>b84f4722-313e-4f85-8f41-cf5417c9c5cb</td>
|
|Microsoft Frameworks|ProductID = 00000000-0000-0000-0000-000000000000 PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"||
|
||||||
<td></td>
|
|Migration UI||MigrationUIApp|
|
||||||
</tr>
|
|MiracastView|906beeda-b7e6-4ddc-ba8d-ad5031223ef9|906beeda-b7e6-4ddc-ba8d-ad5031223ef9|
|
||||||
<tr class="even">
|
|Mixed Reality Portal||Microsoft.Windows.HolographicFirstRun|
|
||||||
<td>Bing lock images</td>
|
|Money|1e0440f1-7abf-4b9a-863d-177970eefb5e|Microsoft.BingFinance|
|
||||||
<td>5f28c179-2780-41df-b966-27807b8de02c</td>
|
|Movies and TV|6affe59e-0467-4701-851f-7ac026e21665|Microsoft.ZuneVideo|
|
||||||
<td></td>
|
|Music downloads|3da8a0c1-f7e5-47c0-a680-be8fd013f747||
|
||||||
</tr>
|
|Navigation bar|2cd23676-8f68-4d07-8dd2-e693d4b01279||
|
||||||
<tr class="odd">
|
|Network services|62f172d1-f552-4749-871c-2afd1c95c245||
|
||||||
<td>Block and filter</td>
|
|News|9c3e8cad-6702-4842-8f61-b8b33cc9caf1|Microsoft.BingNews|
|
||||||
<td>59553c14-5701-49a2-9909-264d034deb3d</td>
|
|OneDrive|ad543082-80ec-45bb-aa02-ffe7f4182ba8|Microsoft.MicrosoftSkydrive|
|
||||||
<td></td>
|
|OneNote|ca05b3ab-f157-450c-8c49-a1f127f5e71d|Microsoft.Office.OneNote|
|
||||||
</tr>
|
|Outlook Calendar and Mail|a558feba-85d7-4665-b5d8-a2ff9c19799b|Microsoft.WindowsCommunicationsApps|
|
||||||
<tr class="odd">
|
|People|60be1fb8-3291-4b21-bd39-2221ab166481|Microsoft.People|
|
||||||
<td>Broker plug-in (same as Work or school account)</td>
|
|Phone|5b04b775-356b-4aa0-aaf8-6491ffea5611|5b04b775-356b-4aa0-aaf8-6491ffea5611|
|
||||||
<td></td>
|
|Phone (dialer)|f41b5d0e-ee94-4f47-9cfe-3d3934c5a2c7|Microsoft.CommsPhone|
|
||||||
<td>Microsoft.AAD.BrokerPlugin</td>
|
|Phone reset dialog|2864278d-09b5-46f7-b502-1c24139ecbdd||
|
||||||
</tr>
|
|Photos|fca55e1b-b9a4-4289-882f-084ef4145005|Microsoft.Windows.Photos|
|
||||||
<tr class="even">
|
|Podcasts|c3215724-b279-4206-8c3e-61d1a9d63ed3|Microsoft.MSPodcast|
|
||||||
<td>Calculator</td>
|
|Podcast downloads|063773e7-f26f-4a92-81f0-aa71a1161e30||
|
||||||
<td>b58171c6-c70c-4266-a2e8-8f9c994f4456</td>
|
|PowerPoint|b50483c4-8046-4e1b-81ba-590b24935798|Microsoft.Office.PowerPoint|
|
||||||
<td>Microsoft.WindowsCalculator</td>
|
|PrintDialog|0d32eeb1-32f0-40da-8558-cea6fcbec4a4|Microsoft.PrintDialog|
|
||||||
</tr>
|
|Purchase dialog|c60e79ca-063b-4e5d-9177-1309357b2c3f||
|
||||||
<tr class="odd">
|
|Rate your device|aec3bfad-e38c-4994-9c32-50bd030730ec||
|
||||||
<td>Camera</td>
|
|RingtoneApp.WindowsPhone|3e962450-486b-406b-abb5-d38b4ee7e6fe|Microsoft.Tonepicker|
|
||||||
<td>f0d8fefd-31cd-43a1-a45a-d0276db069f1</td>
|
|Save ringtone|d8cf8ec7-ec6d-4892-aab9-1e3a4b5fa24b||
|
||||||
<td>Microsoft.WindowsCamera</td>
|
|Settings|2a4e62d8-8809-4787-89f8-69d0f01654fb|2a4e62d8-8809-4787-89f8-69d0f01654fb|
|
||||||
</tr>
|
|Settings||SystemSettings|
|
||||||
<tr class="even">
|
|Setup wizard|07d87655-e4f0-474b-895a-773790ad4a32||
|
||||||
<td>CertInstaller</td>
|
|Sharing|b0894dfd-4671-4bb9-bc17-a8b39947ffb6||
|
||||||
<td>4c4ad968-7100-49de-8cd1-402e198d869e</td>
|
|Sign in for Windows 10 Holographic||WebAuthBridgeInternetSso, WebAuthBridgeInternet, WebAuthBridgeIntranetSso, WebAuthBrokerInternetSso, WebAuthBrokerInternetSso, WebAuthBrokerInternetSso, WebAuthBrokerInternet, WebAuthBrokerIntranetSso, SignIn|
|
||||||
<td></td>
|
|Skype|c3f8e570-68b3-4d6a-bdbb-c0a3f4360a51|Microsoft.SkypeApp|
|
||||||
</tr>
|
|Skype Video|27e26f40-e031-48a6-b130-d1f20388991a|Microsoft.Messaging|
|
||||||
<tr class="odd">
|
|Sports|0f4c8c7e-7114-4e1e-a84c-50664db13b17|Microsoft.BingSports|
|
||||||
<td>Color profile</td>
|
|SSMHost|e232aa77-2b6d-442c-b0c3-f3bb9788af2a||
|
||||||
<td>b08997ca-60ab-4dce-b088-f92e9c7994f3</td>
|
|Start|5b04b775-356b-4aa0-aaf8-6491ffea5602|5b04b775-356b-4aa0-aaf8-6491ffea5602|
|
||||||
<td></td>
|
|Storage|5b04b775-356b-4aa0-aaf8-6491ffea564d|5b04b775-356b-4aa0-aaf8-6491ffea564d|
|
||||||
</tr>
|
|Store|7d47d89a-7900-47c5-93f2-46eb6d94c159|Microsoft.WindowsStore|
|
||||||
<tr class="even">
|
|Touch (gestures and touch)|bbc57c87-46af-4c2c-824e-ac8104cceb38||
|
||||||
<td>Connect</td>
|
|Voice recorder|7311b9c5-a4e9-4c74-bc3c-55b06ba95ad0|Microsoft.WindowsSoundRecorder|
|
||||||
<td>af7d2801-56c0-4eb1-824b-dd91cdf7ece5</td>
|
|Wallet|587a4577-7868-4745-a29e-f996203f1462|Microsoft.MicrosoftWallet|
|
||||||
<td>Microsoft.DevicesFlow</td>
|
|Wallet|12ae577e-f8d1-4197-a207-4d24c309ff8f|Microsoft.Wallet|
|
||||||
</tr>
|
|Weather|63c2a117-8604-44e7-8cef-df10be3a57c8|Microsoft.BingWeather|
|
||||||
<tr class="odd">
|
|Windows default lock screen|cdd63e31-9307-4ccb-ab62-1ffa5721b503||
|
||||||
<td>Contact Support</td>
|
|Windows Feedback|7604089d-d13f-4a2d-9998-33fc02b63ce3|Microsoft.WindowsFeedback|
|
||||||
<td>0db5fcff-4544-458a-b320-e352dfd9ca2b</td>
|
|Word|258f115c-48f4-4adb-9a68-1387e634459b|Microsoft.Office.Word|
|
||||||
<td>Windows.ContactSupport</td>
|
|Work or school account|e5f8b2c4-75ae-45ee-9be8-212e34f77747|Microsoft.AAD.BrokerPlugin|
|
||||||
</tr>
|
|Xbox|b806836f-eebe-41c9-8669-19e243b81b83|Microsoft.XboxApp|
|
||||||
<tr class="even">
|
|Xbox identity provider|ba88225b-059a-45a2-a8eb-d3580283e49d|Microsoft.XboxIdentityProvider|
|
||||||
<td>Cortana</td>
|
|
||||||
<td>fd68dcf4-166f-4c55-a4ca-348020f71b94</td>
|
|
||||||
<td>Microsoft.Windows.Cortana</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Cortana Listen UI</td>
|
|
||||||
<td></td>
|
|
||||||
<td>CortanaListenUI</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Credentials Dialog Host</td>
|
|
||||||
<td></td>
|
|
||||||
<td>Microsoft.CredDialogHost</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Device Portal PIN UX</td>
|
|
||||||
<td></td>
|
|
||||||
<td>holopairingapp</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Email and accounts</td>
|
|
||||||
<td>39cf127b-8c67-c149-539a-c02271d07060</td>
|
|
||||||
<td>Microsoft.AccountsControl</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Enterprise installs app</td>
|
|
||||||
<td>da52fa01-ac0f-479d-957f-bfe4595941cb</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Equalizer</td>
|
|
||||||
<td>373cb76e-7f6c-45aa-8633-b00e85c73261</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Excel</td>
|
|
||||||
<td>ead3e7c0-fae6-4603-8699-6a448138f4dc</td>
|
|
||||||
<td>Microsoft.Office.Excel</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Facebook</td>
|
|
||||||
<td>82a23635-5bd9-df11-a844-00237de2db9e</td>
|
|
||||||
<td>Microsoft.MSFacebook</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Field Medic</td>
|
|
||||||
<td>73c58570-d5a7-46f8-b1b2-2a90024fc29c</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>File Explorer</td>
|
|
||||||
<td>c5e2524a-ea46-4f67-841f-6a9465d9d515</td>
|
|
||||||
<td>c5e2524a-ea46-4f67-841f-6a9465d9d515</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>FM Radio</td>
|
|
||||||
<td>f725010e-455d-4c09-ac48-bcdef0d4b626</td>
|
|
||||||
<td>f725010e-455d-4c09-ac48-bcdef0d4b626</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Get Started</td>
|
|
||||||
<td>b3726308-3d74-4a14-a84c-867c8c735c3c</td>
|
|
||||||
<td>Microsoft.Getstarted</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Glance</td>
|
|
||||||
<td>106e0a97-8b19-42cf-8879-a8ed2598fcbb</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Groove Music</td>
|
|
||||||
<td>d2b6a184-da39-4c9a-9e0a-8b589b03dec0</td>
|
|
||||||
<td>Microsoft.ZuneMusic</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Hands-Free Activation</td>
|
|
||||||
<td>df6c9621-e873-4e86-bb56-93e9f21b1d6f</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Hands-Free Activation</td>
|
|
||||||
<td>72803bd5-4f36-41a4-a349-e83e027c4722</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>HAP update background worker</td>
|
|
||||||
<td>73c73cdd-4dea-462c-bd83-fa983056a4ef</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Holographic Shell</td>
|
|
||||||
<td></td>
|
|
||||||
<td>HoloShell</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Lumia motion data</td>
|
|
||||||
<td>8fc25fd2-4e2e-4873-be44-20e57f6ec52b</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Maps</td>
|
|
||||||
<td>ed27a07e-af57-416b-bc0c-2596b622ef7d</td>
|
|
||||||
<td>Microsoft.WindowsMaps</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Messaging</td>
|
|
||||||
<td>27e26f40-e031-48a6-b130-d1f20388991a</td>
|
|
||||||
<td>Microsoft.Messaging</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Microsoft account</td>
|
|
||||||
<td>3a4fae89-7b7e-44b4-867b-f7e2772b8253</td>
|
|
||||||
<td>Microsoft.CloudExperienceHost</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Microsoft Edge</td>
|
|
||||||
<td>395589fb-5884-4709-b9df-f7d558663ffd</td>
|
|
||||||
<td>Microsoft.MicrosoftEdge</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Microsoft Frameworks</td>
|
|
||||||
<td>ProductID = 00000000-0000-0000-0000-000000000000
|
|
||||||
<p>PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"</p></td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Migration UI</td>
|
|
||||||
<td></td>
|
|
||||||
<td>MigrationUIApp</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>MiracastView</td>
|
|
||||||
<td>906beeda-b7e6-4ddc-ba8d-ad5031223ef9</td>
|
|
||||||
<td>906beeda-b7e6-4ddc-ba8d-ad5031223ef9</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Mixed Reality Portal</td>
|
|
||||||
<td></td>
|
|
||||||
<td>Microsoft.Windows.HolographicFirstRun</td>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Money</td>
|
|
||||||
<td>1e0440f1-7abf-4b9a-863d-177970eefb5e</td>
|
|
||||||
<td>Microsoft.BingFinance</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Movies and TV</td>
|
|
||||||
<td>6affe59e-0467-4701-851f-7ac026e21665</td>
|
|
||||||
<td>Microsoft.ZuneVideo</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Music downloads</td>
|
|
||||||
<td>3da8a0c1-f7e5-47c0-a680-be8fd013f747</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Navigation bar</td>
|
|
||||||
<td>2cd23676-8f68-4d07-8dd2-e693d4b01279</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Network services</td>
|
|
||||||
<td>62f172d1-f552-4749-871c-2afd1c95c245</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>News</td>
|
|
||||||
<td>9c3e8cad-6702-4842-8f61-b8b33cc9caf1</td>
|
|
||||||
<td>Microsoft.BingNews</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>OneDrive</td>
|
|
||||||
<td>ad543082-80ec-45bb-aa02-ffe7f4182ba8</td>
|
|
||||||
<td>Microsoft.MicrosoftSkydrive</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>OneNote</td>
|
|
||||||
<td>ca05b3ab-f157-450c-8c49-a1f127f5e71d</td>
|
|
||||||
<td>Microsoft.Office.OneNote</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Outlook Calendar and Mail</td>
|
|
||||||
<td>a558feba-85d7-4665-b5d8-a2ff9c19799b</td>
|
|
||||||
<td>Microsoft.WindowsCommunicationsApps</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>People</td>
|
|
||||||
<td>60be1fb8-3291-4b21-bd39-2221ab166481</td>
|
|
||||||
<td>Microsoft.People</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Phone</td>
|
|
||||||
<td>5b04b775-356b-4aa0-aaf8-6491ffea5611</td>
|
|
||||||
<td>5b04b775-356b-4aa0-aaf8-6491ffea5611</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Phone (dialer)</td>
|
|
||||||
<td>f41b5d0e-ee94-4f47-9cfe-3d3934c5a2c7</td>
|
|
||||||
<td>Microsoft.CommsPhone</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Phone reset dialog</td>
|
|
||||||
<td>2864278d-09b5-46f7-b502-1c24139ecbdd</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Photos</td>
|
|
||||||
<td>fca55e1b-b9a4-4289-882f-084ef4145005</td>
|
|
||||||
<td>Microsoft.Windows.Photos</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Podcasts</td>
|
|
||||||
<td>c3215724-b279-4206-8c3e-61d1a9d63ed3</td>
|
|
||||||
<td>Microsoft.MSPodcast</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Podcast downloads</td>
|
|
||||||
<td>063773e7-f26f-4a92-81f0-aa71a1161e30</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>PowerPoint</td>
|
|
||||||
<td>b50483c4-8046-4e1b-81ba-590b24935798</td>
|
|
||||||
<td>Microsoft.Office.PowerPoint</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>PrintDialog</td>
|
|
||||||
<td>0d32eeb1-32f0-40da-8558-cea6fcbec4a4</td>
|
|
||||||
<td>Microsoft.PrintDialog</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Purchase dialog</td>
|
|
||||||
<td>c60e79ca-063b-4e5d-9177-1309357b2c3f</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Rate your device</td>
|
|
||||||
<td>aec3bfad-e38c-4994-9c32-50bd030730ec</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>RingtoneApp.WindowsPhone</td>
|
|
||||||
<td>3e962450-486b-406b-abb5-d38b4ee7e6fe</td>
|
|
||||||
<td>Microsoft.Tonepicker</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Save ringtone</td>
|
|
||||||
<td>d8cf8ec7-ec6d-4892-aab9-1e3a4b5fa24b</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Settings</td>
|
|
||||||
<td>2a4e62d8-8809-4787-89f8-69d0f01654fb</td>
|
|
||||||
<td>2a4e62d8-8809-4787-89f8-69d0f01654fb</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Settings</td>
|
|
||||||
<td></td>
|
|
||||||
<td>SystemSettings</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Setup wizard</td>
|
|
||||||
<td>07d87655-e4f0-474b-895a-773790ad4a32</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Sharing</td>
|
|
||||||
<td>b0894dfd-4671-4bb9-bc17-a8b39947ffb6</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Sign in for Windows 10 Holographic</td>
|
|
||||||
<td></td>
|
|
||||||
<td>WebAuthBridgeInternetSso, WebAuthBridgeInternet, WebAuthBridgeIntranetSso, WebAuthBrokerInternetSso, WebAuthBrokerInternetSso, WebAuthBrokerInternetSso, WebAuthBrokerInternet, WebAuthBrokerIntranetSso, SignIn</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Skype</td>
|
|
||||||
<td>c3f8e570-68b3-4d6a-bdbb-c0a3f4360a51</td>
|
|
||||||
<td>Microsoft.SkypeApp</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Skype Video</td>
|
|
||||||
<td>27e26f40-e031-48a6-b130-d1f20388991a</td>
|
|
||||||
<td>Microsoft.Messaging</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Sports</td>
|
|
||||||
<td>0f4c8c7e-7114-4e1e-a84c-50664db13b17</td>
|
|
||||||
<td>Microsoft.BingSports</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>SSMHost</td>
|
|
||||||
<td>e232aa77-2b6d-442c-b0c3-f3bb9788af2a</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Start</td>
|
|
||||||
<td>5b04b775-356b-4aa0-aaf8-6491ffea5602</td>
|
|
||||||
<td>5b04b775-356b-4aa0-aaf8-6491ffea5602</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Storage</td>
|
|
||||||
<td>5b04b775-356b-4aa0-aaf8-6491ffea564d</td>
|
|
||||||
<td>5b04b775-356b-4aa0-aaf8-6491ffea564d</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Store</td>
|
|
||||||
<td>7d47d89a-7900-47c5-93f2-46eb6d94c159</td>
|
|
||||||
<td>Microsoft.WindowsStore</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Touch (gestures and touch)</td>
|
|
||||||
<td>bbc57c87-46af-4c2c-824e-ac8104cceb38</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Voice recorder</td>
|
|
||||||
<td>7311b9c5-a4e9-4c74-bc3c-55b06ba95ad0</td>
|
|
||||||
<td>Microsoft.WindowsSoundRecorder</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Wallet</td>
|
|
||||||
<td>587a4577-7868-4745-a29e-f996203f1462</td>
|
|
||||||
<td>Microsoft.MicrosoftWallet</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Wallet</td>
|
|
||||||
<td>12ae577e-f8d1-4197-a207-4d24c309ff8f</td>
|
|
||||||
<td>Microsoft.Wallet</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Weather</td>
|
|
||||||
<td>63c2a117-8604-44e7-8cef-df10be3a57c8</td>
|
|
||||||
<td>Microsoft.BingWeather</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Windows default lock screen</td>
|
|
||||||
<td>cdd63e31-9307-4ccb-ab62-1ffa5721b503</td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Windows Feedback</td>
|
|
||||||
<td>7604089d-d13f-4a2d-9998-33fc02b63ce3</td>
|
|
||||||
<td>Microsoft.WindowsFeedback</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Word</td>
|
|
||||||
<td>258f115c-48f4-4adb-9a68-1387e634459b</td>
|
|
||||||
<td>Microsoft.Office.Word</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Work or school account</td>
|
|
||||||
<td>e5f8b2c4-75ae-45ee-9be8-212e34f77747</td>
|
|
||||||
<td>Microsoft.AAD.BrokerPlugin</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Xbox</td>
|
|
||||||
<td>b806836f-eebe-41c9-8669-19e243b81b83</td>
|
|
||||||
<td>Microsoft.XboxApp</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Xbox identity provider</td>
|
|
||||||
<td>ba88225b-059a-45a2-a8eb-d3580283e49d</td>
|
|
||||||
<td>Microsoft.XboxIdentityProvider</td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## <a href="" id="allow-list-examples"></a>Allowlist examples
|
## <a href="" id="allow-list-examples"></a>Allowlist examples
|
||||||
|
|
||||||
|
@ -18,62 +18,21 @@ The **Assign seat** operation assigns seat for a specified user in the Microsoft
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**POST:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
```http
|
||||||
<col width="50%" />
|
https://bspmts.mp.microsoft.com/V1/Inventory/{productId}/{skuId}/Seats/{username}
|
||||||
</colgroup>
|
```
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Method</th>
|
|
||||||
<th>Request URI</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>POST</p></td>
|
|
||||||
<td><p>https://bspmts.mp.microsoft.com/V1/Inventory/{productId}/{skuId}/Seats/{username}</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%" />
|
|username|string|Requires UserPrincipalName (UPN). User name of the target user account.|
|
||||||
</colgroup>
|
|
||||||
<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>username</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Requires UserPrincipalName (UPN). User name of the target user account.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
|
|
||||||
@ -81,58 +40,9 @@ The following parameters may be specified in the request URI.
|
|||||||
|
|
||||||
The response body contains [SeatDetails](data-structures-windows-store-for-business.md#seatdetails).
|
The response body contains [SeatDetails](data-structures-windows-store-for-business.md#seatdetails).
|
||||||
|
|
||||||
<table>
|
|Error code|Description|Retry|Data field|Details|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |--- |
|
||||||
<col width="20%" />
|
|400|Invalid parameters|No|Parameter name <br>Reason: Invalid parameter<br>Details: String|Invalid can include productId, skuId or userName|
|
||||||
<col width="20%" />
|
|404|Not found||Item type: Inventory, User, Seat<br> <br>Values: ProductId/SkuId, UserName, ProductId/SkuId/UserName|ItemType: Inventory User Seat<br> <br>Values: ProductId/SkuId UserName ProductId/SkuId/UserName|
|
||||||
<col width="20%" />
|
|409|Conflict||Reason: Not online||
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Error code</th>
|
|
||||||
<th>Description</th>
|
|
||||||
<th>Retry</th>
|
|
||||||
<th>Data field</th>
|
|
||||||
<th>Details</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: Invalid parameter</p>
|
|
||||||
<p>Details: String</p></td>
|
|
||||||
<td><p>Invalid can include productId, skuId or userName</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>404</p></td>
|
|
||||||
<td><p>Not found</p></td>
|
|
||||||
<td></td>
|
|
||||||
<td><p>Item type: Inventory, User, Seat</p>
|
|
||||||
<p>Values: ProductId/SkuId, UserName, ProductId/SkuId/UserName</p></td>
|
|
||||||
<td><p>ItemType: Inventory User Seat</p>
|
|
||||||
<p>Values: ProductId/SkuId UserName ProductId/SkuId/UserName</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>409</p></td>
|
|
||||||
<td><p>Conflict</p></td>
|
|
||||||
<td></td>
|
|
||||||
<td><p>Reason: Not online</p></td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -135,7 +135,7 @@ Use the following steps to register a cloud-based MDM application with Azure AD.
|
|||||||
|
|
||||||
8. Enter the login URL for your MDM service.
|
8. Enter the login URL for your MDM service.
|
||||||
|
|
||||||
9. For the App ID, enter **https://<your\_tenant\_name>/ContosoMDM**, then select OK.
|
9. For the App ID, enter `https://<your_tenant_name>/ContosoMDM`, then select OK.
|
||||||
|
|
||||||
10. While still in the Azure portal, select the **Configure** tab of your application.
|
10. While still in the Azure portal, select the **Configure** tab of your application.
|
||||||
|
|
||||||
@ -187,40 +187,14 @@ The following image show how MDM applications show up in the Azure app gallery.
|
|||||||
|
|
||||||
The following table shows the required information to create an entry in the Azure AD app gallery.
|
The following table shows the required information to create an entry in the Azure AD app gallery.
|
||||||
|
|
||||||
<table>
|
|Item|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|**Application ID**|The client ID of your MDM app that is configured within your tenant. This ID is the unique identifier for your multi-tenant app.|
|
||||||
<col width="50%" />
|
|**Publisher**|A string that identifies the publisher of the app.|
|
||||||
</colgroup>
|
|**Application URL**|A URL to the landing page of your app where your administrators can get more information about the MDM app and contains a link to the landing page of your app. This URL isn't used for the actual enrollment.|
|
||||||
<thead>
|
|**Description**|A brief description of your MDM app, which must be under 255 characters.|
|
||||||
<tr class="header">
|
|**Icons**|A set of logo icons for the MDM app. Dimensions: 45 X 45, 150 X 122, 214 X 215|
|
||||||
<th>Item</th>
|
|
||||||
<th>Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>Application ID</strong></p></td>
|
|
||||||
<td><p>The client ID of your MDM app that is configured within your tenant. This ID is the unique identifier for your multi-tenant app.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>Publisher</strong></p></td>
|
|
||||||
<td><p>A string that identifies the publisher of the app.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>Application URL</strong></p></td>
|
|
||||||
<td><p>A URL to the landing page of your app where your administrators can get more information about the MDM app and contains a link to the landing page of your app. This URL isn't used for the actual enrollment.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>Description</strong></p></td>
|
|
||||||
<td><p>A brief description of your MDM app, which must be under 255 characters.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>Icons</strong></p></td>
|
|
||||||
<td><p>A set of logo icons for the MDM app. Dimensions: 45 X 45, 150 X 122, 214 X 215</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
### Add on-premises MDM to the app gallery
|
### Add on-premises MDM to the app gallery
|
||||||
@ -250,42 +224,10 @@ The CSS files provided by Microsoft contain version information and we recommend
|
|||||||
|
|
||||||
An MDM page must adhere to a predefined theme depending on the scenario that is displayed. For example, if the CXH-HOSTHTTP header is FRX, which is the OOBE scenario, then the page must support a dark theme with blue background color, which uses WinJS file Ui-dark.css ver 4.0 and oobe-desktop.css ver 1.0.4.
|
An MDM page must adhere to a predefined theme depending on the scenario that is displayed. For example, if the CXH-HOSTHTTP header is FRX, which is the OOBE scenario, then the page must support a dark theme with blue background color, which uses WinJS file Ui-dark.css ver 4.0 and oobe-desktop.css ver 1.0.4.
|
||||||
|
|
||||||
<table>
|
|CXH-HOST (HTTP HEADER)|Scenario|Background Theme|WinJS|Scenario CSS|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |--- |
|
||||||
<col width="20%" />
|
|FRX|OOBE|Dark theme + blue background color|Filename: Ui-dark.css|Filename: oobe-dekstop.css|
|
||||||
<col width="20%" />
|
|MOSET|Settings/Post OOBE|Light theme|Filename: Ui-light.css|Filename: settings-desktop.css|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>CXH-HOST (HTTP HEADER)</th>
|
|
||||||
<th>Scenario</th>
|
|
||||||
<th>Background Theme</th>
|
|
||||||
<th>WinJS</th>
|
|
||||||
<th>Scenario CSS</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>FRX</td>
|
|
||||||
<td>OOBE</td>
|
|
||||||
<td>Dark theme + blue background color</td>
|
|
||||||
<td>Filename: Ui-dark.css</td>
|
|
||||||
<td>Filename: oobe-dekstop.css</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>MOSET</td>
|
|
||||||
<td>Settings/
|
|
||||||
<p>Post OOBE</p></td>
|
|
||||||
<td>Light theme</td>
|
|
||||||
<td>Filename: Ui-light.css</td>
|
|
||||||
<td>Filename: settings-desktop.css</td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
## Terms of Use protocol semantics
|
## Terms of Use protocol semantics
|
||||||
|
|
||||||
@ -293,40 +235,16 @@ The Terms of Use endpoint is hosted by the MDM server. During the Azure AD Join
|
|||||||
|
|
||||||
### Redirect to the Terms of Use endpoint
|
### Redirect to the Terms of Use endpoint
|
||||||
|
|
||||||
This redirect is a full page redirect to the Terms of User endpoint hosted by the MDM. Here's an example URL, https:<span></span>//fabrikam.contosomdm.com/TermsOfUse.
|
This redirect is a full page redirect to the Terms of User endpoint hosted by the MDM. Here's an example URL, `https://fabrikam.contosomdm.com/TermsOfUse`.
|
||||||
|
|
||||||
The following parameters are passed in the query string:
|
The following parameters are passed in the query string:
|
||||||
|
|
||||||
<table>
|
|Item|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|redirect_uri|After the user accepts or rejects the Terms of Use, the user is redirected to this URL.|
|
||||||
<col width="50%" />
|
|client-request-id|A GUID that is used to correlate logs for diagnostic and debugging purposes. Use this parameter to log or trace the state of the enrollment request to help find the root cause of failures.|
|
||||||
</colgroup>
|
|api-version|Specifies the version of the protocol requested by the client. This value provides a mechanism to support version revisions of the protocol.|
|
||||||
<thead>
|
|mode|Specifies that the device is organization owned when mode=azureadjoin. This parameter isn't present for BYOD devices.|
|
||||||
<tr class="header">
|
|
||||||
<th>Item</th>
|
|
||||||
<th>Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>redirect_uri</p></td>
|
|
||||||
<td><p>After the user accepts or rejects the Terms of Use, the user is redirected to this URL.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>client-request-id</p></td>
|
|
||||||
<td><p>A GUID that is used to correlate logs for diagnostic and debugging purposes. Use this parameter to log or trace the state of the enrollment request to help find the root cause of failures.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>api-version</p></td>
|
|
||||||
<td><p>Specifies the version of the protocol requested by the client. This value provides a mechanism to support version revisions of the protocol.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>mode</p></td>
|
|
||||||
<td><p>Specifies that the device is organization owned when mode=azureadjoin. This parameter isn't present for BYOD devices.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
### Access token
|
### Access token
|
||||||
@ -337,37 +255,13 @@ Azure AD issues a bearer access token. The token is passed in the authorization
|
|||||||
|
|
||||||
The following claims are expected in the access token passed by Windows to the Terms of Use endpoint:
|
The following claims are expected in the access token passed by Windows to the Terms of Use endpoint:
|
||||||
|
|
||||||
<table>
|
|Item|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Object ID|Identifier of the user object corresponding to the authenticated user.|
|
||||||
<col width="50%" />
|
|UPN|A claim containing the user principal name (UPN) of the authenticated user.|
|
||||||
</colgroup>
|
|TID|A claim representing the tenant ID of the tenant. In the example above, it's Fabrikam.|
|
||||||
<thead>
|
|Resource|A sanitized URL representing the MDM application. Example: `https://fabrikam.contosomdm.com` |
|
||||||
<tr class="header">
|
|
||||||
<th>Item</th>
|
|
||||||
<th>Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Object ID</p></td>
|
|
||||||
<td><p>Identifier of the user object corresponding to the authenticated user.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>UPN</p></td>
|
|
||||||
<td><p>A claim containing the user principal name (UPN) of the authenticated user.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>TID</p></td>
|
|
||||||
<td><p>A claim representing the tenant ID of the tenant. In the example above, it's Fabrikam.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Resource</p></td>
|
|
||||||
<td><p>A sanitized URL representing the MDM application. Example, https:<span></span>//fabrikam.contosomdm.com.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
<br/>
|
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> There's no device ID claim in the access token because the device may not yet be enrolled at this time.
|
> There's no device ID claim in the access token because the device may not yet be enrolled at this time.
|
||||||
@ -428,184 +322,35 @@ Location: ms-appx-web://App1/ToUResponse?error=access_denied&error_description=A
|
|||||||
|
|
||||||
The following table shows the error codes.
|
The following table shows the error codes.
|
||||||
|
|
||||||
<table>
|
|Cause|HTTP status|Error|Description|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|api-version|302|invalid_request|unsupported version|
|
||||||
<col width="25%" />
|
|Tenant or user data are missing or other required prerequisites for device enrollment are not met|302|unauthorized_client|unauthorized user or tenant|
|
||||||
<col width="25%" />
|
|Azure AD token validation failed|302|unauthorized_client|unauthorized_client|
|
||||||
<col width="25%" />
|
|internal service error|302|server_error|internal service error|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Cause</th>
|
|
||||||
<th>HTTP status</th>
|
|
||||||
<th>Error</th>
|
|
||||||
<th>Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>api-version</p></td>
|
|
||||||
<td><p>302</p></td>
|
|
||||||
<td><p>invalid_request</p></td>
|
|
||||||
<td><p>unsupported version</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Tenant or user data are missing or other required prerequisites for device enrollment are not met</p></td>
|
|
||||||
<td><p>302</p></td>
|
|
||||||
<td><p>unauthorized_client</p></td>
|
|
||||||
<td><p>unauthorized user or tenant</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Azure AD token validation failed</p></td>
|
|
||||||
<td><p>302</p></td>
|
|
||||||
<td><p>unauthorized_client</p></td>
|
|
||||||
<td><p>unauthorized_client</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>internal service error</p></td>
|
|
||||||
<td><p>302</p></td>
|
|
||||||
<td><p>server_error</p></td>
|
|
||||||
<td><p>internal service error</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
## Enrollment protocol with Azure AD
|
## Enrollment protocol with Azure AD
|
||||||
|
|
||||||
With Azure integrated MDM enrollment, there's no discovery phase and the discovery URL is directly passed down to the system from Azure. The following table shows the comparison between the traditional and Azure enrollments.
|
With Azure integrated MDM enrollment, there's no discovery phase and the discovery URL is directly passed down to the system from Azure. The following table shows the comparison between the traditional and Azure enrollments.
|
||||||
|
|
||||||
<table>
|
|Detail|Traditional MDM enrollment|Azure AD Join (organization-owned device)|Azure AD adds a work account (user-owned device)|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|MDM auto-discovery using email address to retrieve MDM discovery URL|Enrollment|Not applicable<br>Discovery URL provisioned in Azure||
|
||||||
<col width="25%" />
|
|Uses MDM discovery URL|Enrollment<br>Enrollment renewal<br>ROBO|Enrollment<br>Enrollment renewal<br>ROBO|Enrollment<br>Enrollment renewal<br>ROBO|
|
||||||
<col width="25%" />
|
|Is MDM enrollment required?|Yes|Yes|No<br>User can decline.|
|
||||||
<col width="25%" />
|
|Authentication type|OnPremise<br>Federated<br>Certificate|Federated|Federated|
|
||||||
</colgroup>
|
|EnrollmentPolicyServiceURL|Optional (all auth)|Optional (all auth)|Optional (all auth)|
|
||||||
<thead>
|
|EnrollmentServiceURL|Required (all auth)|Used (all auth)|Used (all auth)|
|
||||||
<tr class="header">
|
|EnrollmentServiceURL includes OS Version, OS Platform, and other attributes provided by MDM discovery URL|Highly recommended|Highly recommended|Highly recommended|
|
||||||
<th>Detail</th>
|
|AuthenticationServiceURL used|Used (Federated auth)|Skipped|Skipped|
|
||||||
<th>Traditional MDM enrollment</th>
|
|BinarySecurityToken|Custom per MDM|Azure AD issued token|Azure AD issued token|
|
||||||
<th>Azure AD Join (organization-owned device)</th>
|
|EnrollmentType|Full|Device|Full|
|
||||||
<th>Azure AD adds a work account (user-owned device)</th>
|
|Enrolled certificate type|User certificate|Device certificate|User certificate|
|
||||||
</tr>
|
|Enrolled certificate store|My/User|My/System|My/User|
|
||||||
</thead>
|
|CSR subject name|User Principal Name|Device ID|User Principal Name|
|
||||||
<tbody>
|
|EnrollmentData Terms of Use binary blob as AdditionalContext for EnrollmentServiceURL|Not supported|Supported|Supported|
|
||||||
<tr class="odd">
|
|CSPs accessible during enrollment|Windows 10 support: <br/>- DMClient <br/>- CertificateStore <br/>- RootCATrustedCertificates <br/> - ClientCertificateInstall <br/>- EnterpriseModernAppManagement <br/> - PassportForWork <br/> - Policy <br/> - w7 APPLICATION|||
|
||||||
<td><p>MDM auto-discovery using email address to retrieve MDM discovery URL</p></td>
|
|
||||||
<td><p>Enrollment</p></td>
|
|
||||||
<td><p>Not applicable</p>
|
|
||||||
<p>Discovery URL provisioned in Azure</p></td>
|
|
||||||
<td><p></p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Uses MDM discovery URL</p></td>
|
|
||||||
<td><p>Enrollment</p>
|
|
||||||
<p>Enrollment renewal</p>
|
|
||||||
<p>ROBO</p></td>
|
|
||||||
<td><p>Enrollment</p>
|
|
||||||
<p>Enrollment renewal</p>
|
|
||||||
<p>ROBO</p></td>
|
|
||||||
<td><p>Enrollment</p>
|
|
||||||
<p>Enrollment renewal</p>
|
|
||||||
<p>ROBO</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Is MDM enrollment required?</p></td>
|
|
||||||
<td><p>Yes</p></td>
|
|
||||||
<td><p>Yes</p></td>
|
|
||||||
<td><p>No</p>
|
|
||||||
<p>User can decline.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Authentication type</p></td>
|
|
||||||
<td><p>OnPremise</p>
|
|
||||||
<p>Federated</p>
|
|
||||||
<p>Certificate</p></td>
|
|
||||||
<td><p>Federated</p></td>
|
|
||||||
<td><p>Federated</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>EnrollmentPolicyServiceURL</p></td>
|
|
||||||
<td><p>Optional (all auth)</p></td>
|
|
||||||
<td><p>Optional (all auth)</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td><p>Optional (all auth)</p>
|
|
||||||
<p></p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>EnrollmentServiceURL</p></td>
|
|
||||||
<td><p>Required (all auth)</p></td>
|
|
||||||
<td><p>Used (all auth)</p></td>
|
|
||||||
<td><p>Used (all auth)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>EnrollmentServiceURL includes OS Version, OS Platform, and other attributes provided by MDM discovery URL</p></td>
|
|
||||||
<td><p>Highly recommended</p></td>
|
|
||||||
<td><p>Highly recommended</p></td>
|
|
||||||
<td><p>Highly recommended</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>AuthenticationServiceURL used</p></td>
|
|
||||||
<td><p>Used (Federated auth)</p></td>
|
|
||||||
<td><p>Skipped</p></td>
|
|
||||||
<td><p>Skipped</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>BinarySecurityToken</p></td>
|
|
||||||
<td><p>Custom per MDM</p></td>
|
|
||||||
<td><p>Azure AD issued token</p></td>
|
|
||||||
<td><p>Azure AD issued token</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>EnrollmentType</p></td>
|
|
||||||
<td><p>Full</p></td>
|
|
||||||
<td><p>Device</p></td>
|
|
||||||
<td><p>Full</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Enrolled certificate type</p></td>
|
|
||||||
<td><p>User certificate</p></td>
|
|
||||||
<td><p>Device certificate</p></td>
|
|
||||||
<td><p>User certificate</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Enrolled certificate store</p></td>
|
|
||||||
<td><p>My/User</p></td>
|
|
||||||
<td><p>My/System</p></td>
|
|
||||||
<td><p>My/User</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>CSR subject name</p></td>
|
|
||||||
<td><p>User Principal Name</p></td>
|
|
||||||
<td><p>Device ID</p></td>
|
|
||||||
<td><p>User Principal Name</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>EnrollmentData Terms of Use binary blob as AdditionalContext for EnrollmentServiceURL</p></td>
|
|
||||||
<td><p>Not supported</p></td>
|
|
||||||
<td><p>Supported</p></td>
|
|
||||||
<td><p>Supported</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>CSPs accessible during enrollment</p></td>
|
|
||||||
<td><p>Windows 10 support:</p>
|
|
||||||
<ul>
|
|
||||||
<li>DMClient</li>
|
|
||||||
<li>CertificateStore</li>
|
|
||||||
<li>RootCATrustedCertificates</li>
|
|
||||||
<li>ClientCertificateInstall</li>
|
|
||||||
<li>EnterpriseModernAppManagement</li>
|
|
||||||
<li>PassportForWork</li>
|
|
||||||
<li>Policy</li>
|
|
||||||
<li>w7 APPLICATION</li>
|
|
||||||
</ul>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Management protocol with Azure AD
|
## Management protocol with Azure AD
|
||||||
|
|
||||||
@ -737,202 +482,41 @@ When a user is enrolled into MDM through Azure Active Directory Join and then di
|
|||||||
|
|
||||||
## Error codes
|
## Error codes
|
||||||
|
|
||||||
<table>
|
|Code|ID|Error message|
|
||||||
<colgroup>
|
|--- |--- |--- |
|
||||||
<col width="33%" />
|
|0x80180001|"idErrorServerConnectivity", // MENROLL_E_DEVICE_MESSAGE_FORMAT_ERROR|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<col width="33%" />
|
|0x80180002|"idErrorAuthenticationFailure", // MENROLL_E_DEVICE_AUTHENTICATION_ERROR|There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<col width="33%" />
|
|0x80180003|"idErrorAuthorizationFailure", // MENROLL_E_DEVICE_AUTHORIZATION_ERROR|This user isn't authorized to enroll. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
</colgroup>
|
|0x80180004|"idErrorMDMCertificateError", // MENROLL_E_DEVICE_CERTIFCATEREQUEST_ERROR|There was a certificate error. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<thead>
|
|0x80180005|"idErrorServerConnectivity", // MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<tr class="header">
|
|0x80180006|"idErrorServerConnectivity", // MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<th>Code</th>
|
|0x80180007|"idErrorAuthenticationFailure", // MENROLL_E_DEVICE_INVALIDSECURITY_ERROR|There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<th>ID</th>
|
|0x80180008|"idErrorServerConnectivity", // MENROLL_E_DEVICE_UNKNOWN_ERROR|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<th>Error message</th>
|
|0x80180009|"idErrorAlreadyInProgress", // MENROLL_E_ENROLLMENT_IN_PROGRESS|Another enrollment is in progress. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
</tr>
|
|0x8018000A|"idErrorMDMAlreadyEnrolled", // MENROLL_E_DEVICE_ALREADY_ENROLLED|This device is already enrolled. You can contact your system administrator with the error code {0}.|
|
||||||
</thead>
|
|0x8018000D|"idErrorMDMCertificateError", // MENROLL_E_DISCOVERY_SEC_CERT_DATE_INVALID|There was a certificate error. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<tbody>
|
|0x8018000E|"idErrorAuthenticationFailure", // MENROLL_E_PASSWORD_NEEDED|There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<tr class="odd">
|
|0x8018000F|"idErrorAuthenticationFailure", // MENROLL_E_WAB_ERROR|There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<td>0x80180001</td>
|
|0x80180010|"idErrorServerConnectivity", // MENROLL_E_CONNECTIVITY|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<td>"idErrorServerConnectivity", // MENROLL_E_DEVICE_MESSAGE_FORMAT_ERROR</td>
|
|0x80180012|"idErrorMDMCertificateError", // MENROLL_E_INVALIDSSLCERT|There was a certificate error. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|0x80180013|"idErrorDeviceLimit", // MENROLL_E_DEVICECAPREACHED|Looks like there are too many devices or users for this account. Contact your system administrator with the error code {0}.|
|
||||||
</tr>
|
|0x80180014|"idErrorMDMNotSupported", // MENROLL_E_DEVICENOTSUPPORTED|This feature isn't supported. Contact your system administrator with the error code {0}.|
|
||||||
<tr class="even">
|
|0x80180015|"idErrorMDMNotSupported", // MENROLL_E_NOTSUPPORTED|This feature isn't supported. Contact your system administrator with the error code {0}.|
|
||||||
<td>0x80180002</td>
|
|0x80180016|"idErrorMDMRenewalRejected", // MENROLL_E_NOTELIGIBLETORENEW|The server did not accept the request. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<td>"idErrorAuthenticationFailure", // MENROLL_E_DEVICE_AUTHENTICATION_ERROR</td>
|
|0x80180017|"idErrorMDMAccountMaintenance", // MENROLL_E_INMAINTENANCE|The service is in maintenance. You can try to do this again later or contact your system administrator with the error code {0}.|
|
||||||
<td><p>There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|0x80180018|"idErrorMDMLicenseError", // MENROLL_E_USERLICENSE|There was an error with your license. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
</tr>
|
|0x80180019|"idErrorInvalidServerConfig", // MENROLL_E_ENROLLMENTDATAINVALID|Looks like the server isn't correctly configured. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<tr class="odd">
|
|"rejectedTermsOfUse"|"idErrorRejectedTermsOfUse"|Your organization requires that you agree to the Terms of Use. Please try again or ask your support person for more information.|
|
||||||
<td>0x80180003</td>
|
|0x801c0001|"idErrorServerConnectivity", // DSREG_E_DEVICE_MESSAGE_FORMAT_ERROR|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<td>"idErrorAuthorizationFailure", // MENROLL_E_DEVICE_AUTHORIZATION_ERROR</td>
|
|0x801c0002|"idErrorAuthenticationFailure", // DSREG_E_DEVICE_AUTHENTICATION_ERROR|There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<td><p>This user isn't authorized to enroll. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|0x801c0003|"idErrorAuthorizationFailure", // DSREG_E_DEVICE_AUTHORIZATION_ERROR|This user isn't authorized to enroll. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
</tr>
|
|0x801c0006|"idErrorServerConnectivity", // DSREG_E_DEVICE_INTERNALSERVICE_ERROR|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<tr class="even">
|
|0x801c000B|"idErrorUntrustedServer", // DSREG_E_DISCOVERY_REDIRECTION_NOT_TRUSTED|The server being contacted isn't trusted. Contact your system administrator with the error code {0}.|
|
||||||
<td>0x80180004</td>
|
|0x801c000C|"idErrorServerConnectivity", // DSREG_E_DISCOVERY_FAILED|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<td>"idErrorMDMCertificateError", // MENROLL_E_DEVICE_CERTIFCATEREQUEST_ERROR</td>
|
|0x801c000E|"idErrorDeviceLimit", // DSREG_E_DEVICE_REGISTRATION_QUOTA_EXCCEEDED|Looks like there are too many devices or users for this account. Contact your system administrator with the error code {0}.|
|
||||||
<td><p>There was a certificate error. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|0x801c000F|"idErrorDeviceRequiresReboot", // DSREG_E_DEVICE_REQUIRES_REBOOT|A reboot is required to complete device registration.|
|
||||||
</tr>
|
|0x801c0010|"idErrorInvalidCertificate", // DSREG_E_DEVICE_AIK_VALIDATION_ERROR|Looks like you have an invalid certificate. Contact your system administrator with the error code {0}.|
|
||||||
<tr class="odd">
|
|0x801c0011|"idErrorAuthenticationFailure", // DSREG_E_DEVICE_ATTESTATION_ERROR|There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<td>0x80180005</td>
|
|0x801c0012|"idErrorServerConnectivity", // DSREG_E_DISCOVERY_BAD_MESSAGE_ERROR|There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}|
|
||||||
<td>"idErrorServerConnectivity", // MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR</td>
|
|0x801c0013|"idErrorAuthenticationFailure", // DSREG_E_TENANTID_NOT_FOUND|There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|0x801c0014|"idErrorAuthenticationFailure", // DSREG_E_USERSID_NOT_FOUND|There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x80180006</td>
|
|
||||||
<td>"idErrorServerConnectivity", // MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR</td>
|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x80180007</td>
|
|
||||||
<td>"idErrorAuthenticationFailure", // MENROLL_E_DEVICE_INVALIDSECURITY_ERROR</td>
|
|
||||||
<td><p>There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x80180008</td>
|
|
||||||
<td>"idErrorServerConnectivity", // MENROLL_E_DEVICE_UNKNOWN_ERROR</td>
|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x80180009</td>
|
|
||||||
<td>"idErrorAlreadyInProgress", // MENROLL_E_ENROLLMENT_IN_PROGRESS</td>
|
|
||||||
<td><p>Another enrollment is in progress. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x8018000A</td>
|
|
||||||
<td>"idErrorMDMAlreadyEnrolled", // MENROLL_E_DEVICE_ALREADY_ENROLLED</td>
|
|
||||||
<td><p>This device is already enrolled. You can contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x8018000D</td>
|
|
||||||
<td>"idErrorMDMCertificateError", // MENROLL_E_DISCOVERY_SEC_CERT_DATE_INVALID</td>
|
|
||||||
<td><p>There was a certificate error. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x8018000E</td>
|
|
||||||
<td>"idErrorAuthenticationFailure", // MENROLL_E_PASSWORD_NEEDED</td>
|
|
||||||
<td><p>There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x8018000F</td>
|
|
||||||
<td>"idErrorAuthenticationFailure", // MENROLL_E_WAB_ERROR</td>
|
|
||||||
<td><p>There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x80180010</td>
|
|
||||||
<td>"idErrorServerConnectivity", // MENROLL_E_CONNECTIVITY</td>
|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x80180012</td>
|
|
||||||
<td>"idErrorMDMCertificateError", // MENROLL_E_INVALIDSSLCERT</td>
|
|
||||||
<td><p>There was a certificate error. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x80180013</td>
|
|
||||||
<td>"idErrorDeviceLimit", // MENROLL_E_DEVICECAPREACHED</td>
|
|
||||||
<td><p>Looks like there are too many devices or users for this account. Contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x80180014</td>
|
|
||||||
<td>"idErrorMDMNotSupported", // MENROLL_E_DEVICENOTSUPPORTED</td>
|
|
||||||
<td><p>This feature isn't supported. Contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x80180015</td>
|
|
||||||
<td>"idErrorMDMNotSupported", // MENROLL_E_NOTSUPPORTED</td>
|
|
||||||
<td><p>This feature isn't supported. Contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x80180016</td>
|
|
||||||
<td>"idErrorMDMRenewalRejected", // MENROLL_E_NOTELIGIBLETORENEW</td>
|
|
||||||
<td><p>The server did not accept the request. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x80180017</td>
|
|
||||||
<td>"idErrorMDMAccountMaintenance", // MENROLL_E_INMAINTENANCE</td>
|
|
||||||
<td><p>The service is in maintenance. You can try to do this again later or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x80180018</td>
|
|
||||||
<td>"idErrorMDMLicenseError", // MENROLL_E_USERLICENSE</td>
|
|
||||||
<td><p>There was an error with your license. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x80180019</td>
|
|
||||||
<td>"idErrorInvalidServerConfig", // MENROLL_E_ENROLLMENTDATAINVALID</td>
|
|
||||||
<td><p>Looks like the server isn't correctly configured. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>"rejectedTermsOfUse"</td>
|
|
||||||
<td>"idErrorRejectedTermsOfUse"</td>
|
|
||||||
<td><p>Your organization requires that you agree to the Terms of Use. Please try again or ask your support person for more information.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x801c0001</td>
|
|
||||||
<td>"idErrorServerConnectivity", // DSREG_E_DEVICE_MESSAGE_FORMAT_ERROR</td>
|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x801c0002</td>
|
|
||||||
<td>"idErrorAuthenticationFailure", // DSREG_E_DEVICE_AUTHENTICATION_ERROR</td>
|
|
||||||
<td><p>There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x801c0003</td>
|
|
||||||
<td>"idErrorAuthorizationFailure", // DSREG_E_DEVICE_AUTHORIZATION_ERROR</td>
|
|
||||||
<td><p>This user isn't authorized to enroll. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x801c0006</td>
|
|
||||||
<td>"idErrorServerConnectivity", // DSREG_E_DEVICE_INTERNALSERVICE_ERROR</td>
|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x801c000B</td>
|
|
||||||
<td>"idErrorUntrustedServer", // DSREG_E_DISCOVERY_REDIRECTION_NOT_TRUSTED</td>
|
|
||||||
<td>The server being contacted isn't trusted. Contact your system administrator with the error code {0}.</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x801c000C</td>
|
|
||||||
<td>"idErrorServerConnectivity", // DSREG_E_DISCOVERY_FAILED</td>
|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x801c000E</td>
|
|
||||||
<td>"idErrorDeviceLimit", // DSREG_E_DEVICE_REGISTRATION_QUOTA_EXCCEEDED</td>
|
|
||||||
<td><p>Looks like there are too many devices or users for this account. Contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x801c000F</td>
|
|
||||||
<td>"idErrorDeviceRequiresReboot", // DSREG_E_DEVICE_REQUIRES_REBOOT</td>
|
|
||||||
<td><p>A reboot is required to complete device registration.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x801c0010</td>
|
|
||||||
<td>"idErrorInvalidCertificate", // DSREG_E_DEVICE_AIK_VALIDATION_ERROR</td>
|
|
||||||
<td><p>Looks like you have an invalid certificate. Contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x801c0011</td>
|
|
||||||
<td>"idErrorAuthenticationFailure", // DSREG_E_DEVICE_ATTESTATION_ERROR</td>
|
|
||||||
<td><p>There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x801c0012</td>
|
|
||||||
<td>"idErrorServerConnectivity", // DSREG_E_DISCOVERY_BAD_MESSAGE_ERROR</td>
|
|
||||||
<td><p>There was an error communicating with the server. You can try to do this again or contact your system administrator with the error code {0}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>0x801c0013</td>
|
|
||||||
<td>"idErrorAuthenticationFailure", // DSREG_E_TENANTID_NOT_FOUND</td>
|
|
||||||
<td><p>There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>0x801c0014</td>
|
|
||||||
<td>"idErrorAuthenticationFailure", // DSREG_E_USERSID_NOT_FOUND</td>
|
|
||||||
<td><p>There was a problem authenticating your account or device. You can try to do this again or contact your system administrator with the error code {0}.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -17,14 +17,15 @@ ms.date: 10/25/2021
|
|||||||
|
|
||||||
The BrowserFavorite configuration service provider is used to add and remove URLs from the favorites list on a device.
|
The BrowserFavorite configuration service provider is used to add and remove URLs from the favorites list on a device.
|
||||||
|
|
||||||
> **Note** BrowserFavorite CSP is only supported in Windows Phone 8.1.
|
> [!Note]
|
||||||
|
> BrowserFavorite CSP is only supported in Windows Phone 8.1.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The BrowserFavorite configuration service provider manages only the favorites at the root favorite folder level. It does not manage subfolders under the root favorite folder nor does it manage favorites under a subfolder.
|
The BrowserFavorite configuration service provider manages only the favorites at the root favorite folder level. It does not manage subfolders under the root favorite folder nor does it manage favorites under a subfolder.
|
||||||
|
|
||||||
> **Note**
|
> [!Note]
|
||||||
This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_INTERNET\_EXPLORER\_FAVORITES capabilities to be accessed from a network configuration application.
|
> This configuration service provider requires the ID\_CAP\_CSP\_FOUNDATION and ID\_CAP\_INTERNET\_EXPLORER\_FAVORITES capabilities to be accessed from a network configuration application.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -39,7 +40,8 @@ favorite name
|
|||||||
<a href="" id="favorite-name-------------"></a>***favorite name***
|
<a href="" id="favorite-name-------------"></a>***favorite name***
|
||||||
Required. Specifies the user-friendly name of the favorite URL that is displayed in the Favorites list of Internet Explorer.
|
Required. Specifies the user-friendly name of the favorite URL that is displayed in the Favorites list of Internet Explorer.
|
||||||
|
|
||||||
> **Note** The *favorite name* should contain only characters that are valid in the Windows file system. The invalid characters are: \\ / : \* ? " < > |
|
> [!Note]
|
||||||
|
> The *favorite name* should contain only characters that are valid in the Windows file system. The invalid characters are: \\ / : \* ? " < > |
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -69,40 +71,12 @@ Adding a new browser favorite.
|
|||||||
|
|
||||||
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="50%" />
|
|Parm-query|Yes|
|
||||||
<col width="50%" />
|
|Noparm|Yes|
|
||||||
</colgroup>
|
|Nocharacteristic|Yes|
|
||||||
<thead>
|
|Characteristic-query|Yes<br> <br>Recursive query: Yes<br> <br>Top-level 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></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>
|
|
||||||
<p>Recursive query: Yes</p>
|
|
||||||
<p>Top-level query: Yes</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
@ -18,66 +18,22 @@ The **Bulk assign and reclaim seats from users** operation returns reclaimed or
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**POST**:
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Method</th>
|
|
||||||
<th>Request URI</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>POST</p></td>
|
|
||||||
<td><p>https:<span></span>//bspmts.mp.microsoft.com/V1/Inventory/{productId}/{skuId}/Seats</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
```http
|
||||||
|
https:<span></span>//bspmts.mp.microsoft.com/V1/Inventory/{productId}/{skuId}/Seats
|
||||||
|
```
|
||||||
|
|
||||||
### 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%" />
|
|username|string|Requires UserPrincipalName (UPN). User name of the target user account.|
|
||||||
</colgroup>
|
|seatAction|[SeatAction](data-structures-windows-store-for-business.md#seataction) ||
|
||||||
<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>username</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Requires UserPrincipalName (UPN). User name of the target user account.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>seatAction</p></td>
|
|
||||||
<td><p><a href="data-structures-windows-store-for-business.md#seataction" data-raw-source="[SeatAction](data-structures-windows-store-for-business.md#seataction)">SeatAction</a></p></td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
@ -86,37 +42,8 @@ The following parameters may be specified in the request URI.
|
|||||||
|
|
||||||
The response body contains [BulkSeatOperationResultSet](data-structures-windows-store-for-business.md#bulkseatoperationresultset).
|
The response body contains [BulkSeatOperationResultSet](data-structures-windows-store-for-business.md#bulkseatoperationresultset).
|
||||||
|
|
||||||
<table>
|
|Error code|Description|Retry|Data field|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|404|Not found||Item type: Inventory<br> Values: ProductId/SkuId|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<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>404</p></td>
|
|
||||||
<td><p>Not found</p></td>
|
|
||||||
<td></td>
|
|
||||||
<td><p>Item type: Inventory</p>
|
|
||||||
<p>Values: ProductId/SkuId</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -30,32 +30,11 @@ CellularSettings
|
|||||||
<a href="" id="dataroam"></a>**DataRoam**
|
<a href="" id="dataroam"></a>**DataRoam**
|
||||||
<p> Optional. Integer. Specifies the default roaming value. Valid values are:</p>
|
<p> Optional. Integer. Specifies the default roaming value. Valid values are:</p>
|
||||||
|
|
||||||
<table><table>
|
|Value|Setting|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|0|Don’t roam|
|
||||||
<col width="80%" />
|
|1|Don’t roam (or Domestic roaming if applicable)|
|
||||||
</colgroup>
|
|2|Roam|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Value</th>
|
|
||||||
<th>Setting</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>Don’t roam</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>1</p></td>
|
|
||||||
<td><p>Don’t roam (or Domestic roaming if applicable)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>2</p></td>
|
|
||||||
<td><p>Roam</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
@ -70,38 +70,14 @@ CM_CellularEntries
|
|||||||
<a href="" id="connectiontype"></a>**ConnectionType**
|
<a href="" id="connectiontype"></a>**ConnectionType**
|
||||||
<p>Optional. Type: String. Specifies the type of connection used for the APN. The following connection types are available:
|
<p>Optional. Type: String. Specifies the type of connection used for the APN. The following connection types are available:
|
||||||
|
|
||||||
<table><table>
|
|Connection type|Usage|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|Gprs|Default. Used for GPRS type connections (GPRS + GSM + EDGE + UMTS + LTE).|
|
||||||
<col width="80%" />
|
|Cdma|Used for CDMA type connections (1XRTT + EVDO).|
|
||||||
</colgroup>
|
|Lte|Used for LTE type connections (eHRPD + LTE) when the device is registered HOME.|
|
||||||
<tbody>
|
|Legacy|Used for GPRS + GSM + EDGE + UMTS connections.|
|
||||||
<tr class="odd">
|
|Lte_iwlan|Used for GPRS type connections that may be offloaded over WiFi|
|
||||||
<td><p>Gprs</p></td>
|
|Iwlan|Used for connections that are implemented over WiFi offload only|
|
||||||
<td><p>Default. Used for GPRS type connections (GPRS + GSM + EDGE + UMTS + LTE).</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Cdma</p></td>
|
|
||||||
<td><p>Used for CDMA type connections (1XRTT + EVDO).</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Lte</p></td>
|
|
||||||
<td><p>Used for LTE type connections (eHRPD + LTE) when the device is registered HOME.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Legacy</p></td>
|
|
||||||
<td><p>Used for GPRS + GSM + EDGE + UMTS connections.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Lte_iwlan</p></td>
|
|
||||||
<td><p>Used for GPRS type connections that may be offloaded over WiFi</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Iwlan</p></td>
|
|
||||||
<td><p>Used for connections that are implemented over WiFi offload only</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -295,36 +271,13 @@ Configuring a CDMA connection:
|
|||||||
|
|
||||||
## Microsoft Custom Elements
|
## Microsoft Custom Elements
|
||||||
|
|
||||||
|
|
||||||
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>
|
|Element|Available|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Nocharacteristic|Yes|
|
||||||
<col width="50%" />
|
|Characteristic-query|Yes|
|
||||||
</colgroup>
|
|Parm-query|Yes|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Element</th>
|
|
||||||
<th>Available</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<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>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Parm-query</p></td>
|
|
||||||
<td><p>Yes</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
@ -29,7 +29,7 @@ Each policy entry identifies one or more applications in combination with a host
|
|||||||
|
|
||||||
The following shows the CMPolicy configuration service provider management object in tree format as used by both Open Mobile Alliance (OMA) Client Provisioning and OMA Device Management.
|
The following shows the CMPolicy configuration service provider management object in tree format as used by both Open Mobile Alliance (OMA) Client Provisioning and OMA Device Management.
|
||||||
|
|
||||||
```
|
```console
|
||||||
./Vendor/MSFT
|
./Vendor/MSFT
|
||||||
CMPolicy
|
CMPolicy
|
||||||
----PolicyName
|
----PolicyName
|
||||||
@ -42,6 +42,7 @@ CMPolicy
|
|||||||
----------------ConnectionID
|
----------------ConnectionID
|
||||||
----------------Type
|
----------------Type
|
||||||
```
|
```
|
||||||
|
|
||||||
<a href="" id="policyname"></a>***policyName***
|
<a href="" id="policyname"></a>***policyName***
|
||||||
Defines the name of the policy.
|
Defines the name of the policy.
|
||||||
|
|
||||||
@ -83,154 +84,44 @@ For `CMST_CONNECTION_NAME`, specify the connection name. For example, if you hav
|
|||||||
|
|
||||||
For `CMST_CONNECTION_TYPE`, specify the GUID for the desired connection type. The curly brackets {} around the GUID are required. The following connection types are available:
|
For `CMST_CONNECTION_TYPE`, specify the GUID for the desired connection type. The curly brackets {} around the GUID are required. The following connection types are available:
|
||||||
|
|
||||||
<table>
|
|Connection type|GUID|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|GSM|{A05DC613-E393-40ad-AA89-CCCE04277CD9}|
|
||||||
<col width="80%" />
|
|CDMA|{274AD55A-4A70-4E35-93B3-AE2D2E6727FC}|
|
||||||
</colgroup>
|
|Legacy 3GPP|{6DE4C04B-B74E-47FA-99E5-8F2097C06A92}|
|
||||||
<thead>
|
|LTE|{2378E547-8312-46A5-905E-5C581E92693B}|
|
||||||
<tr class="header">
|
|Wi-Fi|{8568B401-858E-4B7B-B3DF-0FD4927F131B}|
|
||||||
<th>Connection type</th>
|
|Wi-Fi hotspot|{072FC7DC-1D93-40D1-9BB0-2114D7D73434}|
|
||||||
<th>GUID</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>GSM</p></td>
|
|
||||||
<td><p>{A05DC613-E393-40ad-AA89-CCCE04277CD9}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>CDMA</p></td>
|
|
||||||
<td><p>{274AD55A-4A70-4E35-93B3-AE2D2E6727FC}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Legacy 3GPP</p></td>
|
|
||||||
<td><p>{6DE4C04B-B74E-47FA-99E5-8F2097C06A92}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>LTE</p></td>
|
|
||||||
<td><p>{2378E547-8312-46A5-905E-5C581E92693B}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Wi-Fi</p></td>
|
|
||||||
<td><p>{8568B401-858E-4B7B-B3DF-0FD4927F131B}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Wi-Fi hotspot</p></td>
|
|
||||||
<td><p>{072FC7DC-1D93-40D1-9BB0-2114D7D73434}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
For `CMST_CONNECTION_NETWORK_TYPE`, specify the GUID for the desired network type. The curly brackets {} around the GUID are required. The following network types are available:
|
For `CMST_CONNECTION_NETWORK_TYPE`, specify the GUID for the desired network type. The curly brackets {} around the GUID are required. The following network types are available:
|
||||||
|
|
||||||
<table>
|
|Network type|GUID|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|GPRS|{AFB7D659-FC1F-4EA5-BDD0-0FDA62676D96}|
|
||||||
<col width="80%" />
|
|1XRTT|{B1E700AE-A62F-49FF-9BBE-B880C995F27D}|
|
||||||
</colgroup>
|
|EDGE|{C347F8EC-7095-423D-B838-7C7A7F38CD03}|
|
||||||
<thead>
|
|WCDMA UMTS|{A72F04C6-9BE6-4151-B5EF-15A53E12C482}|
|
||||||
<tr class="header">
|
|WCDMA FOMA|{B8326098-F845-42F3-804E-8CC3FF7B50B4}|
|
||||||
<th>Network type</th>
|
|1XEVDO|{DD42DF39-EBDF-407C-8146-1685416401B2}|
|
||||||
<th>GUID</th>
|
|1XEVDV|{61BF1BFD-5218-4CD4-949C-241CA3F326F6}|
|
||||||
</tr>
|
|HSPA HSDPA|{047F7282-BABD-4893-AA77-B8B312657F8C}|
|
||||||
</thead>
|
|HSPA HSUPA|{1536A1C6-A4AF-423C-8884-6BDDA3656F84}|
|
||||||
<tbody>
|
|LTE|{B41CBF43-6994-46FF-9C2F-D6CA6D45889B}|
|
||||||
<tr class="odd">
|
|EHRPD|{7CFA04A5-0F3F-445C-88A4-C86ED2AD94EA}|
|
||||||
<td><p>GPRS</p></td>
|
|Ethernet 10 Mbps|{97D3D1B3-854A-4C32-BD1C-C13069078370}|
|
||||||
<td><p>{AFB7D659-FC1F-4EA5-BDD0-0FDA62676D96}</p></td>
|
|Ethernet 100 Mbps|{A8F4FE66-8D04-43F5-9DD2-2A85BD21029B}|
|
||||||
</tr>
|
|Ethernet Gbps|{556C1E6B-B8D4-448E-836D-9451BA4CCE75}|
|
||||||
<tr class="even">
|
|
||||||
<td><p>1XRTT</p></td>
|
|
||||||
<td><p>{B1E700AE-A62F-49FF-9BBE-B880C995F27D}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>EDGE</p></td>
|
|
||||||
<td><p>{C347F8EC-7095-423D-B838-7C7A7F38CD03}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>WCDMA UMTS</p></td>
|
|
||||||
<td><p>{A72F04C6-9BE6-4151-B5EF-15A53E12C482}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>WCDMA FOMA</p></td>
|
|
||||||
<td><p>{B8326098-F845-42F3-804E-8CC3FF7B50B4}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>1XEVDO</p></td>
|
|
||||||
<td><p>{DD42DF39-EBDF-407C-8146-1685416401B2}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>1XEVDV</p></td>
|
|
||||||
<td><p>{61BF1BFD-5218-4CD4-949C-241CA3F326F6}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>HSPA HSDPA</p></td>
|
|
||||||
<td><p>{047F7282-BABD-4893-AA77-B8B312657F8C}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>HSPA HSUPA</p></td>
|
|
||||||
<td><p>{1536A1C6-A4AF-423C-8884-6BDDA3656F84}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>LTE</p></td>
|
|
||||||
<td><p>{B41CBF43-6994-46FF-9C2F-D6CA6D45889B}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>EHRPD</p></td>
|
|
||||||
<td><p>{7CFA04A5-0F3F-445C-88A4-C86ED2AD94EA}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Ethernet 10 Mbps</p></td>
|
|
||||||
<td><p>{97D3D1B3-854A-4C32-BD1C-C13069078370}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Ethernet 100 Mbps</p></td>
|
|
||||||
<td><p>{A8F4FE66-8D04-43F5-9DD2-2A85BD21029B}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Ethernet Gbps</p></td>
|
|
||||||
<td><p>{556C1E6B-B8D4-448E-836D-9451BA4CCE75}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
For `CMST_CONNECTION_DEVICE_TYPE`, specify the GUID for the desired device type. The curly brackets {} around the GUID are required. The following device types are available:
|
For `CMST_CONNECTION_DEVICE_TYPE`, specify the GUID for the desired device type. The curly brackets {} around the GUID are required. The following device types are available:
|
||||||
|
|
||||||
<table>
|
|Device type|GUID|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|Cellular device|{F9A53167-4016-4198-9B41-86D9522DC019}|
|
||||||
<col width="80%" />
|
|Ethernet|{97844272-00C7-4572-B20A-D8D861C095F2}|
|
||||||
</colgroup>
|
|Bluetooth|{1D793123-701A-4fd0-B6AE-9C3C57E99C2C}|
|
||||||
<thead>
|
|Virtual|{EAA02CE5-9C70-4E87-97FE-55C9DEC847D4}|
|
||||||
<tr class="header">
|
|
||||||
<th>Device type</th>
|
|
||||||
<th>GUID</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Cellular device</p></td>
|
|
||||||
<td><p>{F9A53167-4016-4198-9B41-86D9522DC019}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Ethernet</p></td>
|
|
||||||
<td><p>{97844272-00C7-4572-B20A-D8D861C095F2}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Bluetooth</p></td>
|
|
||||||
<td><p>{1D793123-701A-4fd0-B6AE-9C3C57E99C2C}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Virtual</p></td>
|
|
||||||
<td><p>{EAA02CE5-9C70-4E87-97FE-55C9DEC847D4}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -479,36 +370,11 @@ Adding a host-based mapping policy:
|
|||||||
## Microsoft Custom Elements
|
## Microsoft Custom Elements
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|Element|Available|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|parm-query|Yes|
|
||||||
<col width="50%" />
|
|uncharacteristic|Yes|
|
||||||
</colgroup>
|
|characteristic-query|Yes<br> <br>Recursive query: Yes<br> <br>Top-level query: Yes|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Element</th>
|
|
||||||
<th>Available</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>parm-query</p></td>
|
|
||||||
<td><p>Yes</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>uncharacteristic</p></td>
|
|
||||||
<td><p>Yes</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>characteristic-query</p></td>
|
|
||||||
<td><p>Yes</p>
|
|
||||||
<p>Recursive query: Yes</p>
|
|
||||||
<p>Top-level query: Yes</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
@ -29,7 +29,8 @@ Each policy entry identifies one or more applications in combination with a host
|
|||||||
**Default Policies**: Policies are applied in order of their scope with the most specific policies considered before the more general policies. The phone’s default behavior applies to all applications and all domains and is only used when no other, more specific policy is available. The default policy is to use any available Wi-Fi network first and then any available APN.
|
**Default Policies**: Policies are applied in order of their scope with the most specific policies considered before the more general policies. The phone’s default behavior applies to all applications and all domains and is only used when no other, more specific policy is available. The default policy is to use any available Wi-Fi network first and then any available APN.
|
||||||
|
|
||||||
The following shows the CMPolicyEnterprise configuration service provider management object in tree format as used by both Open Mobile Alliance (OMA) Client Provisioning and OMA Device Management.
|
The following shows the CMPolicyEnterprise configuration service provider management object in tree format as used by both Open Mobile Alliance (OMA) Client Provisioning and OMA Device Management.
|
||||||
```
|
|
||||||
|
```console
|
||||||
./Vendor/MSFT
|
./Vendor/MSFT
|
||||||
CMPolicy
|
CMPolicy
|
||||||
----PolicyName
|
----PolicyName
|
||||||
@ -83,156 +84,44 @@ For `CMST_CONNECTION_NAME`, specify the connection name. For example, if you hav
|
|||||||
|
|
||||||
For `CMST_CONNECTION_TYPE`, specify the GUID for the desired connection type. The curly brackets {} around the GUID are required. The following connection types are available:
|
For `CMST_CONNECTION_TYPE`, specify the GUID for the desired connection type. The curly brackets {} around the GUID are required. The following connection types are available:
|
||||||
|
|
||||||
<table>
|
|Connection type|GUID|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|GSM|{A05DC613-E393-40ad-AA89-CCCE04277CD9}|
|
||||||
<col width="50%" />
|
|CDMA|{274AD55A-4A70-4E35-93B3-AE2D2E6727FC}|
|
||||||
</colgroup>
|
|Legacy 3GPP|{6DE4C04B-B74E-47FA-99E5-8F2097C06A92}|
|
||||||
<thead>
|
|LTE|{2378E547-8312-46A5-905E-5C581E92693B}|
|
||||||
<tr class="header">
|
|Wi-Fi|{8568B401-858E-4B7B-B3DF-0FD4927F131B}|
|
||||||
<th>Connection type</th>
|
|Wi-Fi hotspot|{072FC7DC-1D93-40D1-9BB0-2114D7D73434}|
|
||||||
<th>GUID</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>GSM</p></td>
|
|
||||||
<td><p>{A05DC613-E393-40ad-AA89-CCCE04277CD9}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>CDMA</p></td>
|
|
||||||
<td><p>{274AD55A-4A70-4E35-93B3-AE2D2E6727FC}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Legacy 3GPP</p></td>
|
|
||||||
<td><p>{6DE4C04B-B74E-47FA-99E5-8F2097C06A92}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>LTE</p></td>
|
|
||||||
<td><p>{2378E547-8312-46A5-905E-5C581E92693B}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Wi-Fi</p></td>
|
|
||||||
<td><p>{8568B401-858E-4B7B-B3DF-0FD4927F131B}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Wi-Fi hotspot</p></td>
|
|
||||||
<td><p>{072FC7DC-1D93-40D1-9BB0-2114D7D73434}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
For `CMST_CONNECTION_NETWORK_TYPE`, specify the GUID for the desired network type. The curly brackets {} around the GUID are required. The following network types are available:
|
For `CMST_CONNECTION_NETWORK_TYPE`, specify the GUID for the desired network type. The curly brackets {} around the GUID are required. The following network types are available:
|
||||||
|
|
||||||
<table>
|
|Network type|GUID|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|GPRS|{AFB7D659-FC1F-4EA5-BDD0-0FDA62676D96}|
|
||||||
<col width="50%" />
|
|1XRTT|{B1E700AE-A62F-49FF-9BBE-B880C995F27D}|
|
||||||
</colgroup>
|
|EDGE|{C347F8EC-7095-423D-B838-7C7A7F38CD03}|
|
||||||
<thead>
|
|WCDMA UMTS|{A72F04C6-9BE6-4151-B5EF-15A53E12C482}|
|
||||||
<tr class="header">
|
|WCDMA FOMA|{B8326098-F845-42F3-804E-8CC3FF7B50B4}|
|
||||||
<th>Network type</th>
|
|1XEVDO|{DD42DF39-EBDF-407C-8146-1685416401B2}|
|
||||||
<th>GUID</th>
|
|1XEVDV|{61BF1BFD-5218-4CD4-949C-241CA3F326F6}|
|
||||||
</tr>
|
|HSPA HSDPA|{047F7282-BABD-4893-AA77-B8B312657F8C}|
|
||||||
</thead>
|
|HSPA HSUPA|{1536A1C6-A4AF-423C-8884-6BDDA3656F84}|
|
||||||
<tbody>
|
|LTE|{B41CBF43-6994-46FF-9C2F-D6CA6D45889B}|
|
||||||
<tr class="odd">
|
|EHRPD|{7CFA04A5-0F3F-445C-88A4-C86ED2AD94EA}|
|
||||||
<td><p>GPRS</p></td>
|
|Ethernet 10Mbps|{97D3D1B3-854A-4C32-BD1C-C13069078370}|
|
||||||
<td><p>{AFB7D659-FC1F-4EA5-BDD0-0FDA62676D96}</p></td>
|
|Ethernet 100Mbps|{A8F4FE66-8D04-43F5-9DD2-2A85BD21029B}|
|
||||||
</tr>
|
|Ethernet Gbps|{556C1E6B-B8D4-448E-836D-9451BA4CCE75}|
|
||||||
<tr class="even">
|
|
||||||
<td><p>1XRTT</p></td>
|
|
||||||
<td><p>{B1E700AE-A62F-49FF-9BBE-B880C995F27D}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>EDGE</p></td>
|
|
||||||
<td><p>{C347F8EC-7095-423D-B838-7C7A7F38CD03}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>WCDMA UMTS</p></td>
|
|
||||||
<td><p>{A72F04C6-9BE6-4151-B5EF-15A53E12C482}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>WCDMA FOMA</p></td>
|
|
||||||
<td><p>{B8326098-F845-42F3-804E-8CC3FF7B50B4}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>1XEVDO</p></td>
|
|
||||||
<td><p>{DD42DF39-EBDF-407C-8146-1685416401B2}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>1XEVDV</p></td>
|
|
||||||
<td><p>{61BF1BFD-5218-4CD4-949C-241CA3F326F6}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>HSPA HSDPA</p></td>
|
|
||||||
<td><p>{047F7282-BABD-4893-AA77-B8B312657F8C}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>HSPA HSUPA</p></td>
|
|
||||||
<td><p>{1536A1C6-A4AF-423C-8884-6BDDA3656F84}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>LTE</p></td>
|
|
||||||
<td><p>{B41CBF43-6994-46FF-9C2F-D6CA6D45889B}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>EHRPD</p></td>
|
|
||||||
<td><p>{7CFA04A5-0F3F-445C-88A4-C86ED2AD94EA}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Ethernet 10Mbps</p></td>
|
|
||||||
<td><p>{97D3D1B3-854A-4C32-BD1C-C13069078370}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Ethernet 100Mbps</p></td>
|
|
||||||
<td><p>{A8F4FE66-8D04-43F5-9DD2-2A85BD21029B}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Ethernet Gbps</p></td>
|
|
||||||
<td><p>{556C1E6B-B8D4-448E-836D-9451BA4CCE75}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
For `CMST_CONNECTION_DEVICE_TYPE`, specify the GUID for the desired device type. The curly brackets {} around the GUID are required. The following device types are available:
|
For `CMST_CONNECTION_DEVICE_TYPE`, specify the GUID for the desired device type. The curly brackets {} around the GUID are required. The following device types are available:
|
||||||
|
|
||||||
<table>
|
|Device type|GUID|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Cellular device|{F9A53167-4016-4198-9B41-86D9522DC019}|
|
||||||
<col width="50%" />
|
|Ethernet|{97844272-00C7-4572-B20A-D8D861C095F2}|
|
||||||
</colgroup>
|
|Bluetooth|{1D793123-701A-4fd0-B6AE-9C3C57E99C2C}|
|
||||||
<thead>
|
|Virtual|{EAA02CE5-9C70-4E87-97FE-55C9DEC847D4}|
|
||||||
<tr class="header">
|
|
||||||
<th>Device type</th>
|
|
||||||
<th>GUID</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Cellular device</p></td>
|
|
||||||
<td><p>{F9A53167-4016-4198-9B41-86D9522DC019}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Ethernet</p></td>
|
|
||||||
<td><p>{97844272-00C7-4572-B20A-D8D861C095F2}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Bluetooth</p></td>
|
|
||||||
<td><p>{1D793123-701A-4fd0-B6AE-9C3C57E99C2C}</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Virtual</p></td>
|
|
||||||
<td><p>{EAA02CE5-9C70-4E87-97FE-55C9DEC847D4}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="type"></a>**Type**
|
<a href="" id="type"></a>**Type**
|
||||||
Specifies the type of connection being referenced. The following list describes the available connection types:
|
Specifies the type of connection being referenced. The following list describes the available connection types:
|
||||||
@ -479,36 +368,11 @@ Adding a host-based mapping policy:
|
|||||||
## Microsoft Custom Elements
|
## Microsoft Custom Elements
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|Element|Available|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|parm-query|Yes|
|
||||||
<col width="50%" />
|
|nocharacteristic|Yes|
|
||||||
</colgroup>
|
|characteristic-query|Yes<br> <br>Recursive query: Yes<br> <br>Top level query: Yes|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Element</th>
|
|
||||||
<th>Available</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>parm-query</p></td>
|
|
||||||
<td><p>Yes</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>nocharacteristic</p></td>
|
|
||||||
<td><p>Yes</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>characteristic-query</p></td>
|
|
||||||
<td><p>Yes</p>
|
|
||||||
<p>Recursive query: Yes</p>
|
|
||||||
<p>Top level query: Yes</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
|
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -356,57 +356,30 @@ If the **Specify intranet Microsoft update service location** policy is enabled,
|
|||||||
|
|
||||||
If the **Allow Telemetry** policy is enabled and the Options value is set to 0, then the **Defer upgrades by**, **Defer updates by** and **Pause Updates and Upgrades** settings have no effect.
|
If the **Allow Telemetry** policy is enabled and the Options value is set to 0, then the **Defer upgrades by**, **Defer updates by** and **Pause Updates and Upgrades** settings have no effect.
|
||||||
|
|
||||||
<table>
|
- **Update category**: OS upgrade
|
||||||
<colgroup>
|
- **Maximum deferral**: 8 months
|
||||||
<col width="25%" />
|
- **Deferral increment**: 1 month
|
||||||
<col width="25%" />
|
- **Update type/notes**: Upgrade - 3689BDC8-B205-4AF4-8D4A-A63924C5E9D5
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Update category</th>
|
|
||||||
<th>Maximum deferral</th>
|
|
||||||
<th>Deferral increment</th>
|
|
||||||
<th>Update type/notes</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>OS upgrade</p></td>
|
|
||||||
<td><p>8 months</p></td>
|
|
||||||
<td><p>1 month</p></td>
|
|
||||||
<td><p>Upgrade - 3689BDC8-B205-4AF4-8D4A-A63924C5E9D5</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Update</p></td>
|
|
||||||
<td><p>1 month</p></td>
|
|
||||||
<td><p>1 week</p></td>
|
|
||||||
<td><div class="alert">
|
|
||||||
<strong>Note</strong>
|
|
||||||
If a machine has Microsoft Update enabled, any Microsoft Updates in these categories will also observe Defer / Pause logic.
|
|
||||||
</div>
|
|
||||||
<ul>
|
|
||||||
<li>Security Update - 0FA1201D-4330-4FA8-8AE9-B877473B6441</li>
|
|
||||||
<li>Critical Update - E6CF1350-C01B-414D-A61F-263D14D133B4</li>
|
|
||||||
<li>Update Rollup - 28BC880E-0592-4CBF-8F95-C79B17911D5F</li>
|
|
||||||
<li>Service Pack - 68C5B0A3-D1A6-4553-AE49-01D3A7827828</li>
|
|
||||||
<li>Tools - B4832BD8-E735-4761-8DAF-37F882276DAB</li>
|
|
||||||
<li>Feature Pack - B54E7D24-7ADD-428F-8B75-90A396FA584F</li>
|
|
||||||
<li>Update - CD5FFD1E-E932-4E3A-BF74-18BF0B1BBD83</li>
|
|
||||||
<li>Driver - EBFC1FC5-71A4-4F7B-9ACA-3B9A503104A0</li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Other/cannot defer</p></td>
|
|
||||||
<td><p>No deferral</p></td>
|
|
||||||
<td><p>No deferral</p></td>
|
|
||||||
<td><p>Any update category not enumerated above falls into this category.</p>
|
|
||||||
<p>Definition Update - E0789628-CE08-4437-BE74-2495B842F43B</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
- **Update category**: Update
|
||||||
|
- **Maximum deferral**: 1 month
|
||||||
|
- **Deferral increment**: 1 week
|
||||||
|
- **Update type/notes**: If a machine has Microsoft Update enabled, any Microsoft Updates in these categories will also observe Defer / Pause logic.
|
||||||
|
|
||||||
|
- Security Update - 0FA1201D-4330-4FA8-8AE9-B877473B6441
|
||||||
|
- Critical Update - E6CF1350-C01B-414D-A61F-263D14D133B4
|
||||||
|
- Update Rollup - 28BC880E-0592-4CBF-8F95-C79B17911D5F
|
||||||
|
- Service Pack - 68C5B0A3-D1A6-4553-AE49-01D3A7827828
|
||||||
|
- Tools - B4832BD8-E735-4761-8DAF-37F882276DAB
|
||||||
|
- Feature Pack - B54E7D24-7ADD-428F-8B75-90A396FA584F
|
||||||
|
- Update - CD5FFD1E-E932-4E3A-BF74-18BF0B1BBD83
|
||||||
|
- Driver - EBFC1FC5-71A4-4F7B-9ACA-3B9A503104A0
|
||||||
|
|
||||||
|
- **Update category**: Other/cannot defer
|
||||||
|
- **Maximum deferral**: No deferral
|
||||||
|
- **Deferral increment**: No deferral
|
||||||
|
- **Update type/notes**: Any update category not enumerated above falls into this category.
|
||||||
|
- Definition Update - E0789628-CE08-4437-BE74-2495B842F43B
|
||||||
|
|
||||||
<a href="" id="update-deferupgradeperiod"></a>**Update/DeferUpgradePeriod**
|
<a href="" id="update-deferupgradeperiod"></a>**Update/DeferUpgradePeriod**
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
@ -878,71 +851,16 @@ Here are the new policies added in Windows 10, version 1607 in [Policy CSP](pol
|
|||||||
|
|
||||||
Here's the list of corresponding Group Policy settings in HKLM\\Software\\Policies\\Microsoft\\Windows\\WindowsUpdate.
|
Here's the list of corresponding Group Policy settings in HKLM\\Software\\Policies\\Microsoft\\Windows\\WindowsUpdate.
|
||||||
|
|
||||||
<table>
|
|GPO key|Type|Value|
|
||||||
<colgroup>
|
|--- |--- |--- |
|
||||||
<col width="33%" />
|
|BranchReadinessLevel|REG_DWORD|16: systems take Feature Updates on the Current Branch (CB) train<br><br>32: systems take Feature Updates on the Current Branch for Business<br><br>Other value or absent: receive all applicable updates (CB)|
|
||||||
<col width="33%" />
|
|DeferQualityUpdates|REG_DWORD|1: defer quality updates<br><br>Other value or absent: don’t defer quality updates|
|
||||||
<col width="33%" />
|
|DeferQualityUpdatesPeriodInDays|REG_DWORD|0-30: days to defer quality updates|
|
||||||
</colgroup>
|
|PauseQualityUpdates|REG_DWORD|1: pause quality updates<br><br>Other value or absent: don’t pause quality updates|
|
||||||
<thead>
|
|DeferFeatureUpdates|REG_DWORD|1: defer feature updates<br><br>Other value or absent: don’t defer feature updates|
|
||||||
<tr class="header">
|
|DeferFeatureUpdatesPeriodInDays|REG_DWORD|0-180: days to defer feature updates|
|
||||||
<th>GPO key</th>
|
|PauseFeatureUpdates|REG_DWORD|1: pause feature updates<br><br>Other value or absent: don’t pause feature updates|
|
||||||
<th>Type</th>
|
|ExcludeWUDriversInQualityUpdate|REG_DWORD|1: exclude WU drivers<br><br>Other value or absent: offer WU drivers|
|
||||||
<th>Value</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>BranchReadinessLevel</p></td>
|
|
||||||
<td><p>REG_DWORD</p></td>
|
|
||||||
<td><p>16: systems take Feature Updates on the Current Branch (CB) train</p>
|
|
||||||
<p>32: systems take Feature Updates on the Current Branch for Business</p>
|
|
||||||
<p>Other value or absent: receive all applicable updates (CB)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>DeferQualityUpdates</p></td>
|
|
||||||
<td><p>REG_DWORD</p></td>
|
|
||||||
<td><p>1: defer quality updates</p>
|
|
||||||
<p>Other value or absent: don’t defer quality updates</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>DeferQualityUpdatesPeriodInDays</p></td>
|
|
||||||
<td><p>REG_DWORD</p></td>
|
|
||||||
<td><p>0-30: days to defer quality updates</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>PauseQualityUpdates</p></td>
|
|
||||||
<td><p>REG_DWORD</p></td>
|
|
||||||
<td><p>1: pause quality updates</p>
|
|
||||||
<p>Other value or absent: don’t pause quality updates</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>DeferFeatureUpdates</p></td>
|
|
||||||
<td><p>REG_DWORD</p></td>
|
|
||||||
<td><p>1: defer feature updates</p>
|
|
||||||
<p>Other value or absent: don’t defer feature updates</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>DeferFeatureUpdatesPeriodInDays</p></td>
|
|
||||||
<td><p>REG_DWORD</p></td>
|
|
||||||
<td><p>0-180: days to defer feature updates</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>PauseFeatureUpdates</p></td>
|
|
||||||
<td><p>REG_DWORD</p></td>
|
|
||||||
<td><p>1: pause feature updates</p>
|
|
||||||
<p>Other value or absent: don’t pause feature updates</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>ExcludeWUDriversInQualityUpdate</p></td>
|
|
||||||
<td><p>REG_DWORD</p></td>
|
|
||||||
<td><p>1: exclude WU drivers</p>
|
|
||||||
<p>Other value or absent: offer WU drivers</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Here's the list of older policies that are still supported for backward compatibility. You can use these older policies for Windows 10, version 1511 devices.
|
Here's the list of older policies that are still supported for backward compatibility. You can use these older policies for Windows 10, version 1511 devices.
|
||||||
|
|
||||||
|
@ -328,220 +328,50 @@ If there's no infinite schedule set, then a 24-hour schedule is created and sche
|
|||||||
|
|
||||||
**Valid poll schedule: sigmoid polling schedule with infinite schedule (Recommended).**
|
**Valid poll schedule: sigmoid polling schedule with infinite schedule (Recommended).**
|
||||||
|
|
||||||
<table>
|
|Schedule name|Schedule set by the server|Actual value queried on device|
|
||||||
<colgroup>
|
|--- |--- |--- |
|
||||||
<col width="33%" />
|
|IntervalForFirstSetOfRetries|15|15|
|
||||||
<col width="33%" />
|
|NumberOfFirstRetries|5|5|
|
||||||
<col width="33%" />
|
|IntervalForSecondSetOfRetries|60|60|
|
||||||
</colgroup>
|
|NumberOfSecondRetries|10|10|
|
||||||
<thead>
|
|IntervalForRemainingScheduledRetries|1440|1440|
|
||||||
<tr class="header">
|
|NumberOfRemainingScheduledRetries|0|0|
|
||||||
<th>Schedule name</th>
|
|
||||||
<th>Schedule set by the server</th>
|
|
||||||
<th>Actual value queried on device</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForFirstSetOfRetries</p></td>
|
|
||||||
<td><p>15</p></td>
|
|
||||||
<td><p>15</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfFirstRetries</p></td>
|
|
||||||
<td><p>5</p></td>
|
|
||||||
<td><p>5</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForSecondSetOfRetries</p></td>
|
|
||||||
<td><p>60</p></td>
|
|
||||||
<td><p>60</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfSecondRetries</p></td>
|
|
||||||
<td><p>10</p></td>
|
|
||||||
<td><p>10</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForRemainingScheduledRetries</p></td>
|
|
||||||
<td><p>1440</p></td>
|
|
||||||
<td><p>1440</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfRemainingScheduledRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Valid poll schedule: initial enrollment only \[no infinite schedule\]**
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="33%" />
|
|
||||||
<col width="33%" />
|
|
||||||
<col width="33%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Schedule name</th>
|
|
||||||
<th>Schedule set by the server</th>
|
|
||||||
<th>Actual value queried on device</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForFirstSetOfRetries</p></td>
|
|
||||||
<td><p>15</p></td>
|
|
||||||
<td><p>15</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfFirstRetries</p></td>
|
|
||||||
<td><p>5</p></td>
|
|
||||||
<td><p>5</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForSecondSetOfRetries</p></td>
|
|
||||||
<td><p>60</p></td>
|
|
||||||
<td><p>60</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfSecondRetries</p></td>
|
|
||||||
<td><p>10</p></td>
|
|
||||||
<td><p>10</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForRemainingScheduledRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfRemainingScheduledRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
**Valid poll schedule: initial enrollment only [no infinite schedule]**
|
||||||
|
|
||||||
|
|Schedule name|Schedule set by the server|Actual value queried on device|
|
||||||
|
|--- |--- |--- |
|
||||||
|
|IntervalForFirstSetOfRetries|15|15|
|
||||||
|
|NumberOfFirstRetries|5|5|
|
||||||
|
|IntervalForSecondSetOfRetries|60|60|
|
||||||
|
|NumberOfSecondRetries|10|10|
|
||||||
|
|IntervalForRemainingScheduledRetries|0|0|
|
||||||
|
|NumberOfRemainingScheduledRetries|0|0|
|
||||||
|
|
||||||
**Invalid poll schedule: disable all poll schedules**
|
**Invalid poll schedule: disable all poll schedules**
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> Disabling poll schedules results in UNDEFINED behavior and enrollment may fail if poll schedules are all set to zero.
|
> Disabling poll schedules results in UNDEFINED behavior and enrollment may fail if poll schedules are all set to zero.
|
||||||
|
|
||||||
|
|Schedule name|Schedule set by the server|Actual value queried on device|
|
||||||
|
|--- |--- |--- |
|
||||||
<table>
|
|IntervalForFirstSetOfRetries|0|0|
|
||||||
<colgroup>
|
|NumberOfFirstRetries|0|0|
|
||||||
<col width="33%" />
|
|IntervalForSecondSetOfRetries|0|0|
|
||||||
<col width="33%" />
|
|NumberOfSecondRetries|0|0|
|
||||||
<col width="33%" />
|
|IntervalForRemainingScheduledRetries|0|0|
|
||||||
</colgroup>
|
|NumberOfRemainingScheduledRetries|0|0|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Schedule name</th>
|
|
||||||
<th>Schedule set by the server</th>
|
|
||||||
<th>Actual value queried on device</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForFirstSetOfRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfFirstRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForSecondSetOfRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfSecondRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForRemainingScheduledRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfRemainingScheduledRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Invalid poll schedule: two infinite schedules**
|
**Invalid poll schedule: two infinite schedules**
|
||||||
|
|
||||||
<table>
|
|Schedule name|Schedule set by server|Actual schedule set on device|Actual experience|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|IntervalForFirstSetOfRetries|15|15|Device polls|
|
||||||
<col width="25%" />
|
|NumberOfFirstRetries|5|5|Device polls|
|
||||||
<col width="25%" />
|
|IntervalForSecondSetOfRetries|1440|1440|Device polls the server once in 24 hours|
|
||||||
<col width="25%" />
|
|NumberOfSecondRetries|0|0|Device polls the server once in 24 hours|
|
||||||
</colgroup>
|
|IntervalForRemainingScheduledRetries|1440|0|Third schedule is disabled|
|
||||||
<thead>
|
|NumberOfRemainingScheduledRetries|0|0|Third schedule is disabled|
|
||||||
<tr class="header">
|
|
||||||
<th>Schedule name</th>
|
|
||||||
<th>Schedule set by server</th>
|
|
||||||
<th>Actual schedule set on device</th>
|
|
||||||
<th>Actual experience</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForFirstSetOfRetries</p></td>
|
|
||||||
<td><p>15</p></td>
|
|
||||||
<td><p>15</p></td>
|
|
||||||
<td><p>Device polls</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfFirstRetries</p></td>
|
|
||||||
<td><p>5</p></td>
|
|
||||||
<td><p>5</p></td>
|
|
||||||
<td><p>Device polls</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForSecondSetOfRetries</p></td>
|
|
||||||
<td><p>1440</p></td>
|
|
||||||
<td><p>1440</p></td>
|
|
||||||
<td><p>Device polls the server once in 24 hours</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfSecondRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>Device polls the server once in 24 hours</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>IntervalForRemainingScheduledRetries</p></td>
|
|
||||||
<td><p>1440</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>Third schedule is disabled</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>NumberOfRemainingScheduledRetries</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>Third schedule is disabled</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If the device was previously enrolled in MDM with polling schedule configured using the registry key values directly, the MDM provider that supports using DMClient CSP to update polling schedule must first send an Add command to add a **./Vendor/MSFT/DMClient/Enrollment/<ProviderID>/Poll** node before it sends a Get/Replace command to query or update polling parameters using the DMClient CSP
|
If the device was previously enrolled in MDM with polling schedule configured using the registry key values directly, the MDM provider that supports using DMClient CSP to update polling schedule must first send an Add command to add a **./Vendor/MSFT/DMClient/Enrollment/<ProviderID>/Poll** node before it sends a Get/Replace command to query or update polling parameters using the DMClient CSP
|
||||||
|
|
||||||
@ -654,58 +484,17 @@ Supported operation is Get.
|
|||||||
|
|
||||||
The status error mapping is listed below.
|
The status error mapping is listed below.
|
||||||
|
|
||||||
<table>
|
|Status|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|0|Success|
|
||||||
<col width="80%" />
|
|1|Failure: invalid PFN|
|
||||||
</colgroup>
|
|2|Failure: invalid or expired device authentication with MSA|
|
||||||
<thead>
|
|3|Failure: WNS client registration failed due to an invalid or revoked PFN|
|
||||||
<tr class="header">
|
|4|Failure: no Channel URI assigned|
|
||||||
<th>Status</th>
|
|5|Failure: Channel URI has expired|
|
||||||
<th>Description</th>
|
|6|Failure: Channel URI failed to be revoked|
|
||||||
</tr>
|
|7|Failure: push notification received, but unable to establish an OMA-DM session due to power or connectivity limitations.|
|
||||||
</thead>
|
|8|Unknown error|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>0</p></td>
|
|
||||||
<td><p>Success</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>1</p></td>
|
|
||||||
<td><p>Failure: invalid PFN</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>2</p></td>
|
|
||||||
<td><p>Failure: invalid or expired device authentication with MSA</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>3</p></td>
|
|
||||||
<td><p>Failure: WNS client registration failed due to an invalid or revoked PFN</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>4</p></td>
|
|
||||||
<td><p>Failure: no Channel URI assigned</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>5</p></td>
|
|
||||||
<td><p>Failure: Channel URI has expired</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>6</p></td>
|
|
||||||
<td><p>Failure: Channel URI failed to be revoked</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>7</p></td>
|
|
||||||
<td><p>Failure: push notification received, but unable to establish an OMA-DM session due to power or connectivity limitations.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>8</p></td>
|
|
||||||
<td><p>Unknown error</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="provider-providerid-customenrollmentcompletepage"></a>**Provider/*ProviderID*/CustomEnrollmentCompletePage**
|
<a href="" id="provider-providerid-customenrollmentcompletepage"></a>**Provider/*ProviderID*/CustomEnrollmentCompletePage**
|
||||||
Optional. Added in Windows 10, version 1703.
|
Optional. Added in Windows 10, version 1703.
|
||||||
|
@ -92,42 +92,13 @@ If **DMProcessConfigXMLFiltered** retrieves a document, the *pbstrXmlOut* holds
|
|||||||
|
|
||||||
Returns the standard **HRESULT** value **S\_OK** to indicate success. The following table shows more error codes that can be returned:
|
Returns the standard **HRESULT** value **S\_OK** to indicate success. The following table shows more error codes that can be returned:
|
||||||
|
|
||||||
<table>
|
|Return code|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|**CONFIG_E_OBJECTBUSY**|Another instance of the configuration management service is currently running.|
|
||||||
<col width="50%" />
|
|**CONFIG_E_ENTRYNOTFOUND**|No metabase entry was found.|
|
||||||
</colgroup>
|
|**CONFIG_E_CSPEXCEPTION**|An exception occurred in one of the configuration service providers.|
|
||||||
<thead>
|
|**CONFIG_E_TRANSACTIONINGFAILURE**|A configuration service provider failed to roll back properly. The affected settings might be in an unknown state.|
|
||||||
<tr class="header">
|
|**CONFIG_E_BAD_XML**|The XML input is invalid or malformed.|
|
||||||
<th>Return code</th>
|
|
||||||
<th>Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>CONFIG_E_OBJECTBUSY</strong></p></td>
|
|
||||||
<td><p>Another instance of the configuration management service is currently running.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>CONFIG_E_ENTRYNOTFOUND</strong></p></td>
|
|
||||||
<td><p>No metabase entry was found.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>CONFIG_E_CSPEXCEPTION</strong></p></td>
|
|
||||||
<td><p>An exception occurred in one of the configuration service providers.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>CONFIG_E_TRANSACTIONINGFAILURE</strong></p></td>
|
|
||||||
<td><p>A configuration service provider failed to roll back properly. The affected settings might be in an unknown state.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>CONFIG_E_BAD_XML</strong></p></td>
|
|
||||||
<td><p>The XML input is invalid or malformed.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Remarks
|
## Remarks
|
||||||
|
|
||||||
@ -190,38 +161,14 @@ if ( bstr != NULL )
|
|||||||
|
|
||||||
## Requirements
|
## Requirements
|
||||||
|
|
||||||
<table>
|
|Requirement|Support|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Minimum supported client|None supported|
|
||||||
<col width="50%" />
|
|Minimum supported server|None supported|
|
||||||
</colgroup>
|
|Minimum supported phone|Windows Phone 8.1|
|
||||||
<tbody>
|
|Header|Dmprocessxmlfiltered.h|
|
||||||
<tr class="odd">
|
|Library|Dmprocessxmlfiltered.lib|
|
||||||
<td><p>Minimum supported client</p></td>
|
|DLL|Dmprocessxmlfiltered.dll|
|
||||||
<td><p>None supported</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Minimum supported server</p></td>
|
|
||||||
<td><p>None supported</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Minimum supported phone</p></td>
|
|
||||||
<td><p>Windows Phone 8.1</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Header</p></td>
|
|
||||||
<td><p>Dmprocessxmlfiltered.h</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Library</p></td>
|
|
||||||
<td><p>Dmprocessxmlfiltered.lib</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>DLL</p></td>
|
|
||||||
<td><p>Dmprocessxmlfiltered.dll</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
## See also
|
## See also
|
||||||
|
|
||||||
|
@ -17,7 +17,8 @@ ms.date: 06/26/2017
|
|||||||
|
|
||||||
The EnterpriseAppManagement enterprise configuration service provider is used to handle enterprise application management tasks such as installing an enterprise application token, the first auto-downloadable app link, querying installed enterprise applications (name and version), auto updating already installed enterprise applications, and removing all installed enterprise apps (including the enterprise app token) during unenrollment.
|
The EnterpriseAppManagement enterprise configuration service provider is used to handle enterprise application management tasks such as installing an enterprise application token, the first auto-downloadable app link, querying installed enterprise applications (name and version), auto updating already installed enterprise applications, and removing all installed enterprise apps (including the enterprise app token) during unenrollment.
|
||||||
|
|
||||||
> **Note** The EnterpriseAppManagement CSP is only supported in Windows 10 Mobile.
|
> [!NOTE]
|
||||||
|
> The EnterpriseAppManagement CSP is only supported in Windows 10 Mobile.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -81,7 +82,8 @@ Optional. The character string that contains the search criteria to search for t
|
|||||||
|
|
||||||
Supported operations are Get and Add.
|
Supported operations are Get and Add.
|
||||||
|
|
||||||
> **Note** Do NOT use Subject=CN%3DB1C43CD0-1624-5FBB-8E54-34CF17DFD3A1\\x00. The server must replace this value in the supplied client certificate. If your server returns a client certificate containing the same Subject value, this can cause unexpected behavior. The server should always override the subject value and not use the default device-provided Device ID Subject= Subject=CN%3DB1C43CD0-1624-5FBB-8E54-34CF17DFD3A1\\x00
|
> [!NOTE]
|
||||||
|
> Do NOT use Subject=CN%3DB1C43CD0-1624-5FBB-8E54-34CF17DFD3A1\\x00. The server must replace this value in the supplied client certificate. If your server returns a client certificate containing the same Subject value, this can cause unexpected behavior. The server should always override the subject value and not use the default device-provided Device ID Subject= Subject=CN%3DB1C43CD0-1624-5FBB-8E54-34CF17DFD3A1\\x00
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -158,48 +160,16 @@ Supported operations are Get, Add, and Replace.
|
|||||||
<a href="" id="-download-productid-status"></a>**/Download/*ProductID*/Status**
|
<a href="" id="-download-productid-status"></a>**/Download/*ProductID*/Status**
|
||||||
Required. The integer value that indicates the status of the current download process. The following table shows the possible values.
|
Required. The integer value that indicates the status of the current download process. The following table shows the possible values.
|
||||||
|
|
||||||
<table>
|
|Value|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|0: CONFIRM|Waiting for confirmation from user.|
|
||||||
<col width="50%" />
|
|1: QUEUED|Waiting for download to start.|
|
||||||
</colgroup>
|
|2: DOWNLOADING|In the process of downloading.|
|
||||||
<tbody>
|
|3: DOWNLOADED|Waiting for installation to start.|
|
||||||
<tr class="odd">
|
|4: INSTALLING|Handed off for installation.|
|
||||||
<td><p>0: CONFIRM</p></td>
|
|5: INSTALLED|Successfully installed|
|
||||||
<td><p>Waiting for confirmation from user.</p></td>
|
|6: FAILED|Application was rejected (not signed properly, bad XAP format, not enrolled properly, etc.)|
|
||||||
</tr>
|
|7:DOWNLOAD_FAILED|Unable to connect to server, file doesn't exist, etc.|
|
||||||
<tr class="even">
|
|
||||||
<td><p>1: QUEUED</p></td>
|
|
||||||
<td><p>Waiting for download to start.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>2: DOWNLOADING</p></td>
|
|
||||||
<td><p>In the process of downloading.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>3: DOWNLOADED</p></td>
|
|
||||||
<td><p>Waiting for installation to start.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>4: INSTALLING</p></td>
|
|
||||||
<td><p>Handed off for installation.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>5: INSTALLED</p></td>
|
|
||||||
<td><p>Successfully installed</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>6: FAILED</p></td>
|
|
||||||
<td><p>Application was rejected (not signed properly, bad XAP format, not enrolled properly, etc.)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>7:DOWNLOAD_FAILED</p></td>
|
|
||||||
<td><p>Unable to connect to server, file doesn't exist, etc.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Scope is dynamic. Supported operations are Get, Add, and Replace.
|
Scope is dynamic. Supported operations are Get, Add, and Replace.
|
||||||
|
|
||||||
@ -463,10 +433,10 @@ Install or update the installed app with the product ID “{B316008A-141D-4A79-8
|
|||||||
|
|
||||||
To perform an XAP update, create the Name, URL, Version, and DownloadInstall nodes first, then perform an “execute” on the “DownloadInstall” node (all within an “Atomic” operation). If the application does not exist, the application will be silently installed without any user interaction. If the application cannot be installed, the user will be notified with an Alert dialog.
|
To perform an XAP update, create the Name, URL, Version, and DownloadInstall nodes first, then perform an “execute” on the “DownloadInstall” node (all within an “Atomic” operation). If the application does not exist, the application will be silently installed without any user interaction. If the application cannot be installed, the user will be notified with an Alert dialog.
|
||||||
|
|
||||||
> **Note**
|
> [!NOTE]
|
||||||
> 1. If a previous app-update node existed for this product ID (the node can persist for up to 1 week or 7 days after an installation has completed), then a 418 (already exist) error would be returned on the “Add”. To get around the 418 error, the server should issue a Replace command for the Name, URL, and Version nodes, and then execute on the “DownloadInstall” (within an “Atomic” operation).
|
> - If a previous app-update node existed for this product ID (the node can persist for up to 1 week or 7 days after an installation has completed), then a 418 (already exist) error would be returned on the “Add”. To get around the 418 error, the server should issue a Replace command for the Name, URL, and Version nodes, and then execute on the “DownloadInstall” (within an “Atomic” operation).
|
||||||
|
>
|
||||||
2. The application product ID curly braces need to be escaped where { is %7B and } is %7D.
|
> - The application product ID curly braces need to be escaped where { is %7B and } is %7D.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -17,12 +17,14 @@ ms.date: 07/12/2017
|
|||||||
|
|
||||||
The EnterpriseAssignedAccess configuration service provider allows IT administrators to configure settings, such as language and themes, lock down a device, and configure custom layouts on a device. For example, the administrator can lock down a device so that only applications specified in an Allow list are available. Apps not on the Allow list remain installed on the device, but are hidden from view and blocked from launching.
|
The EnterpriseAssignedAccess configuration service provider allows IT administrators to configure settings, such as language and themes, lock down a device, and configure custom layouts on a device. For example, the administrator can lock down a device so that only applications specified in an Allow list are available. Apps not on the Allow list remain installed on the device, but are hidden from view and blocked from launching.
|
||||||
|
|
||||||
> **Note** The EnterpriseAssignedAccess CSP is only supported in Windows 10 Mobile.
|
> [!NOTE]
|
||||||
|
> The EnterpriseAssignedAccess CSP is only supported in Windows 10 Mobile.
|
||||||
|
|
||||||
For more information about how to interact with the lockdown XML at runtime, see [**DeviceLockdownProfile class**](/uwp/api/Windows.Embedded.DeviceLockdown.DeviceLockdownProfile).
|
For more information about how to interact with the lockdown XML at runtime, see [**DeviceLockdownProfile class**](/uwp/api/Windows.Embedded.DeviceLockdown.DeviceLockdownProfile).
|
||||||
|
|
||||||
The following shows the EnterpriseAssignedAccess configuration service provider in tree format as used by both the Open Mobile Alliance (OMA) Device Management (DM) and OMA Client Provisioning.
|
The following shows the EnterpriseAssignedAccess configuration service provider in tree format as used by both the Open Mobile Alliance (OMA) Device Management (DM) and OMA Client Provisioning.
|
||||||
```
|
|
||||||
|
```console
|
||||||
./Vendor/MSFT
|
./Vendor/MSFT
|
||||||
EnterpriseAssignedAccess
|
EnterpriseAssignedAccess
|
||||||
----AssignedAccess
|
----AssignedAccess
|
||||||
@ -38,6 +40,7 @@ EnterpriseAssignedAccess
|
|||||||
----Locale
|
----Locale
|
||||||
--------Language
|
--------Language
|
||||||
```
|
```
|
||||||
|
|
||||||
The following list shows the characteristics and parameters.
|
The following list shows the characteristics and parameters.
|
||||||
|
|
||||||
<a href="" id="-vendor-msft-enterpriseassignedaccess-"></a>**./Vendor/MSFT/EnterpriseAssignedAccess/**
|
<a href="" id="-vendor-msft-enterpriseassignedaccess-"></a>**./Vendor/MSFT/EnterpriseAssignedAccess/**
|
||||||
@ -631,110 +634,30 @@ Supported operations are Get and Replace.
|
|||||||
<a href="" id="theme-themeaccentcolorid"></a>**Theme/ThemeAccentColorID**
|
<a href="" id="theme-themeaccentcolorid"></a>**Theme/ThemeAccentColorID**
|
||||||
The accent color to apply as the foreground color for tiles, controls, and other visual elements on the device. The following table shows the possible values.
|
The accent color to apply as the foreground color for tiles, controls, and other visual elements on the device. The following table shows the possible values.
|
||||||
|
|
||||||
<table>
|
|Value|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|0|Lime|
|
||||||
<col width="50%" />
|
|1|Green|
|
||||||
</colgroup>
|
|2|Emerald|
|
||||||
<thead>
|
|3|Teal (Viridian)|
|
||||||
<tr class="header">
|
|4|Cyan (Blue)|
|
||||||
<th>Value</th>
|
|5|Cobalt|
|
||||||
<th>Description</th>
|
|6|Indigo|
|
||||||
</tr>
|
|7|Violet (Purple)|
|
||||||
</thead>
|
|8|Pink|
|
||||||
<tbody>
|
|9|Magenta|
|
||||||
<tr class="odd">
|
|10|Crimson|
|
||||||
<td><p><strong>0</strong></p></td>
|
|11|Red|
|
||||||
<td><p>Lime</p></td>
|
|12|Orange (Mango)|
|
||||||
</tr>
|
|13|Amber|
|
||||||
<tr class="even">
|
|14|Yellow|
|
||||||
<td><p><strong>1</strong></p></td>
|
|15|Brown|
|
||||||
<td><p>Green</p></td>
|
|16|Olive|
|
||||||
</tr>
|
|17|Steel|
|
||||||
<tr class="odd">
|
|18|Mauve|
|
||||||
<td><p><strong>2</strong></p></td>
|
|19|Sienna|
|
||||||
<td><p>Emerald</p></td>
|
|101 through 104|Optional colors, as defined by the OEM|
|
||||||
</tr>
|
|151|Custom accent color for Enterprise|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>3</strong></p></td>
|
|
||||||
<td><p>Teal (Viridian)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>4</strong></p></td>
|
|
||||||
<td><p>Cyan (Blue)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>5</strong></p></td>
|
|
||||||
<td><p>Cobalt</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>6</strong></p></td>
|
|
||||||
<td><p>Indigo</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>7</strong></p></td>
|
|
||||||
<td><p>Violet (Purple)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>8</strong></p></td>
|
|
||||||
<td><p>Pink</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>9</strong></p></td>
|
|
||||||
<td><p>Magenta</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>10</strong></p></td>
|
|
||||||
<td><p>Crimson</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>11</strong></p></td>
|
|
||||||
<td><p>Red</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>12</strong></p></td>
|
|
||||||
<td><p>Orange (Mango)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>13</strong></p></td>
|
|
||||||
<td><p>Amber</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>14</strong></p></td>
|
|
||||||
<td><p>Yellow</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>15</strong></p></td>
|
|
||||||
<td><p>Brown</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>16</strong></p></td>
|
|
||||||
<td><p>Olive</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>17</strong></p></td>
|
|
||||||
<td><p>Steel</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>18</strong></p></td>
|
|
||||||
<td><p>Mauve</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>19</strong></p></td>
|
|
||||||
<td><p>Sienna</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>101</strong> through <strong>104</strong></p></td>
|
|
||||||
<td><p>Optional colors, as defined by the OEM</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>151</strong></p></td>
|
|
||||||
<td><p>Custom accent color for Enterprise</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Supported operations are Get and Replace.
|
Supported operations are Get and Replace.
|
||||||
|
|
||||||
@ -758,440 +681,119 @@ An integer that specifies the time zone of the device. The following table shows
|
|||||||
|
|
||||||
Supported operations are Get and Replace.
|
Supported operations are Get and Replace.
|
||||||
|
|
||||||
<table>
|
|Value|Time zone|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="20%" />
|
|0|UTC-12 International Date Line West|
|
||||||
<col width="80%" />
|
|100|UTC+13 Samoa|
|
||||||
</colgroup>
|
|110|UTC-11 Coordinated Universal Time-11|
|
||||||
<thead>
|
|200|UTC-10 Hawaii|
|
||||||
<tr class="header">
|
|300|UTC-09 Alaska|
|
||||||
<th>Value</th>
|
|400|UTC-08 Pacific Time (US & Canada)|
|
||||||
<th>Time zone</th>
|
|410|UTC-08 Baja California|
|
||||||
</tr>
|
|500|UTC-07 Mountain Time (US & Canada)|
|
||||||
</thead>
|
|510|UTC-07 Chihuahua, La Paz, Mazatlan|
|
||||||
<tbody>
|
|520|UTC-07 Arizona|
|
||||||
<tr class="odd">
|
|600|UTC-06 Saskatchewan|
|
||||||
<td><p><strong>0</strong></p></td>
|
|610|UTC-06 Central America|
|
||||||
<td><p>UTC-12 International Date Line West</p></td>
|
|620|UTC-06 Central Time (US & Canada)|
|
||||||
</tr>
|
|630|UTC-06 Guadalajara, Mexico City, Monterrey|
|
||||||
<tr class="even">
|
|700|UTC-05 Eastern Time (US & Canada)|
|
||||||
<td><p><strong>100</strong></p></td>
|
|710|UTC-05 Bogota, Lima, Quito|
|
||||||
<td><p>UTC+13 Samoa</p></td>
|
|720|UTC-05 Indiana (East)|
|
||||||
</tr>
|
|800|UTC-04 Atlantic Time (Canada)|
|
||||||
<tr class="odd">
|
|810|UTC-04 Cuiaba|
|
||||||
<td><p><strong>110</strong></p></td>
|
|820|UTC-04 Santiago|
|
||||||
<td><p>UTC-11 Coordinated Universal Time-11</p></td>
|
|830|UTC-04 Georgetown, La Paz, Manaus, San Juan|
|
||||||
</tr>
|
|840|UTC-04 Caracas|
|
||||||
<tr class="even">
|
|850|UTC-04 Asuncion|
|
||||||
<td><p><strong>200</strong></p></td>
|
|900|UTC-03:30 Newfoundland|
|
||||||
<td><p>UTC-10 Hawaii</p></td>
|
|910|UTC-03 Brasilia|
|
||||||
</tr>
|
|920|UTC-03 Greenland|
|
||||||
<tr class="odd">
|
|930|UTC-03 Montevideo|
|
||||||
<td><p><strong>300</strong></p></td>
|
|940|UTC-03 Cayenne, Fortaleza|
|
||||||
<td><p>UTC-09 Alaska</p></td>
|
|950|UTC-03 Buenos Aires|
|
||||||
</tr>
|
|960|UTC-03 Salvador|
|
||||||
<tr class="even">
|
|1000|UTC-02 Mid-Atlantic|
|
||||||
<td><p><strong>400</strong></p></td>
|
|1010|UTC-02 Coordinated Universal Time-02|
|
||||||
<td><p>UTC-08 Pacific Time (US & Canada)</p></td>
|
|1100|UTC-01 Azores|
|
||||||
</tr>
|
|1110|UTC-01 Cabo Verde|
|
||||||
<tr class="odd">
|
|1200|UTC Dublin, Edinburgh, Lisbon, London|
|
||||||
<td><p><strong>410</strong></p></td>
|
|1210|UTC Monrovia, Reykjavik|
|
||||||
<td><p>UTC-08 Baja California</p></td>
|
|1220|UTC Casablanca|
|
||||||
</tr>
|
|1230|UTC Coordinated Universal Time|
|
||||||
<tr class="even">
|
|1300|UTC+01 Belgrade, Bratislava, Budapest, Ljubljana, Prague|
|
||||||
<td><p><strong>500</strong></p></td>
|
|1310|UTC+01 Sarajevo, Skopje, Warsaw, Zagreb|
|
||||||
<td><p>UTC-07 Mountain Time (US & Canada)</p></td>
|
|1320|UTC+01 Brussels, Copenhagen, Madrid, Paris|
|
||||||
</tr>
|
|1330|UTC+01 West Central Africa|
|
||||||
<tr class="odd">
|
|1340|UTC+01 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna|
|
||||||
<td><p><strong>510</strong></p></td>
|
|1350|UTC+01 Windhoek|
|
||||||
<td><p>UTC-07 Chihuahua, La Paz, Mazatlan</p></td>
|
|1360|UTC+01 Tripoli|
|
||||||
</tr>
|
|1400|UTC+02 E. Europe|
|
||||||
<tr class="even">
|
|1410|UTC+02 Cairo|
|
||||||
<td><p><strong>520</strong></p></td>
|
|1420|UTC+02 Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius|
|
||||||
<td><p>UTC-07 Arizona</p></td>
|
|1430|UTC+02 Athens, Bucharest|
|
||||||
</tr>
|
|1440|UTC+02 Jerusalem|
|
||||||
<tr class="odd">
|
|1450|UTC+02 Amman|
|
||||||
<td><p><strong>600</strong></p></td>
|
|1460|UTC+02 Beirut|
|
||||||
<td><p>UTC-06 Saskatchewan</p></td>
|
|1470|UTC+02 Harare, Pretoria|
|
||||||
</tr>
|
|1480|UTC+02 Damascus|
|
||||||
<tr class="even">
|
|1490|UTC+02 Istanbul|
|
||||||
<td><p><strong>610</strong></p></td>
|
|1500|UTC+03 Kuwait, Riyadh|
|
||||||
<td><p>UTC-06 Central America</p></td>
|
|1510|UTC+03 Baghdad|
|
||||||
</tr>
|
|1520|UTC+03 Nairobi|
|
||||||
<tr class="odd">
|
|1530|UTC+03 Kaliningrad, Minsk|
|
||||||
<td><p><strong>620</strong></p></td>
|
|1540|UTC+04 Moscow, St. Petersburg, Volgograd|
|
||||||
<td><p>UTC-06 Central Time (US & Canada)</p></td>
|
|1550|UTC+03 Tehran|
|
||||||
</tr>
|
|1600|UTC+04 Abu Dhabi, Muscat|
|
||||||
<tr class="even">
|
|1610|UTC+04 Baku|
|
||||||
<td><p><strong>630</strong></p></td>
|
|1620|UTC+04 Yerevan|
|
||||||
<td><p>UTC-06 Guadalajara, Mexico City, Monterrey</p></td>
|
|1630|UTC+04 Kabul|
|
||||||
</tr>
|
|1640|UTC+04 Tbilisi|
|
||||||
<tr class="odd">
|
|1650|UTC+04 Port Louis|
|
||||||
<td><p><strong>700</strong></p></td>
|
|1700|UTC+06 Ekaterinburg|
|
||||||
<td><p>UTC-05 Eastern Time (US & Canada)</p></td>
|
|1710|UTC+05 Tashkent|
|
||||||
</tr>
|
|1720|UTC+05 Chennai, Kolkata, Mumbai, New Delhi|
|
||||||
<tr class="even">
|
|1730|UTC+05 Sri Jayawardenepura|
|
||||||
<td><p><strong>710</strong></p></td>
|
|1740|UTC+05 Kathmandu|
|
||||||
<td><p>UTC-05 Bogota, Lima, Quito</p></td>
|
|1750|UTC+05 Islamabad, Karachi|
|
||||||
</tr>
|
|1800|UTC+06 Astana|
|
||||||
<tr class="odd">
|
|1810|UTC+07 Novosibirsk|
|
||||||
<td><p><strong>720</strong></p></td>
|
|1820|UTC+06 Yangon (Rangoon)|
|
||||||
<td><p>UTC-05 Indiana (East)</p></td>
|
|1830|UTC+06 Dhaka|
|
||||||
</tr>
|
|1900|UTC+08 Krasnoyarsk|
|
||||||
<tr class="even">
|
|1910|UTC+07 Bangkok, Hanoi, Jakarta|
|
||||||
<td><p><strong>800</strong></p></td>
|
|1900|UTC+08 Krasnoyarsk|
|
||||||
<td><p>UTC-04 Atlantic Time (Canada)</p></td>
|
|2000|UTC+08 Beijing, Chongqing, Hong Kong SAR, Urumqi|
|
||||||
</tr>
|
|2010|UTC+09 Irkutsk|
|
||||||
<tr class="odd">
|
|2020|UTC+08 Kuala Lumpur, Singapore|
|
||||||
<td><p><strong>810</strong></p></td>
|
|2030|UTC+08 Taipei|
|
||||||
<td><p>UTC-04 Cuiaba</p></td>
|
|2040|UTC+08 Perth|
|
||||||
</tr>
|
|2050|UTC+08 Ulaanbaatar|
|
||||||
<tr class="even">
|
|2100|UTC+09 Seoul|
|
||||||
<td><p><strong>820</strong></p></td>
|
|2110|UTC+09 Osaka, Sapporo, Tokyo|
|
||||||
<td><p>UTC-04 Santiago</p></td>
|
|2120|UTC+10 Yakutsk|
|
||||||
</tr>
|
|2130|UTC+09 Darwin|
|
||||||
<tr class="odd">
|
|2140|UTC+09 Adelaide|
|
||||||
<td><p><strong>830</strong></p></td>
|
|2200|UTC+10 Canberra, Melbourne, Sydney|
|
||||||
<td><p>UTC-04 Georgetown, La Paz, Manaus, San Juan</p></td>
|
|2210|UTC+10 Brisbane|
|
||||||
</tr>
|
|2220|UTC+10 Hobart|
|
||||||
<tr class="even">
|
|2230|UTC+11 Vladivostok|
|
||||||
<td><p><strong>840</strong></p></td>
|
|2240|UTC+10 Guam, Port Moresby|
|
||||||
<td><p>UTC-04 Caracas</p></td>
|
|2300|UTC+11 Solomon Is., New Caledonia|
|
||||||
</tr>
|
|2310|UTC+12 Magadan|
|
||||||
<tr class="odd">
|
|2400|UTC+12 Fiji|
|
||||||
<td><p><strong>850</strong></p></td>
|
|2410|UTC+12 Auckland, Wellington|
|
||||||
<td><p>UTC-04 Asuncion</p></td>
|
|2420|UTC+12 Petropavlovsk-Kamchatsky|
|
||||||
</tr>
|
|2430|UTC+12 Coordinated Universal Time +12|
|
||||||
<tr class="even">
|
|2500|UTC+13 Nuku'alofa|
|
||||||
<td><p><strong>900</strong></p></td>
|
|
||||||
<td><p>UTC-03:30 Newfoundland</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>910</strong></p></td>
|
|
||||||
<td><p>UTC-03 Brasilia</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>920</strong></p></td>
|
|
||||||
<td><p>UTC-03 Greenland</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>930</strong></p></td>
|
|
||||||
<td><p>UTC-03 Montevideo</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>940</strong></p></td>
|
|
||||||
<td><p>UTC-03 Cayenne, Fortaleza</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>950</strong></p></td>
|
|
||||||
<td><p>UTC-03 Buenos Aires</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>960</strong></p></td>
|
|
||||||
<td><p>UTC-03 Salvador</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1000</strong></p></td>
|
|
||||||
<td><p>UTC-02 Mid-Atlantic</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1010</strong></p></td>
|
|
||||||
<td><p>UTC-02 Coordinated Universal Time-02</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1100</strong></p></td>
|
|
||||||
<td><p>UTC-01 Azores</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1110</strong></p></td>
|
|
||||||
<td><p>UTC-01 Cabo Verde</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1200</strong></p></td>
|
|
||||||
<td><p>UTC Dublin, Edinburgh, Lisbon, London</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1210</strong></p></td>
|
|
||||||
<td><p>UTC Monrovia, Reykjavik</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1220</strong></p></td>
|
|
||||||
<td><p>UTC Casablanca</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1230</strong></p></td>
|
|
||||||
<td><p>UTC Coordinated Universal Time</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1300</strong></p></td>
|
|
||||||
<td><p>UTC+01 Belgrade, Bratislava, Budapest, Ljubljana, Prague</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1310</strong></p></td>
|
|
||||||
<td><p>UTC+01 Sarajevo, Skopje, Warsaw, Zagreb</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1320</strong></p></td>
|
|
||||||
<td><p>UTC+01 Brussels, Copenhagen, Madrid, Paris</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1330</strong></p></td>
|
|
||||||
<td><p>UTC+01 West Central Africa</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1340</strong></p></td>
|
|
||||||
<td><p>UTC+01 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1350</strong></p></td>
|
|
||||||
<td><p>UTC+01 Windhoek</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1360</strong></p></td>
|
|
||||||
<td><p>UTC+01 Tripoli</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1400</strong></p></td>
|
|
||||||
<td><p>UTC+02 E. Europe</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1410</strong></p></td>
|
|
||||||
<td><p>UTC+02 Cairo</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1420</strong></p></td>
|
|
||||||
<td><p>UTC+02 Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1430</strong></p></td>
|
|
||||||
<td><p>UTC+02 Athens, Bucharest</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1440</strong></p></td>
|
|
||||||
<td><p>UTC+02 Jerusalem</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1450</strong></p></td>
|
|
||||||
<td><p>UTC+02 Amman</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1460</strong></p></td>
|
|
||||||
<td><p>UTC+02 Beirut</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1470</strong></p></td>
|
|
||||||
<td><p>UTC+02 Harare, Pretoria</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1480</strong></p></td>
|
|
||||||
<td><p>UTC+02 Damascus</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1490</strong></p></td>
|
|
||||||
<td><p>UTC+02 Istanbul</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1500</strong></p></td>
|
|
||||||
<td><p>UTC+03 Kuwait, Riyadh</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1510</strong></p></td>
|
|
||||||
<td><p>UTC+03 Baghdad</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1520</strong></p></td>
|
|
||||||
<td><p>UTC+03 Nairobi</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1530</strong></p></td>
|
|
||||||
<td><p>UTC+03 Kaliningrad, Minsk</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1540</strong></p></td>
|
|
||||||
<td><p>UTC+04 Moscow, St. Petersburg, Volgograd</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1550</strong></p></td>
|
|
||||||
<td><p>UTC+03 Tehran</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1600</strong></p></td>
|
|
||||||
<td><p>UTC+04 Abu Dhabi, Muscat</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1610</strong></p></td>
|
|
||||||
<td><p>UTC+04 Baku</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1620</strong></p></td>
|
|
||||||
<td><p>UTC+04 Yerevan</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1630</strong></p></td>
|
|
||||||
<td><p>UTC+04 Kabul</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1640</strong></p></td>
|
|
||||||
<td><p>UTC+04 Tbilisi</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1650</strong></p></td>
|
|
||||||
<td><p>UTC+04 Port Louis</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1700</strong></p></td>
|
|
||||||
<td><p>UTC+06 Ekaterinburg</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1710</strong></p></td>
|
|
||||||
<td><p>UTC+05 Tashkent</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1720</strong></p></td>
|
|
||||||
<td><p>UTC+05 Chennai, Kolkata, Mumbai, New Delhi</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1730</strong></p></td>
|
|
||||||
<td><p>UTC+05 Sri Jayawardenepura</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1740</strong></p></td>
|
|
||||||
<td><p>UTC+05 Kathmandu</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1750</strong></p></td>
|
|
||||||
<td><p>UTC+05 Islamabad, Karachi</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1800</strong></p></td>
|
|
||||||
<td><p>UTC+06 Astana</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1810</strong></p></td>
|
|
||||||
<td><p>UTC+07 Novosibirsk</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1820</strong></p></td>
|
|
||||||
<td><p>UTC+06 Yangon (Rangoon)</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1830</strong></p></td>
|
|
||||||
<td><p>UTC+06 Dhaka</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1900</strong></p></td>
|
|
||||||
<td><p>UTC+08 Krasnoyarsk</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>1910</strong></p></td>
|
|
||||||
<td><p>UTC+07 Bangkok, Hanoi, Jakarta</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>1900</strong></p></td>
|
|
||||||
<td><p>UTC+08 Krasnoyarsk</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2000</strong></p></td>
|
|
||||||
<td><p>UTC+08 Beijing, Chongqing, Hong Kong SAR, Urumqi</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2010</strong></p></td>
|
|
||||||
<td><p>UTC+09 Irkutsk</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2020</strong></p></td>
|
|
||||||
<td><p>UTC+08 Kuala Lumpur, Singapore</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2030</strong></p></td>
|
|
||||||
<td><p>UTC+08 Taipei</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2040</strong></p></td>
|
|
||||||
<td><p>UTC+08 Perth</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2050</strong></p></td>
|
|
||||||
<td><p>UTC+08 Ulaanbaatar</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2100</strong></p></td>
|
|
||||||
<td><p>UTC+09 Seoul</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2110</strong></p></td>
|
|
||||||
<td><p>UTC+09 Osaka, Sapporo, Tokyo</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2120</strong></p></td>
|
|
||||||
<td><p>UTC+10 Yakutsk</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2130</strong></p></td>
|
|
||||||
<td><p>UTC+09 Darwin</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2140</strong></p></td>
|
|
||||||
<td><p>UTC+09 Adelaide</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2200</strong></p></td>
|
|
||||||
<td><p>UTC+10 Canberra, Melbourne, Sydney</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2210</strong></p></td>
|
|
||||||
<td><p>UTC+10 Brisbane</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2220</strong></p></td>
|
|
||||||
<td><p>UTC+10 Hobart</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2230</strong></p></td>
|
|
||||||
<td><p>UTC+11 Vladivostok</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2240</strong></p></td>
|
|
||||||
<td><p>UTC+10 Guam, Port Moresby</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2300</strong></p></td>
|
|
||||||
<td><p>UTC+11 Solomon Is., New Caledonia</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2310</strong></p></td>
|
|
||||||
<td><p>UTC+12 Magadan</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2400</strong></p></td>
|
|
||||||
<td><p>UTC+12 Fiji</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2410</strong></p></td>
|
|
||||||
<td><p>UTC+12 Auckland, Wellington</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2420</strong></p></td>
|
|
||||||
<td><p>UTC+12 Petropavlovsk-Kamchatsky</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p><strong>2430</strong></p></td>
|
|
||||||
<td><p>UTC+12 Coordinated Universal Time +12</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p><strong>2500</strong></p></td>
|
|
||||||
<td><p>UTC+13 Nuku'alofa</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
<a href="" id="locale-language-"></a>**Locale/Language/**
|
<a href="" id="locale-language-"></a>**Locale/Language/**
|
||||||
The culture code that identifies the language to display on a device, and specifies the formatting of numbers, currencies, time, and dates. For language values, see [Locale IDs Assigned by Microsoft](/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c).
|
The culture code that identifies the language to display on a device, and specifies the formatting of numbers, currencies, time, and dates. For language values, see [Locale IDs Assigned by Microsoft](/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c).
|
||||||
|
|
||||||
The language setting is configured in the Default User profile only.
|
The language setting is configured in the Default User profile only.
|
||||||
|
|
||||||
> **Note** Apply the Locale ID only after the corresponding language packs are built into and supported for the OS image running on the device. The specified language will be applied as the phone language and a restart may be required.
|
> [!NOTE]
|
||||||
|
> Apply the Locale ID only after the corresponding language packs are built into and supported for the OS image running on the device. The specified language will be applied as the phone language and a restart may be required.
|
||||||
|
|
||||||
Supported operations are Get and Replace.
|
Supported operations are Get and Replace.
|
||||||
|
|
||||||
@ -1200,7 +802,8 @@ Supported operations are Get and Replace.
|
|||||||
|
|
||||||
The XML examples in this section show how to perform various tasks by using OMA client provisioning.
|
The XML examples in this section show how to perform various tasks by using OMA client provisioning.
|
||||||
|
|
||||||
> **Note** These examples are XML snippets and do not include all sections that are required for a complete lockdown XML file.
|
> [!NOTE]
|
||||||
|
> These examples are XML snippets and do not include all sections that are required for a complete lockdown XML file.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -1469,212 +1072,45 @@ The following example shows how to set the language.
|
|||||||
|
|
||||||
## <a href="" id="productid"></a>Product IDs in Windows 10 Mobile
|
## <a href="" id="productid"></a>Product IDs in Windows 10 Mobile
|
||||||
|
|
||||||
|
|
||||||
The following table lists the product ID and AUMID for each app that is included in Windows 10 Mobile.
|
The following table lists the product ID and AUMID for each app that is included in Windows 10 Mobile.
|
||||||
|
|
||||||
<table>
|
|App|Product ID|AUMID|
|
||||||
<colgroup>
|
|--- |--- |--- |
|
||||||
<col width="33%" />
|
|Alarms and clock|44F7D2B4-553D-4BEC-A8B7-634CE897ED5F|Microsoft.WindowsAlarms_8wekyb3d8bbwe!App|
|
||||||
<col width="33%" />
|
|Calculator|B58171C6-C70C-4266-A2E8-8F9C994F4456|Microsoft.WindowsCalculator_8wekyb3d8bbwe!App|
|
||||||
<col width="33%" />
|
|Camera|F0D8FEFD-31CD-43A1-A45A-D0276DB069F1|Microsoft.WindowsCamera_8wekyb3d8bbwe!App|
|
||||||
</colgroup>
|
|Contact Support|0DB5FCFF-4544-458A-B320-E352DFD9CA2B|Windows.ContactSupport_cw5n1h2txyewy!App|
|
||||||
<thead>
|
|Cortana|FD68DCF4-166F-4C55-A4CA-348020F71B94|Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI|
|
||||||
<tr class="header">
|
|Excel|EAD3E7C0-FAE6-4603-8699-6A448138F4DC|Microsoft.Office.Excel_8wekyb3d8bbwe!microsoft.excel|
|
||||||
<th>App</th>
|
|Facebook|82A23635-5BD9-DF11-A844-00237DE2DB9E|Microsoft.MSFacebook_8wekyb3d8bbwe!x82a236355bd9df11a84400237de2db9e|
|
||||||
<th>Product ID</th>
|
|File Explorer|C5E2524A-EA46-4F67-841F-6A9465D9D515|c5e2524a-ea46-4f67-841f-6a9465d9d515_cw5n1h2txyewy!App|
|
||||||
<th>AUMID</th>
|
|FM Radio|F725010E-455D-4C09-AC48-BCDEF0D4B626|N/A|
|
||||||
</tr>
|
|Get Started|B3726308-3D74-4A14-A84C-867C8C735C3C|Microsoft.Getstarted_8wekyb3d8bbwe!App|
|
||||||
</thead>
|
|Groove Music|D2B6A184-DA39-4C9A-9E0A-8B589B03DEC0|Microsoft.ZuneMusic_8wekyb3d8bbwe!Microsoft.ZuneMusic|
|
||||||
<tbody>
|
|Maps|ED27A07E-AF57-416B-BC0C-2596B622EF7D|Microsoft.WindowsMaps_8wekyb3d8bbwe!App|
|
||||||
<tr class="odd">
|
|Messaging|27E26F40-E031-48A6-B130-D1F20388991A|Microsoft.Messaging_8wekyb3d8bbwe!x27e26f40ye031y48a6yb130yd1f20388991ax|
|
||||||
<td>Alarms and clock</td>
|
|Microsoft Edge|395589FB-5884-4709-B9DF-F7D558663FFD|Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge|
|
||||||
<td>44F7D2B4-553D-4BEC-A8B7-634CE897ED5F</td>
|
|Money|1E0440F1-7ABF-4B9A-863D-177970EEFB5E|Microsoft.BingFinance_8wekyb3d8bbwe!AppexFinance|
|
||||||
<td>Microsoft.WindowsAlarms_8wekyb3d8bbwe!App</td>
|
|Movies and TV|6AFFE59E-0467-4701-851F-7AC026E21665|Microsoft.ZuneVideo_8wekyb3d8bbwe!Microsoft.ZuneVideo|
|
||||||
</tr>
|
|News|9C3E8CAD-6702-4842-8F61-B8B33CC9CAF1|Microsoft.BingNews_8wekyb3d8bbwe!AppexNews|
|
||||||
<tr class="even">
|
|OneDrive|AD543082-80EC-45BB-AA02-FFE7F4182BA8|Microsoft.MicrosoftSkydrive_8wekyb3d8bbwe!App|
|
||||||
<td>Calculator</td>
|
|OneNote|CA05B3AB-F157-450C-8C49-A1F127F5E71D|Microsoft.Office.OneNote_8wekyb3d8bbwe!microsoft.onenoteim|
|
||||||
<td>B58171C6-C70C-4266-A2E8-8F9C994F4456</td>
|
|Outlook Calendar|A558FEBA-85D7-4665-B5D8-A2FF9C19799B|Microsoft.WindowsCommunicationsApps_8wekyb3d8bbwe!Microsoft.WindowsLive.Calendar|
|
||||||
<td>Microsoft.WindowsCalculator_8wekyb3d8bbwe!App</td>
|
|Outlook Mail|A558FEBA-85D7-4665-B5D8-A2FF9C19799B|Microsoft.WindowsCommunicationsApps_8wekyb3d8bbwe!Microsoft.WindowsLive.Mail|
|
||||||
</tr>
|
|People|60BE1FB8-3291-4B21-BD39-2221AB166481|Microsoft.People_8wekyb3d8bbwe!xb94d6231y84ddy49a8yace3ybc955e769e85x|
|
||||||
<tr class="odd">
|
|Phone (dialer)|F41B5D0E-EE94-4F47-9CFE-3D3934C5A2C7|Microsoft.CommsPhone_8wekyb3d8bbwe!App|
|
||||||
<td>Camera</td>
|
|Photos|FCA55E1B-B9A4-4289-882F-084EF4145005|Microsoft.Windows.Photos_8wekyb3d8bbwe!App|
|
||||||
<td>F0D8FEFD-31CD-43A1-A45A-D0276DB069F1</td>
|
|Podcasts|C3215724-B279-4206-8C3E-61D1A9D63ED3|Microsoft.MSPodcast_8wekyb3d8bbwe!xc3215724yb279y4206y8c3ey61d1a9d63ed3x|
|
||||||
<td>Microsoft.WindowsCamera_8wekyb3d8bbwe!App</td>
|
|PowerPoint|B50483C4-8046-4E1B-81BA-590B24935798|Microsoft.Office.PowerPoint_8wekyb3d8bbwe!microsoft.pptim|
|
||||||
</tr>
|
|Settings|2A4E62D8-8809-4787-89F8-69D0F01654FB|2a4e62d8-8809-4787-89f8-69d0f01654fb_8wekyb3d8bbwe!App|
|
||||||
<tr class="even">
|
|Skype|C3F8E570-68B3-4D6A-BDBB-C0A3F4360A51|Microsoft.SkypeApp_kzf8qxf38zg5c!Skype.AppId|
|
||||||
<td>Contact Support</td>
|
|Skype Video|27E26F40-E031-48A6-B130-D1F20388991A|Microsoft.Messaging_8wekyb3d8bbwe!App|
|
||||||
<td>0DB5FCFF-4544-458A-B320-E352DFD9CA2B</td>
|
|Sports|0F4C8C7E-7114-4E1E-A84C-50664DB13B17|Microsoft.BingSports_8wekyb3d8bbwe!AppexSports|
|
||||||
<td>Windows.ContactSupport_cw5n1h2txyewy!App</td>
|
|Storage|5B04B775-356B-4AA0-AAF8-6491FFEA564D|N/A|
|
||||||
</tr>
|
|Store|7D47D89A-7900-47C5-93F2-46EB6D94C159|Microsoft.WindowsStore_8wekyb3d8bbwe!App|
|
||||||
<tr class="odd">
|
|Voice recorder|7311B9C5-A4E9-4C74-BC3C-55B06BA95AD0|Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe!App|
|
||||||
<td>Cortana</td>
|
|Wallet|587A4577-7868-4745-A29E-F996203F1462|Microsoft.MicrosoftWallet_8wekyb3d8bbwe!App|
|
||||||
<td>FD68DCF4-166F-4C55-A4CA-348020F71B94</td>
|
|Weather|63C2A117-8604-44E7-8CEF-DF10BE3A57C8|Microsoft.BingWeather_8wekyb3d8bbwe!App|
|
||||||
<td>Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI</td>
|
|Windows Feedback|7604089D-D13F-4A2D-9998-33FC02B63CE3|Microsoft.WindowsFeedback_8wekyb3d8bbwe!App|
|
||||||
</tr>
|
|Word|258F115C-48F4-4ADB-9A68-1387E634459B|Microsoft.Office.Word_8wekyb3d8bbwe!microsoft.word|
|
||||||
<tr class="even">
|
|Xbox|B806836F-EEBE-41C9-8669-19E243B81B83|Microsoft.XboxApp_8wekyb3d8bbwe!Microsoft.XboxApp|
|
||||||
<td>Excel</td>
|
|
||||||
<td>EAD3E7C0-FAE6-4603-8699-6A448138F4DC</td>
|
|
||||||
<td>Microsoft.Office.Excel_8wekyb3d8bbwe!microsoft.excel</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Facebook</td>
|
|
||||||
<td>82A23635-5BD9-DF11-A844-00237DE2DB9E</td>
|
|
||||||
<td>Microsoft.MSFacebook_8wekyb3d8bbwe!x82a236355bd9df11a84400237de2db9e</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>File Explorer</td>
|
|
||||||
<td>C5E2524A-EA46-4F67-841F-6A9465D9D515</td>
|
|
||||||
<td>c5e2524a-ea46-4f67-841f-6a9465d9d515_cw5n1h2txyewy!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>FM Radio</td>
|
|
||||||
<td>F725010E-455D-4C09-AC48-BCDEF0D4B626</td>
|
|
||||||
<td>N/A</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Get Started</td>
|
|
||||||
<td>B3726308-3D74-4A14-A84C-867C8C735C3C</td>
|
|
||||||
<td>Microsoft.Getstarted_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Groove Music</td>
|
|
||||||
<td>D2B6A184-DA39-4C9A-9E0A-8B589B03DEC0</td>
|
|
||||||
<td>Microsoft.ZuneMusic_8wekyb3d8bbwe!Microsoft.ZuneMusic</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Maps</td>
|
|
||||||
<td>ED27A07E-AF57-416B-BC0C-2596B622EF7D</td>
|
|
||||||
<td>Microsoft.WindowsMaps_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Messaging</td>
|
|
||||||
<td>27E26F40-E031-48A6-B130-D1F20388991A</td>
|
|
||||||
<td>Microsoft.Messaging_8wekyb3d8bbwe!x27e26f40ye031y48a6yb130yd1f20388991ax</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Microsoft Edge</td>
|
|
||||||
<td>395589FB-5884-4709-B9DF-F7D558663FFD</td>
|
|
||||||
<td>Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Money</td>
|
|
||||||
<td>1E0440F1-7ABF-4B9A-863D-177970EEFB5E</td>
|
|
||||||
<td>Microsoft.BingFinance_8wekyb3d8bbwe!AppexFinance</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Movies and TV</td>
|
|
||||||
<td>6AFFE59E-0467-4701-851F-7AC026E21665</td>
|
|
||||||
<td>Microsoft.ZuneVideo_8wekyb3d8bbwe!Microsoft.ZuneVideo</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>News</td>
|
|
||||||
<td>9C3E8CAD-6702-4842-8F61-B8B33CC9CAF1</td>
|
|
||||||
<td>Microsoft.BingNews_8wekyb3d8bbwe!AppexNews</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>OneDrive</td>
|
|
||||||
<td>AD543082-80EC-45BB-AA02-FFE7F4182BA8</td>
|
|
||||||
<td>Microsoft.MicrosoftSkydrive_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>OneNote</td>
|
|
||||||
<td>CA05B3AB-F157-450C-8C49-A1F127F5E71D</td>
|
|
||||||
<td>Microsoft.Office.OneNote_8wekyb3d8bbwe!microsoft.onenoteim</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Outlook Calendar</td>
|
|
||||||
<td><p>A558FEBA-85D7-4665-B5D8-A2FF9C19799B</p></td>
|
|
||||||
<td><p>Microsoft.WindowsCommunicationsApps_8wekyb3d8bbwe!Microsoft.WindowsLive.Calendar</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Outlook Mail</td>
|
|
||||||
<td><p>A558FEBA-85D7-4665-B5D8-A2FF9C19799B</p></td>
|
|
||||||
<td><p>Microsoft.WindowsCommunicationsApps_8wekyb3d8bbwe!Microsoft.WindowsLive.Mail</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>People</td>
|
|
||||||
<td>60BE1FB8-3291-4B21-BD39-2221AB166481</td>
|
|
||||||
<td>Microsoft.People_8wekyb3d8bbwe!xb94d6231y84ddy49a8yace3ybc955e769e85x</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Phone (dialer)</td>
|
|
||||||
<td>F41B5D0E-EE94-4F47-9CFE-3D3934C5A2C7</td>
|
|
||||||
<td>Microsoft.CommsPhone_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Photos</td>
|
|
||||||
<td>FCA55E1B-B9A4-4289-882F-084EF4145005</td>
|
|
||||||
<td>Microsoft.Windows.Photos_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Podcasts</td>
|
|
||||||
<td>C3215724-B279-4206-8C3E-61D1A9D63ED3</td>
|
|
||||||
<td>Microsoft.MSPodcast_8wekyb3d8bbwe!xc3215724yb279y4206y8c3ey61d1a9d63ed3x</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>PowerPoint</td>
|
|
||||||
<td>B50483C4-8046-4E1B-81BA-590B24935798</td>
|
|
||||||
<td>Microsoft.Office.PowerPoint_8wekyb3d8bbwe!microsoft.pptim</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Settings</td>
|
|
||||||
<td>2A4E62D8-8809-4787-89F8-69D0F01654FB</td>
|
|
||||||
<td>2a4e62d8-8809-4787-89f8-69d0f01654fb_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Skype</td>
|
|
||||||
<td>C3F8E570-68B3-4D6A-BDBB-C0A3F4360A51</td>
|
|
||||||
<td>Microsoft.SkypeApp_kzf8qxf38zg5c!Skype.AppId</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Skype Video</td>
|
|
||||||
<td>27E26F40-E031-48A6-B130-D1F20388991A</td>
|
|
||||||
<td>Microsoft.Messaging_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Sports</td>
|
|
||||||
<td>0F4C8C7E-7114-4E1E-A84C-50664DB13B17</td>
|
|
||||||
<td>Microsoft.BingSports_8wekyb3d8bbwe!AppexSports</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Storage</td>
|
|
||||||
<td>5B04B775-356B-4AA0-AAF8-6491FFEA564D</td>
|
|
||||||
<td>N/A</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Store</td>
|
|
||||||
<td>7D47D89A-7900-47C5-93F2-46EB6D94C159</td>
|
|
||||||
<td>Microsoft.WindowsStore_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Voice recorder</td>
|
|
||||||
<td>7311B9C5-A4E9-4C74-BC3C-55B06BA95AD0</td>
|
|
||||||
<td>Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Wallet</td>
|
|
||||||
<td>587A4577-7868-4745-A29E-F996203F1462</td>
|
|
||||||
<td>Microsoft.MicrosoftWallet_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Weather</td>
|
|
||||||
<td>63C2A117-8604-44E7-8CEF-DF10BE3A57C8</td>
|
|
||||||
<td>Microsoft.BingWeather_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Windows Feedback</td>
|
|
||||||
<td>7604089D-D13F-4A2D-9998-33FC02B63CE3</td>
|
|
||||||
<td>Microsoft.WindowsFeedback_8wekyb3d8bbwe!App</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Word</td>
|
|
||||||
<td>258F115C-48F4-4ADB-9A68-1387E634459B</td>
|
|
||||||
<td>Microsoft.Office.Word_8wekyb3d8bbwe!microsoft.word</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Xbox</td>
|
|
||||||
<td>B806836F-EEBE-41C9-8669-19E243B81B83</td>
|
|
||||||
<td>Microsoft.XboxApp_8wekyb3d8bbwe!Microsoft.XboxApp</td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
@ -30,7 +30,8 @@ To learn more about WIP, see the following articles:
|
|||||||
- [General guidance and best practices for Windows Information Protection (WIP)](/windows/security/information-protection/windows-information-protection/guidance-and-best-practices-wip)
|
- [General guidance and best practices for Windows Information Protection (WIP)](/windows/security/information-protection/windows-information-protection/guidance-and-best-practices-wip)
|
||||||
|
|
||||||
The following shows the EnterpriseDataProtection CSP in tree format.
|
The following shows the EnterpriseDataProtection CSP in tree format.
|
||||||
```
|
|
||||||
|
```console
|
||||||
./Device/Vendor/MSFT
|
./Device/Vendor/MSFT
|
||||||
EnterpriseDataProtection
|
EnterpriseDataProtection
|
||||||
----Settings
|
----Settings
|
||||||
@ -45,6 +46,7 @@ EnterpriseDataProtection
|
|||||||
--------EDPShowIcons
|
--------EDPShowIcons
|
||||||
----Status
|
----Status
|
||||||
```
|
```
|
||||||
|
|
||||||
<a href="" id="--device-vendor-msft-enterprisedataprotection"></a>**./Device/Vendor/MSFT/EnterpriseDataProtection**
|
<a href="" id="--device-vendor-msft-enterprisedataprotection"></a>**./Device/Vendor/MSFT/EnterpriseDataProtection**
|
||||||
The root node for the CSP.
|
The root node for the CSP.
|
||||||
|
|
||||||
@ -72,7 +74,6 @@ Changing the primary enterprise ID is not supported and may cause unexpected beh
|
|||||||
> The client requires domain name to be canonical, otherwise the setting will be rejected by the client.
|
> The client requires domain name to be canonical, otherwise the setting will be rejected by the client.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Here are the steps to create canonical domain names:
|
Here are the steps to create canonical domain names:
|
||||||
|
|
||||||
1. Transform the ASCII characters (A-Z only) to lowercase. For example, Microsoft.COM -> microsoft.com.
|
1. Transform the ASCII characters (A-Z only) to lowercase. For example, Microsoft.COM -> microsoft.com.
|
||||||
@ -112,7 +113,6 @@ The CSP checks the current edition and hardware support (TPM), and returns an er
|
|||||||
> This setting is only supported in Windows 10 Mobile.
|
> This setting is only supported in Windows 10 Mobile.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Supported operations are Add, Get, Replace, and Delete. Value type is integer.
|
Supported operations are Add, Get, Replace, and Delete. Value type is integer.
|
||||||
|
|
||||||
<a href="" id="settings-datarecoverycertificate"></a>**Settings/DataRecoveryCertificate**
|
<a href="" id="settings-datarecoverycertificate"></a>**Settings/DataRecoveryCertificate**
|
||||||
@ -124,7 +124,7 @@ Specifies a recovery certificate that can be used for data recovery of encrypted
|
|||||||
DRA information from MDM policy must be a serialized binary blob identical to what we expect from GP.
|
DRA information from MDM policy must be a serialized binary blob identical to what we expect from GP.
|
||||||
The binary blob is the serialized version of following structure:
|
The binary blob is the serialized version of following structure:
|
||||||
|
|
||||||
``` syntax
|
```cpp
|
||||||
//
|
//
|
||||||
// Recovery Policy Data Structures
|
// Recovery Policy Data Structures
|
||||||
//
|
//
|
||||||
@ -243,7 +243,6 @@ typedef enum _PUBLIC_KEY_SOURCE_TAG {
|
|||||||
EfsCertificate,
|
EfsCertificate,
|
||||||
EfsCertificateThumbprint
|
EfsCertificateThumbprint
|
||||||
} PUBLIC_KEY_SOURCE_TAG, *PPUBLIC_KEY_SOURCE_TAG;
|
} PUBLIC_KEY_SOURCE_TAG, *PPUBLIC_KEY_SOURCE_TAG;
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
For EFSCertificate KeyTag, it is expected to be a DER ENCODED binary certificate.
|
For EFSCertificate KeyTag, it is expected to be a DER ENCODED binary certificate.
|
||||||
@ -300,36 +299,9 @@ A read-only bit mask that indicates the current state of WIP on the Device. The
|
|||||||
|
|
||||||
Suggested values:
|
Suggested values:
|
||||||
|
|
||||||
<table>
|
|Reserved for future use|WIP mandatory settings<br>Set = 1<br>Not set = 0|Reserved for future use|AppLocker configured<br>Yes = 1<br>No = 0|WIP on = 1<br>WIP off = 0|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |--- |
|
||||||
<col width="20%" />
|
|4|3|2|1|0|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
</colgroup>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Reserved for future use</p></td>
|
|
||||||
<td><p>WIP mandatory settings</p>
|
|
||||||
<p>Set = 1</p>
|
|
||||||
<p>Not set = 0</p></td>
|
|
||||||
<td><p>Reserved for future use</p></td>
|
|
||||||
<td><p>AppLocker configured</p>
|
|
||||||
<p>Yes = 1</p>
|
|
||||||
<p>No = 0</p></td>
|
|
||||||
<td><p>WIP on = 1</p>
|
|
||||||
<p>WIP off = 0</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>4</p></td>
|
|
||||||
<td><p>3</p></td>
|
|
||||||
<td><p>2</p></td>
|
|
||||||
<td><p>1</p></td>
|
|
||||||
<td><p>0</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -259,41 +259,12 @@ The following table describes the fields in the previous sample:
|
|||||||
|
|
||||||
The following table describes the fields in the previous sample:
|
The following table describes the fields in the previous sample:
|
||||||
|
|
||||||
<table>
|
|Name|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Add|This is required to precede the Exec command.<li>CmdID - Input value used to reference the request. Responses includes this value, which can be use to match the request and response.<li>LocURI - Path to Win32 CSP command processor, including the Product ID (in this example, 1803A630-3C38-4D2B-9B9A-0CB37243539C) property escaped for XML formatting.|
|
||||||
<col width="50%" />
|
|Exec|The Exec node includes the parameters and properties requires to locate, download, validate and perform product installation.<li>CmdID - Input value used to reference the request. Responses will include this value which can be used to match request and response.<li>LocURI - Path to Win32 CSP command processor, including the Product ID (in this example, 1803A630-3C38-4D2B-9B9A-0CB37243539C) property escaped for XML formatting.<li>Data - The Data node contains an embedded XML, of type “MsiInstallJob”<li>MsiInstallJob - Contains all information required for the successful download, validation and execution of the MSI installation process (see section at the end of this document for details on this embedded data object).|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Name</th>
|
|
||||||
<th>Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Add</td>
|
|
||||||
<td>This is required to precede the Exec command.
|
|
||||||
<ul>
|
|
||||||
<li>CmdID - Input value used to reference the request. Responses includes this value, which can be use to match the request and response.</li>
|
|
||||||
<li>LocURI - Path to Win32 CSP command processor, including the Product ID (in this example, 1803A630-3C38-4D2B-9B9A-0CB37243539C) property escaped for XML formatting.</li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Exec</td>
|
|
||||||
<td>The Exec node includes the parameters and properties requires to locate, download, validate and perform product installation.
|
|
||||||
<ul>
|
|
||||||
<li>CmdID - Input value used to reference the request. Responses will include this value which can be used to match request and response.</li>
|
|
||||||
<li>LocURI - Path to Win32 CSP command processor, including the Product ID (in this example, 1803A630-3C38-4D2B-9B9A-0CB37243539C) property escaped for XML formatting.</li>
|
|
||||||
<li>Data - The Data node contains an embedded XML, of type “MsiInstallJob”</li>
|
|
||||||
<li>MsiInstallJob - Contains all information required for the successful download, validation and execution of the MSI installation process (see section at the end of this document for details on this embedded data object).</li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
> [!Note]
|
> [!Note]
|
||||||
> Information status on the MSI job will be reported using standard OMA-DM notification mechanism. The status reported is represented using standard MSIEXEC return codes as HRESULT as defined in the MSIEXEC topic on Microsoft TechNet at [Msiexec (command-line options)](https://technet.microsoft.com/library/cc759262%28v=ws.10%29.aspx).
|
> Information status on the MSI job will be reported using standard OMA-DM notification mechanism. The status reported is represented using standard MSIEXEC return codes as HRESULT as defined in the MSIEXEC topic on Microsoft TechNet at [Msiexec (command-line options)](https://technet.microsoft.com/library/cc759262%28v=ws.10%29.aspx).
|
||||||
|
|
||||||
@ -353,70 +324,20 @@ The following table describes the fields in the previous sample:
|
|||||||
|
|
||||||
The following table MsiInstallJob describes the schema elements.
|
The following table MsiInstallJob describes the schema elements.
|
||||||
|
|
||||||
<table>
|
|Element|Description|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|MsiInstallJob|root element<br>"Attribute: "id - the application identifier of the application being installed|
|
||||||
<col width="50%" />
|
|Product|child element of MsiInstallJob<br>Attribute: “Version” – string representation of application version|
|
||||||
</colgroup>
|
|Download|child element of Product. Container for download configuration information.|
|
||||||
<thead>
|
|ContentURLList|child element of Download. Contains list of 1 or more content download URL locators in the form of ContentURL elements.|
|
||||||
<tr class="header">
|
|ContentURL|Location content should be downloaded from. Must be a property formatted URL that points to the .MSI file.|
|
||||||
<th>Element</th>
|
|Validation|Contains information used to validate contend authenticity. • FileHash – SHA256 hash value of file content|
|
||||||
<th>Description</th>
|
|FileHash|SHA256 hash value of file content|
|
||||||
</tr>
|
|Enforcement|installation properties to be used when installing this MSI|
|
||||||
</thead>
|
|CommandLine|Command-line options to be used when calling MSIEXEC.exe|
|
||||||
<tbody>
|
|TimeOut|Amount of time, in minutes that the installation process can run before the installer considers the installation may have failed and no longer monitors the installation operation.|
|
||||||
<tr class="odd">
|
|RetryCount|The number of times the download and installation operation will be retried before the installation will be marked as failed.|
|
||||||
<td>MsiInstallJob</td>
|
|RetryInterval|Amount of time, in minutes between retry operations.|
|
||||||
<td>root element
|
|
||||||
<p>"Attribute: "id - the application identifier of the application being installed</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Product</td>
|
|
||||||
<td>child element of MsiInstallJob
|
|
||||||
<p>Attribute: “Version” – string representation of application version</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>Download</td>
|
|
||||||
<td>child element of Product. Container for download configuration information.</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>ContentURLList</td>
|
|
||||||
<td>child element of Download. Contains list of 1 or more content download URL locators in the form of ContentURL elements.</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>ContentURL</td>
|
|
||||||
<td>Location content should be downloaded from. Must be a property formatted URL that points to the .MSI file.</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Validation</td>
|
|
||||||
<td>Contains information used to validate contend authenticity. • FileHash – SHA256 hash value of file content</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>FileHash</td>
|
|
||||||
<td>SHA256 hash value of file content</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>Enforcement</td>
|
|
||||||
<td>installation properties to be used when installing this MSI</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>CommandLine</td>
|
|
||||||
<td>Command-line options to be used when calling MSIEXEC.exe</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>TimeOut</td>
|
|
||||||
<td>Amount of time, in minutes that the installation process can run before the installer considers the installation may have failed and no longer monitors the installation operation.</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>RetryCount</td>
|
|
||||||
<td>The number of times the download and installation operation will be retried before the installation will be marked as failed.</td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>RetryInterval</td>
|
|
||||||
<td>Amount of time, in minutes between retry operations.</td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -453,85 +374,17 @@ The following tables shows how app targeting and MSI package type (per-user, per
|
|||||||
|
|
||||||
For Intune standalone environment, the MSI package will determine the MSI execution context.
|
For Intune standalone environment, the MSI package will determine the MSI execution context.
|
||||||
|
|
||||||
<table>
|
|Target|Per-user MSI|Per-machine MSI|Dual mode MSI|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|User|Install the MSI per-user<br>LocURI contains a User prefix, such as ./User|Install the MSI per-device<br>LocURI contains a Device prefix, such as ./Device|Install the MSI per-user<br>LocURI contains a User prefix, such as ./User|
|
||||||
<col width="25%" />
|
|System|Install the MSI per-user<br>LocURI contains a User prefix, such as ./User|Install the MSI per-device<br>LocURI contains a Device prefix, such as ./Device|Install the MSI per-user<br>LocURI contains a User prefix, such as ./User|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Target</th>
|
|
||||||
<th>Per-user MSI</th>
|
|
||||||
<th>Per-machine MSI</th>
|
|
||||||
<th>Dual mode MSI</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>User</td>
|
|
||||||
<td>Install the MSI per-user
|
|
||||||
<p>LocURI contains a User prefix, such as ./User</p></td>
|
|
||||||
<td>Install the MSI per-device
|
|
||||||
<p>LocURI contains a Device prefix, such as ./Device</p></td>
|
|
||||||
<td>Install the MSI per-user
|
|
||||||
<p>LocURI contains a User prefix, such as ./User</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>System</td>
|
|
||||||
<td>Install the MSI per-user
|
|
||||||
<p>LocURI contains a User prefix, such as ./User</p></td>
|
|
||||||
<td>Install the MSI per-device
|
|
||||||
<p>LocURI contains a Device prefix, such as ./Device</p></td>
|
|
||||||
<td>Install the MSI per-user
|
|
||||||
<p>LocURI contains a User prefix, such as ./User</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The following table applies to SCCM hybrid environment.
|
The following table applies to SCCM hybrid environment.
|
||||||
|
|
||||||
<table>
|
|Target|Per-user MSI|Per-machine MSI|Dual mode MSI|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|User|Install the MSI per-user<br>LocURI contains a User prefix, such as ./User|Install the MSI per-device<br>LocURI contains a Device prefix, such as ./Device|Install the MSI per-user<br>LocURI contains a User prefix, such as ./User|
|
||||||
<col width="25%" />
|
|System|Install the MSI per-user<br>LocURI contains a User prefix, such as ./User|Install the MSI per-device<br>LocURI contains a Device prefix, such as ./Device|Install the MSI per- system context<br>LocURI contains a Device prefix, such as ./Device|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Target</th>
|
|
||||||
<th>Per-user MSI</th>
|
|
||||||
<th>Per-machine MSI</th>
|
|
||||||
<th>Dual mode MSI</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td>User</td>
|
|
||||||
<td>Install the MSI per-user
|
|
||||||
<p>LocURI contains a User prefix, such as ./User</p></td>
|
|
||||||
<td>Install the MSI per-device
|
|
||||||
<p>LocURI contains a Device prefix, such as ./Device</p></td>
|
|
||||||
<td>Install the MSI per-user
|
|
||||||
<p>LocURI contains a User prefix, such as ./User</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td>System</td>
|
|
||||||
<td>Install the MSI per-user
|
|
||||||
<p>LocURI contains a User prefix, such as ./User</p></td>
|
|
||||||
<td>Install the MSI per-device
|
|
||||||
<p>LocURI contains a Device prefix, such as ./Device</p></td>
|
|
||||||
<td>Install the MSI per- system context
|
|
||||||
<p>LocURI contains a Device prefix, such as ./Device</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## How to determine the package type from the MSI package
|
## How to determine the package type from the MSI package
|
||||||
|
|
||||||
|
@ -21,143 +21,34 @@ The **Get Inventory** operation retrieves information from the Microsoft Store f
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**GET:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</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?continuationToken={ContinuationToken}&modifiedSince={ModifiedSince}&licenseTypes={LicenseType}&maxResults={MaxResults}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
```http
|
||||||
|
https://bspmts.mp.microsoft.com/V1/Inventory?continuationToken={ContinuationToken}&modifiedSince={ModifiedSince}&licenseTypes={LicenseType}&maxResults={MaxResults}
|
||||||
|
```
|
||||||
### 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|Default value|Description|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |
|
||||||
<col width="25%" />
|
|continuationToken|string|Null||
|
||||||
<col width="25%" />
|
|modifiedSince|datetime|Null|Optional. Used to determine changes since a specific date.|
|
||||||
<col width="25%" />
|
|licenseTypes|collection of [LicenseType](data-structures-windows-store-for-business.md#licensetype)|{online,offline}|Optional. A collection of license types|
|
||||||
<col width="25%" />
|
|maxResults|integer-32|25|Optional. Specifies the maximum number of applications returned in a single query.|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Parameter</th>
|
|
||||||
<th>Type</th>
|
|
||||||
<th>Default value</th>
|
|
||||||
<th>Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>continuationToken</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Null</p></td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>modifiedSince</p></td>
|
|
||||||
<td><p>datetime</p></td>
|
|
||||||
<td><p>Null</p></td>
|
|
||||||
<td><p>Optional. Used to determine changes since a specific date.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>licenseTypes</p></td>
|
|
||||||
<td><p>collection of <a href="data-structures-windows-store-for-business.md#licensetype" data-raw-source="[LicenseType](data-structures-windows-store-for-business.md#licensetype)">LicenseType</a></p></td>
|
|
||||||
<td><p>{online,offline}</p></td>
|
|
||||||
<td><p>Optional. A collection of license types</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>maxResults</p></td>
|
|
||||||
<td><p>integer-32</p></td>
|
|
||||||
<td><p>25</p></td>
|
|
||||||
<td><p>Optional. Specifies the maximum number of applications returned in a single query.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Here are some examples.
|
Here are some examples.
|
||||||
|
|
||||||
<table>
|
|Query type|Example query|
|
||||||
<colgroup>
|
|--- |--- |
|
||||||
<col width="50%" />
|
|Online and offline|[https://bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=online&licenseTypes=offline&maxResults=25](https://bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=online&licenseTypes=offline&maxResults=25)|
|
||||||
<col width="50%" />
|
|Online only|[https://bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=online&maxResults=25](https://bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=online&maxResults=25)|
|
||||||
</colgroup>
|
|Offline only|[https://bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=offline&maxResults=25](https://bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=offline&maxResults=25)|
|
||||||
<thead>
|
|Both license types and a time filter|[https://bspmts.mp.microsoft.com/V1/Inventory?modifiedSince=2015-07-13T14%3a02%3a25.6863382-07%3a00&licenseTypes=online&licenseTypes=offline&maxResults=25](https://bspmts.mp.microsoft.com/V1/Inventory?modifiedSince=2015-07-13T14%3a02%3a25.6863382-07%3a00&licenseTypes=online&licenseTypes=offline&maxResults=25)|
|
||||||
<tr class="header">
|
|
||||||
<th>Query type</th>
|
|
||||||
<th>Example query</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Online and offline</p></td>
|
|
||||||
<td><p>https:<span></span>//bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=online&licenseTypes=offline&maxResults=25</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Online only</p></td>
|
|
||||||
<td><p>https:<span></span>//bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=online&maxResults=25</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>Offline only</p></td>
|
|
||||||
<td><p>https:<span></span>//bspmts.mp.microsoft.com/V1/Inventory?licenseTypes=offline&maxResults=25</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>Both license types and a time filter</p></td>
|
|
||||||
<td><p>https:<span></span>//bspmts.mp.microsoft.com/V1/Inventory?modifiedSince=2015-07-13T14%3a02%3a25.6863382-07%3a00&licenseTypes=online&licenseTypes=offline&maxResults=25</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<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>Invalid modified date, license, or continuationToken</p>
|
|
||||||
<p>Details: String</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|Error code|Description|Retry|Data field|
|
||||||
|
|--- |--- |--- |--- |
|
||||||
|
|400|Invalid parameters|No|Parameter name<br><br>Invalid modified date, license, or continuationToken<br><br>Details: String|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
|
|
||||||
|
@ -18,97 +18,27 @@ The **Get localized product details** operation retrieves the localization infor
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**GET:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
```http
|
||||||
<col width="50%" />
|
https://bspmts.mp.microsoft.com/V1/Products/{ProductId}/{SkuId}/LocalizedDetails/{language}
|
||||||
</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/Products/{ProductId}/{SkuId}/LocalizedDetails/{language}</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%" />
|
|language|string|Required. Language in ISO format, such as en-us, en-ca.|
|
||||||
</colgroup>
|
|
||||||
<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>language</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Required. Language in ISO format, such as en-us, en-ca.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|Error code|Description|Retry|Data field|
|
||||||
<table>
|
|--- |--- |--- |--- |
|
||||||
<colgroup>
|
|400|Invalid parameters|No|Parameter name<br>Reason: Missing parameter or invalid parameter<br>Details: String|
|
||||||
<col width="25%" />
|
|404|Not found||Item type: productId, skuId, language|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<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><p>Item type: productId, skuId, language</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
|
|
||||||
|
@ -18,102 +18,27 @@ The **Get offline license** operation retrieves the offline license information
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**POST:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
```http
|
||||||
<col width="50%" />
|
https://bspmts.mp.microsoft.com/V1/Products/{productId}/{skuId}/OfflineLicense/{contentId}
|
||||||
</colgroup>
|
```
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Method</th>
|
|
||||||
<th>Request URI</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>POST</p></td>
|
|
||||||
<td><p>https://bspmts.mp.microsoft.com/V1/Products/{productId}/{skuId}/OfflineLicense/{contentId}</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. Identifies a specific product that has been acquired.|
|
||||||
<col width="33%" />
|
|skuId|string|Required. The SKU identifier.|
|
||||||
<col width="33%" />
|
|contentId|string|Required. Identifies a specific application.|
|
||||||
</colgroup>
|
|
||||||
<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. Identifies a specific product that has been acquired.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>skuId</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Required. The SKU identifier.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>contentId</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Required. Identifies a specific application.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<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 owned, Not offline</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|Error code|Description|Retry|Data field|
|
||||||
|
|--- |--- |--- |--- |
|
||||||
|
|400|Invalid parameters|No|Parameter name<br>Reason: Missing parameter or invalid parameter<br>Details: String|
|
||||||
|
|404|Not found|||
|
||||||
|
|409|Conflict||Reason: Not owned, Not offline|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
|
|
||||||
|
@ -18,92 +18,26 @@ The **Get product details** operation retrieves the product information from the
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**GET:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</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/Products/{productId}/{skuId}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
```http
|
||||||
|
https://bspmts.mp.microsoft.com/V1/Products/{productId}/{skuId}
|
||||||
|
```
|
||||||
|
|
||||||
### 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%" />
|
|
||||||
</colgroup>
|
|
||||||
<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>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|Error code|Description|Retry|Data field|
|
||||||
|
|--- |--- |--- |--- |
|
||||||
|
|400|Invalid parameters|No|Parameter name<br>Reason: Missing parameter or invalid parameter<br>Details: String|
|
||||||
|
|404|Not found|||
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<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>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
|
|
||||||
### Response body
|
### Response body
|
||||||
|
@ -18,108 +18,27 @@ The **Get product package** operation retrieves the information about a specific
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**GET:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</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/Products/{productId}/{skuId}/Packages/{packageId}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
```http
|
||||||
|
https://bspmts.mp.microsoft.com/V1/Products/{productId}/{skuId}/Packages/{packageId}
|
||||||
|
```
|
||||||
|
|
||||||
### 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%" />
|
|packageId|string|Required.|
|
||||||
</colgroup>
|
|
||||||
<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>packageId</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Required.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Error code</th>
|
|
||||||
<th>Description</th>
|
|
||||||
<th>Retry</th>
|
|
||||||
<th>Data field</th>
|
|
||||||
<th>Details</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: Invalid parameter</p>
|
|
||||||
<p>Details: String</p></td>
|
|
||||||
<td><p>Can be productId, skuId, or packageId</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>404</p></td>
|
|
||||||
<td><p>Not found</p></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td><p>Item type: Product/SKU</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>409</p></td>
|
|
||||||
<td><p>Conflict</p></td>
|
|
||||||
<td></td>
|
|
||||||
<td><p>Reason: Not owned</p></td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|Error code|Description|Retry|Data field|Details|
|
||||||
|
|--- |--- |--- |--- |--- |
|
||||||
|
|400|Invalid parameters|No|Parameter name <br/> <br/>Reason: Invalid parameter <br/> <br/>Details: String|Can be productId, skuId, or packageId|
|
||||||
|
|404|Not found|||Item type: Product/SKU|
|
||||||
|
|409|Conflict||Reason: Not owned||
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
|
|
||||||
|
@ -18,97 +18,27 @@ The **Get product packages** operation retrieves the information about applicati
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**GET:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
```http
|
||||||
<col width="50%" />
|
https://bspmts.mp.microsoft.com/V1/Products/{productId}/{skuId}/Packages
|
||||||
</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/Products/{productId}/{skuId}/Packages</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%" />
|
|
||||||
</colgroup>
|
|
||||||
<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>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<col width="25%" />
|
|
||||||
<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 owned</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|Error code|Description|Retry|Data field|
|
||||||
|
|--- |--- |--- |--- |
|
||||||
|
|400|Invalid parameters|No|Parameter name <br/> <br/>Reason: Missing parameter or invalid parameter <br/> <br/>Details: String|
|
||||||
|
|404|Not found|||
|
||||||
|
|409|Conflict||Reason: Not owned|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
|
|
||||||
|
@ -18,61 +18,21 @@ The **Get seat** operation retrieves the information about an active seat for a
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**GET:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</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/{username}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
```http
|
||||||
|
https://bspmts.mp.microsoft.com/V1/Inventory/{productId}/{skuId}/Seats/{username}
|
||||||
|
```
|
||||||
|
|
||||||
### 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%" />
|
|username|string|Requires UserPrincipalName (UPN). User name of the target user account.|
|
||||||
</colgroup>
|
|
||||||
<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>username</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Requires UserPrincipalName (UPN). User name of the target user account.</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
@ -81,56 +41,8 @@ The following parameters may be specified in the request URI.
|
|||||||
|
|
||||||
The response body contains [SeatDetails](data-structures-windows-store-for-business.md#seatdetails).
|
The response body contains [SeatDetails](data-structures-windows-store-for-business.md#seatdetails).
|
||||||
|
|
||||||
<table>
|
|Error code|Description|Retry|Data field|Details|
|
||||||
<colgroup>
|
|--- |--- |--- |--- |--- |
|
||||||
<col width="20%" />
|
|400|Invalid parameters|No|Parameter name <br/><br/>Reason: Missing parameter or invalid parameter<br/><br/>Details: String|Invalid can include productId, skuId or username|
|
||||||
<col width="20%" />
|
|404|Not found|||ItemType: Inventory, User, Seat<br/><br/>Values: ProductId/SkuId, UserName, ProductId/SkuId/Username|
|
||||||
<col width="20%" />
|
|409|Conflict||Reason: Not online||
|
||||||
<col width="20%" />
|
|
||||||
<col width="20%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Error code</th>
|
|
||||||
<th>Description</th>
|
|
||||||
<th>Retry</th>
|
|
||||||
<th>Data field</th>
|
|
||||||
<th>Details</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>
|
|
||||||
<td><p>Invalid can include productId, skuId or username</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>404</p></td>
|
|
||||||
<td><p>Not found</p></td>
|
|
||||||
<td></td>
|
|
||||||
<td></td>
|
|
||||||
<td><p>ItemType: Inventory, User, Seat</p>
|
|
||||||
<p>Values: ProductId/SkuId, UserName, ProductId/SkuId/Username</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>409</p></td>
|
|
||||||
<td><p>Conflict</p></td>
|
|
||||||
<td></td>
|
|
||||||
<td><p>Reason: Not online</p></td>
|
|
||||||
<td></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -18,61 +18,21 @@ The **Get seats assigned to a user** operation retrieves information about assig
|
|||||||
|
|
||||||
## Request
|
## Request
|
||||||
|
|
||||||
<table>
|
**GET:**
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</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:<span></span>//bspmts.mp.microsoft.com/V1/Users/{username}/Seats?continuationToken={ContinuationToken}&maxResults={MaxResults}</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
```http
|
||||||
|
https:<span></span>//bspmts.mp.microsoft.com/V1/Users/{username}/Seats?continuationToken={ContinuationToken}&maxResults={MaxResults}
|
||||||
|
```
|
||||||
|
|
||||||
### 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%" />
|
|useName|string|Requires UserPrincipalName (UPN). User name of the target user account.|
|
||||||
<col width="33%" />
|
|continuationToken|string|Optional.|
|
||||||
<col width="33%" />
|
|maxResults|inteter-32|Optional. Default = 25, Maximum = 100|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th>Parameter</th>
|
|
||||||
<th>Type</th>
|
|
||||||
<th>Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>useName</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Requires UserPrincipalName (UPN). User name of the target user account.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td><p>continuationToken</p></td>
|
|
||||||
<td><p>string</p></td>
|
|
||||||
<td><p>Optional.</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td><p>maxResults</p></td>
|
|
||||||
<td><p>inteter-32</p></td>
|
|
||||||
<td><p>Optional. Default = 25, Maximum = 100</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
## Response
|
## Response
|
||||||
@ -81,39 +41,10 @@ The following parameters may be specified in the request URI.
|
|||||||
|
|
||||||
The response body contain [SeatDetailsResultSet](data-structures-windows-store-for-business.md#seatdetailsresultset).
|
The response body contain [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><br>Reason: Invalid parameter<br><br>Details: String|
|
||||||
<col width="25%" />
|
|404|Not found||Item type: User<br><br>Values: UserName|
|
||||||
<col width="25%" />
|
|
||||||
<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: 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><p>Item type: User</p>
|
|
||||||
<p>Values: UserName</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
@ -23,7 +23,7 @@ If you have a file that you suspect might be malware or is being incorrectly det
|
|||||||
|
|
||||||
## How do I send a malware file to Microsoft?
|
## How do I send a malware file to Microsoft?
|
||||||
|
|
||||||
You can send us files that you think might be malware or files that have been incorrectly detected through the [sample submission portal](https://www.microsoft.com/wdsi/filesubmission).
|
You can send us files that you think might be malware or files that have been incorrectly detected through the [sample submission portal](https://www.microsoft.com/en-us/wdsi/filesubmission).
|
||||||
|
|
||||||
We receive a large number of samples from many sources. Our analysis is prioritized by the number of file detections and the type of submission. You can help us complete a quick analysis by providing detailed information about the product you were using and what you were doing when you found the file.
|
We receive a large number of samples from many sources. Our analysis is prioritized by the number of file detections and the type of submission. You can help us complete a quick analysis by providing detailed information about the product you were using and what you were doing when you found the file.
|
||||||
|
|
||||||
@ -31,7 +31,7 @@ After you sign in, you will be able to track your submissions.
|
|||||||
|
|
||||||
## Can I send a sample by email?
|
## Can I send a sample by email?
|
||||||
|
|
||||||
No, we only accept submissions through our [sample submission portal](https://www.microsoft.com/wdsi/filesubmission).
|
No, we only accept submissions through our [sample submission portal](https://www.microsoft.com/en-us/wdsi/filesubmission).
|
||||||
|
|
||||||
## Can I submit a sample without signing in?
|
## Can I submit a sample without signing in?
|
||||||
|
|
||||||
@ -43,7 +43,7 @@ The [Software Assurance ID (SAID)](https://www.microsoft.com/licensing/licensing
|
|||||||
|
|
||||||
### How do I dispute the detection of my program?
|
### How do I dispute the detection of my program?
|
||||||
|
|
||||||
[Submit the file](https://www.microsoft.com/wdsi/filesubmission) in question as a software developer. Wait until your submission has a final determination.
|
[Submit the file](https://www.microsoft.com/en-us/wdsi/filesubmission) in question as a software developer. Wait until your submission has a final determination.
|
||||||
|
|
||||||
If you’re not satisfied with our determination of the submission, use the developer contact form provided with the submission results to reach Microsoft. We will use the information you provide to investigate further if necessary.
|
If you’re not satisfied with our determination of the submission, use the developer contact form provided with the submission results to reach Microsoft. We will use the information you provide to investigate further if necessary.
|
||||||
|
|
||||||
@ -51,7 +51,7 @@ We encourage all software vendors and developers to read about [how Microsoft id
|
|||||||
|
|
||||||
## How do I track or view past sample submissions?
|
## How do I track or view past sample submissions?
|
||||||
|
|
||||||
You can track your submissions through the [submission history page](https://www.microsoft.com/wdsi/submissionhistory).
|
You can track your submissions through the [submission history page](https://www.microsoft.com/en-us/wdsi/submissionhistory).
|
||||||
|
|
||||||
## What does the submission status mean?
|
## What does the submission status mean?
|
||||||
|
|
||||||
@ -63,7 +63,7 @@ Each submission is shown to be in one of the following status types:
|
|||||||
|
|
||||||
* Closed—a final determination has been given by an analyst
|
* Closed—a final determination has been given by an analyst
|
||||||
|
|
||||||
You can see the status of any files you submit to us on the [submission history page](https://www.microsoft.com/wdsi/submissionhistory).
|
You can see the status of any files you submit to us on the [submission history page](https://www.microsoft.com/en-us/wdsi/submissionhistory).
|
||||||
|
|
||||||
## How does Microsoft prioritize submissions
|
## How does Microsoft prioritize submissions
|
||||||
|
|
||||||
|
@ -10,7 +10,7 @@ ms.reviewer: jogeurte
|
|||||||
ms.author: jogeurte
|
ms.author: jogeurte
|
||||||
ms.manager: jsuther
|
ms.manager: jsuther
|
||||||
manager: dansimp
|
manager: dansimp
|
||||||
ms.date: 04/14/2021
|
ms.date: 11/06/2021
|
||||||
ms.technology: windows-sec
|
ms.technology: windows-sec
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
@ -32,7 +32,7 @@ This topic describes how to deploy Windows Defender Application Control (WDAC) p
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> To use this procedure, download and distribute the [WDAC policy refresh tool](https://aka.ms/refreshpolicy) to all managed endpoints. Ensure your WDAC policies allow the WDAC policy refresh tool or use a managed installer to distribute the tool.
|
> To use this procedure, download and distribute the [WDAC policy refresh tool](https://aka.ms/refreshpolicy) to all managed endpoints. Ensure your WDAC policies allow the WDAC policy refresh tool or use a managed installer to distribute the tool.
|
||||||
|
|
||||||
## Script-based deployment process for Windows 10 version 1903 and above
|
## Deploying policies for Windows 10 version 1903 and above
|
||||||
|
|
||||||
1. Initialize the variables to be used by the script.
|
1. Initialize the variables to be used by the script.
|
||||||
|
|
||||||
@ -56,23 +56,7 @@ This topic describes how to deploy Windows Defender Application Control (WDAC) p
|
|||||||
& $RefreshPolicyTool
|
& $RefreshPolicyTool
|
||||||
```
|
```
|
||||||
|
|
||||||
### Deploying signed policies
|
## Deploying policies for Windows 10 versions earlier than 1903
|
||||||
|
|
||||||
In addition to the steps outlined above, the binary policy file must also be copied to the device's EFI partition. Deploying your policy via [MEM](/windows/security/threat-protection/windows-defender-application-control/deploy-windows-defender-application-control-policies-using-intune) or the Application Control CSP will handle this step automatically.
|
|
||||||
|
|
||||||
1. Mount the EFI volume and make the directory, if it does not exist, in an elevated PowerShell prompt:
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
mountvol J: /S
|
|
||||||
J:
|
|
||||||
mkdir J:\EFI\Microsoft\Boot\CiPolicies\Active
|
|
||||||
```
|
|
||||||
|
|
||||||
2. Copy the signed policy binary as `{PolicyGUID}.cip` to `J:\EFI\Microsoft\Boot\CiPolicies\Active`.
|
|
||||||
|
|
||||||
3. Reboot the system.
|
|
||||||
|
|
||||||
## Script-based deployment process for Windows 10 versions earlier than 1903
|
|
||||||
|
|
||||||
1. Initialize the variables to be used by the script.
|
1. Initialize the variables to be used by the script.
|
||||||
|
|
||||||
@ -93,3 +77,25 @@ In addition to the steps outlined above, the binary policy file must also be cop
|
|||||||
```powershell
|
```powershell
|
||||||
Invoke-CimMethod -Namespace root\Microsoft\Windows\CI -ClassName PS_UpdateAndCompareCIPolicy -MethodName Update -Arguments @{FilePath = $DestinationBinary}
|
Invoke-CimMethod -Namespace root\Microsoft\Windows\CI -ClassName PS_UpdateAndCompareCIPolicy -MethodName Update -Arguments @{FilePath = $DestinationBinary}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Deploying signed policies
|
||||||
|
|
||||||
|
In addition to the steps outlined above, the binary policy file must also be copied to the device's EFI partition. Deploying your policy via [MEM](/windows/security/threat-protection/windows-defender-application-control/deploy-windows-defender-application-control-policies-using-intune) or the Application Control CSP will handle this step automatically.
|
||||||
|
|
||||||
|
1. Mount the EFI volume and make the directory, if it does not exist, in an elevated PowerShell prompt:
|
||||||
|
|
||||||
|
```powershell
|
||||||
|
$MountPoint = 'C:\EFI'
|
||||||
|
$EFIDestinationFolder = "$MountPoint\Microsoft\Boot\CiPolicies\Active"
|
||||||
|
$EFIPartition = (Get-Partition | Where-Object IsSystem).AccessPaths[0]
|
||||||
|
mkdir $EFIDestinationFolder
|
||||||
|
mountvol $MountPoint $EFIPartition
|
||||||
|
```
|
||||||
|
|
||||||
|
2. Copy the signed policy to the created folder:
|
||||||
|
|
||||||
|
```powershell
|
||||||
|
Copy-Item -Path $PolicyBinary -Destination $EFIDestinationFolder -Force
|
||||||
|
```
|
||||||
|
|
||||||
|
3. Restart the system.
|
||||||
|
@ -37,14 +37,11 @@ You can prevent users from modifying settings in the Exploit protection area. Th
|
|||||||
You can only prevent users from modifying Exploit protection settings by using Group Policy.
|
You can only prevent users from modifying Exploit protection settings by using Group Policy.
|
||||||
|
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
>
|
|
||||||
> ### Requirements
|
|
||||||
>
|
|
||||||
> You must have Windows 10, version 1709 or later. The ADMX/ADML template files for earlier versions of Windows do not include these Group Policy settings.
|
> You must have Windows 10, version 1709 or later. The ADMX/ADML template files for earlier versions of Windows do not include these Group Policy settings.
|
||||||
|
|
||||||
1. On your Group Policy management machine, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)), right-click the Group Policy Object you want to configure and click **Edit**.
|
1. On your Group Policy management machine, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)), right-click the Group Policy Object you want to configure and click **Edit**.
|
||||||
|
|
||||||
2. In the **Group Policy Management Editor** go to **Computer configuration** and click **Administrative templates**.
|
2. In the **Group Policy Management Editor** go to **Computer configuration**, select **Policies** and then **Administrative templates**.
|
||||||
|
|
||||||
3. Expand the tree to **Windows components > Windows Security > App and browser protection**.
|
3. Expand the tree to **Windows components > Windows Security > App and browser protection**.
|
||||||
|
|
||||||
@ -59,14 +56,11 @@ You can choose to hide the entire section by using Group Policy. The section wil
|
|||||||
This can only be done in Group Policy.
|
This can only be done in Group Policy.
|
||||||
|
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
>
|
> You must have Windows 10, version 1709 or later. The ADMX/ADML template files for earlier versions of Windows do not include these Group Policy settings.
|
||||||
> ### Requirements
|
|
||||||
>
|
|
||||||
> You must have Windows 10, version 1709 (the Fall Creators Update). The ADMX/ADML template files for earlier versions of Windows do not include these Group Policy settings.
|
|
||||||
|
|
||||||
1. On your Group Policy management machine, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)), right-click the Group Policy Object you want to configure and click **Edit**.
|
1. On your Group Policy management machine, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)), right-click the Group Policy Object you want to configure and click **Edit**.
|
||||||
|
|
||||||
2. In the **Group Policy Management Editor** go to **Computer configuration** and click **Administrative templates**.
|
2. In the **Group Policy Management Editor** go to **Computer configuration**, select **Policies** and then **Administrative templates**.
|
||||||
|
|
||||||
3. Expand the tree to **Windows components > Windows Security > App and browser protection**.
|
3. Expand the tree to **Windows components > Windows Security > App and browser protection**.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user