mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge branch 'master' into fix--MD037/no-space-in-emphasis
This commit is contained in:
commit
ae0fb89541
@ -11,7 +11,7 @@ ms.topic: include
|
||||
|
||||
| | |
|
||||
|----------|------|
|
||||
|**Single-app**<p><a href="/images/Picture1.png" alt="Full-sized view single-app digital/interactive signage" target="_blank"></a><p>**Digital/interactive signage**<p>Displays a specific site in full-screen mode, running Microsoft Edge InPrivate protecting user data.<ul><li>**Digital signage** does not require user interaction.<p>***Example.*** Use digital signage for things like a rotating advertisement or menu.<p></li><li>**Interactive signage**, on the other hand, requires user interaction within the page but doesn’t allow for any other uses, such as browsing the internet.<p>***Example.*** Use interactive signage for things like a building business directory or restaurant order/pay station.</li></ul><p>**Policy setting** = Not configured (0 default)<p> | <p> <p><a href="/images/Picture2.png" alt="Full-sized view single-app public browsing" target="_blank"></a> <p><strong>Public browsing</strong><p>Runs a limited multi-tab version of Microsoft Edge, protecting user data. Microsoft Edge is the only app users can use on the device, preventing them from customizing Microsoft Edge. Users can only browse publically or end their browsing session.<p>The single-app public browsing mode is the only kiosk mode that has an <strong>End session</strong> button. Microsoft Edge also resets the session after a specified time of user inactivity. Both restart Microsoft Edge and clear the user’s session.<p><em><strong>Example.</strong></em> A public library or hotel concierge desk are two examples of public browsing that provides access to Microsoft Edge and other apps. <p><strong>Policy setting</strong> = Enabled (1) |
|
||||
| **Multi-app**<p><a href="/images/Picture5.png" alt="Full-sized view multi-app normal browsing" target="_blank"></a><p>**Normal browsing**<p>Runs a full-version of Microsoft Edge with all browsing features and preserves the user data and state between sessions.<p>Some features may not work depending on what other apps you have configured in assigned access. For example, installing extensions or books from the Microsoft store are not allowed if the store is not available. Also, if Internet Explorer 11 is set up in assigned access, you can enable [EnterpriseModeSiteList](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-enterprisemodesitelist) to automatically switch users to Internet Explorer 11 for sites that need backward compatibility support.<p>**Policy setting** = Not configured (0 default) | <p> <p><a href="/images/Picture6.png" alt="Full-sized view multi-app public browsing" target="_blank"></a><p><strong>Public browsing</strong><p>Runs a multi-tab version of Microsoft Edge InPrivate with a tailored experience for kiosks that runs in full-screen mode. Users can open and close Microsoft Edge and launch other apps if allowed by assigned access. Instead of an End session button to clear their browsing session, the user closes Microsoft Edge normally.<p>In this configuration, Microsoft Edge can interact with other applications. For example, if Internet Explorer 11 is set up in multi-app assigned access, you can enable [EnterpriseModeSiteList](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-enterprisemodesitelist) to automatically switch users to Internet Explorer 11 for sites that need backward compatibility support. <p><em><strong>Example.</strong></em> A public library or hotel concierge desk are two examples of public browsing that provides access to Microsoft Edge and other apps.<p><strong>Policy setting</strong> = Enabled (1) |
|
||||
|**Single-app**<p><a href="../images/Picture1.png" alt="Full-sized view single-app digital/interactive signage" target="_blank"></a><p>**Digital/interactive signage**<p>Displays a specific site in full-screen mode, running Microsoft Edge InPrivate protecting user data.<ul><li>**Digital signage** does not require user interaction.<p>***Example.*** Use digital signage for things like a rotating advertisement or menu.<p></li><li>**Interactive signage**, on the other hand, requires user interaction within the page but doesn’t allow for any other uses, such as browsing the internet.<p>***Example.*** Use interactive signage for things like a building business directory or restaurant order/pay station.</li></ul><p>**Policy setting** = Not configured (0 default)<p> | <p> <p><a href="../images/Picture2.png" alt="Full-sized view single-app public browsing" target="_blank"></a> <p><strong>Public browsing</strong><p>Runs a limited multi-tab version of Microsoft Edge, protecting user data. Microsoft Edge is the only app users can use on the device, preventing them from customizing Microsoft Edge. Users can only browse publically or end their browsing session.<p>The single-app public browsing mode is the only kiosk mode that has an <strong>End session</strong> button. Microsoft Edge also resets the session after a specified time of user inactivity. Both restart Microsoft Edge and clear the user’s session.<p><em><strong>Example.</strong></em> A public library or hotel concierge desk are two examples of public browsing that provides access to Microsoft Edge and other apps. <p><strong>Policy setting</strong> = Enabled (1) |
|
||||
| **Multi-app**<p><a href="../images/Picture5.png" alt="Full-sized view multi-app normal browsing" target="_blank"></a><p>**Normal browsing**<p>Runs a full-version of Microsoft Edge with all browsing features and preserves the user data and state between sessions.<p>Some features may not work depending on what other apps you have configured in assigned access. For example, installing extensions or books from the Microsoft store are not allowed if the store is not available. Also, if Internet Explorer 11 is set up in assigned access, you can enable [EnterpriseModeSiteList](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-enterprisemodesitelist) to automatically switch users to Internet Explorer 11 for sites that need backward compatibility support.<p>**Policy setting** = Not configured (0 default) | <p> <p><a href="../images/Picture6.png" alt="Full-sized view multi-app public browsing" target="_blank"></a><p><strong>Public browsing</strong><p>Runs a multi-tab version of Microsoft Edge InPrivate with a tailored experience for kiosks that runs in full-screen mode. Users can open and close Microsoft Edge and launch other apps if allowed by assigned access. Instead of an End session button to clear their browsing session, the user closes Microsoft Edge normally.<p>In this configuration, Microsoft Edge can interact with other applications. For example, if Internet Explorer 11 is set up in multi-app assigned access, you can enable [EnterpriseModeSiteList](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-enterprisemodesitelist) to automatically switch users to Internet Explorer 11 for sites that need backward compatibility support. <p><em><strong>Example.</strong></em> A public library or hotel concierge desk are two examples of public browsing that provides access to Microsoft Edge and other apps.<p><strong>Policy setting</strong> = Enabled (1) |
|
||||
|
||||
---
|
||||
|
@ -24,7 +24,7 @@ IE11 works differently with search, based on whether your organization is domain
|
||||
|
||||
- **Non-domain-joined computers.** A single word entry is treated as an intranet site. However, if the term doesn't resolve to a site, IE11 then treats the entry as a search term and opens your default search provider.
|
||||
|
||||
To explicitly go to an intranet site, regardless of the environment, users can type either a trailing slash like ` contoso/` or the `https://` prefix. Either of these will cause IE11 to treat the entry as an intranet search. You can also change the default behavior so that IE11 treats your single word entry in the address bar as an intranet site, regardless of your environment.
|
||||
To explicitly go to an intranet site, regardless of the environment, users can type either a trailing slash like `contoso/` or the `https://` prefix. Either of these will cause IE11 to treat the entry as an intranet search. You can also change the default behavior so that IE11 treats your single word entry in the address bar as an intranet site, regardless of your environment.
|
||||
|
||||
**To enable single-word intranet search**
|
||||
|
||||
|
@ -31,13 +31,13 @@ Here are some things you can try saying (remember to say "Hey Cortana" first):
|
||||
- Restart.
|
||||
- Go to sleep.
|
||||
- Mute.
|
||||
- Launch <app name>.
|
||||
- Move <app name> here (gaze at the spot you want the app to move to).
|
||||
- Launch `<app name>`.
|
||||
- Move `<app name>` here (gaze at the spot you want the app to move to).
|
||||
- Go to Start.
|
||||
- Take a picture.
|
||||
- Start recording. (Starts recording a video.)
|
||||
- Stop recording. (Stops recording a video.)
|
||||
- Call <contact>. (Requires Skype.)
|
||||
- Call `<contact>`. (Requires Skype.)
|
||||
- What time is it?
|
||||
- Show me the latest NBA scores.
|
||||
- How much battery do I have left?
|
||||
|
@ -1,37 +1,43 @@
|
||||
---
|
||||
title: Set up HoloLens (HoloLens)
|
||||
description: The first time you set up HoloLens, you'll need a Wi-Fi network and either a Microsoft or Azure Active Directory account.
|
||||
title: Set up a new HoloLens
|
||||
description: This guide walks through first time set up. You'll need a Wi-Fi network and either a Microsoft (MSA) or Azure Active Directory (AAD) account.
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
author: scooley
|
||||
ms.author: scooley
|
||||
ms.topic: quickstart
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.date: 07/14/2019
|
||||
---
|
||||
|
||||
# Set up HoloLens
|
||||
# Set up HoloLens for the first time
|
||||
|
||||
Before you get started setting up your HoloLens, make sure you have a Wi-Fi network and a Microsoft account or an Azure Active Directory (Azure AD) account.
|
||||
Follow along to set up a HoloLens for the first time. At the end of this quickstart, you'll be able to use HoloLens and navigate HoloLens settings on-device.
|
||||
|
||||
## Network connectivity requirements
|
||||
This is a high level unboxing guide to become familiar with HoloLens.
|
||||
See [Set up HoloLens in the enterprise](hololens-requirements.md) to configure HoloLens for scale enterprise deployment and ongoing device management.
|
||||
|
||||
The first time you use your HoloLens, you'll be guided through connecting to a Wi-Fi network. You need to connect HoloLens to a Wi-Fi network with Internet connectivity so that the user account can be authenticated.
|
||||
## Prerequisites
|
||||
|
||||
- It can be an open Wi-Fi or password-protected Wi-Fi network.
|
||||
- The Wi-Fi network cannot require certificates to connect.
|
||||
- The Wi-Fi network does not need to provide access to enterprise resources or intranet sites.
|
||||
- Internet access.
|
||||
- Wi-Fi is the easiest way to do first set up on both HoloLens and HoloLens 2. It can be an open Wi-Fi or password-protected Wi-Fi network; the Wi-Fi network does not need to provide access to enterprise resources or intranet sites.
|
||||
- HoloLens 2 can connect to the internet via ethernet and a USB-C adapter.
|
||||
- a user account - Microsoft (MSA) or Azure Active Directory (AAD)
|
||||
|
||||
## HoloLens setup
|
||||
## Prepare for first-boot
|
||||
|
||||
The HoloLens setup process combines a quick tutorial on using HoloLens with the steps needed to connect to the network and add an account.
|
||||
Become familiar with the HoloLens hardware and prepare to turn your HoloLens on for the first time.
|
||||
|
||||
1. Be sure your HoloLens is [charged](https://support.microsoft.com/help/12627), then [adjust it](https://support.microsoft.com/help/12632) for a comfortable fit.
|
||||
2. [Turn on HoloLens](https://support.microsoft.com/help/12642). You will be guided through a calibration procedure and how to perform [the gestures](https://support.microsoft.com/help/12644/hololens-use-gestures) that you will use to operate HoloLens.
|
||||
3. Next, you'll be guided through connecting to a Wi-Fi network.
|
||||
4. After HoloLens connects to the Wi-Fi network, you select between **My work or school owns it** and **I own it**.
|
||||
1. Be sure your HoloLens is [charged](https://support.microsoft.com/help/12627)
|
||||
1. [Adjust fit](https://support.microsoft.com/help/12632) for a comfortable fit.
|
||||
1. [Turn on HoloLens](https://support.microsoft.com/help/12642). You will be guided through a calibration procedure and how to perform [the gestures](https://support.microsoft.com/help/12644/hololens-use-gestures) that you will use to operate HoloLens.
|
||||
|
||||
## Set up your HoloLens
|
||||
|
||||
Set up your HoloLens and your user account.
|
||||
|
||||
1. Connect to the internet (select Wi-Fi).
|
||||
1. Sign in to your user account. You'll choose between **My work or school owns it** and **I own it**.
|
||||
- When you choose **My work or school owns it**, you sign in with an Azure AD account. If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens will be enrolled in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available, so you will need to [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
|
||||
1. Enter your organizational account.
|
||||
2. Accept privacy statement.
|
||||
@ -40,7 +46,30 @@ The HoloLens setup process combines a quick tutorial on using HoloLens with the
|
||||
- When you choose **I own it**, you sign in with a Microsoft account. After setup is complete, you can [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
|
||||
1. Enter your Microsoft account.
|
||||
2. Enter your password. If your Microsoft account requires [two-step verification (2FA)](https://blogs.technet.microsoft.com/microsoft_blog/2013/04/17/microsoft-account-gets-more-secure/), complete the verification process.
|
||||
5. The device sets your time zone based on information obtained from the Wi-Fi network.
|
||||
6. Next, you learn how to perform the bloom gesture and how to select and place the Start screen. After you place the Start screen, setup is complete and you can begin using HoloLens.
|
||||
1. The device sets your time zone based on information obtained from the Wi-Fi network.
|
||||
1. Follow the first-start guides to learn how to interact with holograms, control the HoloLens with your voice, and access the start menu.
|
||||
|
||||
Congratulations! Setup is complete and you can begin using HoloLens.
|
||||
|
||||
## Explore HoloLens
|
||||
|
||||
### Check out on-device settings and desktop
|
||||
|
||||
HoloLens doesn't have an on-device command line. With that in mind, the settings section in HoloLens plays an important role in diagnosing problems on-device. Understanding the information available to HoloLens users will pay dividends when troubleshooting or configuring the device.
|
||||
|
||||
Open settings by opening the start menu and clicking on the **Settings** in the top bar. You can also ask Cortana to open settings.
|
||||
|
||||
Follow [this guide](https://docs.microsoft.com/windows/mixed-reality/navigating-the-windows-mixed-reality-home) to navigate around the HoloLens home.
|
||||
|
||||
### Connect bluetooth devices
|
||||
|
||||
Connecting a bluetooth keyboard makes typing on HoloLens as efficient as a Windows PC.
|
||||
|
||||
[Connect a bluetooth keyboard or clicker](https://support.microsoft.com/en-us/help/12636).
|
||||
|
||||
## Next steps
|
||||
|
||||
Start planning for HoloLens at scale with HoloLens' enterprise management features.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [HoloLens in the enterprise](hololens-requirements.md)
|
BIN
devices/hololens/images/hololens2-side-render.png
Normal file
BIN
devices/hololens/images/hololens2-side-render.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 3.8 MiB |
@ -1,46 +1,51 @@
|
||||
---
|
||||
title: Microsoft HoloLens (HoloLens)
|
||||
description: HoloLens provides extra features designed for business in the Commercial Suite.
|
||||
description: Landing page for HoloLens commercial and enterprise management.
|
||||
ms.prod: hololens
|
||||
ms.sitesec: library
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
author: scooley
|
||||
ms.author: scooley
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2018
|
||||
ms.date: 07/14/2019
|
||||
---
|
||||
|
||||
# Microsoft HoloLens
|
||||
|
||||
|
||||
<table><tbody>
|
||||
<tr><td style="border: 0px;width: 75%;valign= top"><p>Microsoft HoloLens is the first fully self-contained holographic computer running Windows 10.</p><p> Microsoft HoloLens is available in the <strong>Development Edition</strong>, which runs Windows Holographic (an edition of Windows 10 designed for HoloLens), and in the <strong>Commercial Suite</strong>, which runs Windows Holographic for Business when you apply the Enterprise license file to the device.</p></td><td align="left" style="border: 0px"><img src="images/hololens.png" alt="Hololens"/></td></tr>
|
||||
<tr><td style="border: 0px;width: 75%;valign= top">
|
||||
<p>Microsoft HoloLens is the first fully self-contained holographic computer running Windows 10.</p>
|
||||
|
||||
<p>Now, with the introduction of HoloLens 2, every device provides commercial ready management enhanced by the reliability, security, and scalability of cloud and AI services from Microsoft.</p>
|
||||
|
||||
</td><td align="left" style="border: 0px"></td></tr>
|
||||
</tbody></table>
|
||||
|
||||
## In this section
|
||||
## Guides in this section
|
||||
|
||||
| Guide | Description |
|
||||
| --- | --- |
|
||||
| [Get started with HoloLens](hololens-setup.md) | Set up HoloLens for the first time. |
|
||||
| [Set up HoloLens in the enterprise](hololens-requirements.md) | Configure HoloLens for scale enterprise deployment and ongoing device management. |
|
||||
| [Install and manage applications on HoloLens](hololens-install-apps.md) |Install and manage important applications on HoloLens at scale. |
|
||||
| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) | Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary. |
|
||||
| [Get support](https://support.microsoft.com/products/hololens) |Connect with Microsoft support resources for HoloLens in enterprise. |
|
||||
|
||||
## Quick reference by topic
|
||||
|
||||
| Topic | Description |
|
||||
| --- | --- |
|
||||
| [What's new in Microsoft HoloLens](hololens-whats-new.md) | Discover the new features in the latest update. |
|
||||
| [HoloLens in the enterprise: requirements](hololens-requirements.md) | Lists requirements for general use, Wi-Fi, and device management |
|
||||
| [Set up HoloLens](hololens-setup.md) | How to set up HoloLens for the first time |
|
||||
[Install localized version of HoloLens](hololens-install-localized.md) | Install the Chinese or Japanese version of HoloLens
|
||||
| [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md) | How to upgrade your Development Edition HoloLens to Windows Holographic for Business |
|
||||
| [Enroll HoloLens in MDM](hololens-enroll-mdm.md) | Manage multiple HoloLens devices simultaneously using solutions like Microsoft Intune |
|
||||
| [Manage updates to HoloLens](hololens-updates.md) | Use mobile device management (MDM) policies to configure settings for updates. |
|
||||
| [Set up HoloLens in kiosk mode](hololens-kiosk.md) | Enable kiosk mode for HoloLens, which limits the user's ability to launch new apps or change the running app |
|
||||
[Share HoloLens with multiple people](hololens-multiple-users.md) | Multiple users can shared a HoloLens device by using their Azure Active Directory accounts. |
|
||||
| [What's new in Microsoft HoloLens](hololens-whats-new.md) | Discover new features in the latest updates. |
|
||||
| [Configure HoloLens using a provisioning package](hololens-provisioning.md) | Provisioning packages make it easy for IT administrators to configure HoloLens devices without imaging |
|
||||
| [Install apps on HoloLens](hololens-install-apps.md) | Use Microsoft Store for Business, mobile device management (MDM), or the Windows Device Portal to install apps on HoloLens |
|
||||
| [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) | Learn how to use Bitlocker device encryption to protect files and information stored on the HoloLens |
|
||||
| [Change history for Microsoft HoloLens documentation](change-history-hololens.md) | See new and updated topics in the HoloLens documentation library. |
|
||||
| [HoloLens MDM support](hololens-enroll-mdm.md) | Manage multiple HoloLens devices simultaneously using Mobile Device Management (MDM) solutions like Microsoft Intune. |
|
||||
| [HoloLens update management](hololens-updates.md) | Use mobile device management (MDM) policies to configure settings for updates. |
|
||||
| [HoloLens user management](hololens-multiple-users.md) | Multiple users can shared a HoloLens device by using their Azure Active Directory accounts. |
|
||||
| [HoloLens application access management](hololens-kiosk.md) | Manage application access for different user groups. |
|
||||
| [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) | Learn how to use Bitlocker device encryption to protect files and information stored on the HoloLens. |
|
||||
| [Install localized version of HoloLens](hololens-install-localized.md) | Configure HoloLens for different locale. |
|
||||
|
||||
## Related resources
|
||||
|
||||
- [Help for using HoloLens](https://support.microsoft.com/products/hololens)
|
||||
|
||||
- [Documentation for Holographic app development](https://developer.microsoft.com/windows/mixed-reality/development)
|
||||
|
||||
- [HoloLens Commercial Suite](https://www.microsoft.com/microsoft-hololens/hololens-commercial)
|
||||
|
||||
- [HoloLens release notes](https://developer.microsoft.com/en-us/windows/mixed-reality/release_notes)
|
||||
* [Documentation for Holographic app development](https://developer.microsoft.com/windows/mixed-reality/development)
|
||||
* [HoloLens Commercial Suite](https://www.microsoft.com/microsoft-hololens/hololens-commercial)
|
||||
* [HoloLens release notes](https://developer.microsoft.com/en-us/windows/mixed-reality/release_notes)
|
||||
|
@ -5,7 +5,7 @@
|
||||
## Overview
|
||||
### [What's new in Surface Hub 2S for IT admins](surface-hub-2s-whats-new.md)
|
||||
### [Surface Hub 2S tech specs](surface-hub-2s-techspecs.md)
|
||||
### [Operating system essentials (Surface Hub) ](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
### [Operating system essentials (Surface Hub)](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
### [Adjust Surface Hub 2S brightness, volume, and input](surface-hub-2s-onscreen-display.md)
|
||||
|
||||
## Plan
|
||||
|
@ -534,7 +534,7 @@ if ($status.Count -gt 0)
|
||||
elseif ($v[0] -eq "F")
|
||||
{
|
||||
$color = "red"
|
||||
$v += " Go to http://aka.ms/shubtshoot"
|
||||
$v += " Go to https://aka.ms/shubtshoot"
|
||||
}
|
||||
|
||||
Write-Host -NoNewline $k -ForegroundColor $color
|
||||
@ -978,7 +978,7 @@ if ($status.Count -gt 0)
|
||||
elseif ($v[0] -eq "F")
|
||||
{
|
||||
$color = "red"
|
||||
$v += " Go to http://aka.ms/shubtshoot for help"
|
||||
$v += " Go to https://aka.ms/shubtshoot for help"
|
||||
}
|
||||
|
||||
Write-Host -NoNewline $k -ForegroundColor $color
|
||||
|
@ -127,7 +127,7 @@ The administrative features in Windows 10 Enterprise, such as the Microsoft Mana
|
||||
|
||||
### Remote management and monitoring
|
||||
|
||||
Surface Hub supports remote management through mobile device management (MDM) solutions such as [Microsoft Intune](https://docs.microsoft.com/en-us/intune/) and monitoring through [Azure Monitor](https://azure.microsoft.com/services/monitor/).
|
||||
Surface Hub supports remote management through mobile device management (MDM) solutions such as [Microsoft Intune](https://docs.microsoft.com/intune/) and monitoring through [Azure Monitor](https://azure.microsoft.com/services/monitor/).
|
||||
|
||||
*Organization policies that this may affect:* <br> Surface Hub doesn't support installing Win32 agents required by most traditional PC management and monitoring tools, such as System Center Operations Manager.
|
||||
|
||||
|
@ -14,7 +14,9 @@
|
||||
"resource": [
|
||||
{
|
||||
"files": [
|
||||
"**/images/**"
|
||||
"**/images/**",
|
||||
"**/*.pptx",
|
||||
"**/*.pdf"
|
||||
],
|
||||
"exclude": [
|
||||
"**/obj/**"
|
||||
|
@ -21,7 +21,7 @@ You can install additional apps on your Surface Hub to fit your team or organiza
|
||||
A few things to know about apps on Surface Hub:
|
||||
- Surface Hub only runs [Universal Windows Platform (UWP) apps](https://msdn.microsoft.com/windows/uwp/get-started/whats-a-uwp). Apps created using the [Desktop App Converter](https://docs.microsoft.com/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter) will not run on Surface Hub.
|
||||
- Apps must be targeted for the [Universal device family](https://msdn.microsoft.com/library/windows/apps/dn894631) or Windows Team device family.
|
||||
- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from Microsoft Store for Business.
|
||||
- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from [Microsoft Store for Business](https://businessstore.microsoft.com/store).
|
||||
- By default, apps must be Store-signed to be installed. During testing and development, you can also choose to run developer-signed UWP apps by placing the device in developer mode.
|
||||
- When submitting an app to the Microsoft Store, developers need to set Device family availability and Organizational licensing options to make sure an app will be available to run on Surface Hub.
|
||||
- You need admin credentials to install apps on your Surface Hub. Since the device is designed to be used in communal spaces like meeting rooms, people can't access the Microsoft Store to download and install apps.
|
||||
|
@ -20,7 +20,7 @@ You can install additional apps to fit your team or organization's needs.
|
||||
|
||||
- Surface Hub only runs [Universal Windows Platform (UWP) apps](https://msdn.microsoft.com/windows/uwp/get-started/whats-a-uwp). Apps created using the [Desktop App Converter](https://docs.microsoft.com/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter) will not run on Surface Hub.
|
||||
- Apps must be targeted for the [Universal device family](https://msdn.microsoft.com/library/windows/apps/dn894631) or Windows Team device family.
|
||||
- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from Microsoft Store for Business.
|
||||
- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from [Microsoft Store for Business](https://businessstore.microsoft.com/store).
|
||||
- By default, apps must be Store-signed to be installed. During testing and development, you can also choose to run developer-signed UWP apps by placing the device in developer mode.
|
||||
- When developing and submitting apps to the Microsoft Store, set Device family availability and Organizational licensing options to ensure that apps are available to run on Surface Hub.
|
||||
- You need admin credentials to install apps on Surface Hub. Designed for use in meeting rooms and other shared spaces, Surface Hub prevents regular users from accessing the Microsoft Store to download and install apps.
|
||||
|
@ -39,4 +39,4 @@ Password-less phone sign-in simplifies signing-in to your meetings and files on
|
||||
3. If prompted, enter the PIN or biometric ID on your phone to complete sign-in.
|
||||
|
||||
## Learn more
|
||||
For more information, see [Password-less phone sign-in with the Microsoft Authenticator app](https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-authentication-phone-sign-in).
|
||||
For more information, see [Password-less phone sign-in with the Microsoft Authenticator app](https://docs.microsoft.com/azure/active-directory/authentication/howto-authentication-phone-sign-in).
|
||||
|
@ -44,6 +44,6 @@ If you affiliate Surface Hub 2S with on-premises Active Directory Domain Service
|
||||
|
||||
## Azure Active Directory
|
||||
|
||||
When choosing to affiliate your Surface Hub 2S with Azure AD, any user in the Global Admins Security Group can sign in to the Settings app on Surface Hub 2S. Alternatively, you can configure the Device Administrator role to sign in to the Settings app. For more information, see [Administrator role permissions in Azure Active Directory](https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#device-administrators). Currently, no other group can be delegated to sign in to the Settings app on Surface Hub 2S.
|
||||
When choosing to affiliate your Surface Hub 2S with Azure AD, any user in the Global Admins Security Group can sign in to the Settings app on Surface Hub 2S. Alternatively, you can configure the Device Administrator role to sign in to the Settings app. For more information, see [Administrator role permissions in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles#device-administrators). Currently, no other group can be delegated to sign in to the Settings app on Surface Hub 2S.
|
||||
|
||||
If you enabled Intune Automatic Enrollment for your organization, Surface Hub 2S will automatically enroll itself with Intune. The device’s Bitlocker key is automatically saved in Azure AD. When affiliating Surface Hub 2S with Azure AD, single sign-on and Easy Authentication will not work.
|
||||
|
@ -43,7 +43,7 @@ When you first start Surface Hub 2S, the device automatically enters first time
|
||||
|
||||
## Configuring device admin accounts
|
||||
|
||||
You can only set up device admins during first time Setup. For more information, refer to [Surface Hub 2S device affiliation](https://docs.microsoft.com/en-us/surface-hub/surface-hub-2s-prepare-environment#device-affiliation).
|
||||
You can only set up device admins during first time Setup. For more information, refer to [Surface Hub 2S device affiliation](https://docs.microsoft.com/surface-hub/surface-hub-2s-prepare-environment#device-affiliation).
|
||||
|
||||
In the **Setup admins for this device** window, select one of the following options: Active Directory Domain Services, Azure Active Directory, or Local admin.
|
||||
|
||||
@ -91,7 +91,7 @@ If you insert a USB thumb drive with a provisioning package into one of the USB
|
||||
|
||||
 <br>
|
||||
|
||||
3. If you created a multiple devices CSV file, you will be able to choose a device configuration. For more information, refer to [Create provisioning packages for Surface Hub 2S](https://docs.microsoft.com/en-us/surface-hub/surface-hub-2s-deploy#provisioning-multiple-devices-csv-file).
|
||||
3. If you created a multiple devices CSV file, you will be able to choose a device configuration. For more information, refer to [Create provisioning packages for Surface Hub 2S](https://docs.microsoft.com/surface-hub/surface-hub-2s-deploy#provisioning-multiple-devices-csv-file).
|
||||
|
||||
|
||||
 <br>
|
||||
|
@ -226,8 +226,16 @@ create a reset package using PowerShell to reset SEMM.
|
||||
|
||||
## Version History
|
||||
|
||||
|
||||
|
||||
### Version 2.43.136.0
|
||||
* Support to enable/disable simulatenous multithreating
|
||||
* Separate options for WiFi and Bluetooth for some devices
|
||||
* Battery Limit removed for Surface Studio
|
||||
|
||||
### Version 2.26.136.0
|
||||
* Add support to Surface Studio 2
|
||||
* Battery Limit feature
|
||||
|
||||
### Version 2.21.136.0
|
||||
* Add support to Surface Pro 6
|
||||
|
@ -19,7 +19,7 @@ ms.date: 06/16/2016
|
||||
|
||||
Removes a package record and the applications associated with it.
|
||||
|
||||
` SFTMIME DELETE PACKAGE:package-name [/LOG log-pathname | /CONSOLE | /GUI]`
|
||||
`SFTMIME DELETE PACKAGE:package-name [/LOG log-pathname | /CONSOLE | /GUI]`
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
|
@ -31,23 +31,23 @@ There is only one Application Virtualization Client Tray instance for each user
|
||||
|
||||
|
||||
|
||||
` Sfttray.exe /?`
|
||||
`Sfttray.exe /?`
|
||||
|
||||
### Command Usage
|
||||
|
||||
` Sfttray.exe [/HIDE | /SHOW]`
|
||||
`Sfttray.exe [/HIDE | /SHOW]`
|
||||
|
||||
` Sfttray.exe [/HIDE | /SHOW] [/QUIET] [/EXE alternate-exe] /LAUNCH app [args]`
|
||||
`Sfttray.exe [/HIDE | /SHOW] [/QUIET] [/EXE alternate-exe] /LAUNCH app [args]`
|
||||
|
||||
` Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOAD app [/SFTFILE sft]`
|
||||
`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOAD app [/SFTFILE sft]`
|
||||
|
||||
` Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOADALL`
|
||||
`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOADALL`
|
||||
|
||||
` Sfttray.exe [/HIDE | /SHOW] [/QUIET] /REFRESHALL`
|
||||
`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /REFRESHALL`
|
||||
|
||||
` Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LAUNCHRESULT <UNIQUE ID> /LAUNCH app [args]`
|
||||
`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LAUNCHRESULT <UNIQUE ID> /LAUNCH app [args]`
|
||||
|
||||
` Sfttray.exe /EXIT`
|
||||
`Sfttray.exe /EXIT`
|
||||
|
||||
### Command-Line Switches
|
||||
|
||||
|
@ -51,21 +51,16 @@ Use the following procedure to install the publishing server on a separate compu
|
||||
|
||||
9. To verify if the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: <strong>http://publishingserver:pubport</strong>. If the server is running correctly information similar to the following will be displayed:
|
||||
|
||||
`<Publishing Protocol="1.0">`
|
||||
|
||||
` <Packages>`
|
||||
|
||||
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
|
||||
|
||||
` </Packages>`
|
||||
|
||||
` <NoGroup>`
|
||||
|
||||
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
|
||||
|
||||
` </NoGroup>`
|
||||
|
||||
`</Publishing>`
|
||||
```xml
|
||||
<Publishing Protocol="1.0">
|
||||
<Packages>
|
||||
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
|
||||
</Packages>
|
||||
<NoGroup>
|
||||
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
|
||||
</NoGroup>
|
||||
</Publishing>
|
||||
```
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
|
@ -51,21 +51,16 @@ Use the following procedure to install the publishing server on a separate compu
|
||||
|
||||
9. To verify if the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: <strong>http://publishingserver:pubport</strong>. If the server is running correctly information similar to the following will be displayed:
|
||||
|
||||
`<Publishing Protocol="1.0">`
|
||||
|
||||
` <Packages>`
|
||||
|
||||
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
|
||||
|
||||
` </Packages>`
|
||||
|
||||
` <NoGroup>`
|
||||
|
||||
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
|
||||
|
||||
` </NoGroup>`
|
||||
|
||||
`</Publishing>`
|
||||
```xml
|
||||
<Publishing Protocol="1.0">
|
||||
<Packages>
|
||||
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
|
||||
</Packages>
|
||||
<NoGroup>
|
||||
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
|
||||
</NoGroup>
|
||||
</Publishing>
|
||||
```
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
|
@ -88,49 +88,55 @@ You can use the following procedure to move the MBAM Recovery and Hardware Datab
|
||||
|
||||
Modify the MBAM Recovery and Hardware Database to use the full recovery mode.
|
||||
|
||||
`USE master;`
|
||||
```sql
|
||||
USE master;
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`ALTER DATABASE "MBAM Recovery and Hardware"`
|
||||
ALTER DATABASE "MBAM Recovery and Hardware"
|
||||
|
||||
` SET RECOVERY FULL;`
|
||||
SET RECOVERY FULL;
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
Create MBAM Recovery and Hardware Database Data and MBAM Recovery logical backup devices.
|
||||
|
||||
`USE master`
|
||||
```sql
|
||||
USE master
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',`
|
||||
EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',
|
||||
|
||||
`'Z:\MBAM Recovery and Hardware Database Data.bak';`
|
||||
'Z:\MBAM Recovery and Hardware Database Data.bak';
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
Back up the full MBAM Recovery and Hardware database.
|
||||
|
||||
`BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];`
|
||||
```sql
|
||||
BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]`
|
||||
BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]
|
||||
|
||||
`TO FILE = 'Z:\SQLServerInstanceCertificateFile'`
|
||||
TO FILE = 'Z:\SQLServerInstanceCertificateFile'
|
||||
|
||||
`WITH PRIVATE KEY`
|
||||
WITH PRIVATE KEY
|
||||
|
||||
`(`
|
||||
(
|
||||
|
||||
` FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
|
||||
FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
|
||||
|
||||
` ENCRYPTION BY PASSWORD = '$PASSWORD$'`
|
||||
ENCRYPTION BY PASSWORD = '$PASSWORD$'
|
||||
|
||||
`);`
|
||||
);
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
**Note**
|
||||
Replace the values from the preceding example with those that match your environment:
|
||||
@ -181,43 +187,51 @@ You can use the following procedure to move the MBAM Recovery and Hardware Datab
|
||||
|
||||
4. To automate this procedure, create a SQL file (.sql) that contains the following SQL script:
|
||||
|
||||
`-- Restore MBAM Recovery and Hardware Database. `
|
||||
```sql
|
||||
-- Restore MBAM Recovery and Hardware Database.
|
||||
|
||||
`USE master`
|
||||
USE master
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
Drop the certificate created by MBAM Setup.
|
||||
|
||||
`DROP CERTIFICATE [MBAM Recovery Encryption Certificate]`
|
||||
```sql
|
||||
DROP CERTIFICATE [MBAM Recovery Encryption Certificate]
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
Add certificate
|
||||
|
||||
`CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]`
|
||||
```sql
|
||||
CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]
|
||||
|
||||
`FROM FILE = 'Z: \SQLServerInstanceCertificateFile'`
|
||||
FROM FILE = 'Z: \SQLServerInstanceCertificateFile'
|
||||
|
||||
`WITH PRIVATE KEY`
|
||||
WITH PRIVATE KEY
|
||||
|
||||
`(`
|
||||
(
|
||||
|
||||
` FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
|
||||
FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
|
||||
|
||||
` DECRYPTION BY PASSWORD = '$PASSWORD$'`
|
||||
DECRYPTION BY PASSWORD = '$PASSWORD$'
|
||||
|
||||
`);`
|
||||
);
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
Restore the MBAM Recovery and Hardware database data and the log files.
|
||||
|
||||
`RESTORE DATABASE [MBAM Recovery and Hardware]`
|
||||
```sql
|
||||
RESTORE DATABASE [MBAM Recovery and Hardware]
|
||||
|
||||
` FROM DISK = 'Z:\MBAM Recovery and Hardware Database Data.bak'`
|
||||
FROM DISK = 'Z:\MBAM Recovery and Hardware Database Data.bak'
|
||||
|
||||
` WITH REPLACE`
|
||||
WITH REPLACE
|
||||
```
|
||||
|
||||
**Note**
|
||||
Replace the values from the preceding example with those that match your environment:
|
||||
@ -354,35 +368,37 @@ If you choose to move the MBAM Compliance Status Database feature from one compu
|
||||
|
||||
2. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
|
||||
|
||||
`-- Modify the MBAM Compliance Status Database to use the full recovery model.`
|
||||
```sql
|
||||
-- Modify the MBAM Compliance Status Database to use the full recovery model.
|
||||
|
||||
`USE master;`
|
||||
USE master;
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`ALTER DATABASE "MBAM Compliance Status"`
|
||||
ALTER DATABASE "MBAM Compliance Status"
|
||||
|
||||
` SET RECOVERY FULL;`
|
||||
SET RECOVERY FULL;
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`-- Create MBAM Compliance Status Data logical backup devices.`
|
||||
-- Create MBAM Compliance Status Data logical backup devices.
|
||||
|
||||
`USE master`
|
||||
USE master
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',`
|
||||
EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',
|
||||
|
||||
`'Z: \MBAM Compliance Status Database Data.bak';`
|
||||
'Z: \MBAM Compliance Status Database Data.bak';
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
-- Back up the full MBAM Recovery and Hardware database.
|
||||
|
||||
`BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];`
|
||||
BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
3. Run the SQL file with a command that is similar to the following one, by using the SQL Server PowerShell:
|
||||
|
||||
@ -422,19 +438,21 @@ If you choose to move the MBAM Compliance Status Database feature from one compu
|
||||
|
||||
3. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
|
||||
|
||||
`-- Create MBAM Compliance Status Database Data logical backup devices. `
|
||||
```sql
|
||||
-- Create MBAM Compliance Status Database Data logical backup devices.
|
||||
|
||||
`Use master`
|
||||
Use master
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
-- Restore the MBAM Compliance Status database data files.
|
||||
|
||||
`RESTORE DATABASE [MBAM Compliance Status Database]`
|
||||
RESTORE DATABASE [MBAM Compliance Status Database]
|
||||
|
||||
` FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'`
|
||||
FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'
|
||||
|
||||
` WITH REPLACE`
|
||||
WITH REPLACE
|
||||
```
|
||||
|
||||
4. Run the SQL File with a command that is similar to the following one, by using the SQL Server PowerShell:
|
||||
|
||||
|
@ -88,49 +88,51 @@ To move the Recovery Database from one computer to another (for example, from Se
|
||||
|
||||
Modify the MBAM Recovery Database to use the full recovery mode.
|
||||
|
||||
`USE master;`
|
||||
```sql
|
||||
USE master;
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`ALTER DATABASE "MBAM Recovery and Hardware"`
|
||||
ALTER DATABASE "MBAM Recovery and Hardware"
|
||||
|
||||
` SET RECOVERY FULL;`
|
||||
SET RECOVERY FULL;
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
-- Create MBAM Recovery Database Data and MBAM Recovery logical backup devices.
|
||||
|
||||
`USE master`
|
||||
USE master
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',`
|
||||
EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',
|
||||
|
||||
`'Z:\MBAM Recovery Database Data.bak';`
|
||||
'Z:\MBAM Recovery Database Data.bak';
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
-- Back up the full MBAM Recovery Database.
|
||||
|
||||
`BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];`
|
||||
BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]`
|
||||
BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]
|
||||
|
||||
`TO FILE = 'Z:\SQLServerInstanceCertificateFile'`
|
||||
TO FILE = 'Z:\SQLServerInstanceCertificateFile'
|
||||
|
||||
`WITH PRIVATE KEY`
|
||||
WITH PRIVATE KEY
|
||||
|
||||
`(`
|
||||
(
|
||||
|
||||
` FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
|
||||
FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
|
||||
|
||||
` ENCRYPTION BY PASSWORD = '$PASSWORD$'`
|
||||
ENCRYPTION BY PASSWORD = '$PASSWORD$'
|
||||
|
||||
`);`
|
||||
);
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
**Note**
|
||||
Replace the following values in the example above with those that match your environment:
|
||||
@ -183,43 +185,45 @@ To move the Recovery Database from one computer to another (for example, from Se
|
||||
|
||||
4. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
|
||||
|
||||
`-- Restore MBAM Recovery Database. `
|
||||
```sql
|
||||
-- Restore MBAM Recovery Database.
|
||||
|
||||
`USE master`
|
||||
USE master
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
-- Drop certificate created by MBAM Setup.
|
||||
|
||||
`DROP CERTIFICATE [MBAM Recovery Encryption Certificate]`
|
||||
DROP CERTIFICATE [MBAM Recovery Encryption Certificate]
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
--Add certificate
|
||||
|
||||
`CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]`
|
||||
CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]
|
||||
|
||||
`FROM FILE = 'Z: \SQLServerInstanceCertificateFile'`
|
||||
FROM FILE = 'Z: \SQLServerInstanceCertificateFile'
|
||||
|
||||
`WITH PRIVATE KEY`
|
||||
WITH PRIVATE KEY
|
||||
|
||||
`(`
|
||||
(
|
||||
|
||||
` FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
|
||||
FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
|
||||
|
||||
` DECRYPTION BY PASSWORD = '$PASSWORD$'`
|
||||
DECRYPTION BY PASSWORD = '$PASSWORD$'
|
||||
|
||||
`);`
|
||||
);
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
-- Restore the MBAM Recovery Database data and log files.
|
||||
|
||||
`RESTORE DATABASE [MBAM Recovery and Hardware]`
|
||||
RESTORE DATABASE [MBAM Recovery and Hardware]
|
||||
|
||||
` FROM DISK = 'Z:\MBAM Recovery Database Data.bak'`
|
||||
FROM DISK = 'Z:\MBAM Recovery Database Data.bak'
|
||||
|
||||
` WITH REPLACE`
|
||||
WITH REPLACE
|
||||
```
|
||||
|
||||
**Note**
|
||||
Replace the following values in the example above with those that match your environment:
|
||||
@ -362,35 +366,37 @@ If you want to move the MBAM Compliance and Audit Database from one computer to
|
||||
|
||||
2. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
|
||||
|
||||
`-- Modify the MBAM Compliance Status Database to use the full recovery model.`
|
||||
```sql
|
||||
-- Modify the MBAM Compliance Status Database to use the full recovery model.
|
||||
|
||||
`USE master;`
|
||||
USE master;
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`ALTER DATABASE "MBAM Compliance Status"`
|
||||
ALTER DATABASE "MBAM Compliance Status"
|
||||
|
||||
` SET RECOVERY FULL;`
|
||||
SET RECOVERY FULL;
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`-- Create MBAM Compliance Status Data logical backup devices.`
|
||||
-- Create MBAM Compliance Status Data logical backup devices.
|
||||
|
||||
`USE master`
|
||||
USE master
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
`EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',`
|
||||
EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',
|
||||
|
||||
`'Z: \MBAM Compliance Status Database Data.bak';`
|
||||
'Z: \MBAM Compliance Status Database Data.bak';
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
-- Back up the full MBAM Recovery database.
|
||||
|
||||
`BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];`
|
||||
BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];
|
||||
|
||||
`GO`
|
||||
GO
|
||||
```
|
||||
|
||||
3. Run the SQL file by using a Windows PowerShell command line that is similar to the following:
|
||||
|
||||
@ -430,19 +436,21 @@ If you want to move the MBAM Compliance and Audit Database from one computer to
|
||||
|
||||
3. To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
|
||||
|
||||
`-- Create MBAM Compliance Status Database Data logical backup devices. `
|
||||
```sql
|
||||
-- Create MBAM Compliance Status Database Data logical backup devices.
|
||||
|
||||
`Use master`
|
||||
Use master
|
||||
|
||||
`GO`
|
||||
GO
|
||||
|
||||
-- Restore the MBAM Compliance Status database data files.
|
||||
|
||||
`RESTORE DATABASE [MBAM Compliance Status]`
|
||||
RESTORE DATABASE [MBAM Compliance Status]
|
||||
|
||||
` FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'`
|
||||
FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'
|
||||
|
||||
` WITH REPLACE`
|
||||
WITH REPLACE
|
||||
```
|
||||
|
||||
4. Run the SQL File by using a Windows PowerShell command line that is similar to the following:
|
||||
|
||||
|
@ -240,7 +240,7 @@ Version identifies the version of the settings location template for administrat
|
||||
|
||||
**Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!--
|
||||
Version History
|
||||
|
||||
@ -279,8 +279,8 @@ Author identifies the creator of the settings location template. Two optional ch
|
||||
|
||||
Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example:
|
||||
|
||||
``` syntax
|
||||
<Process>
|
||||
```xml
|
||||
<Process>
|
||||
<Filename>MyApplication.exe</Filename>
|
||||
<Architecture>Win64</Architecture>
|
||||
<ProductName> MyApplication </ProductName>
|
||||
@ -297,7 +297,7 @@ Processes contains at least one `<Process>` element, which in turn contains the
|
||||
<Build Minimum="0" Maximum="0" />
|
||||
<Patch Minimum="5" Maximum="5" />
|
||||
</FileVersion>
|
||||
</Process>
|
||||
</Process>
|
||||
```
|
||||
|
||||
### Filename
|
||||
@ -354,14 +354,14 @@ UE-V does not support ARM processors in this version.
|
||||
|
||||
ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example:
|
||||
|
||||
``` syntax
|
||||
<Process>
|
||||
```xml
|
||||
<Process>
|
||||
<Filename>MyApplication.exe</Filename>
|
||||
<ProductName>My Application 6.x by Contoso.com</ProductName>
|
||||
<ProductVersion>
|
||||
<Major Minimum="6" Maximum="6" />
|
||||
</ProductVersion>
|
||||
</Process>
|
||||
</Process>
|
||||
```
|
||||
|
||||
### FileDescription
|
||||
@ -374,9 +374,8 @@ FileDescription is an optional tag that allows for an administrative description
|
||||
|
||||
For example, in a suited application, it might be useful to provide reminders about the function of two executables (MyApplication.exe and MyApplicationHelper.exe), as shown here:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Processes>
|
||||
|
||||
<Process>
|
||||
<Filename>MyApplication.exe</Filename>
|
||||
<FileDescription>My Application Main Engine</ FileDescription>
|
||||
@ -408,44 +407,44 @@ The product and file version elements may be left unspecified. Doing so makes th
|
||||
|
||||
Product version: 1.0 specified in the UE-V Generator produces the following XML:
|
||||
|
||||
``` syntax
|
||||
<ProductVersion>
|
||||
```xml
|
||||
<ProductVersion>
|
||||
<Major Minimum="1" Maximum="1" />
|
||||
<Minor Minimum="0" Maximum="0" />
|
||||
</ProductVersion>
|
||||
</ProductVersion>
|
||||
```
|
||||
|
||||
**Example 2:**
|
||||
|
||||
File version: 5.0.2.1000 specified in the UE-V Generator produces the following XML:
|
||||
|
||||
``` syntax
|
||||
<FileVersion>
|
||||
```xml
|
||||
<FileVersion>
|
||||
<Major Minimum="5" Maximum="5" />
|
||||
<Minor Minimum="0" Maximum="0" />
|
||||
<Build Minimum="2" Maximum="2" />
|
||||
<Patch Minimum="1000" Maximum="1000" />
|
||||
</FileVersion>
|
||||
</FileVersion>
|
||||
```
|
||||
|
||||
**Incorrect Example 1 – incomplete range:**
|
||||
|
||||
Only the Minimum attribute is present. Maximum must be included in a range as well.
|
||||
|
||||
``` syntax
|
||||
<ProductVersion>
|
||||
```xml
|
||||
<ProductVersion>
|
||||
<Major Minimum="2" />
|
||||
</ProductVersion>
|
||||
</ProductVersion>
|
||||
```
|
||||
|
||||
**Incorrect Example 2 – Minor specified without Major element:**
|
||||
|
||||
Only the Minor element is present. Major must be included as well.
|
||||
|
||||
``` syntax
|
||||
<ProductVersion>
|
||||
```xml
|
||||
<ProductVersion>
|
||||
<Minor Minimum="0" Maximum="0" />
|
||||
</ProductVersion>
|
||||
</ProductVersion>
|
||||
```
|
||||
|
||||
### FileVersion
|
||||
@ -462,8 +461,8 @@ Including a FileVersion element for an application allows for more granular fine
|
||||
|
||||
The child elements and syntax rules for FileVersion are identical to those of ProductVersion.
|
||||
|
||||
``` syntax
|
||||
<Process>
|
||||
```xml
|
||||
<Process>
|
||||
<Filename>MSACCESS.EXE</Filename>
|
||||
<Architecture>Win32</Architecture>
|
||||
<ProductVersion>
|
||||
@ -474,7 +473,7 @@ The child elements and syntax rules for FileVersion are identical to those of Pr
|
||||
<Major Minimum="14" Maximum="14" />
|
||||
<Minor Minimum="0" Maximum="0" />
|
||||
</FileVersion>
|
||||
</Process>
|
||||
</Process>
|
||||
```
|
||||
|
||||
### <a href="" id="application21"></a>Application Element
|
||||
@ -1177,8 +1176,8 @@ Version identifies the version of the settings location template for administrat
|
||||
|
||||
**Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
|
||||
|
||||
``` syntax
|
||||
<!--
|
||||
```xml
|
||||
<!--
|
||||
Version History
|
||||
|
||||
Version 1 Jul 05, 2012 Initial template created by Generator - Denise@Contoso.com
|
||||
@ -1186,7 +1185,7 @@ Version identifies the version of the settings location template for administrat
|
||||
Version 3 Jan 01, 2013 Added font settings support - Mark@Contoso.com
|
||||
Version 4 Jan 31, 2013 Added support for plugin settings - Tony@Contoso.com
|
||||
-->
|
||||
<Version>4</Version>
|
||||
<Version>4</Version>
|
||||
```
|
||||
|
||||
**Important**
|
||||
@ -1216,8 +1215,8 @@ Author identifies the creator of the settings location template. Two optional ch
|
||||
|
||||
Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example:
|
||||
|
||||
``` syntax
|
||||
<Process>
|
||||
```xml
|
||||
<Process>
|
||||
<Filename>MyApplication.exe</Filename>
|
||||
<Architecture>Win64</Architecture>
|
||||
<ProductName> MyApplication </ProductName>
|
||||
@ -1234,7 +1233,7 @@ Processes contains at least one `<Process>` element, which in turn contains the
|
||||
<Build Minimum="0" Maximum="0" />
|
||||
<Patch Minimum="5" Maximum="5" />
|
||||
</FileVersion>
|
||||
</Process>
|
||||
</Process>
|
||||
```
|
||||
|
||||
### Filename
|
||||
@ -1291,14 +1290,14 @@ UE-V does not support ARM processors in this version.
|
||||
|
||||
ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example:
|
||||
|
||||
``` syntax
|
||||
<Process>
|
||||
```xml
|
||||
<Process>
|
||||
<Filename>MyApplication.exe</Filename>
|
||||
<ProductName>My Application 6.x by Contoso.com</ProductName>
|
||||
<ProductVersion>
|
||||
<Major Minimum="6" Maximum="6" />
|
||||
</ProductVersion>
|
||||
</Process>
|
||||
</Process>
|
||||
```
|
||||
|
||||
### FileDescription
|
||||
@ -1311,9 +1310,8 @@ FileDescription is an optional tag that allows for an administrative description
|
||||
|
||||
For example, in a suited application, it might be useful to provide reminders about the function of two executables (MyApplication.exe and MyApplicationHelper.exe), as shown here:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Processes>
|
||||
|
||||
<Process>
|
||||
<Filename>MyApplication.exe</Filename>
|
||||
<FileDescription>My Application Main Engine</ FileDescription>
|
||||
@ -1345,44 +1343,44 @@ The product and file version elements may be left unspecified. Doing so makes th
|
||||
|
||||
Product version: 1.0 specified in the UE-V Generator produces the following XML:
|
||||
|
||||
``` syntax
|
||||
<ProductVersion>
|
||||
```xml
|
||||
<ProductVersion>
|
||||
<Major Minimum="1" Maximum="1" />
|
||||
<Minor Minimum="0" Maximum="0" />
|
||||
</ProductVersion>
|
||||
</ProductVersion>
|
||||
```
|
||||
|
||||
**Example 2:**
|
||||
|
||||
File version: 5.0.2.1000 specified in the UE-V Generator produces the following XML:
|
||||
|
||||
``` syntax
|
||||
<FileVersion>
|
||||
```xml
|
||||
<FileVersion>
|
||||
<Major Minimum="5" Maximum="5" />
|
||||
<Minor Minimum="0" Maximum="0" />
|
||||
<Build Minimum="2" Maximum="2" />
|
||||
<Patch Minimum="1000" Maximum="1000" />
|
||||
</FileVersion>
|
||||
</FileVersion>
|
||||
```
|
||||
|
||||
**Incorrect Example 1 – incomplete range:**
|
||||
|
||||
Only the Minimum attribute is present. Maximum must be included in a range as well.
|
||||
|
||||
``` syntax
|
||||
<ProductVersion>
|
||||
```xml
|
||||
<ProductVersion>
|
||||
<Major Minimum="2" />
|
||||
</ProductVersion>
|
||||
</ProductVersion>
|
||||
```
|
||||
|
||||
**Incorrect Example 2 – Minor specified without Major element:**
|
||||
|
||||
Only the Minor element is present. Major must be included as well.
|
||||
|
||||
``` syntax
|
||||
<ProductVersion>
|
||||
```xml
|
||||
<ProductVersion>
|
||||
<Minor Minimum="0" Maximum="0" />
|
||||
</ProductVersion>
|
||||
</ProductVersion>
|
||||
```
|
||||
|
||||
### FileVersion
|
||||
@ -1399,8 +1397,8 @@ Including a FileVersion element for an application allows for more granular fine
|
||||
|
||||
The child elements and syntax rules for FileVersion are identical to those of ProductVersion.
|
||||
|
||||
``` syntax
|
||||
<Process>
|
||||
```xml
|
||||
<Process>
|
||||
<Filename>MSACCESS.EXE</Filename>
|
||||
<Architecture>Win32</Architecture>
|
||||
<ProductVersion>
|
||||
@ -1411,7 +1409,7 @@ The child elements and syntax rules for FileVersion are identical to those of Pr
|
||||
<Major Minimum="14" Maximum="14" />
|
||||
<Minor Minimum="0" Maximum="0" />
|
||||
</FileVersion>
|
||||
</Process>
|
||||
</Process>
|
||||
```
|
||||
|
||||
### <a href="" id="application"></a>Application Element
|
||||
|
@ -43,13 +43,11 @@ Microsoft Store adds the app to **Products and services**. Click **Manage**, **A
|
||||
|
||||
<!---  -->
|
||||
|
||||
3. Use **Refine results** to search for online-licensed apps under **License type**.
|
||||
4. From the list of online-licensed apps, click the ellipses for the app you want, and then choose **Add to private store**.
|
||||
3. Click on the application to open the application settings, then select **Private store availability**.
|
||||
4. Select **Everyone** to make application available for all people in your organization.
|
||||
|
||||
<!---  -->
|
||||
|
||||
The value under **Private store** for the app will change to pending. It will take approximately thirty-six hours before the app is available in the private store.
|
||||
|
||||
>[!Note]
|
||||
> If you are working with a new Line-of-Business (LOB) app, you have to wait for the app to be available in **Products & services** before adding it to your private store. For more information, see [Working with line-of-business apps](working-with-line-of-business-apps.md).
|
||||
|
||||
|
@ -42,7 +42,7 @@ Before attempting this procedure, you should read and understand the information
|
||||
|
||||
2. To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
|
||||
|
||||
``` syntax
|
||||
```powershell
|
||||
<#
|
||||
.SYNOPSIS
|
||||
This Windows PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats.
|
||||
@ -59,9 +59,6 @@ Before attempting this procedure, you should read and understand the information
|
||||
.\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\SIDs.txt -Width 200
|
||||
#>
|
||||
|
||||
[]()
|
||||
|
||||
[]()
|
||||
function ConvertSIDToHexFormat
|
||||
{
|
||||
param([System.Security.Principal.SecurityIdentifier]$sidToConvert)
|
||||
|
@ -60,13 +60,13 @@ When managing over OMA DM, make sure to always use a unique GUID. Provisioning w
|
||||
|
||||
Braces { } are required around the GUID. In OMA Client Provisioning, you can type the braces. For example:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<characteristic type="{C556E16F-56C4-4EDB-9C64-D9469EE1FBE0}"/>
|
||||
```
|
||||
|
||||
For OMA DM, you must use the ASCII values of %7B and %7D for the opening and closing braces, respectively. For example, if the GUID is "C556E16F-56C4-4EDB-9C64-D9469EE1FBE0", type:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Target>
|
||||
<LocURI>
|
||||
./Vendor/MSFT/ActiveSync/Accounts/%7BC556E16F-56C4-4EDB-9C64-D9469EE1FBE0%7D
|
||||
|
@ -14,6 +14,7 @@ ms.date: 09/18/2018
|
||||
|
||||
# AssignedAccess CSP
|
||||
|
||||
**Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.**
|
||||
|
||||
The AssignedAccess configuration service provider (CSP) is used to set the device to run in kiosk mode. Once the CSP has been executed, then the next user login that is associated with the kiosk mode puts the device into the kiosk mode running the application specified in the CSP configuration.
|
||||
|
||||
@ -134,7 +135,7 @@ Additionally, the Status payload includes the following fields:
|
||||
Supported operation is Get.
|
||||
|
||||
<a href="" id="assignedaccess-shelllauncher"></a>**./Device/Vendor/MSFT/AssignedAccess/ShellLauncher**
|
||||
Added in Windows 10,version 1803. This node accepts a ShellLauncherConfiguration xml as input. Click [link](#shelllauncherconfiguration-xsd) to see the schema. Shell Launcher V2 is introduced in Windows 10, version 1903 to support both UWP and Win32 apps as the custom shell. For more information, see [Shell Launcher](https://docs.microsoft.com/en-us/windows/configuration/kiosk-shelllauncher).
|
||||
Added in Windows 10,version 1803. This node accepts a ShellLauncherConfiguration xml as input. Click [link](#shelllauncherconfiguration-xsd) to see the schema. Shell Launcher V2 is introduced in Windows 10, version 1903 to support both UWP and Win32 apps as the custom shell. For more information, see [Shell Launcher](https://docs.microsoft.com/windows/configuration/kiosk-shelllauncher).
|
||||
|
||||
> [!Note]
|
||||
> You cannot set both ShellLauncher and KioskModeApp at the same time on the device.
|
||||
@ -246,6 +247,8 @@ KioskModeApp Replace
|
||||
|
||||
## AssignedAccessConfiguration XSD
|
||||
|
||||
Below schema is for AssignedAccess Configuration up to Windows 10 1803 release.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<xs:schema
|
||||
@ -253,9 +256,14 @@ KioskModeApp Replace
|
||||
xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:default="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:rs5="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
targetNamespace="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
>
|
||||
|
||||
<xs:import namespace="http://schemas.microsoft.com/AssignedAccess/201810/config"/>
|
||||
<xs:import namespace="http://schemas.microsoft.com/AssignedAccess/2020/config"/>
|
||||
|
||||
<xs:complexType name="profile_list_t">
|
||||
<xs:sequence minOccurs="1" >
|
||||
<xs:element name="Profile" type="profile_t" minOccurs="1" maxOccurs="unbounded"/>
|
||||
@ -270,6 +278,7 @@ KioskModeApp Replace
|
||||
<xs:choice>
|
||||
<xs:sequence minOccurs="1" maxOccurs="1">
|
||||
<xs:element name="AllAppsList" type="allappslist_t" minOccurs="1" maxOccurs="1"/>
|
||||
<xs:element ref="rs5:FileExplorerNamespaceRestrictions" minOccurs="0" maxOccurs="1"/>
|
||||
<xs:element name="StartLayout" type="xs:string" minOccurs="1" maxOccurs="1"/>
|
||||
<xs:element name="Taskbar" type="taskbar_t" minOccurs="1" maxOccurs="1"/>
|
||||
</xs:sequence>
|
||||
@ -286,6 +295,10 @@ KioskModeApp Replace
|
||||
<xs:selector xpath="default:App"/>
|
||||
<xs:field xpath="@AppUserModelId|@DesktopAppPath"/>
|
||||
</xs:unique>
|
||||
<xs:unique name="OnlyOneAppCanHaveAutoLaunch">
|
||||
<xs:selector xpath="default:App"/>
|
||||
<xs:field xpath="@rs5:AutoLaunch"/>
|
||||
</xs:unique>
|
||||
</xs:element>
|
||||
</xs:sequence>
|
||||
</xs:complexType>
|
||||
@ -304,8 +317,14 @@ KioskModeApp Replace
|
||||
<xs:complexType name="app_t">
|
||||
<xs:attribute name="AppUserModelId" type="xs:string"/>
|
||||
<xs:attribute name="DesktopAppPath" type="xs:string"/>
|
||||
<xs:attributeGroup ref="autoLaunch_attributeGroup"/>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:attributeGroup name="autoLaunch_attributeGroup">
|
||||
<xs:attribute ref="rs5:AutoLaunch"/>
|
||||
<xs:attribute ref="rs5:AutoLaunchArguments" use="optional"/>
|
||||
</xs:attributeGroup>
|
||||
|
||||
<xs:complexType name="taskbar_t">
|
||||
<xs:attribute name="ShowTaskbar" type="xs:boolean" use="required"/>
|
||||
</xs:complexType>
|
||||
@ -322,7 +341,8 @@ KioskModeApp Replace
|
||||
|
||||
<xs:complexType name="config_list_t">
|
||||
<xs:sequence minOccurs="1" >
|
||||
<xs:element name="Config" type="config_t" minOccurs="1" maxOccurs="unbounded"/>
|
||||
<xs:element ref="v3:GlobalProfile" minOccurs="0" maxOccurs="1"/>
|
||||
<xs:element name="Config" type="config_t" minOccurs="0" maxOccurs="unbounded"/>
|
||||
</xs:sequence>
|
||||
</xs:complexType>
|
||||
|
||||
@ -340,6 +360,7 @@ KioskModeApp Replace
|
||||
|
||||
<xs:complexType name="autologon_account_t">
|
||||
<xs:attribute name="HiddenId" type="guid_t" fixed="{74331115-F68A-4DF9-8D2C-52BA2CE2ADB1}"/>
|
||||
<xs:attribute ref="rs5:DisplayName" use="optional" />
|
||||
</xs:complexType>
|
||||
|
||||
<xs:complexType name="group_t">
|
||||
@ -365,6 +386,22 @@ KioskModeApp Replace
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
|
||||
<xs:complexType name="fileExplorerNamespaceRestrictions_t">
|
||||
<xs:sequence minOccurs="1">
|
||||
<xs:element name="AllowedNamespace" type="allowedFileExplorerNamespace_t"/>
|
||||
</xs:sequence>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:complexType name="allowedFileExplorerNamespace_t">
|
||||
<xs:attribute name="Name" type="allowedFileExplorerNamespaceValues_t"/>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:simpleType name="allowedFileExplorerNamespaceValues_t">
|
||||
<xs:restriction base="xs:string">
|
||||
<xs:enumeration value="Downloads"/>
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
|
||||
<!--below is the definition of the config xml content-->
|
||||
<xs:element name="AssignedAccessConfiguration">
|
||||
<xs:complexType>
|
||||
@ -385,7 +422,94 @@ KioskModeApp Replace
|
||||
</xs:complexType>
|
||||
</xs:element>
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
Here is the schema for new features introduced in Windows 10 1809 release
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<xs:schema
|
||||
elementFormDefault="qualified"
|
||||
xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:default="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
targetNamespace="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
>
|
||||
|
||||
<xs:import namespace="http://schemas.microsoft.com/AssignedAccess/2020/config"/>
|
||||
|
||||
<xs:complexType name="fileExplorerNamespaceRestrictions_t">
|
||||
<xs:choice>
|
||||
<xs:sequence minOccurs="0">
|
||||
<xs:element name="AllowedNamespace" type="allowedFileExplorerNamespace_t" minOccurs="0"/>
|
||||
<xs:element ref="v3:AllowRemovableDrives" minOccurs="0" maxOccurs="1"/>
|
||||
</xs:sequence>
|
||||
<xs:element ref="v3:NoRestriction" minOccurs="0" maxOccurs="1" />
|
||||
</xs:choice>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:complexType name="allowedFileExplorerNamespace_t">
|
||||
<xs:attribute name="Name" type="allowedFileExplorerNamespaceValues_t" use="required"/>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:simpleType name="allowedFileExplorerNamespaceValues_t">
|
||||
<xs:restriction base="xs:string">
|
||||
<xs:enumeration value="Downloads"/>
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
|
||||
<xs:element name="FileExplorerNamespaceRestrictions" type="fileExplorerNamespaceRestrictions_t" />
|
||||
|
||||
<xs:attribute name="AutoLaunch" type="xs:boolean"/>
|
||||
|
||||
<xs:attribute name="AutoLaunchArguments" type="xs:string"/>
|
||||
|
||||
<xs:attribute name="DisplayName" type="xs:string"/>
|
||||
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
Schema for Windows 10 prerelease
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<xs:schema
|
||||
elementFormDefault="qualified"
|
||||
xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
xmlns:default="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
xmlns:vc="http://www.w3.org/2007/XMLSchema-versioning"
|
||||
vc:minVersion="1.1"
|
||||
targetNamespace="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
>
|
||||
|
||||
<xs:simpleType name="guid_t">
|
||||
<xs:restriction base="xs:string">
|
||||
<xs:pattern value="\{[0-9a-fA-F]{8}\-([0-9a-fA-F]{4}\-){3}[0-9a-fA-F]{12}\}"/>
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
|
||||
<xs:complexType name="globalProfile_t">
|
||||
<xs:attribute name="Id" type="guid_t" />
|
||||
</xs:complexType>
|
||||
|
||||
<xs:element name="AllowRemovableDrives"/>
|
||||
<xs:element name="NoRestriction" />
|
||||
<xs:element name="GlobalProfile" type="globalProfile_t" />
|
||||
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
To authorize a compatible configuration XML that includes 1809 or prerelease elements and attributes, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. e.g. to configure auto-launch feature which is added in 1809 release, use below sample, notice an alias r1809 is given to the 201810 namespace for 1809 release, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
|
||||
```xml
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:r1809="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
>
|
||||
<Profiles>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" r1809:AutoLaunch="true" r1809:AutoLaunchArguments="1.txt"/>
|
||||
```
|
||||
|
||||
## Example AssignedAccessConfiguration XML
|
||||
@ -796,7 +920,7 @@ StatusConfiguration Get
|
||||
|
||||
StatusConfiguration Replace On
|
||||
|
||||
```syntax
|
||||
```xml
|
||||
<SyncML xmlns='SYNCML:SYNCML1.2'>
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -1219,7 +1343,7 @@ ShellLauncherConfiguration Get
|
||||
|
||||
## AssignedAccessAlert XSD
|
||||
|
||||
```syntax
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<xs:schema
|
||||
elementFormDefault="qualified"
|
||||
|
@ -360,7 +360,7 @@ Supported operations are Add, Get, and Replace.
|
||||
|
||||
Add a root certificate to the MDM server.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
@ -379,7 +379,7 @@ Add a root certificate to the MDM server.
|
||||
|
||||
Get all installed client certificates.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
@ -394,7 +394,7 @@ Get all installed client certificates.
|
||||
|
||||
Delete a root certificate.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
@ -409,7 +409,7 @@ Delete a root certificate.
|
||||
|
||||
Configure the device to enroll a client certificate through SCEP.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Atomic>
|
||||
<CmdID>100</CmdID>
|
||||
<Add>
|
||||
@ -588,7 +588,7 @@ Configure the device to enroll a client certificate through SCEP.
|
||||
|
||||
Configure the device to automatically renew an MDM client certificate with the specified renew period and retry interval.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Atomic>
|
||||
<CmdID>1</CmdID>
|
||||
<Replace>
|
||||
|
@ -198,7 +198,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid
|
||||
|
||||
To delete a connection, you must first delete any associated proxies and then delete the connection. The following example shows how to delete the proxy and then the connection.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
<characteristic type="CM_ProxyEntries">
|
||||
<nocharacteristic type="GPRS_Proxy"/>
|
||||
@ -214,7 +214,7 @@ To delete a connection, you must first delete any associated proxies and then de
|
||||
|
||||
Configuring a GPRS connection:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
<characteristic type="CM_CellularEntries">
|
||||
<characteristic type="GPRSConn">
|
||||
@ -231,7 +231,7 @@ Configuring a GPRS connection:
|
||||
|
||||
Configuring an LTE connection:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
<characteristic type="CM_CellularEntries">
|
||||
<characteristic type="LteConn">
|
||||
@ -250,7 +250,7 @@ Configuring an LTE connection:
|
||||
|
||||
Configuring a CDMA connection:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
<characteristic type="CM_CellularEntries">
|
||||
<characteristic type="CDMAConn">
|
||||
|
@ -240,7 +240,7 @@ Specifies the type of connection being referenced. The following list describes
|
||||
|
||||
Adding an application-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
|
||||
<characteristic type="CM_CellularEntries">
|
||||
@ -285,7 +285,7 @@ Adding an application-based mapping policy. In this example, the ConnectionId fo
|
||||
|
||||
Adding a host-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
|
||||
<characteristic type="CM_CellularEntries">
|
||||
@ -334,7 +334,7 @@ Adding a host-based mapping policy. In this example, the ConnectionId for type C
|
||||
|
||||
Adding an application-based mapping policy:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Atomic>
|
||||
@ -401,7 +401,7 @@ Adding an application-based mapping policy:
|
||||
|
||||
Adding a host-based mapping policy:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Atomic>
|
||||
|
@ -240,7 +240,7 @@ Specifies the type of connection being referenced. The following list describes
|
||||
|
||||
Adding an application-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
|
||||
<characteristic type="CM_CellularEntries">
|
||||
@ -285,7 +285,7 @@ Adding an application-based mapping policy. In this example, the ConnectionId fo
|
||||
|
||||
Adding a host-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
|
||||
<characteristic type="CM_CellularEntries">
|
||||
@ -334,7 +334,7 @@ Adding a host-based mapping policy. In this example, the ConnectionId for type C
|
||||
|
||||
Adding an application-based mapping policy:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Atomic>
|
||||
@ -401,7 +401,7 @@ Adding an application-based mapping policy:
|
||||
|
||||
Adding a host-based mapping policy:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Atomic>
|
||||
|
@ -38,7 +38,7 @@ Package Full Name of the App that needs be launched in the background. This can
|
||||
|
||||
**Set StartupAppID**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -60,7 +60,7 @@ Package Full Name of the App that needs be launched in the background. This can
|
||||
|
||||
**Get all background tasks**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Get>
|
||||
@ -78,7 +78,7 @@ Package Full Name of the App that needs be launched in the background. This can
|
||||
|
||||
**Add background task**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Add>
|
||||
|
@ -648,7 +648,7 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
|
||||
|
||||
Example
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
<Item>
|
||||
@ -919,7 +919,7 @@ The following screenshots of the administrator console shows the list of update
|
||||
|
||||
Set auto update to notify and defer.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
<SyncBody>
|
||||
<Replace xmlns="">
|
||||
|
@ -70,7 +70,7 @@ The parent node to group SIM2 specific information in case of dual SIM mode.
|
||||
|
||||
The following sample shows how to query roaming status and phone number on the device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -88,7 +88,7 @@ The following sample shows how to query roaming status and phone number on the d
|
||||
|
||||
Response from the phone.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Results>
|
||||
<CmdID>3</CmdID>
|
||||
<MsgRef>1</MsgRef>
|
||||
|
@ -126,7 +126,7 @@ Required. This node has the same set of policy nodes as the **ProviderID** node.
|
||||
|
||||
Set device lock policies:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Atomic>
|
||||
<CmdID>13</CmdID>
|
||||
<Add>
|
||||
|
@ -420,7 +420,7 @@ Default value is 0 meaning no keyword.
|
||||
|
||||
Get provider **Keywords**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Get>
|
||||
@ -440,7 +440,7 @@ Get provider **Keywords**
|
||||
|
||||
Set provider **Keywords**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
|
@ -105,7 +105,7 @@ After the previous package is sent, the unenrollment process begins.
|
||||
|
||||
When the server initiates disconnection, all undergoing sessions for the enrollment ID are aborted immediately to avoid deadlocks. The server will not get a response for the unenrollment, instead a generic alert notification is sent with messageid=1.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Alert>
|
||||
<CmdID>4</CmdID>
|
||||
<Data>1226</Data>
|
||||
|
@ -70,7 +70,7 @@ Supported operation is Get.
|
||||
|
||||
The following is a Get command example.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>12</CmdID>
|
||||
<Item>
|
||||
@ -173,7 +173,7 @@ To work around the timeout, you can use this setting to keep the session alive b
|
||||
|
||||
Here is an example of DM message sent by the device when it is in pending state:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncHdr>
|
||||
<VerDTD>1.2</VerDTD>
|
||||
@ -229,7 +229,7 @@ Added in Windows 10, version 1607. The list of management server URLs in the fo
|
||||
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>101</CmdID>
|
||||
<Item>
|
||||
@ -770,7 +770,7 @@ Note that <LocURI>./Vendor/MSFT/DMClient/Unenroll</LocURI> is suppor
|
||||
|
||||
The following SyncML shows how to remotely unenroll the device. Note that this command should be inserted in the general DM packages sent from the server to the device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Exec>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
|
@ -29,7 +29,7 @@ The following diagram shows the DynamicManagement configuration service provider
|
||||
<p style="margin-left: 20px">Default value is False. Supported operations are Get and Replace.</p>
|
||||
<p style="margin-left: 20px">Example to turn on NotificationsEnabled:</p>
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>100</CmdID>
|
||||
<Item>
|
||||
@ -84,7 +84,7 @@ The following diagram shows the DynamicManagement configuration service provider
|
||||
|
||||
Disable Cortana based on Geo location and time, From 9am-5pm, when in the 100 meters radius of the specified latitude/longitude
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>200</CmdID>
|
||||
<Item>
|
||||
@ -138,7 +138,7 @@ Disable Cortana based on Geo location and time, From 9am-5pm, when in the 100 me
|
||||
|
||||
Disable camera using network trigger with time trigger, from 9-5, when ip4 gateway is 192.168.0.1
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>300</CmdID>
|
||||
<Item>
|
||||
@ -193,7 +193,7 @@ Disable camera using network trigger with time trigger, from 9-5, when ip4 gatew
|
||||
|
||||
Delete a context
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Delete>
|
||||
<CmdID>400</CmdID>
|
||||
<Item>
|
||||
@ -206,7 +206,7 @@ Delete a context
|
||||
|
||||
Get ContextStatus and SignalDefinition from a specific context
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>400</CmdID>
|
||||
<Item>
|
||||
|
@ -64,7 +64,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
|
||||
> [!NOTE]
|
||||
> The \<Data> payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -114,7 +114,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
|
||||
|
||||
Here is the snippet from appv.admx:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Publishing Server 2 -->
|
||||
<policy name="Publishing_Server2_Policy" class="Machine" displayName="$(string.PublishingServer2)"
|
||||
explainText="$(string.Publishing_Server_Help)" presentation="$(presentation.Publishing_Server2)"
|
||||
@ -206,7 +206,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
|
||||
|
||||
Here is the example XML for Publishing_Server2_Policy :
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<data id="Publishing_Server2_Name_Prompt" value="Name"/>
|
||||
<data id="Publishing_Server_URL_Prompt" value="http://someuri"/>
|
||||
<data id="Global_Publishing_Refresh_Options" value="1"/>
|
||||
@ -226,7 +226,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
|
||||
> [!NOTE]
|
||||
> The \<Data> payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
@ -264,7 +264,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
|
||||
|
||||
The \<Data> payload is \<disabled/>. Here is an example to disable AppVirtualization/PublishingAllowServer2.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
|
@ -275,7 +275,7 @@ After the installation of updates is completed, the IT Admin can use the DURepor
|
||||
<a href="" id="example-script"></a>
|
||||
## Example PowerShell script
|
||||
|
||||
``` syntax
|
||||
```powershell
|
||||
param (
|
||||
# [Parameter (Mandatory=$true, HelpMessage="Input File")]
|
||||
[String]$inputFile,
|
||||
|
@ -78,7 +78,7 @@ Note that performing a full inventory of a device can be resource intensive on t
|
||||
|
||||
Here is an example of a query for all apps on the device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get all apps under AppManagement -->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -92,7 +92,7 @@ Here is an example of a query for all apps on the device.
|
||||
|
||||
Here is an example of a query for a specific app for a user.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get all information of a specific app for a user -->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -121,7 +121,7 @@ For detailed descriptions of each node, see [EnterpriseModernAppManagement CSP](
|
||||
|
||||
Here is an example of a query for all app licenses on a device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get all app licenses for the device -->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -135,7 +135,7 @@ Here is an example of a query for all app licenses on a device.
|
||||
|
||||
Here is an example of a query for all app licenses for a user.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get a specific app license for a user -->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -161,7 +161,7 @@ For more information about the AllowAllTrustedApps policy, see [Policy CSP](poli
|
||||
|
||||
Here are some examples.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get policy (Default)-->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -199,7 +199,7 @@ For more information about the AllowDeveloperUnlock policy, see [Policy CSP](pol
|
||||
|
||||
Here is an example.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get policy (Default)-->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -244,7 +244,7 @@ Here are the requirements for this scenario:
|
||||
|
||||
Here are some examples.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Exec>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
@ -281,7 +281,7 @@ In the SyncML, you need to specify the following information in the Exec command
|
||||
|
||||
Here is an example of an offline license installation.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Exec>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
@ -315,7 +315,7 @@ The Add command for the package family name is required to ensure proper removal
|
||||
|
||||
Here is an example of a line-of-business app installation.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Add PackageFamilyName -->
|
||||
<Add>
|
||||
<CmdID>0</CmdID>
|
||||
@ -342,7 +342,7 @@ Here is an example of a line-of-business app installation.
|
||||
|
||||
Here is an example of an app installation with dependencies.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Add PackageFamilyName -->
|
||||
<Add>
|
||||
<CmdID>0</CmdID>
|
||||
@ -376,7 +376,7 @@ Here is an example of an app installation with dependencies.
|
||||
|
||||
Here is an example of an app installation with dependencies and optional packages.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Add PackageFamilyName -->
|
||||
<Add>
|
||||
<CmdID>0</CmdID>
|
||||
@ -438,7 +438,7 @@ Here is an example of app installation.
|
||||
> **Note** This is only supported in Windows 10 for desktop editions.
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Add PackageFamilyName -->
|
||||
<Add>
|
||||
<CmdID>0</CmdID>
|
||||
@ -475,7 +475,7 @@ Here is an example of app installation with dependencies.
|
||||
> **Note** This is only supported in Windows 10 for desktop editions.
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Add PackageFamilyName -->
|
||||
<Add>
|
||||
<CmdID>0</CmdID>
|
||||
@ -526,7 +526,7 @@ When an app is installed successfully, the node is cleaned up and no longer pres
|
||||
|
||||
Here is an example of a query for a specific app installation.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get all app status under AppInstallation for a specific app-->
|
||||
<Get>
|
||||
<CmdID>2</CmdID>
|
||||
@ -540,7 +540,7 @@ Here is an example of a query for a specific app installation.
|
||||
|
||||
Here is an example of a query for all app installations.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get all app status under AppInstallation-->
|
||||
<Get>
|
||||
<CmdID>2</CmdID>
|
||||
@ -558,7 +558,7 @@ Application installations can take some time to complete, hence they are done as
|
||||
|
||||
Here is an example of an alert.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Alert>
|
||||
<CmdID>4</CmdID>
|
||||
<Data>1226</Data>
|
||||
@ -594,7 +594,7 @@ To uninstall an app, you delete it under the origin node, package family name, a
|
||||
|
||||
Here is an example for uninstalling all versions of an app for a user.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Uninstall App for a Package Family-->
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
@ -608,7 +608,7 @@ Here is an example for uninstalling all versions of an app for a user.
|
||||
|
||||
Here is an example for uninstalling a specific version of the app for a user.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Uninstall App for a specific package full name-->
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
@ -631,7 +631,7 @@ Removing provisioned app occurs in the device context.
|
||||
|
||||
Here is an example for removing a provisioned app from a device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!— Remove Provisioned App for a Package Family-->
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
@ -645,7 +645,7 @@ Here is an example for removing a provisioned app from a device.
|
||||
|
||||
Here is an example for removing a specific version of a provisioned app from a device:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Remove Provisioned App for a specific package full name-->
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
@ -663,7 +663,7 @@ You can remove app licenses from a device per app based on the content ID.
|
||||
|
||||
Here is an example for removing an app license for a user.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Remove App License for a User-->
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
@ -677,7 +677,7 @@ Here is an example for removing an app license for a user.
|
||||
|
||||
Here is an example for removing an app license for a provisioned package (device context).
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Remove App License for a provisioned package (device) -->
|
||||
<Delete>
|
||||
<CmdID>1</CmdID>
|
||||
@ -697,7 +697,7 @@ For user-based uninstallation, use ./User in the LocURI, and for provisioning, u
|
||||
|
||||
Here is an example. There is only one uninstall for hosted and store apps.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Alert>
|
||||
<Data>1226</Data>
|
||||
<Item>
|
||||
@ -723,7 +723,7 @@ To update an app from Microsoft Store, the device requires contact with the stor
|
||||
|
||||
Here is an example of an update scan.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!— Initiate a update scan for a user-->
|
||||
<Exec>
|
||||
<CmdID>1</CmdID>
|
||||
@ -737,7 +737,7 @@ Here is an example of an update scan.
|
||||
|
||||
Here is an example of a status check.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!— Get last error related to the update scan-->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -766,7 +766,7 @@ Turning off updates only applies to updates from the Microsoft Store at the devi
|
||||
|
||||
Here is an example.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!— Prevent app from being automatically updated-->
|
||||
<Replace>
|
||||
<CmdID>1</CmdID>
|
||||
@ -795,7 +795,7 @@ You can install app on non-system volumes, such as a secondary partition or remo
|
||||
|
||||
Here is an example.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get policy (Default)-->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -832,7 +832,7 @@ The RestrictAppDataToSystemVolume policy in [Policy CSP](policy-configuration-se
|
||||
|
||||
Here is an example.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get policy (Default)-->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
@ -873,7 +873,7 @@ The valid values are 0 (off, default value) and 1 (on).
|
||||
|
||||
Here is an example.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!-- Get policy (Default)-->
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
|
@ -132,7 +132,7 @@ The following image shows the EnterpriseAPN configuration service provider in tr
|
||||
|
||||
## Examples
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!--
|
||||
Copyright (c) Microsoft Corporation. All rights reserved.
|
||||
-->
|
||||
|
@ -209,7 +209,7 @@ The Microsoft Store application has a GUID of d5dc1ebb-a7f1-df11-9264-00237de2db
|
||||
|
||||
Use the following SyncML format to query to see if the application is installed on a managed device:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
@ -222,7 +222,7 @@ Use the following SyncML format to query to see if the application is installed
|
||||
|
||||
Response from the device (it contains list of subnodes if this app is installed in the device).
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Results>
|
||||
<CmdID>3</CmdID>
|
||||
<MsgRef>1</MsgRef>
|
||||
@ -266,7 +266,7 @@ The value actually applied to the device can be queried via the nodes under the
|
||||
|
||||
Enroll enterprise ID “4000000001” for the first time:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -293,7 +293,7 @@ Enroll enterprise ID “4000000001” for the first time:
|
||||
|
||||
Update the enrollment token (for example, to update an expired application enrollment token):
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -310,7 +310,7 @@ Update the enrollment token (for example, to update an expired application enrol
|
||||
|
||||
Query all installed applications that belong to enterprise id “4000000001”:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -325,7 +325,7 @@ Query all installed applications that belong to enterprise id “4000000001”:
|
||||
|
||||
Response from the device (that contains two installed applications):
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Results>
|
||||
<CmdID>3</CmdID>
|
||||
<MsgRef>1</MsgRef>
|
||||
@ -444,7 +444,7 @@ To perform an XAP update, create the Name, URL, Version, and DownloadInstall nod
|
||||
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Atomic>
|
||||
<CmdID>2</CmdID>
|
||||
<!-- The Add command can be used if the download node does not have a matching product ID
|
||||
@ -514,7 +514,7 @@ To perform an XAP update, create the Name, URL, Version, and DownloadInstall nod
|
||||
|
||||
Uninstall an installed enterprise application with product ID “{7BB316008A-141D-4A79-810F-8B764C4CFDFB }”:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Delete>
|
||||
|
@ -61,7 +61,7 @@ Application | <img src="images/enterpriseassignedaccess-csp.png" alt="modern app
|
||||
Application | Include PinToStart to display an app on the Start screen. For apps pinned to the Start screen, identify a tile size (small, medium, or large), and a location. The size of a small tile is 1 column x 1 row, a medium tile is 2 x 2, and a large tile is 4 x 2. For the tile location, the first value indicates the column and the second value indicates the row. A value of 0 (zero) indicates the first column, a value of 1 indicates the second column, and so on. Include autoRun as an attribute to configure the application to run automatically.
|
||||
|
||||
Application example:
|
||||
``` syntax
|
||||
```xml
|
||||
<Application productId="{2A4E62D8-8809-4787-89F8-69D0F01654FB}" autoRun="true">
|
||||
<PinToStart>
|
||||
<Size>Large</Size>
|
||||
@ -78,7 +78,7 @@ Entry | Description
|
||||
Application | Multiple App Packages enable multiple apps to exist inside the same package. Since ProductIds identify packages and not applications, specifying a ProductId is not enough to distinguish between individual apps inside a multiple app package. Trying to include application from a multiple app package with just a ProductId can result in unexpected behavior. To support pinning applications in multiple app packages, use an AUMID parameter in lockdown XML. For the list of product ID and AUMID, see [ProductIDs in Windows 10 Mobile](#productid). The following example shows how to pin both Outlook mail and Outlook calendar.
|
||||
|
||||
Application example:
|
||||
``` syntax
|
||||
```xml
|
||||
<Apps>
|
||||
<!-- Outlook Calendar -->
|
||||
<Application productId="{A558FEBA-85D7-4665-B5D8-A2FF9C19799B}"
|
||||
@ -110,7 +110,7 @@ Entry | Description
|
||||
Folder | A folder should be contained in `<Applications/>` node among with other `<Application/>` nodes, it shares most grammar with the Application Node, **folderId** is mandatory, **folderName** is optional, which is the folder name displayed on Start. **folderId** is a unique unsigned integer for each folder.
|
||||
|
||||
Folder example:
|
||||
``` syntax
|
||||
```xml
|
||||
<Application folderId="4" folderName="foldername">
|
||||
<PinToStart>
|
||||
<Size>Large</Size>
|
||||
@ -123,7 +123,7 @@ Folder example:
|
||||
```
|
||||
An application that belongs in the folder would add an optional attribute **ParentFolderId**, which maps to **folderId** of the folder. In this case, the location of this application will be located inside the folder.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Application productId="{2A4E62D8-8809-4787-89F8-69D0F01654FB}">
|
||||
<PinToStart>
|
||||
<Size>Medium</Size>
|
||||
@ -252,7 +252,7 @@ For example, in place of SettingPageDisplay, you would use ms-settings:display.
|
||||
|
||||
Here is an example for Windows 10, version 1703.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Settings>
|
||||
<System name="ms-settings:display"/>
|
||||
<System name="ms-settings:appsforwebsites"/>
|
||||
@ -327,14 +327,14 @@ Starting in Windows 10, version 1703, Quick action settings no longer require an
|
||||
|
||||
In this example, all settings pages and quick action settings are allowed. An empty \<Settings> node indicates that none of the settings are blocked.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Settings>
|
||||
</Settings>
|
||||
```
|
||||
|
||||
In this example for Windows 10, version 1511, all System setting pages are enabled. Note that the System page group is added as well as all of the System subpage names.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Settings>
|
||||
<System name="SettingsPageGroupPCSystem" />
|
||||
<System name="SettingsPageDisplay" />
|
||||
@ -350,7 +350,7 @@ In this example for Windows 10, version 1511, all System setting pages are ena
|
||||
```
|
||||
Here is an example for Windows 10, version 1703.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Settings>
|
||||
<System name="ms-settings:display"/>
|
||||
<System name="ms-settings:appsforwebsites"/>
|
||||
@ -382,7 +382,7 @@ Buttons | The following list identifies the hardware buttons on the device that
|
||||
> Custom buttons are hardware buttons that can be added to devices by OEMs.
|
||||
|
||||
Buttons example:
|
||||
``` syntax
|
||||
```xml
|
||||
<Buttons>
|
||||
<ButtonLockdownList>
|
||||
<!-- Lockdown all buttons -->
|
||||
@ -407,7 +407,7 @@ The Search and custom buttons can be <em>remapped</em> or configured to open a s
|
||||
|
||||
To remap a button in lockdown XML, you supply the button name, the button event (typically "press"), and the product ID for the application the button will open.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<ButtonRemapList>
|
||||
<Button name="Search">
|
||||
<ButtonEvent name="Press">
|
||||
@ -503,7 +503,7 @@ MenuItems | Use **DisableMenuItems** to prevent use of the context menu, which i
|
||||
|
||||
MenuItems example:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<MenuItems>
|
||||
<DisableMenuItems/>
|
||||
</MenuItems>
|
||||
@ -1196,7 +1196,7 @@ The XML examples in this section show how to perform various tasks by using OMA
|
||||
|
||||
The following example shows how to add a new policy.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
<characteristic type="EnterpriseAssignedAccess">
|
||||
<characteristic type="AssignedAccess">
|
||||
@ -1211,7 +1211,7 @@ The following example shows how to add a new policy.
|
||||
|
||||
The following example shows how to specify the language to display on the device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
<characteristic type="EnterpriseAssignedAccess">
|
||||
<characteristic type="Language">
|
||||
@ -1230,7 +1230,7 @@ These XML examples show how to perform various tasks using OMA DM.
|
||||
|
||||
The following example shows how to lock down a device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -1251,7 +1251,7 @@ The following example shows how to lock down a device.
|
||||
|
||||
The following example shows how to change the accent color to one of the standard colors.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -1274,7 +1274,7 @@ The following example shows how to change the accent color to one of the standar
|
||||
|
||||
The following example shows how to change the theme.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -1297,7 +1297,7 @@ The following example shows how to change the theme.
|
||||
|
||||
The following example shows how to set a custom theme accent color for the enterprise environment.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
<CmdID>1</CmdID>
|
||||
@ -1333,7 +1333,7 @@ The following example shows how to set a custom theme accent color for the enter
|
||||
|
||||
Use the examples in this section to set a new lock screen and manage the lock screen features. If using a UNC path, format the LocURI as \\\\host\\share\\image.jpg.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -1351,7 +1351,7 @@ Use the examples in this section to set a new lock screen and manage the lock sc
|
||||
|
||||
The following example shows how to query the device for the file being used as the lock screen.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -1364,7 +1364,7 @@ The following example shows how to query the device for the file being used as t
|
||||
|
||||
The following example shows how to change the existing lock screen image to one of your choosing.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -1389,7 +1389,7 @@ The following example shows how to change the existing lock screen image to one
|
||||
|
||||
The following example shows how to set the time zone to UTC-07 Mountain Time (US & Canada).
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -1411,7 +1411,7 @@ The following example shows how to set the time zone to UTC-07 Mountain Time (US
|
||||
|
||||
The following example shows how to set the time zone to Pacific Standard Time (UTC-08:00) without observing daylight savings time (UTC+01:00).
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -1435,7 +1435,7 @@ The following example shows how to set the time zone to Pacific Standard Time (U
|
||||
|
||||
The following example shows how to set the language.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
|
@ -54,20 +54,14 @@ In Windows 10, version 1703 service release, a new tag \<DownloadFromAad\> was a
|
||||
|
||||
Here is an example:
|
||||
|
||||
```syntax
|
||||
<Enforcement>
|
||||
|
||||
```xml
|
||||
<Enforcement>
|
||||
<CommandLine>/quiet</CommandLine>
|
||||
|
||||
<TimeOut>5</TimeOut>
|
||||
|
||||
<RetryCount>3</RetryCount>
|
||||
|
||||
<RetryInterval>5</RetryInterval>
|
||||
|
||||
<DownloadFromAad>1</DownloadFromAad>
|
||||
|
||||
</Enforcement>
|
||||
</Enforcement>
|
||||
```
|
||||
|
||||
<a href="" id="msi-productid-status"></a>**MSI/*ProductID*/Status**
|
||||
@ -112,7 +106,7 @@ Value type is string. Supported operation is Get.
|
||||
|
||||
**SyncML to request CSP version information**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
<SyncBody>
|
||||
<Get>
|
||||
@ -140,7 +134,7 @@ The following table describes the fields in the previous sample:
|
||||
|
||||
**SyncML to perform MSI operations for application uninstall**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
<SyncBody>
|
||||
<Delete>
|
||||
@ -168,7 +162,7 @@ The following table describes the fields in the previous sample:
|
||||
|
||||
**SyncML to perform MSI operations for application status reporting**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
<SyncBody>
|
||||
<Get>
|
||||
@ -196,7 +190,7 @@ The following table describes the fields in the previous sample:
|
||||
|
||||
**SyncML to perform MSI install operations for an application targeted to a specific user on the device. The Add command is required to preceed the Exec command.**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -290,7 +284,7 @@ The following table describes the fields in the previous sample:
|
||||
|
||||
**SyncML to perform MSI install operations for an application targeted to all users on the device (per-device installation)**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -540,7 +534,7 @@ Here's a list of references:
|
||||
## Alert example
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Alert>
|
||||
<CmdID>4</CmdID>
|
||||
<Data>1224</Data>
|
||||
|
@ -70,7 +70,7 @@ Supported operations is Get.
|
||||
|
||||
The following example shows how to retrieve a file from the device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -83,7 +83,7 @@ The following example shows how to retrieve a file from the device.
|
||||
|
||||
The following example shows the file name that is returned in the body of the response syncML code. In this example, the full path of the file on the device is C:/data/test/bin/filename.txt.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Results>
|
||||
<CmdID>3</CmdID>
|
||||
<MsgRef>1</MsgRef>
|
||||
@ -103,7 +103,7 @@ The following example shows the file name that is returned in the body of the re
|
||||
|
||||
The following example shows how to push a file to the device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
|
@ -52,7 +52,7 @@ Supported operation is Get.
|
||||
|
||||
Here's an example of AppInventoryResults operation.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>11</CmdID>
|
||||
<Item>
|
||||
@ -100,7 +100,7 @@ Supported operation is Get and Replace.
|
||||
|
||||
The following example sets the inventory query for the package names and checks the status for reinstallation for all main packages that are nonStore apps.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>10</CmdID>
|
||||
<Item>
|
||||
@ -208,7 +208,7 @@ Supported operations are Get and Delete.
|
||||
|
||||
Here's an example for uninstalling an app:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<!-- Uninstall app -->
|
||||
@ -345,7 +345,7 @@ Value type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
The following example sets the value for the 'Server'
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!— Configure app settings -->
|
||||
<Add>
|
||||
<CmdID>0</CmdID>
|
||||
@ -363,7 +363,7 @@ The following example sets the value for the 'Server'
|
||||
|
||||
The following example gets all managed app settings for a specific app.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<!—Get app settings -->
|
||||
<Get>
|
||||
<CmdID>0</CmdID>
|
||||
@ -583,7 +583,7 @@ For examples of how to use this CSP to for reporting apps inventory, installatio
|
||||
|
||||
Query the device for a specific app subcategory, such as nonStore apps.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
@ -598,8 +598,7 @@ The result contains a list of apps, such as \<Data>App1/App2/App\</Data\>.
|
||||
|
||||
Subsequent query for a specific app for its properties.
|
||||
|
||||
``` syntax
|
||||
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>1</CmdID>
|
||||
<Item>
|
||||
|
@ -92,7 +92,7 @@ https://EnterpriseEnrollment.Contoso.com/EnrollmentServer/Discovery.svc
|
||||
|
||||
The following example shows the discovery service request.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<?xml version="1.0"?>
|
||||
<s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing"
|
||||
xmlns:s="http://www.w3.org/2003/05/soap-envelope">
|
||||
@ -198,7 +198,7 @@ The server has to send a POST to a redirect URL of the form ms-app://string (the
|
||||
|
||||
The following example shows a response received from the discovery web service which requires authentication via WAB.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
|
||||
xmlns:a="http://www.w3.org/2005/08/addressing">
|
||||
<s:Header>
|
||||
@ -252,7 +252,7 @@ wsse:BinarySecurityToken/attributes/EncodingType: The <wsse:BinarySecurityTok
|
||||
|
||||
The following is an enrollment policy request example with a received security token as client credential.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
|
||||
xmlns:a="http://www.w3.org/2005/08/addressing"
|
||||
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
|
||||
@ -305,7 +305,7 @@ MS-XCEP supports very flexible enrollment policies using various Complex Types a
|
||||
|
||||
The following snippet shows the policy web service response.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope
|
||||
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
|
||||
xmlns:s="http://www.w3.org/2003/05/soap-envelope"
|
||||
@ -399,7 +399,7 @@ The RST may also specify a number of AdditionalContext items, such as DeviceType
|
||||
|
||||
The following example shows the enrollment web service request for federated authentication.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
|
||||
xmlns:a="http://www.w3.org/2005/08/addressing"
|
||||
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
|
||||
@ -505,7 +505,7 @@ Here is a sample RSTR message and a sample of OMA client provisioning XML within
|
||||
|
||||
The following example shows the enrollment web service response.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
|
||||
xmlns:a="http://www.w3.org/2005/08/addressing"
|
||||
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
|
||||
|
@ -134,7 +134,7 @@ Changes to this node require a reboot.
|
||||
|
||||
For CDMA networks that use a separate Network Access Identity (NAI) for Internet sharing, a new parm, TetheringNAI, has been added in the [CM\_CellularEntries configuration service provider](cm-cellularentries-csp.md) configuration service provider. The following sample demonstrates how to specify the connection.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc>
|
||||
<characteristic type="CM_CellularEntries">
|
||||
<characteristic type="TetheringNAIConn">
|
||||
|
@ -59,7 +59,7 @@ Below are protocol changes for MAM enrollment:
|
||||
|
||||
Here is an example provisioning XML for MAM enrollment.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<wap-provisioningdoc version="1.1">
|
||||
<characteristic type="APPLICATION">
|
||||
<parm name="APPID" value="w7"/>
|
||||
|
@ -126,7 +126,7 @@ Here is a list of GUIDs of the most downloaded reqions.
|
||||
|
||||
Here is an example queuing a map package of New York for download.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -144,7 +144,7 @@ Here is an example queuing a map package of New York for download.
|
||||
|
||||
Here is an example that gets the status of the New York map package on the device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Get>
|
||||
|
@ -55,7 +55,7 @@ The following diagram shows the Messaging configuration service provider in tree
|
||||
|
||||
**SyncML example**
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
|
@ -103,7 +103,7 @@ To manually trigger enrollment migration, you can run MDMMaintenenceTask.
|
||||
|
||||
The enrollment server can decline enrollment messages using the SOAP Fault format. Errors created can be sent as follows:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
|
||||
<s:header>
|
||||
<a:action s:mustunderstand="1">http://schemas.microsoft.com/windows/pki/2009/01/enrollment/rstrc/wstep</a:action>
|
||||
@ -200,7 +200,7 @@ The enrollment server can decline enrollment messages using the SOAP Fault forma
|
||||
|
||||
In Windows 10, version 1507, we added the deviceenrollmentserviceerror element. Here is an example:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
|
||||
<s:header>
|
||||
<a:action s:mustunderstand="1">http://schemas.microsoft.com/windows/pki/2009/01/enrollment/rstrc/wstep</a:action>
|
||||
|
@ -74,7 +74,7 @@ Supported operation is Get and Replace. Value type is bool.
|
||||
## Examples
|
||||
|
||||
Get modem
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Get>
|
||||
@ -93,7 +93,7 @@ Get modem
|
||||
```
|
||||
|
||||
Get slots
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Get>
|
||||
@ -112,7 +112,7 @@ Get slots
|
||||
```
|
||||
|
||||
Get slot state
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Get>
|
||||
@ -131,7 +131,7 @@ Get slot state
|
||||
```
|
||||
|
||||
Select slot
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
|
@ -1660,7 +1660,7 @@ The software version information from **DevDetail/SwV** does not match the versi
|
||||
|
||||
Applies only to phone prior to build 10586.218: When ApplicationManagement/ApplicationRestrictions policy is deployed to Windows 10 Mobile, installation and update of apps dependent on Microsoft Frameworks may get blocked with error 0x80073CF9. To work around this issue, you must include the Microsoft Framework Id to your list of allowed apps.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<App ProductId="{00000000-0000-0000-0000-000000000000}" PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
|
||||
```
|
||||
|
||||
@ -1709,7 +1709,7 @@ The following XML sample explains the properties for the EAP TLS XML including c
|
||||
>For PEAP or TTLS Profiles the EAP TLS XML is embedded within some PEAP or TTLS specific elements.
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig">
|
||||
<EapMethod>
|
||||
<Type xmlns="http://www.microsoft.com/provisioning/EapCommon">13</Type>
|
||||
|
@ -19,7 +19,7 @@ The NodeCache configuration service provider is used to manage the client cache.
|
||||
|
||||
NodeCache supports the comparison of hash values instead of actual node values:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Type xmlns="syncml:metinf">
|
||||
application/x-nodemon-sha256
|
||||
</type>
|
||||
@ -76,7 +76,7 @@ Supported operations are Get, Add, and Delete.
|
||||
|
||||
Here's an example for setting the ExpectedValue to nonexistent.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>10</CmdID>
|
||||
<Item>
|
||||
@ -146,7 +146,7 @@ Supported operations are Add, Get, and Delete.
|
||||
|
||||
Creating settings for node caching:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -222,7 +222,7 @@ Creating settings for node caching:
|
||||
|
||||
Getting nodes under Provider ID MDMSRV1, cache version, changed nodes, node, expected value:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Get>
|
||||
<CmdID>18</CmdID>
|
||||
<Item>
|
||||
@ -267,7 +267,7 @@ Getting nodes under Provider ID MDMSRV1, cache version, changed nodes, node, exp
|
||||
|
||||
Replacing the cache version, node URI, and expected value:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<Replace>
|
||||
<CmdID>2</CmdID>
|
||||
<Item>
|
||||
@ -299,7 +299,7 @@ Replacing the cache version, node URI, and expected value:
|
||||
|
||||
For AutoSetExpectedValue, a Replace operation with empty data will query the ./DevDetail/Ext/Microsoft/DeviceName.
|
||||
|
||||
```syntax
|
||||
```xml
|
||||
<Add>
|
||||
<CmdID>2001</CmdID>
|
||||
<Item>
|
||||
@ -335,12 +335,12 @@ A Get operation on ./Vendor/MSFT/NodeCache/MDM%20SyncML%20Server/Nodes/20/Expect
|
||||
|
||||
A Get operation on the ChangedNodesData returns an encoded XML. Here is example:
|
||||
|
||||
```syntax
|
||||
```xml
|
||||
<Nodes><Node Id="10" Uri=""></Node><Node Id="20" Uri="./DevDetail/Ext/Microsoft/DeviceName">U09NRU5FV1ZBTFVF</Node></Nodes>
|
||||
```
|
||||
It represents this:
|
||||
|
||||
```syntax
|
||||
```xml
|
||||
<Nodes>
|
||||
<Node Id="10" Uri=""></Node>
|
||||
<Node Id="20" Uri="./DevDetail/Ext/Microsoft/DeviceName">U09NRU5FV1ZBTFVF</Node>
|
||||
|
@ -67,7 +67,7 @@ The only supported operation is Get.
|
||||
|
||||
Sample SyncML to install Office 365 Business Retail from current channel.
|
||||
|
||||
```syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Exec>
|
||||
@ -89,7 +89,7 @@ Sample SyncML to install Office 365 Business Retail from current channel.
|
||||
|
||||
To uninstall the Office 365 from the system:
|
||||
|
||||
```syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Exec>
|
||||
@ -111,7 +111,7 @@ To uninstall the Office 365 from the system:
|
||||
|
||||
To get the current status of Office 365 on the device.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Get>
|
||||
|
@ -86,7 +86,7 @@ https://EnterpriseEnrollment.Contoso.com/EnrollmentServer/Discovery.svc
|
||||
|
||||
The following example shows the discovery service request.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<?xml version="1.0"?>
|
||||
<s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing"
|
||||
xmlns:s="http://www.w3.org/2003/05/soap-envelope">
|
||||
@ -134,7 +134,7 @@ The discovery response is in the XML format and includes the following fields:
|
||||
|
||||
The following example shows a response received from the discovery web service for OnPremise authentication:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
|
||||
xmlns:a="http://www.w3.org/2005/08/addressing">
|
||||
<s:Header>
|
||||
@ -171,7 +171,7 @@ For the OnPremise authentication policy, the UsernameToken in GetPolicies contai
|
||||
|
||||
The following example shows the policy web service request.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
|
||||
xmlns:a="http://www.w3.org/2005/08/addressing"
|
||||
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
|
||||
@ -219,7 +219,7 @@ MS-XCEP supports very flexible enrollment policies using various Complex Types a
|
||||
|
||||
The following snippet shows the policy web service response.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope
|
||||
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
|
||||
xmlns:s="http://www.w3.org/2003/05/soap-envelope"
|
||||
@ -311,7 +311,7 @@ The RST may also specify a number of AdditionalContext items, such as DeviceType
|
||||
|
||||
The following example shows the enrollment web service request for OnPremise authentication.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
|
||||
xmlns:a="http://www.w3.org/2005/08/addressing"
|
||||
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
|
||||
@ -396,7 +396,7 @@ The following example shows the enrollment web service request for OnPremise aut
|
||||
|
||||
The following example shows the enrollment web service response.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
|
||||
xmlns:a="http://www.w3.org/2005/08/addressing"
|
||||
xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
|
||||
|
@ -273,7 +273,7 @@ Value type is string. Supported operations are Add, Get, Replace, and Delete.
|
||||
|
||||
Here's an example for setting Windows Hello for Business and setting the PIN policies. It also turns on the use of biometrics and TPM.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Add>
|
||||
|
@ -71,7 +71,7 @@ The following diagram shows the Personalization configuration service provider i
|
||||
|
||||
## Example SyncML
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
|
@ -5456,7 +5456,7 @@ The following diagram shows the Policy configuration service provider in tree fo
|
||||
|
||||
Set the minimum password length to 4 characters.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -5478,7 +5478,7 @@ Set the minimum password length to 4 characters.
|
||||
|
||||
Do not allow NFC.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
|
@ -594,7 +594,7 @@ List of semi-colon delimited Package Family Names of Windows apps. Listed Window
|
||||
|
||||
For this policy to work, the Windows apps need to declare in their manifest that they will use the start up task. Example of the declaration here:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<desktop:Extension Category="windows.startupTask">
|
||||
<desktop:StartupTask TaskId="CoffeeStartupTask" Enabled="true" DisplayName="ms-resource:Description" />
|
||||
</desktop:Extension>
|
||||
@ -972,7 +972,7 @@ Value type is string.
|
||||
<!--Example-->
|
||||
Sample SyncML:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.1">
|
||||
<SyncBody>
|
||||
<Add>
|
||||
@ -999,7 +999,7 @@ Sample SyncML:
|
||||
```
|
||||
XSD:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
|
||||
<xs:simpleType name="recurrence" final="restriction">
|
||||
<xs:restriction base="xs:string">
|
||||
|
@ -121,7 +121,7 @@ ADMX Info:
|
||||
To enable this policy, use the following SyncML. This example allows Windows to install compatible devices with a device ID of USB\Composite or USB\Class_FF. To configure multiple classes, use `` as a delimiter.
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -238,7 +238,7 @@ To enable this policy, use the following SyncML. This example allows Windows to
|
||||
Enclose the class GUID within curly brackets {}. To configure multiple classes, use `` as a delimiter.
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -417,7 +417,7 @@ ADMX Info:
|
||||
To enable this policy, use the following SyncML. This example prevents Windows from installing devices that are not specifically described by any other policy setting.
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -519,7 +519,7 @@ ADMX Info:
|
||||
To enable this policy, use the following SyncML. This example prevents Windows from installing compatible devices with a device ID of USB\Composite or USB\Class_FF. To configure multiple classes, use <code>&#xF000;</code> as a delimiter. To apply the policy to matching device classes that are already installed, set DeviceInstall_IDs_Deny_Retroactive to true.
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
@ -626,7 +626,7 @@ To enable this policy, use the following SyncML. This example prevents Windows f
|
||||
Enclose the class GUID within curly brackets {}. To configure multiple classes, use `` as a delimiter. To apply the policy to matching device classes that are already installed, set DeviceInstall_Classes_Deny_Retroactive to true.
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML>
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
|
@ -2249,7 +2249,7 @@ ADMX Info:
|
||||
|
||||
<!--/ADMXBacked-->
|
||||
<!--Example-->
|
||||
```syntax
|
||||
```xml
|
||||
<SyncBody>
|
||||
<Replace>
|
||||
<CmdID>2</CmdID>
|
||||
|
@ -76,7 +76,7 @@ Caution: If a Restricted Groups policy is applied, any current member not on the
|
||||
|
||||
Starting in Windows 10, version 1809, you can use this schema for retrieval and application of the RestrictedGroups/ConfigureGroupMembership policy. A minimum occurrence of 0 members when applying the policy implies clearing the access group and should be used with caution.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0">
|
||||
<xs:simpleType name="member_name">
|
||||
<xs:restriction base="xs:string">
|
||||
|
@ -73,6 +73,9 @@ manager: dansimp
|
||||
<!--Description-->
|
||||
Added in Windows 10, version 1703. Allows IT Admins to control whether users are allowed to install apps from places other than the Store.
|
||||
|
||||
> [!Note]
|
||||
> This policy will block installation only while the device is online. To block offline installation too, **SmartScreen/PreventOverrideForFilesInShell** and **SmartScreen/EnableSmartScreenInShell** policies should also be enabled.
|
||||
|
||||
<!--/Description-->
|
||||
<!--ADMXMapped-->
|
||||
ADMX Info:
|
||||
|
@ -20,7 +20,7 @@ User rights are assigned for user accounts or groups. The name of the policy def
|
||||
|
||||
Here is an example syncml for setting the user right BackupFilesAndDirectories for Administrators and Authenticated Users groups.
|
||||
|
||||
```syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
|
||||
<SyncBody>
|
||||
|
@ -305,7 +305,7 @@ If you disable or don't configure this policy setting, any user can disconnect t
|
||||
|
||||
Here is an example to enable this policy:
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Atomic>
|
||||
|
@ -17,7 +17,7 @@ ms.date: 06/26/2017
|
||||
|
||||
This topic shows the OMA DM device description framework (DDF) for the **Registry** configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<MgmtTree xmlns:MSFT="http://schemas.microsoft.com/MobileDevice/DM">
|
||||
<VerDTD>1.2</VerDTD>
|
||||
<Node>
|
||||
|
@ -102,7 +102,7 @@ Supported operation is Get.
|
||||
## Examples
|
||||
|
||||
|
||||
``` syntax
|
||||
```xml
|
||||
<SyncML xmlns="SYNCML:SYNCML1.2">
|
||||
<SyncBody>
|
||||
<Atomic>
|
||||
|
@ -204,7 +204,7 @@ If the physical computer is still running in a frozen state, follow these steps
|
||||
|
||||
2. From a remote computer that is preferably in the same network and subnet, go to **Registry Editor** \> **Connect Network Registry**. Then, connect to the concerned computer, and verify the following settings:
|
||||
|
||||
* ` `*HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\CrashDumpEnabled`
|
||||
* `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\CrashDumpEnabled`
|
||||
|
||||
Make sure that the [CrashDumpEnabled](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-2000-server/cc976050(v=technet.10)) registry entry is `1`.
|
||||
|
||||
|
@ -91,7 +91,7 @@ When you have the Start layout that you want your users to see, use the [Export-
|
||||
|
||||
2. On a device running Windows 10, version 1607, 1703, or 1803, at the Windows PowerShell command prompt, enter the following command:
|
||||
|
||||
`Export-StartLayout –path <path><file name>.xml `
|
||||
`Export-StartLayout –path <path><file name>.xml`
|
||||
|
||||
On a device running Windows 10, version 1809, run the **Export-StartLayout** with the switch **-UseDesktopApplicationID**. For example:
|
||||
|
||||
|
@ -130,7 +130,7 @@ After you use Group Policy to apply a customized Start and taskbar layout on a c
|
||||
- [Add image for secondary tiles](start-secondary-tiles.md)
|
||||
- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md)
|
||||
- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
- [Customize Windows 10 Start and tasbkar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
- [Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md)
|
||||
|
||||
|
||||
|
@ -26,7 +26,7 @@ ms.topic: article
|
||||
## Full XML sample
|
||||
|
||||
>[!NOTE]
|
||||
>Updated for Windows 10, version 1809.
|
||||
>Updated for Windows 10, version 1903, and Windows 10 Prerelease
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
@ -165,11 +165,479 @@ ms.topic: article
|
||||
</AssignedAccessConfiguration>
|
||||
```
|
||||
|
||||
## Auto Launch Sample XML
|
||||
|
||||
This sample demonstrates that both UWP and Win32 apps can be configured to automatically launch, when assigned access account logs in. One profile can have at most one app configured for auto launch. AutoLaunchArguments are passed to the apps as is and the app needs to handle the arguments explicitly.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:r1809="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
>
|
||||
<Profiles>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" r1809:AutoLaunch="true"/>
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<!-- A link file is required for desktop applications to show on start layout, the link file can be placed under
|
||||
"%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs" if the link file is shared for all users or
|
||||
"%AppData%\Microsoft\Windows\Start Menu\Programs" if the link file is for the specific user only
|
||||
see document https://docs.microsoft.com/windows/configuration/start-layout-xml-desktop
|
||||
-->
|
||||
<!-- for inbox desktop applications, a link file might already exist and can be used directly -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
<Profile Id="{5B328104-BD89-4863-AB27-4ED6EE355485}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" r1809:AutoLaunch="true" r1809:AutoLaunchArguments="1.txt"/>
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\Accessories\notepad.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="false"/>
|
||||
</Profile>
|
||||
</Profiles>
|
||||
<Configs>
|
||||
<Config>
|
||||
<Account>aauser1</Account>
|
||||
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
|
||||
</Config>
|
||||
<Config>
|
||||
<Account>aauser2</Account>
|
||||
<DefaultProfile Id="{5B328104-BD89-4863-AB27-4ED6EE355485}"/>
|
||||
</Config>
|
||||
</Configs>
|
||||
</AssignedAccessConfiguration>
|
||||
|
||||
```
|
||||
|
||||
## [Preview] Global Profile Sample XML
|
||||
Global Profile is currently supported in Windows 10 Prerelease. Global Profile is designed for scenarios where a user does not have a designated profile, yet IT Admin still wants the user to run in lock down mode, or used as mitigation when a profile cannot be determined for an user.
|
||||
|
||||
This sample demonstrates that only a global profile is used, no active user configured. Global profile will be applied when every non-admin account logs in
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:v2="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
>
|
||||
<Profiles>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" v2:AutoLaunch="true" v2:AutoLaunchArguments="123"/>
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<!-- A link file is required for desktop applications to show on start layout, the link file can be placed under
|
||||
"%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs" if the link file is shared for all users or
|
||||
"%AppData%\Microsoft\Windows\Start Menu\Programs" if the link file is for the specific user only
|
||||
see document https://docs.microsoft.com/windows/configuration/start-layout-xml-desktop
|
||||
-->
|
||||
<!-- for inbox desktop applications, a link file might already exist and can be used directly -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
</Profiles>
|
||||
<Configs>
|
||||
<v3:GlobalProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
|
||||
</Configs>
|
||||
</AssignedAccessConfiguration>
|
||||
```
|
||||
|
||||
Below sample shows dedicated profile and global profile mixed usage, aauser would use one profile, everyone else that's non-admin will use another profile.
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:v2="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
>
|
||||
<Profiles>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" v2:AutoLaunch="true" v2:AutoLaunchArguments="123"/>
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<!-- A link file is required for desktop applications to show on start layout, the link file can be placed under
|
||||
"%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs" if the link file is shared for all users or
|
||||
"%AppData%\Microsoft\Windows\Start Menu\Programs" if the link file is for the specific user only
|
||||
see document https://docs.microsoft.com/windows/configuration/start-layout-xml-desktop
|
||||
-->
|
||||
<!-- for inbox desktop applications, a link file might already exist and can be used directly -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
<Profile Id="{5B328104-BD89-4863-AB27-4ED6EE355485}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" v2:AutoLaunch="true" v2:AutoLaunchArguments="1.txt"/>
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\Accessories\notepad.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="false"/>
|
||||
</Profile>
|
||||
</Profiles>
|
||||
<Configs>
|
||||
<v3:GlobalProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
|
||||
<Config>
|
||||
<Account>aauser</Account>
|
||||
<DefaultProfile Id="{5B328104-BD89-4863-AB27-4ED6EE355485}"/>
|
||||
</Config>
|
||||
</Configs>
|
||||
</AssignedAccessConfiguration>
|
||||
|
||||
```
|
||||
|
||||
## [Preview] Folder Access sample xml
|
||||
In Windows 10 1809 release, folder access is locked down that when common file dialog is opened, IT Admin can specify if user has access to the Downloads folder, or no access to any folder at all. This restriction has be redesigned for finer granulatity and easier use, available in current Windows 10 Prerelease.
|
||||
|
||||
IT Admin now can specify user access to Downloads folder, Removable drives, or no restrictions at all. Note that Downloads and Removable Drives can be allowed at the same time.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:v2="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
>
|
||||
<Profiles>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" />
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C24}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" />
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<v2:FileExplorerNamespaceRestrictions>
|
||||
</v2:FileExplorerNamespaceRestrictions>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C25}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" />
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<v2:FileExplorerNamespaceRestrictions>
|
||||
<v2:AllowedNamespace Name="Downloads"/>
|
||||
</v2:FileExplorerNamespaceRestrictions>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C26}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" />
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<v2:FileExplorerNamespaceRestrictions>
|
||||
<v3:AllowRemovableDrives />
|
||||
</v2:FileExplorerNamespaceRestrictions>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C27}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" />
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<v2:FileExplorerNamespaceRestrictions>
|
||||
<v2:AllowedNamespace Name="Downloads"/>
|
||||
<v3:AllowRemovableDrives/>
|
||||
</v2:FileExplorerNamespaceRestrictions>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C28}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" />
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<v2:FileExplorerNamespaceRestrictions>
|
||||
<v3:NoRestriction />
|
||||
</v2:FileExplorerNamespaceRestrictions>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
</Profiles>
|
||||
<Configs>
|
||||
<Config>
|
||||
<Account>multi1</Account>
|
||||
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
|
||||
</Config>
|
||||
<Config>
|
||||
<Account>multi2</Account>
|
||||
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C24}"/>
|
||||
</Config>
|
||||
<Config>
|
||||
<Account>multi3</Account>
|
||||
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C25}"/>
|
||||
</Config>
|
||||
<Config>
|
||||
<Account>multi4</Account>
|
||||
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C26}"/>
|
||||
</Config>
|
||||
<Config>
|
||||
<Account>multi5</Account>
|
||||
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C27}"/>
|
||||
</Config>
|
||||
<Config>
|
||||
<Account>multi6</Account>
|
||||
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C28}"/>
|
||||
</Config>
|
||||
</Configs>
|
||||
</AssignedAccessConfiguration>
|
||||
|
||||
|
||||
```
|
||||
|
||||
## XSD for AssignedAccess configuration XML
|
||||
|
||||
>[!NOTE]
|
||||
>Updated for Windows 10, version 1809.
|
||||
>Updated for Windows 10, version 1903 and Windows 10 Prerelease.
|
||||
Below schema is for AssignedAccess Configuration up to Windows 10 1803 release.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
@ -179,10 +647,12 @@ ms.topic: article
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:default="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:rs5="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
targetNamespace="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
>
|
||||
|
||||
<xs:import namespace="http://schemas.microsoft.com/AssignedAccess/201810/config"/>
|
||||
<xs:import namespace="http://schemas.microsoft.com/AssignedAccess/2020/config"/>
|
||||
|
||||
<xs:complexType name="profile_list_t">
|
||||
<xs:sequence minOccurs="1" >
|
||||
@ -261,7 +731,8 @@ ms.topic: article
|
||||
|
||||
<xs:complexType name="config_list_t">
|
||||
<xs:sequence minOccurs="1" >
|
||||
<xs:element name="Config" type="config_t" minOccurs="1" maxOccurs="unbounded"/>
|
||||
<xs:element ref="v3:GlobalProfile" minOccurs="0" maxOccurs="1"/>
|
||||
<xs:element name="Config" type="config_t" minOccurs="0" maxOccurs="unbounded"/>
|
||||
</xs:sequence>
|
||||
</xs:complexType>
|
||||
|
||||
@ -343,8 +814,7 @@ ms.topic: article
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
## XSD schema for new elements in Windows 10, version 1809
|
||||
|
||||
Here is the schema for new features introduced in Windows 10 1809 release
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<xs:schema
|
||||
@ -352,17 +822,24 @@ ms.topic: article
|
||||
xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:default="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
targetNamespace="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
>
|
||||
|
||||
<xs:import namespace="http://schemas.microsoft.com/AssignedAccess/2020/config"/>
|
||||
|
||||
<xs:complexType name="fileExplorerNamespaceRestrictions_t">
|
||||
<xs:sequence minOccurs="1">
|
||||
<xs:element name="AllowedNamespace" type="allowedFileExplorerNamespace_t"/>
|
||||
<xs:choice>
|
||||
<xs:sequence minOccurs="0">
|
||||
<xs:element name="AllowedNamespace" type="allowedFileExplorerNamespace_t" minOccurs="0"/>
|
||||
<xs:element ref="v3:AllowRemovableDrives" minOccurs="0" maxOccurs="1"/>
|
||||
</xs:sequence>
|
||||
<xs:element ref="v3:NoRestriction" minOccurs="0" maxOccurs="1" />
|
||||
</xs:choice>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:complexType name="allowedFileExplorerNamespace_t">
|
||||
<xs:attribute name="Name" type="allowedFileExplorerNamespaceValues_t"/>
|
||||
<xs:attribute name="Name" type="allowedFileExplorerNamespaceValues_t" use="required"/>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:simpleType name="allowedFileExplorerNamespaceValues_t">
|
||||
@ -381,3 +858,46 @@ ms.topic: article
|
||||
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
Schema for Windows 10 prerelease
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<xs:schema
|
||||
elementFormDefault="qualified"
|
||||
xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
xmlns:default="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
xmlns:vc="http://www.w3.org/2007/XMLSchema-versioning"
|
||||
vc:minVersion="1.1"
|
||||
targetNamespace="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
>
|
||||
|
||||
<xs:simpleType name="guid_t">
|
||||
<xs:restriction base="xs:string">
|
||||
<xs:pattern value="\{[0-9a-fA-F]{8}\-([0-9a-fA-F]{4}\-){3}[0-9a-fA-F]{12}\}"/>
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
|
||||
<xs:complexType name="globalProfile_t">
|
||||
<xs:attribute name="Id" type="guid_t" />
|
||||
</xs:complexType>
|
||||
|
||||
<xs:element name="AllowRemovableDrives"/>
|
||||
<xs:element name="NoRestriction" />
|
||||
<xs:element name="GlobalProfile" type="globalProfile_t" />
|
||||
|
||||
</xs:schema>
|
||||
```
|
||||
|
||||
To authorize a compatible configuration XML that includes 1809 or prerelease elements and attributes, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. e.g. to configure auto-launch feature which is added in 1809 release, use below sample, notice an alias r1809 is given to the 201810 namespace for 1809 release, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
|
||||
```xml
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:r1809="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
>
|
||||
<Profiles>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" r1809:AutoLaunch="true" r1809:AutoLaunchArguments="1.txt"/>
|
||||
```
|
||||
|
@ -172,7 +172,7 @@ Here are the predefined assigned access AppLocker rules for **desktop apps**:
|
||||
The following example allows Groove Music, Movies & TV, Photos, Weather, Calculator, Paint, and Notepad apps to run on the device, with Notepad configured to automatically launch and create a file called `123.text` when the user signs in.
|
||||
|
||||
<span id="apps-sample" />
|
||||
<code>xml
|
||||
```xml
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.ZuneMusic_8wekyb3d8bbwe!Microsoft.ZuneMusic" />
|
||||
@ -184,6 +184,7 @@ The following example allows Groove Music, Movies & TV, Photos, Weather, Calcula
|
||||
<App DesktopAppPath="C:\Windows\System32\notepad.exe" rs5:AutoLaunch="true" rs5:AutoLaunchArguments="123.txt"/>
|
||||
</AllowedApps>
|
||||
</AllAppsList></code>
|
||||
```
|
||||
|
||||
##### FileExplorerNamespaceRestrictions
|
||||
|
||||
@ -217,6 +218,13 @@ The following example shows how to allow user access to the Downloads folder in
|
||||
</Profiles>
|
||||
</AssignedAccessConfiguration>
|
||||
```
|
||||
FileExplorerNamespaceRestriction has been extended in current Windows 10 Prerelease for finer granularity and easier use, see in the [Assigned access XML reference.](kiosk-xml.md) for full samples. The changes will allow IT Admin to configure if user can access Downloads folder, Removable drives, or no restriction at all by using certain new elements. Note that FileExplorerNamesapceRestrictions and AllowedNamespace:Downloads are available in namespace http://schemas.microsoft.com/AssignedAccess/201810/config, AllowRemovableDrives and NoRestriction are defined in a new namespace http://schemas.microsoft.com/AssignedAccess/2020/config.
|
||||
|
||||
* When FileExplorerNamespaceRestrictions node is not used, or used but left empty, user will not be able to access any folder in common dialog (e.g. Save As in Microsoft Edge browser).
|
||||
* When Downloads is mentioned in allowed namespace, user will be able to access Downloads folder.
|
||||
* When AllowRemovableDrives is used, user will be to access removable drives.
|
||||
* When NoRestriction is used, no restriction will be applied to the dialog.
|
||||
* AllowRemovableDrives and AllowedNamespace:Downloads can be used at the same time.
|
||||
|
||||
##### StartLayout
|
||||
|
||||
@ -401,6 +409,67 @@ Group accounts are specified using `<UserGroup>`. Nested groups are not supporte
|
||||
|
||||
<span id="add-xml" />
|
||||
|
||||
#### [Preview] Global Profile
|
||||
Global profile is added in curernt Windows 10 Prerelease. There are times when IT Admin wants to everyone who logging into a specific devices are assigned access users, even there is no dedicated profile for that user, or there are times that Assigned Access could not identify a profile for the user and a fallback profile is wished to use. Global Profile is designed for these scenarios.
|
||||
|
||||
Usage is demonstrated below, by using the new xml namespace and specify GlobalProfile from that namespace. When GlobalProfile is configured, a non-admin account logs in, if this user does not have designated profile in Assigned Access, or Assigned Access fails to determine a profile for current user, global profile will be applied for the user.
|
||||
|
||||
Note:
|
||||
1. GlobalProfile can only be multi-app profile
|
||||
2. Only one GlobalProfile can be used in one AssignedAccess Configuration Xml
|
||||
3. GlobalProfile can be used as the only config, or it can be used among with regular user or group Config.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<AssignedAccessConfiguration
|
||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||
xmlns:v2="http://schemas.microsoft.com/AssignedAccess/201810/config"
|
||||
xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
|
||||
>
|
||||
<Profiles>
|
||||
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
|
||||
<AllAppsList>
|
||||
<AllowedApps>
|
||||
<App AppUserModelId="Microsoft.Microsoft3DViewer_8wekyb3d8bbwe!Microsoft.Microsoft3DViewer" v2:AutoLaunch="true" v2:AutoLaunchArguments="123"/>
|
||||
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
<App AppUserModelId="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<App DesktopAppPath="%SystemRoot%\system32\notepad.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<StartLayout>
|
||||
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout" Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<LayoutOptions StartTileGroupCellWidth="6" />
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6">
|
||||
<start:Group Name="Life at a glance">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="microsoft.windowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowsLive.calendar" />
|
||||
<start:Tile Size="4x2" Column="0" Row="4" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
|
||||
<!-- A link file is required for desktop applications to show on start layout, the link file can be placed under
|
||||
"%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs" if the link file is shared for all users or
|
||||
"%AppData%\Microsoft\Windows\Start Menu\Programs" if the link file is for the specific user only
|
||||
see document https://docs.microsoft.com/windows/configuration/start-layout-xml-desktop
|
||||
-->
|
||||
<!-- for inbox desktop applications, a link file might already exist and can be used directly -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\paint.lnk" />
|
||||
<!-- for 3rd party desktop application, place the link file under appropriate folder -->
|
||||
<start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%AppData%\Microsoft\Windows\Start Menu\Programs\MyLOB.lnk" />
|
||||
</start:Group>
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
]]>
|
||||
</StartLayout>
|
||||
<Taskbar ShowTaskbar="true"/>
|
||||
</Profile>
|
||||
</Profiles>
|
||||
<Configs>
|
||||
<v3:GlobalProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
|
||||
</Configs>
|
||||
</AssignedAccessConfiguration>
|
||||
```
|
||||
|
||||
### Add XML file to provisioning package
|
||||
|
||||
Before you add the XML file to a provisioning package, you can [validate your configuration XML against the XSD](kiosk-xml.md#xsd-for-assignedaccess-configuration-xml).
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Introduction to configuration service providers (CSPs) for IT pros (Windows 10)
|
||||
description: Configuration service providers (CSPs) expose device configuration settings in Windows 10.
|
||||
description: Configuration service providers (CSPs) expose device configuration settings in Windows 10.
|
||||
ms.assetid: 25C1FDCA-0E10-42A1-A368-984FFDB2B7B6
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
@ -16,35 +16,33 @@ ms.date: 07/27/2017
|
||||
|
||||
# Introduction to configuration service providers (CSPs) for IT pros
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
Configuration service providers (CSPs) expose device configuration settings in Windows 10. This topic is written for people who have no experience with CSPs.
|
||||
Configuration service providers (CSPs) expose device configuration settings in Windows 10. This topic is written for people who have no experience with CSPs.
|
||||
|
||||
The CSPs are documented on the [Hardware Dev Center](https://go.microsoft.com/fwlink/p/?LinkId=717390) because CSPs are used by mobile device management (MDM) service providers. This topic explains how IT pros and system administrators can take advantage of many settings available through CSPs to configure devices running Windows 10 and Windows 10 Mobile in their organizations.
|
||||
The CSPs are documented on the [Hardware Dev Center](https://go.microsoft.com/fwlink/p/?LinkId=717390) because CSPs are used by mobile device management (MDM) service providers. This topic explains how IT pros and system administrators can take advantage of many settings available through CSPs to configure devices running Windows 10 and Windows 10 Mobile in their organizations.
|
||||
|
||||
>[!NOTE]
|
||||
>The explanation of CSPs and CSP documentation also apply to Windows Mobile 5, Windows Mobile 6, Windows Phone 7, and Windows Phone 8, but links to current CSPs are for Windows 10 and Windows 10 Mobile.
|
||||
>This explanation of CSPs and CSP documentation also applies to Windows Mobile 5, Windows Mobile 6, Windows Phone 7, and Windows Phone 8, but links to current CSPs are for Windows 10 and Windows 10 Mobile.
|
||||
|
||||
[See what's new for CSPs in Windows 10, version 1809.](https://docs.microsoft.com/windows/client-management/mdm/new-in-windows-mdm-enrollment-management#whatsnew1809)
|
||||
|
||||
## What is a CSP?
|
||||
|
||||
A CSP is an interface in the client operating system, between configuration settings specified in a provisioning document, and configuration settings on the device. CSPs are similar to Group Policy client-side extensions, in that they provide an interface to read, set, modify, or delete configuration settings for a given feature. Typically, these settings map to registry keys, files or permissions. Some of these settings are configurable, and some are read-only.
|
||||
|
||||
A CSP is an interface in the client operating system between configuration settings specified in a provisioning document and configuration settings on the device. Their function is similar to that of Group Policy client-side extensions in that they provide an interface to read, set, modify, or delete configuration settings for a given feature. Typically, these settings map to registry keys, files or permissions. Some of these settings are configurable and some are read-only.
|
||||
|
||||
Starting in Windows Mobile 5.0, CSPs were used to manage Windows mobile devices. In the Windows 10 platform, the management approach for both desktop and mobile devices converges, taking advantage of the same CSPs to configure and manage all devices running Windows 10.
|
||||
Starting with Windows Mobile 5.0, CSPs were used to manage Windows mobile devices. On the Windows 10 platform, the management approach for both desktop and mobile devices converges, taking advantage of the same CSPs to configure and manage all devices running Windows 10.
|
||||
|
||||
Each CSP provides access to specific settings. For example, the [Wi-Fi CSP](https://go.microsoft.com/fwlink/p/?LinkId=717438) contains the settings to create a Wi-Fi profile.
|
||||
|
||||
CSPs are behind many of the management tasks and policies for Windows 10 in Microsoft Intune and non-Microsoft MDM service providers. For example, in Intune, the policy to allow search suggestions in the Microsoft Edge address bar uses **Browser/AllowSearchSuggestionsinAddressBar** in the [Policy CSP](https://go.microsoft.com/fwlink/p/?LinkID=623244).
|
||||
CSPs are behind many of the management tasks and policies for Windows 10, both in Microsoft Intune and in non-Microsoft MDM service providers. For example, in Intune, the policy to allow search suggestions in the Microsoft Edge address bar uses **Browser/AllowSearchSuggestionsinAddressBar** in the [Policy CSP](https://go.microsoft.com/fwlink/p/?LinkID=623244).
|
||||
|
||||

|
||||
|
||||
CSPs receive configuration policies in the XML-based SyncML format pushed to it from an MDM-compliant management server such as Microsoft Intune. Traditional enterprise management systems, such as System Center Configuration Manager, can also target CSPs by using a client-side WMI-to-CSP bridge.
|
||||
CSPs receive configuration policies in the XML-based SyncML format, pushed from an MDM-compliant management server, such as Microsoft Intune. Traditional enterprise management systems, such as System Center Configuration Manager, can also target CSPs, by using a client-side WMI-to-CSP bridge.
|
||||
|
||||
### Synchronization Markup Language (SyncML)
|
||||
|
||||
@ -52,22 +50,21 @@ The Open Mobile Alliance Device Management (OMA-DM) protocol uses the XML-based
|
||||
|
||||
### The WMI-to-CSP Bridge
|
||||
|
||||
The WMI-to-CSP Bridge is a component allowing configuration of Windows 10 CSPs via scripts and traditional enterprise management software such as Configuration Manager using Windows Management Instrumentation (WMI). The bridge is responsible for reading WMI commands and through a component called the common device configurator pass them to a CSP for application on the device.
|
||||
The WMI-to-CSP Bridge is a component allowing configuration of Windows 10 CSPs via scripts and traditional enterprise management software, such as Configuration Manager using Windows Management Instrumentation (WMI). The bridge is responsible for reading WMI commands and through a component called the common device configurator pass them to a CSP for application on the device.
|
||||
|
||||
[Learn how to use the WMI Bridge Provider with PowerShell.](https://go.microsoft.com/fwlink/p/?LinkId=761090)
|
||||
|
||||
## Why should you learn about CSPs?
|
||||
|
||||
|
||||
Generally, enterprises rely on Group Policy or MDM to configure and manage devices. For devices running Windows, MDM services use CSPs to configure your devices.
|
||||
|
||||
In addition, you may have unmanaged devices, or a large number of devices that you want to configure before enrolling them in management, or you want to apply custom settings that aren't available through your MDM service. The [CSP documentation](#bkmk-csp-doc) can help you understand the settings that can be configured or queried.
|
||||
In addition, you may have unmanaged devices, or a large number of devices that you want to configure before enrolling them in management. You may also want to apply custom settings that aren't available through your MDM service. The [CSP documentation](#bkmk-csp-doc) can help you understand the settings that can be configured or queried.
|
||||
|
||||
In addition, some of the topics in the [Windows 10 and Windows 10 Mobile](/windows/windows-10) library on Technet include links to applicable CSP reference topics, such as [Cortana integration in your business or enterprise](../cortana-at-work/cortana-at-work-overview.md) which links to the [Policy CSP](https://go.microsoft.com/fwlink/p/?LinkID=623244). In the CSP topics, you can learn about all of the available configuration settings.
|
||||
Some of the topics in the [Windows 10 and Windows 10 Mobile](/windows/windows-10) library on Technet include links to applicable CSP reference topics, such as [Cortana integration in your business or enterprise](../cortana-at-work/cortana-at-work-overview.md), which links to the [Policy CSP](https://go.microsoft.com/fwlink/p/?LinkID=623244). In the CSP topics, you can learn about all of the available configuration settings.
|
||||
|
||||
### CSPs in Windows Configuration Designer
|
||||
|
||||
You can use Windows Configuration Designer to create [provisioning packages](https://go.microsoft.com/fwlink/p/?LinkId=717466) to apply settings to devices during the out-of-box-experience (OOBE) and after devices are set up. You can use provisioning packages to configure a device's connectivity and enroll the device in MDM. Many of the runtime settings in Windows Configuration Designer are based on CSPs.
|
||||
You can use Windows Configuration Designer to create [provisioning packages](https://go.microsoft.com/fwlink/p/?LinkId=717466) to apply settings to devices during the out-of-box-experience (OOBE), and after the devices are set up. You can also use provisioning packages to configure a device's connectivity and enroll the device in MDM. Many of the runtime settings in Windows Configuration Designer are based on CSPs.
|
||||
|
||||
Many settings in Windows Configuration Designer will display documentation for that setting in the center pane, and will include a reference to the CSP if the setting uses one, as shown in the following image.
|
||||
|
||||
@ -83,12 +80,11 @@ When a CSP is available but is not explicitly included in your MDM solution, you
|
||||
|
||||
### CSPs in Lockdown XML
|
||||
|
||||
Lockdown XML can be used to configure devices running Windows 10 Mobile. You can manually author a [Lockdown XML file](../mobile-devices/lockdown-xml.md) to make use of the configuration settings available through the [EnterpriseAssignedAccess configuration service provider (CSP)](https://go.microsoft.com/fwlink/p/?LinkID=618601). In Windows 10, version 1703, you can also use the new [Lockdown Designer app](../mobile-devices/mobile-lockdown-designer.md) to configure your Lockdown XML.
|
||||
Lockdown XML can be used to configure devices running Windows 10 Mobile. You can manually author a [Lockdown XML file](../mobile-devices/lockdown-xml.md) to make use of the configuration settings available through the [EnterpriseAssignedAccess configuration service provider (CSP)](https://go.microsoft.com/fwlink/p/?LinkID=618601). In Windows 10, version 1703, you can also use the new [Lockdown Designer app](../mobile-devices/mobile-lockdown-designer.md) to configure your Lockdown XML.
|
||||
|
||||
## <a href="" id="bkmk-csp-doc"></a>How do you use the CSP documentation?
|
||||
|
||||
|
||||
All CSPs in Windows 10 are documented in the [Configuration service provider reference](https://go.microsoft.com/fwlink/p/?LinkId=717390).
|
||||
All CSPs in Windows 10 are documented in the [Configuration service provider reference](https://go.microsoft.com/fwlink/p/?LinkId=717390).
|
||||
|
||||
The [main CSP topic](https://go.microsoft.com/fwlink/p/?LinkId=717390) tells you which CSPs are supported on each edition of Windows 10, and links to the documentation for each individual CSP.
|
||||
|
||||
@ -98,17 +94,17 @@ The documentation for each CSP follows the same structure. After an introduction
|
||||
|
||||
The full path to a specific configuration setting is represented by its Open Mobile Alliance - Uniform Resource Identifier (OMA-URI). The URI is relative to the devices’ root node (MSFT, for example). Features supported by a particular CSP can be set by addressing the complete OMA-URI path.
|
||||
|
||||
The following example shows the diagram for the [AssignedAccess CSP](https://go.microsoft.com/fwlink/p/?LinkID=626608). The diagram maps to the XML for that CSP. Notice the different shapes in the diagram: rounded elements are nodes and rectangular elements are settings or policies for which a value must be supplied.
|
||||
The following example shows the diagram for the [AssignedAccess CSP](https://go.microsoft.com/fwlink/p/?LinkID=626608). The diagram maps to the XML for that CSP. Notice the different shapes in the diagram: rounded elements are nodes, and rectangular elements are settings or policies for which a value must be supplied.
|
||||
|
||||

|
||||
|
||||
The element in the tree diagram after the root node tells you the name of the CSP. Knowing this structure, you would recognize in XML the parts of the URI path for that CSP and, if you saw it in XML, you would know which CSP reference to look up. For example, in the following OMS-URI path for the kiosk mode app settings, you can see it uses the [AssignedAccess CSP](https://go.microsoft.com/fwlink/p/?LinkID=626608).
|
||||
The element in the tree diagram after the root node tells you the name of the CSP. Knowing this structure, you would recognize in XML the parts of the URI path for that CSP and, if you saw it in XML, you would know which CSP reference to look up. For example, in the following OMS-URI path for the kiosk mode app settings, you can see that it uses the [AssignedAccess CSP](https://go.microsoft.com/fwlink/p/?LinkID=626608).
|
||||
|
||||
```XML
|
||||
./Vendor/MSFT/AssignedAccess/KioskModeApp
|
||||
```
|
||||
|
||||
When an element in the diagram uses italic font, it indicates a placeholder for specific information, such as the tenant ID in the following example.
|
||||
When an element in the diagram uses _italic_ font, it indicates a placeholder for specific information, such as the tenant ID in the following example.
|
||||
|
||||

|
||||
|
||||
@ -120,12 +116,11 @@ The documentation for most CSPs will also include an XML example.
|
||||
|
||||
## CSP examples
|
||||
|
||||
|
||||
CSPs provide access to a number of settings useful to enterprises. This section introduces two CSPs that an enterprise might find particularly useful.
|
||||
|
||||
- [EnterpriseAssignedAccess CSP](https://go.microsoft.com/fwlink/p/?LinkID=618601)
|
||||
|
||||
The EnterpriseAssignedAccess configuration service provider allows IT administrators to configure settings on a Windows 10 Mobile device. An enterprise can make use of this CSP to create single-use or limited-use mobile devices, such as a handheld device that only runs a price-checking app.
|
||||
The EnterpriseAssignedAccess configuration service provider allows IT administrators to configure settings on a Windows 10 Mobile device. An enterprise can make use of this CSP to create single-use or limited-use mobile devices, such as a handheld device that only runs a price-checking app.
|
||||
|
||||
In addition to lockscreen wallpaper, theme, time zone, and language, the EnterpriseAssignedAccess CSP includes AssignedAccessXml which can be used to lock down the device through the following settings:
|
||||
|
||||
@ -139,7 +134,7 @@ CSPs provide access to a number of settings useful to enterprises. This section
|
||||
- Creating role-specific configurations.
|
||||
- [Policy CSP](https://go.microsoft.com/fwlink/p/?LinkID=623244)
|
||||
|
||||
The Policy configuration service provider enables the enterprise to configure policies on Windows 10 and Windows 10 Mobile. Some of these policy settings can also be applied using Group Policy, and the CSP documentation lists the equivalent Group Policy settings.
|
||||
The Policy configuration service provider enables the enterprise to configure policies on Windows 10 and Windows 10 Mobile. Some of these policy settings can also be applied using Group Policy, and the CSP documentation lists the equivalent Group Policy settings.
|
||||
|
||||
Some of the settings available in the Policy CSP include the following:
|
||||
|
||||
@ -159,7 +154,7 @@ CSPs provide access to a number of settings useful to enterprises. This section
|
||||
- **Update**, such as specifying whether the device could use Microsoft Update, Windows Server Update Services (WSUS), or Microsoft Store
|
||||
- **WiFi**, such as whether to enable Internet sharing
|
||||
|
||||
Here is a list of CSPs supported on Windows 10 Enterprise, Windows 10 Mobile Enterprise, or both:
|
||||
Here is a list of CSPs supported on Windows 10 Enterprise, Windows 10 Mobile Enterprise, or both:
|
||||
|
||||
- [ActiveSync CSP](https://go.microsoft.com/fwlink/p/?LinkId=723219)
|
||||
- [Application CSP](https://go.microsoft.com/fwlink/p/?LinkId=723220)
|
||||
@ -218,13 +213,3 @@ Here is a list of CSPs supported on Windows 10 Enterprise, Windows 10 Mobile E
|
||||
- [Wi-Fi CSP](https://go.microsoft.com/fwlink/p/?LinkID=71743)
|
||||
- [WindowsLicensing CSP](https://go.microsoft.com/fwlink/p/?LinkId=723274)
|
||||
- [WindowsSecurityAuditing CSP](https://go.microsoft.com/fwlink/p/?LinkId=723415)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -67,7 +67,7 @@ Examples of these two deployment advisors are shown below.
|
||||
|
||||
## M365 Enterprise poster
|
||||
|
||||
[](http://aka.ms/m365eposter)
|
||||
[](https://aka.ms/m365eposter)
|
||||
|
||||
## Related Topics
|
||||
|
||||
|
@ -419,7 +419,7 @@ This issue occurs because in Windows 10, version 1903 and later versions, MBR2GP
|
||||
|
||||
To fix this issue, mount the Windows PE image (WIM), copy the missing file from the [Windows 10, version 1903 Assessment and Development Kit (ADK)](https://go.microsoft.com/fwlink/?linkid=2086042) source, and then commit the changes to the WIM. To do this, follow these steps:
|
||||
|
||||
1. Mount the Windows PE WIM to a path (for example, C:\WinPE_Mount). For more information about how to mount WIM files, see [Mount an image](https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/mount-and-modify-a-windows-image-using-dism#mount-an-image).
|
||||
1. Mount the Windows PE WIM to a path (for example, C:\WinPE_Mount). For more information about how to mount WIM files, see [Mount an image](https://docs.microsoft.com/windows-hardware/manufacture/desktop/mount-and-modify-a-windows-image-using-dism#mount-an-image).
|
||||
|
||||
2. Copy the ReAgent files and the ReAgent localization files from the Window 10, version 1903 ADK source folder to the mounted WIM.
|
||||
|
||||
@ -446,7 +446,7 @@ To fix this issue, mount the Windows PE image (WIM), copy the missing file from
|
||||
>![Note]
|
||||
>If you aren't using an English version of Windows, replace "En-Us" in the path with the appropriate string that represents the system language.
|
||||
|
||||
3. After you copy all the files, commit the changes and unmount the Windows PE WIM. MBR2GPT.exe now functions as expected in Windows PE. For information about how to unmount WIM files while committing changes, see [Unmounting an image](https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/mount-and-modify-a-windows-image-using-dism#unmounting-an-image).
|
||||
3. After you copy all the files, commit the changes and unmount the Windows PE WIM. MBR2GPT.exe now functions as expected in Windows PE. For information about how to unmount WIM files while committing changes, see [Unmounting an image](https://docs.microsoft.com/windows-hardware/manufacture/desktop/mount-and-modify-a-windows-image-using-dism#unmounting-an-image).
|
||||
|
||||
|
||||
## Related topics
|
||||
|
@ -6,6 +6,7 @@ ms.mktglfcycl: plan
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
|
@ -6,6 +6,7 @@ ms.mktglfcycl: plan
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
---
|
||||
# Features that are removed or deprecated in Windows 10, version 1709
|
||||
|
@ -6,6 +6,7 @@ ms.mktglfcycl: plan
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
|
@ -39,4 +39,4 @@ Because of the way Windows Defender is associated with the rest of Windows devic
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Windows Defender Antivirus pre-requisites](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/troubleshoot-reporting#confirm-pre-requisites)
|
||||
- [Windows Defender Antivirus pre-requisites](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/troubleshoot-reporting#confirm-pre-requisites)
|
||||
|
@ -147,8 +147,12 @@ Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Mi
|
||||
| 59 - CleanupOneSettings failed to delete LastPersistedEventTimeOrFirstBoot property at registry key path: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Diagnostics\Diagtrack** |The CleanupOneSettings function clears some of the cached values needed by the Appraiser which is the data collector on the monitored device. This helps in the download of the most recent for accurate running of the data collector. Verify that the account has the correct permissions to change or add registry keys. |
|
||||
| 60 - CleanupOneSettings failed to delete registry key: **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\ Diagnostics\Diagtrack\SettingsRequests** | Verify that the account has the correct permissions to change or add registry keys. |
|
||||
| 61 - CleanupOneSettings failed with an exception | CleanupOneSettings failed with an unexpected exception. |
|
||||
| 63 - Diagnostic data is disabled for the device | If AllowTelemetry == 0, devices cannot send diagnostic data. To resolve this, set the **AllowTelemetry** value at **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**. |
|
||||
|
||||
| 62 - AllowTelemetry property value at registry key path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** is not of type REG_DWORD. It should be of type REG_DWORD. | Ensure that the **AllowTelemetry** property at path **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection** is a REG_DWORD. |
|
||||
| 63 - Diagnostic data is disabled for the device | If AllowTelemetry equals **0**, devices cannot send diagnostic data. To resolve this, set the **AllowTelemetry** value at **HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection**. |
|
||||
| 64 - AllowTelemetry property value at registry key path **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** is not of type REG_DWORD. It should be of type REG_DWORD. | Ensure that the **AllowTelemetry** property at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection** is a REG_DWORD. |
|
||||
| 65 - Diagnostic data is disabled for the device | If AllowTelemetry equals **0**, devices cannot send diagnostic data. To resolve this, set the **AllowTelemetry** value at **HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection**. |
|
||||
| 66 - All recent data uploads for the Universal Telemetry Client failed. | Review the UtcConnectionReport in WMI in the namespace **root\cimv2\mdm\dmmap** under the **MDM_Win32CompatibilityAppraiser_UniversalTelemetryClient01** class. Only SYSTEM has access to this class. Use [PSExec](https://docs.microsoft.com/sysinternals/downloads/psexec) to execute your WMI utility as SYSTEM. |
|
||||
| 67 - CheckUtcCsp failed with an exception | There was an error reading the WIM/CIM class **MDM_Win32CompatibilityAppraiser_UniversalTelemetryClient01** in the namespace **root\cimv2\mdm\dmmap**. Review system for WMI errors. |
|
||||
|
||||
|
||||
|
||||
|
@ -89,7 +89,7 @@ In addition, note the following functionality with the Config.xml file:
|
||||
|
||||
- If a parent component is removed from the migration in the Config.xml file by specifying `migrate="no"`, all of its child components will automatically be removed from the migration, even if the child component is set to `migrate="yes"`.
|
||||
|
||||
- If you mistakenly have two lines of code for the same component where one line specifies `migrate="no" `and the other line specifies `migrate="yes"`, the component will be migrated.
|
||||
- If you mistakenly have two lines of code for the same component where one line specifies `migrate="no"` and the other line specifies `migrate="yes"`, the component will be migrated.
|
||||
|
||||
- In USMT there are several migration policies that can be configured in the Config.xml file. For example, you can configure additional **<ErrorControl>**, **<ProfileControl>**, and **<HardLinkStoreControl>** options. For more information, see the [Config.xml File](usmt-configxml-file.md) topic.
|
||||
|
||||
|
@ -50,7 +50,7 @@ Before you modify the .xml files, become familiar with the following guidelines:
|
||||
|
||||
- **File names with brackets**
|
||||
|
||||
If you are migrating a file that has a bracket character (\[ or \]) in the file name, you must insert a carat (^) character directly before the bracket for the bracket character to be valid. For example, if there is a file named File.txt, you must specify `<pattern type="File">c:\documents\mydocs [file^].txt]</pattern> `instead of `<pattern type="File">c:\documents\mydocs [file].txt]</pattern>`.
|
||||
If you are migrating a file that has a bracket character (\[ or \]) in the file name, you must insert a carat (^) character directly before the bracket for the bracket character to be valid. For example, if there is a file named File.txt, you must specify `<pattern type="File">c:\documents\mydocs [file^].txt]</pattern>` instead of `<pattern type="File">c:\documents\mydocs [file].txt]</pattern>`.
|
||||
|
||||
- **Using quotation marks**
|
||||
|
||||
|
@ -1499,7 +1499,7 @@ For example:
|
||||
|
||||
- **MergeMultiSzContent**
|
||||
|
||||
The MergeMultiSzContent function merges the MULTI-SZ content of the registry values that are enumerated by the parent <ObjectSet> element with the content of the equivalent registry values that already exist on the destination computer. `Instruction` and` String` either remove or add content to the resulting MULTI-SZ. Duplicate elements will be removed.
|
||||
The MergeMultiSzContent function merges the MULTI-SZ content of the registry values that are enumerated by the parent <ObjectSet> element with the content of the equivalent registry values that already exist on the destination computer. `Instruction` and `String` either remove or add content to the resulting MULTI-SZ. Duplicate elements will be removed.
|
||||
|
||||
Syntax: MergeMultiSzContent (*Instruction*,*String*,*Instruction*,*String*,…)
|
||||
|
||||
@ -3618,7 +3618,7 @@ The return value that is required by <script> depends on the parent elemen
|
||||
|
||||
Syntax: <script>MigXmlHelper.GetStringContent("*ObjectType*","*EncodedLocationPattern*", "*ExpandContent*")</script>
|
||||
|
||||
Example:` <script>MigXMLHelper.GetStringContent("Registry","HKLM\Software\MyApp\Installer [EXEPATH]")</script>`
|
||||
Example: `<script>MigXMLHelper.GetStringContent("Registry","HKLM\Software\MyApp\Installer [EXEPATH]")</script>`
|
||||
|
||||
- You can use [GenerateUserPatterns](#scriptfunctions) when <script> is within <objectSet>.
|
||||
|
||||
|
@ -8,6 +8,7 @@ ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: mdt
|
||||
author: greg-lindsay
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
search.appverid:
|
||||
- MET150
|
||||
|
@ -8,6 +8,7 @@ ms.localizationpriority: low
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
manager: laurawi
|
||||
ms.author: greg-lindsay
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
|
@ -60,7 +60,7 @@ If the Delivery Optimization Service is inaccessible, the AutoPilot process will
|
||||
|
||||
<tr><td><b>Network Time Protocol (NTP) Sync<b><td>When a Windows device starts up, it will talk to a network time server to ensure that the time on the device is accurate. Ensure that UDP port 123 to time.windows.com is accessible.
|
||||
<tr><td><b>Domain Name Services (DNS)<b><td>To resolve DNS names for all services, the device communicates with a DNS server, typically provided via DHCP. This DNS server must be able to resolve internet names.
|
||||
<tr><td><b>Diagnostics data<b><td>To enable Windows Analytics and related diagnostics capabilities, see <a href="https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization">Configure Windows diagnostic data in your organization</a>.<br>
|
||||
<tr><td><b>Diagnostics data<b><td>Starting in Windows 10, 1903, diagnostic data collection will be enabled by default. To disable Windows Analytics and related diagnostics capabilities, see <a href="https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization#manage-enterprise-diagnostic-data-level">Manage enterprise diagnostic data level</a>.<br>
|
||||
|
||||
If diagnostic data cannot be sent, the Autopilot process will still continue, but services that depend on diagnostic data, such as Windows Analytics, will not work.
|
||||
<tr><td><b>Network Connection Status Indicator (NCSI)<b><td>Windows must be able to tell that the device is able to access the internet. For more information, see <a href="https://docs.microsoft.com/windows/privacy/manage-windows-1709-endpoints#network-connection-status-indicator-ncsi">Network Connection Status Indicator (NCSI)</a>.
|
||||
|
@ -1,4 +1,4 @@
|
||||
# [Windows 10 and Windows 10 Mobile](index.md)
|
||||
# [Windows 10](index.md)
|
||||
## [What's new](/windows/whats-new)
|
||||
## [Release information](/windows/release-information)
|
||||
## [Deployment](/windows/deployment)
|
||||
@ -8,4 +8,4 @@
|
||||
## [Security](/windows/security)
|
||||
## [Privacy](/windows/privacy)
|
||||
## [Troubleshooting](/windows/client-management/windows-10-support-solutions)
|
||||
## [Other Windows client versions](https://docs.microsoft.com/previous-versions/windows)
|
||||
## [Previous Windows versions](https://docs.microsoft.com/previous-versions/windows)
|
||||
|
@ -1,19 +1,22 @@
|
||||
---
|
||||
title: Windows 10 and Windows 10 Mobile (Windows 10)
|
||||
description: Find the latest how to and support content that IT pros need to evaluate, plan, deploy, secure and manage devices running Windows 10 or Windows 10 Mobile.
|
||||
title: Windows 10
|
||||
description: Find the latest how to and support content that IT pros need to evaluate, plan, deploy, secure and manage devices running Windows 10.
|
||||
ms.assetid: 345A4B4E-BC1B-4F5C-9E90-58E647D11C60
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: high
|
||||
author: greg-lindsay
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.date: 10/02/2018
|
||||
ms.date: 07/16/2019
|
||||
ms.author: dansimp
|
||||
ms.date: 09/03/2018
|
||||
ms.reviewer: dansimp
|
||||
manager: dansimp
|
||||
---
|
||||
|
||||
# Windows 10 and Windows 10 Mobile
|
||||
# Windows 10
|
||||
|
||||
Find the latest how to and support content that IT pros need to evaluate, plan, deploy, secure and manage devices running Windows 10 or Windows 10 Mobile.
|
||||
Find the latest how to and support content that IT pros need to evaluate, plan, deploy, secure and manage devices running Windows 10.
|
||||
|
||||
|
||||
|
||||
@ -26,28 +29,28 @@ Find the latest how to and support content that IT pros need to evaluate, plan,
|
||||
<img src="images/whatsnew.png" alt="Read what's new in Windows 10" title="Whats new" />
|
||||
<br/>What's New? </a><br>
|
||||
</td>
|
||||
<td align="center" style="width:25%; border:0;">
|
||||
<td align="center">
|
||||
<a href="/windows/configuration/index">
|
||||
<img src="images/configuration.png" alt="Configure Windows 10 in your enterprise" title="Configure Windows 10" />
|
||||
<br/>Configuration </a><br>
|
||||
</td>
|
||||
<td align="center" style="width:25%; border:0;">
|
||||
<td align="center">
|
||||
<a href="/windows/deployment/index">
|
||||
<img src="images/deployment.png" alt="Windows 10 deployment" title="Windows 10 deployment" />
|
||||
<br/>Deployment </a><br>
|
||||
</tr>
|
||||
<tr style="text-align:center;">
|
||||
<td align="center" style="width:25%; border:0;"><br>
|
||||
<td align="center"><br>
|
||||
<a href="/windows/application-management/index">
|
||||
<img src="images/applicationmanagement.png" alt="Manage applications in your Windows 10 enterprise deployment" title="Application management" />
|
||||
<br/>Application Management </a>
|
||||
<br/>App Management </a>
|
||||
</td>
|
||||
<td align="center" style="width:25%; border:0;"><br>
|
||||
<td align="center"><br>
|
||||
<a href="/windows/client-management/index">
|
||||
<img src="images/clientmanagement.png" alt="Windows 10 client management" title="Client management" />
|
||||
<br/>Client Management </a>
|
||||
</td>
|
||||
<td align="center" style="width:25%; border:0;"><br>
|
||||
<td align="center"><br>
|
||||
<a href="/windows/security/index">
|
||||
<img src="images/threatprotection.png" alt="Windows 10 security" title="W10 security" />
|
||||
<br/>Security </a>
|
||||
@ -59,20 +62,8 @@ Find the latest how to and support content that IT pros need to evaluate, plan,
|
||||
|
||||
## Get to know Windows as a Service (WaaS)
|
||||
|
||||

|
||||
|
||||
The Windows 10 operating system introduces a new way to build, deploy, and service Windows: Windows as a service. Microsoft has reimagined each part of the process, to simplify the lives of IT pros and maintain a consistent Windows 10 experience for its customers.
|
||||
|
||||
These improvements focus on maximizing customer involvement in Windows development, simplifying the deployment and servicing of Windows client computers, and leveling out the resources needed to deploy and maintain Windows over time.
|
||||
|
||||
- [Read more about Windows as a Service](/windows/deployment/update/waas-overview)
|
||||
|
||||
|
||||
## Related topics
|
||||
[Windows 10 TechCenter](https://go.microsoft.com/fwlink/?LinkId=620009)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -196,7 +196,7 @@ Microsoft believes in and practices information minimization. We strive to gathe
|
||||
|
||||
### Enterprise management
|
||||
|
||||
Sharing diagnostic data with Microsoft provides many benefits to enterprises, so we do not recommend turning it off. For most enterprise customers, simply adjusting the diagnostic data level and managing specific components is the best option.
|
||||
Sharing diagnostic data with Microsoft is enabled by default on Windows 10, 1903 and later. Sharing this data provides many benefits to enterprises, so we do not recommend turning it off. For most enterprise customers, simply adjusting the diagnostic data level and managing specific components is the best option.
|
||||
|
||||
Customers can set the diagnostic data level in both the user interface and with existing management tools. Users can change the diagnostic data level in the **Diagnostic data** setting. In the **Settings** app, in **Privacy** > **Diagnostics & feedback**. They can choose between Basic and Full. The Enhanced level will only be displayed as an option when Group Policy or Mobile Device Management (MDM) are invoked with this level. The Security level is not available.
|
||||
|
||||
|
@ -46,7 +46,7 @@ d) use the software in any way that is against the law or to create or propagate
|
||||
|
||||
e) share, publish, distribute, or lend the software, provide the software as a stand-alone hosted solution for others to use, or transfer the software or this agreement to any third party.
|
||||
|
||||
4. EXPORT RESTRICTIONS. You must comply with all domestic and international export laws and regulations that apply to the software, which include restrictions on destinations, end users, and end use. For further information on export restrictions, visit http://aka.ms/exporting.
|
||||
4. EXPORT RESTRICTIONS. You must comply with all domestic and international export laws and regulations that apply to the software, which include restrictions on destinations, end users, and end use. For further information on export restrictions, visit https://aka.ms/exporting.
|
||||
|
||||
5. SUPPORT SERVICES. Microsoft is not obligated under this agreement to provide any support services for the software. Any support provided is “as is”, “with all faults”, and without warranty of any kind.
|
||||
|
||||
|
@ -107,7 +107,7 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
|
||||
| | [Defender/SubmitSamplesConsent](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-defender#defender-submitsamplesconsent) | Stop sending file samples back to Microsoft. **Set to 2 (two)**
|
||||
| 23.1 Windows Defender Smartscreen | [Browser/AllowSmartScreen](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-allowsmartscreen) | Disable Windows Defender Smartscreen. **Set to 0 (zero)**
|
||||
| 23.2 Windows Defender Smartscreen EnableAppInstallControl | [SmartScreen/EnableAppInstallControl](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-smartscreen#smartscreen-enableappinstallcontrol) | Controls whether users are allowed to install apps from places other than the Microsoft Store. **Set to 0 (zero)**
|
||||
| 23.3 Windows Defender Potentially Unwanted Applications(PUA) Protection | [Defender/PUAProtection](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-defender#defender-puaprotection) | Specifies the level of detection for potentially unwanted applications (PUAs). **Set to 1 (one)**
|
||||
| 23.3 Windows Defender Potentially Unwanted Applications(PUA) Protection | [Defender/PUAProtection](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-defender#defender-puaprotection) | Specifies the level of detection for potentially unwanted applications (PUAs). **Set to 1 (one)**
|
||||
| 24. Windows Spotlight | [Experience/AllowWindowsSpotlight](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-experience#experience-allowwindowsspotlight) | Disable Windows Spotlight. **Set to 0 (zero)**
|
||||
| 25. Microsoft Store | [ApplicationManagement/DisableStoreOriginatedApps](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-disablestoreoriginatedapps)| Boolean value that disables the launch of all apps from Microsoft Store that came pre-installed or were downloaded. **Set to 1 (one)**
|
||||
| | [ApplicationManagement/AllowAppStoreAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-allowappstoreautoupdate)| Specifies whether automatic update of apps from Microsoft Store are allowed. **Set to 0 (zero)**
|
||||
@ -115,8 +115,8 @@ For Windows 10, the following MDM policies are available in the [Policy CSP](htt
|
||||
| 26. Windows Update Delivery Optimization | | The following Delivery Optimization MDM policies are available in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx).
|
||||
| | [DeliveryOptimization/DODownloadMode](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-deliveryoptimization#deliveryoptimization-dodownloadmode)| Lets you choose where Delivery Optimization gets or sends updates and apps. **Set to 100 (one hundred)**
|
||||
| 27. Windows Update | [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) | Control automatic updates. **Set to 5 (five)**
|
||||
| 27.1 Windows Update Allow Update Service | [Update/AllowUpdateService](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-allowupdateservice) | Specifies whether the device could use Microsoft Update, Windows Server Update Services (WSUS), or Microsoft Store. **Set to 0 (zero)**
|
||||
| 27.2 Windows Update Service URL| [Update/UpdateServiceUrl](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-updateserviceurl) | Allows the device to check for updates from a WSUS server instead of Microsoft Update. **Set to String** with this Value:
|
||||
| 27.1 Windows Update Allow Update Service | [Update/AllowUpdateService](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowupdateservice) | Specifies whether the device could use Microsoft Update, Windows Server Update Services (WSUS), or Microsoft Store. **Set to 0 (zero)**
|
||||
| 27.2 Windows Update Service URL| [Update/UpdateServiceUrl](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updateserviceurl) | Allows the device to check for updates from a WSUS server instead of Microsoft Update. **Set to String** with this Value:
|
||||
|
||||
<Replace>
|
||||
<CmdID>$CmdID$</CmdID>
|
||||
|
@ -32,6 +32,7 @@ sections:
|
||||
- type: markdown
|
||||
text: "
|
||||
<table border ='0'><tr><td width='65%'>Summary</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>Date resolved</td></tr>
|
||||
<tr><td><div id='535msg'></div><b>Some applications may fail to run as expected on clients of AD FS 2016</b><br>Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016)<br><br><a href = '#535msgdesc'>See details ></a></td><td>OS Build 14393.2941<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4507459' target='_blank'>KB4507459</a></td><td>July 16, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='528msg'></div><b>Devices with Hyper-V enabled may receive BitLocker error 0xC0210000</b><br>Some devices with Hyper-V enabled may start into BitLocker recovery with error 0xC0210000.<br><br><a href = '#528msgdesc'>See details ></a></td><td>OS Build 14393.2969<br><br>May 14, 2019<br><a href ='https://support.microsoft.com/help/4494440' target='_blank'>KB4494440</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4507460' target='_blank'>KB4507460</a></td><td>July 09, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='520msg'></div><b>Difficulty connecting to some iSCSI-based SANs</b><br>Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI.<br><br><a href = '#520msgdesc'>See details ></a></td><td>OS Build 14393.2999<br><br>May 23, 2019<br><a href ='https://support.microsoft.com/help/4499177' target='_blank'>KB4499177</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4509475' target='_blank'>KB4509475</a></td><td>June 27, 2019 <br>02:00 PM PT</td></tr>
|
||||
<tr><td><div id='503msg'></div><b>Event Viewer may close or you may receive an error when using Custom Views</b><br>When trying to expand, view or create Custom Views in Event Viewer, you may receive an error and the app may stop responding or close.<br><br><a href = '#503msgdesc'>See details ></a></td><td>OS Build 14393.3025<br><br>June 11, 2019<br><a href ='https://support.microsoft.com/help/4503267' target='_blank'>KB4503267</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4503294' target='_blank'>KB4503294</a></td><td>June 18, 2019 <br>02:00 PM PT</td></tr>
|
||||
@ -70,6 +71,7 @@ sections:
|
||||
- type: markdown
|
||||
text: "
|
||||
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='535msgdesc'></div><b>Some applications may fail to run as expected on clients of AD FS 2016</b><div>Some applications may fail to run as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installation of <a href='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a> on the server. Applications that may exhibit this behavior use an <strong>IFRAME </strong>during non-interactive authentication requests and receive <strong>X-Frame Options </strong>set to<strong> </strong>DENY.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Server: Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href='https://support.microsoft.com/help/4507459' target='_blank'>KB4507459</a>.</div><br><a href ='#535msg'>Back to top</a></td><td>OS Build 14393.2941<br><br>April 25, 2019<br><a href ='https://support.microsoft.com/help/4493473' target='_blank'>KB4493473</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4507459' target='_blank'>KB4507459</a></td><td>Resolved:<br>July 16, 2019 <br>10:00 AM PT<br><br>Opened:<br>June 04, 2019 <br>05:55 PM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='520msgdesc'></div><b>Difficulty connecting to some iSCSI-based SANs</b><div>Devices may have issues connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing <a href='https://support.microsoft.com/help/4499177' target='_blank'>KB4499177</a>. You may also receive an error in the <strong>System </strong>log section of <strong>Event Viewer </strong>with Event ID 43 from iScsiPrt and a description of “Target failed to respond in time for a login request.”</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href='https://support.microsoft.com/help/4509475' target='_blank'>KB4509475</a>.</div><br><a href ='#520msg'>Back to top</a></td><td>OS Build 14393.2999<br><br>May 23, 2019<br><a href ='https://support.microsoft.com/help/4499177' target='_blank'>KB4499177</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4509475' target='_blank'>KB4509475</a></td><td>Resolved:<br>June 27, 2019 <br>02:00 PM PT<br><br>Opened:<br>June 20, 2019 <br>04:46 PM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='503msgdesc'></div><b>Event Viewer may close or you may receive an error when using Custom Views</b><div>When trying to expand, view, or create <strong>Custom Views </strong>in Event Viewer, you may receive the error, \"MMC has detected an error in a snap-in and will unload it.\" and the app may stop responding or close. You may also receive the same error when using <strong>Filter Current Log</strong> in the <strong>Action </strong>menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise LTSC 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href='https://support.microsoft.com/help/4503294' target='_blank'>KB4503294</a>.</div><br><a href ='#503msg'>Back to top</a></td><td>OS Build 14393.3025<br><br>June 11, 2019<br><a href ='https://support.microsoft.com/help/4503267' target='_blank'>KB4503267</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4503294' target='_blank'>KB4503294</a></td><td>Resolved:<br>June 18, 2019 <br>02:00 PM PT<br><br>Opened:<br>June 12, 2019 <br>11:11 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='488msgdesc'></div><b>Opening Internet Explorer 11 may fail</b><div>Internet Explorer 11 may fail to open if <strong>Default Search Provider</strong> is not set or is malformed.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607</li><li>Server: Windows Server 2019; Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href='https://support.microsoft.com/help/4503267' target='_blank'>KB4503267</a>.</div><br><a href ='#488msg'>Back to top</a></td><td>OS Build 14393.2999<br><br>May 23, 2019<br><a href ='https://support.microsoft.com/help/4499177' target='_blank'>KB4499177</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4503267' target='_blank'>KB4503267</a></td><td>Resolved:<br>June 11, 2019 <br>10:00 AM PT<br><br>Opened:<br>June 05, 2019 <br>05:49 PM PT</td></tr>
|
||||
|
@ -48,8 +48,6 @@ sections:
|
||||
<tr><td><div id='177msg'></div><b>Applications using Microsoft Jet database and Access 95 file format stop working</b><br>Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.<br><br><a href = '#177msgdesc'>See details ></a></td><td>OS Build 15063.1631<br><br>February 12, 2019<br><a href ='https://support.microsoft.com/help/4487020' target='_blank'>KB4487020</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487011' target='_blank'>KB4487011</a></td><td>February 19, 2019 <br>02:00 PM PT</td></tr>
|
||||
<tr><td><div id='184msg'></div><b>Applications using Microsoft Jet database fail to open</b><br>Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.<br><br><a href = '#184msgdesc'>See details ></a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487020' target='_blank'>KB4487020</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='146msg'></div><b>Webpages become unresponsive in Microsoft Edge</b><br>Microsoft Edge users report difficulty browsing and loading webpages.<br><br><a href = '#146msgdesc'>See details ></a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487020' target='_blank'>KB4487020</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='130msg'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><br>Instantiation of SqlConnection can throw an exception after certain updates have been installed.<br><br><a href = '#130msgdesc'>See details ></a></td><td>OS Build 15063.1292<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343889' target='_blank'>KB4343889</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='228msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#228msgdesc'>See details ></a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
||||
@ -113,15 +111,5 @@ sections:
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='196msgdesc'></div><b>First character of the Japanese era name not recognized as an abbreviation</b><div>After installing <a href=\"https://support.microsoft.com/help/4480959\" target=\"_blank\">KB4480959</a>, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4487011\" target=\"_blank\">KB4487011</a>.</div><br><a href ='#196msg'>Back to top</a></td><td>OS Build 15063.1596<br><br>January 15, 2019<br><a href ='https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487011' target='_blank'>KB4487011</a></td><td>Resolved:<br>February 19, 2019 <br>02:00 PM PT<br><br>Opened:<br>January 15, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='184msgdesc'></div><b>Applications using Microsoft Jet database fail to open</b><div>Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 </li><li>Server: Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4487020\" target=\"_blank\">KB4487020</a>.</div><br><a href ='#184msg'>Back to top</a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487020' target='_blank'>KB4487020</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='146msgdesc'></div><b>Webpages become unresponsive in Microsoft Edge</b><div>After installing <a href=\"https://support.microsoft.com/help/4480973\" target=\"_blank\">KB4480973</a>, some Microsoft Edge users report that they:</div><ul><li>Cannot load web pages using a local IP address.</li><li>Cannot load web pages on the Internet using a VPN connection.</li></ul><div>Browsing fails or the web page may become unresponsive.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4486996\" target=\"_blank\">KB4486996</a>. </div><br><a href ='#146msg'>Back to top</a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487020' target='_blank'>KB4487020</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='228msgdesc'></div><b>Unable to access hotspots with third-party applications</b><div>After installing <a href=\"https://support.microsoft.com/help/4480973\" target=\"_blank\">KB4480973</a>, third-party applications may have difficulty authenticating hotspots.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4480959\" target=\"_blank\">KB4480959</a>.</div><br><a href ='#228msg'>Back to top</a></td><td>OS Build 15063.1563<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480973' target='_blank'>KB4480973</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>Resolved:<br>January 15, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
||||
- title: August 2018
|
||||
- items:
|
||||
- type: markdown
|
||||
text: "
|
||||
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='130msgdesc'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><div>After you install the <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/08/30/net-framework-august-2018-preview-of-quality-rollup/\" target=\"_blank\">August Preview of Quality Rollup</a> or <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-framework-september-2018-security-and-quality-rollup\" target=\"_blank\">September 11, 2018 .NET Framework update</a>, instantiation of SqlConnection can throw an exception.</div><div><br></div><div>For more information about this issue, see the following article in the Microsoft Knowledge Base:</div><div><a href=\"https://support.microsoft.com/help/4470809\" target=\"_blank\">4470809</a> SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4480959\" target=\"_blank\">KB4480959</a>.</div><br><a href ='#130msg'>Back to top</a></td><td>OS Build 15063.1292<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343889' target='_blank'>KB4343889</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480959' target='_blank'>KB4480959</a></td><td>Resolved:<br>January 15, 2019 <br>10:00 AM PT<br><br>Opened:<br>August 30, 2018 <br>05:00 PM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
@ -49,8 +49,6 @@ sections:
|
||||
<tr><td><div id='201msg'></div><b>Internet Explorer may fail to load images</b><br>Internet Explorer may fail to load images with a backslash (\\) in their relative source path.<br><br><a href = '#201msgdesc'>See details ></a></td><td>OS Build 16299.967<br><br>February 12, 2019<br><a href ='https://support.microsoft.com/help/4486996' target='_blank'>KB4486996</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487021' target='_blank'>KB4487021</a></td><td>February 19, 2019 <br>02:00 PM PT</td></tr>
|
||||
<tr><td><div id='183msg'></div><b>Applications using Microsoft Jet database fail to open</b><br>Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if column names are greater than 32 characters.<br><br><a href = '#183msgdesc'>See details ></a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4486996' target='_blank'>KB4486996</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='145msg'></div><b>Webpages become unresponsive in Microsoft Edge</b><br>Microsoft Edge users report difficulty browsing and loading webpages.<br><br><a href = '#145msgdesc'>See details ></a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4486996' target='_blank'>KB4486996</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='129msg'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><br>Instantiation of SqlConnection can throw an exception after certain updates have been installed.<br><br><a href = '#129msgdesc'>See details ></a></td><td>OS Build 16299.637<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343893' target='_blank'>KB4343893</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='227msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#227msgdesc'>See details ></a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
||||
@ -123,15 +121,5 @@ sections:
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='195msgdesc'></div><b>First character of the Japanese era name not recognized as an abbreviation</b><div>After installing <a href=\"https://support.microsoft.com/help/4480967\" target=\"_blank\">KB4480967</a>, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4487021\" target=\"_blank\">KB4487021</a>.</div><br><a href ='#195msg'>Back to top</a></td><td>OS Build 16299.936<br><br>January 15, 2019<br><a href ='https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487021' target='_blank'>KB4487021</a></td><td>Resolved:<br>February 19, 2019 <br>02:00 PM PT<br><br>Opened:<br>January 15, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='183msgdesc'></div><b>Applications using Microsoft Jet database fail to open</b><div>Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format.”</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 </li><li>Server: Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 </li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4486996\" target=\"_blank\">KB4486996</a>.</div><br><a href ='#183msg'>Back to top</a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4486996' target='_blank'>KB4486996</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='145msgdesc'></div><b>Webpages become unresponsive in Microsoft Edge</b><div>After installing <a href=\"https://support.microsoft.com/help/4480978\" target=\"_blank\">KB4480978</a>, some Microsoft Edge users report that they:</div><ul><li>Cannot load web pages using a local IP address. </li><li>Cannot load web pages on the Internet using a VPN connection. </li></ul><div>Browsing fails or the web page may become unresponsive. </div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709</li></ul><div></div><div><strong>Resolution: </strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4486996\" target=\"_blank\">KB4486996</a>.</div><br><a href ='#145msg'>Back to top</a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4486996' target='_blank'>KB4486996</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='227msgdesc'></div><b>Unable to access hotspots with third-party applications</b><div>After installing <a href=\"https://support.microsoft.com/help/4480978\" target=\"_blank\">KB4480978</a>, third-party applications may have difficulty authenticating hotspots.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012</li></ul><div></div><div><strong>Resolution: </strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4480967\" target=\"_blank\">KB4480967</a>.</div><br><a href ='#227msg'>Back to top</a></td><td>OS Build 16299.904<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480978' target='_blank'>KB4480978</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>Resolved:<br>January 15, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
||||
- title: August 2018
|
||||
- items:
|
||||
- type: markdown
|
||||
text: "
|
||||
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='129msgdesc'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><div>After you install the <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/08/30/net-framework-august-2018-preview-of-quality-rollup/\" target=\"_blank\">August Preview of Quality Rollup</a> or <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-framework-september-2018-security-and-quality-rollup\" target=\"_blank\">September 11, 2018 .NET Framework update</a>, instantiation of SqlConnection can throw an exception.</div><div><br></div><div>For more information about this issue, see the following article in the Microsoft Knowledge Base:</div><div><a href=\"https://support.microsoft.com/help/4470809\" target=\"_blank\">4470809</a> SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4480967\" target=\"_blank\">KB4480967</a>.</div><br><a href ='#129msg'>Back to top</a></td><td>OS Build 16299.637<br><br>August 30, 2018<br><a href ='https://support.microsoft.com/help/4343893' target='_blank'>KB4343893</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480967' target='_blank'>KB4480967</a></td><td>Resolved:<br>January 15, 2019 <br>10:00 AM PT<br><br>Opened:<br>August 30, 2018 <br>05:00 PM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
@ -49,8 +49,6 @@ sections:
|
||||
<tr><td><div id='200msg'></div><b>Internet Explorer may fail to load images</b><br>Internet Explorer may fail to load images with a backslash (\\) in their relative source path.<br><br><a href = '#200msgdesc'>See details ></a></td><td>OS Build 17134.590<br><br>February 12, 2019<br><a href ='https://support.microsoft.com/help/4487017' target='_blank'>KB4487017</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487029' target='_blank'>KB4487029</a></td><td>February 19, 2019 <br>02:00 PM PT</td></tr>
|
||||
<tr><td><div id='180msg'></div><b>Applications using Microsoft Jet database and Access 95 file format stop working</b><br>Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.<br><br><a href = '#180msgdesc'>See details ></a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487017' target='_blank'>KB4487017</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='148msg'></div><b>Webpages become unresponsive in Microsoft Edge</b><br>Microsoft Edge users report difficulty browsing and loading webpages.<br><br><a href = '#148msgdesc'>See details ></a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487017' target='_blank'>KB4487017</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='131msg'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><br>After you install the August Preview of Quality Rollup or the September 11, 2018 .NET Framework update, instantiation of SqlConnection can throw an exception. <br><br><a href = '#131msgdesc'>See details ></a></td><td>OS Build 17134.285<br><br>September 11, 2018<br><a href ='https://support.microsoft.com/help/4457128' target='_blank'>KB4457128</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480976' target='_blank'>KB4480976</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='226msg'></div><b>Unable to access hotspots with third-party applications</b><br>Third-party applications may have difficulty authenticating hotspots.<br><br><a href = '#226msgdesc'>See details ></a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480976' target='_blank'>KB4480976</a></td><td>January 15, 2019 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
||||
@ -122,7 +120,6 @@ sections:
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='220msgdesc'></div><b>MSXML6 may cause applications to stop responding </b><div>After installing <a href=\"https://support.microsoft.com/help/4480966\" target=\"_blank\">KB4480966</a>, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as <strong>appendChild()</strong>, <strong>insertBefore()</strong>, and <strong>moveNode()</strong>.</div><div><br></div><div>The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012</li></ul><div></div><div><strong>Resolution</strong>: This issue was resolved in <a href=\"https://support.microsoft.com/help/4493464\" target=\"_blank\">KB4493464</a>. </div><br><a href ='#220msg'>Back to top</a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4493464' target='_blank'>KB4493464</a></td><td>Resolved:<br>April 09, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='180msgdesc'></div><b>Applications using Microsoft Jet database and Access 95 file format stop working</b><div>Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. </div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2</li></ul><div></div><div><strong>Resolution</strong>: This issue is resolved in <a href=\"https://support.microsoft.com/help/4487017\" target=\"_blank\">KB4487017</a>.</div><br><a href ='#180msg'>Back to top</a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487017' target='_blank'>KB4487017</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='148msgdesc'></div><b>Webpages become unresponsive in Microsoft Edge</b><div>After installing <a href=\"https://support.microsoft.com/help/4480966\" target=\"_blank\">KB4480966</a>, some Microsoft Edge users report that they: </div><ul><li>Cannot load web pages using a local IP address. </li><li>Cannot load web pages on the Internet using a VPN connection. </li></ul><div>Browsing fails or the web page may become unresponsive. </div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709</li></ul><div></div><div><strong>Resolution</strong>: This issue is resolved in <a href=\"https://support.microsoft.com/help/4487017\" target=\"_blank\">KB4487017</a>. </div><br><a href ='#148msg'>Back to top</a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487017' target='_blank'>KB4487017</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='226msgdesc'></div><b>Unable to access hotspots with third-party applications</b><div>After installing <a href=\"https://support.microsoft.com/help/4480966\" target=\"_blank\">KB4480966</a>, third-party applications may have difficulty authenticating hotspots.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1</li><li>Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012</li></ul><div></div><div><strong>Resolution</strong>: This issue is resolved in <a href=\"https://support.microsoft.com/help/4480976\" target=\"_blank\">KB4480976</a>. </div><br><a href ='#226msg'>Back to top</a></td><td>OS Build 17134.523<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480966' target='_blank'>KB4480966</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480976' target='_blank'>KB4480976</a></td><td>Resolved:<br>January 15, 2019 <br>10:00 AM PT<br><br>Opened:<br>January 08, 2019 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
||||
@ -134,12 +131,3 @@ sections:
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='151msgdesc'></div><b>Cannot pin a web link on the Start menu or the taskbar</b><div>After installing <a href=\"https://support.microsoft.com/help/4471324\" target=\"_blank\">KB4471324</a>, some users cannot pin a web link on the <strong>Start</strong> menu or the taskbar. </div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803</li><li>Server: Windows Server, version 1803</li></ul><div></div><div><strong>Resolution:</strong> This issue is resolved in <a href=\"https://support.microsoft.com/help/4487029\" target=\"_blank\">KB4487029</a>. </div><br><a href ='#151msg'>Back to top</a></td><td>OS Build 17134.471<br><br>December 11, 2018<br><a href ='https://support.microsoft.com/help/4471324' target='_blank'>KB4471324</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487029' target='_blank'>KB4487029</a></td><td>Resolved:<br>February 19, 2019 <br>02:00 PM PT<br><br>Opened:<br>December 11, 2018 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
||||
- title: September 2018
|
||||
- items:
|
||||
- type: markdown
|
||||
text: "
|
||||
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='131msgdesc'></div><b>SqlConnection instantiation exception on .NET 4.6 and later</b><div>After you install the <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/08/30/net-framework-august-2018-preview-of-quality-rollup/\" target=\"_blank\">August Preview of Quality Rollup</a> or <a href=\"https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-framework-september-2018-security-and-quality-rollup\" target=\"_blank\">September 11, 2018 .NET Framework update</a>, instantiation of SqlConnection can throw an exception. </div><div><br></div><div>For more information about this issue, see the following article in the Microsoft Knowledge Base: <a href=\"https://support.microsoft.com/help/4470809\" target=\"_blank\">4470809</a>, SqlConnection instantiation exception on .NET 4.6 and later after August-September 2018 .NET Framework updates.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016</li><li>Server: Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016</li></ul><div></div><div><strong>Resolution: </strong>This issue is resolved in <a href=\"https://support.microsoft.com/help/4480976\" target=\"_blank\">KB4480976</a>. </div><br><a href ='#131msg'>Back to top</a></td><td>OS Build 17134.285<br><br>September 11, 2018<br><a href ='https://support.microsoft.com/help/4457128' target='_blank'>KB4457128</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4480976' target='_blank'>KB4480976</a></td><td>Resolved:<br>January 15, 2019 <br>10:00 AM PT<br><br>Opened:<br>September 11, 2018 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
@ -58,7 +58,7 @@ sections:
|
||||
<tr><td><div id='193msg'></div><b>First character of the Japanese era name not recognized</b><br>The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.<br><br><a href = '#193msgdesc'>See details ></a></td><td>OS Build 17763.316<br><br>February 12, 2019<br><a href ='https://support.microsoft.com/help/4487044' target='_blank'>KB4487044</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>March 01, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='164msg'></div><b>Shared albums may not sync with iCloud for Windows</b><br>Upgrade block: Apple has identified an incompatibility with iCloud for Windows (version 7.7.0.27) where users may experience issues updating or synching Shared Albums.<br><br><a href = '#164msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>March 01, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='161msg'></div><b>Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup</b><br>Upgrade block: Users may see an Intel Audio Display (intcdaud.sys) notification during setup for devices with certain Intel Display Audio Drivers.<br><br><a href = '#161msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>March 01, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='160msg'></div><b>F5 VPN clients losing network connectivity </b><br>Upgrade block: After updating to Window 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.<br><br><a href = '#160msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>March 01, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='160msg'></div><b>F5 VPN clients losing network connectivity </b><br>Upgrade block: After updating to Windows 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.<br><br><a href = '#160msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>March 01, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='147msg'></div><b>Webpages become unresponsive in Microsoft Edge</b><br>Microsoft Edge users report difficulty browsing and loading webpages.<br><br><a href = '#147msgdesc'>See details ></a></td><td>OS Build 17763.253<br><br>January 08, 2019<br><a href ='https://support.microsoft.com/help/4480116' target='_blank'>KB4480116</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487044' target='_blank'>KB4487044</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='168msg'></div><b>Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards</b><br>Upgrade block: Devices utilizing AMD Radeon HD2000 or HD4000 series video cards may experience issues with the lock screen and Microsoft Edge tabs.<br><br><a href = '#168msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487044' target='_blank'>KB4487044</a></td><td>February 12, 2019 <br>10:00 AM PT</td></tr>
|
||||
<tr><td><div id='166msg'></div><b>Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible</b><br>Upgrade block: Microsoft and Trend Micro identified a compatibility issue with the Trend Micro business endpoint security solutions OfficeScan and Worry-Free Business Security.<br><br><a href = '#166msgdesc'>See details ></a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>February 01, 2019 <br>09:00 AM PT</td></tr>
|
||||
@ -152,10 +152,10 @@ sections:
|
||||
text: "
|
||||
<table border ='0'><tr><td width='65%'>Details</td><td width='15%'>Originating update</td><td width='10%'>Status</td><td width='10%'>History</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='438msgdesc'></div><b>Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort</b><div><strong>Upgrade block:</strong> Microsoft has identified issues with certain new Intel display drivers. Intel inadvertently released versions of its display driver (versions 24.20.100.6344, 24.20.100.6345) to OEMs that accidentally turned on unsupported features in Windows. </div><div> </div><div>As a result, after updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers.</div><div><strong>Note:</strong> This Intel display driver issue is different from the Intel Smart Sound Technology driver (version 09.21.00.3755) audio issue previously <a href=\"https://answers.microsoft.com/en-us/windows/forum/all/windows-10-audio-stops-working-after-installing/5a541c88-89e1-4bf3-b356-2837d564b109\" target=\"_blank\">documented</a>.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019 </li></ul><div></div><div><strong>Next steps:</strong> Intel has released updated drivers to OEM device manufacturers. OEMs need to make the updated driver available via Windows Update. For more information, see the <a href=\"https://www.intel.com/content/www/us/en/support/articles/000031612/graphics-drivers.html\" target=\"_blank\">Intel Customer Support article</a>.</div><div><br></div><div><strong>Resolution: </strong>Microsoft has removed the safeguard hold. </div><div><br></div><div><br></div><br><a href ='#438msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>May 21, 2019 <br>07:42 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='164msgdesc'></div><b>Shared albums may not sync with iCloud for Windows</b><div><strong>Upgrade block:</strong> Users who attempt to install iCloud for Windows (version 7.7.0.27) will see a message displayed that this version iCloud for Windows isn't supported and the install will fail.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div>To ensure a seamless experience, Microsoft is blocking devices with iCloud for Windows (version 7.7.0.27) software installed from being offered Window 10, version 1809 until this issue has been resolved. </div><div><br></div><div>We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool from the Microsoft software download website until this issue is resolved. </div><div> </div><div><strong>Resolution</strong>: Apple has released an updated version of iCloud for Windows (version 7.8.1) that resolves compatibility issues encountered when updating or synching Shared Albums after updating to Windows 10, version 1809. We recommend that you update your iCloud for Windows to version 7.8.1 when prompted before attempting to upgrade to Windows 10, version 1809. You can also manually download the latest version of iCloud for Windows by visiting <a href=\"https://support.apple.com/HT204283\" target=\"_blank\">https://support.apple.com/HT204283</a>.</div><br><a href ='#164msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>Resolved:<br>March 01, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='164msgdesc'></div><b>Shared albums may not sync with iCloud for Windows</b><div><strong>Upgrade block:</strong> Users who attempt to install iCloud for Windows (version 7.7.0.27) will see a message displayed that this version iCloud for Windows isn't supported and the install will fail.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div>To ensure a seamless experience, Microsoft is blocking devices with iCloud for Windows (version 7.7.0.27) software installed from being offered Windows 10, version 1809 until this issue has been resolved. </div><div><br></div><div>We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool from the Microsoft software download website until this issue is resolved. </div><div> </div><div><strong>Resolution</strong>: Apple has released an updated version of iCloud for Windows (version 7.8.1) that resolves compatibility issues encountered when updating or synching Shared Albums after updating to Windows 10, version 1809. We recommend that you update your iCloud for Windows to version 7.8.1 when prompted before attempting to upgrade to Windows 10, version 1809. You can also manually download the latest version of iCloud for Windows by visiting <a href=\"https://support.apple.com/HT204283\" target=\"_blank\">https://support.apple.com/HT204283</a>.</div><br><a href ='#164msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>Resolved:<br>March 01, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='161msgdesc'></div><b>Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup</b><div><strong>Upgrade block:</strong> Microsoft and Intel have identified a compatibility issue with a range of Intel Display Audio device drivers (intcdaud.sys, versions 10.25.0.3 - 10.25.0.8) that may result in excessive processor demand and reduced battery life. As a result, the update process to the Windows 10 October 2018 Update (Windows 10, version 1809) will fail and affected devices will automatically revert to the previous working configuration. </div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div>If you see a \"What needs your attention\" notification during installation of the October 2018 Update, you have one of these affected drivers on your system. On the notification, click <strong>Back</strong> to remain on your current version of Windows 10. </div><div> </div><div>To ensure a seamless experience, we are blocking devices from being offered the October 2018 Update until updated Intel device drivers are installed on your current operating system. We recommend that you do not attempt to manually update to Windows 10, version 1809, using the Update Now button or the Media Creation Tool from the <a href=\"https://www.microsoft.com/software-download/windows10\" target=\"_blank\">Microsoft Software Download Center</a> until newer Intel device drivers are available with the update. You can either wait for newer drivers to be installed automatically through Windows Update or check with your computer manufacturer for the latest device driver software availability and installation procedures. For more information about this issue, see <a href=\"https://www.intel.com/content/www/us/en/support/articles/000030792/graphics-drivers.html\" target=\"_blank\">Intel's customer support guidance</a>.</div><div> </div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4482887\" target=\"_blank\">KB4482887</a> and the upgrade block removed. </div><br><a href ='#161msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>Resolved:<br>March 01, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='160msgdesc'></div><b>F5 VPN clients losing network connectivity </b><div><strong>Upgrade block:</strong> After updating to Window 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4482887\" target=\"_blank\">KB4482887</a> and the upgrade block removed. </div><br><a href ='#160msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>Resolved:<br>March 01, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='168msgdesc'></div><b>Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards</b><div><strong>Note:</strong> AMD no longer supports Radeon HD2000 and HD4000 series graphic processor units (GPUs).</div><div> </div><div><strong>Upgrade block:</strong> After updating to Window 10, version 1809, Microsoft Edge tabs may stop working when a device is configured with AMD Radeon HD2000 or HD4000 series video cards. Customers may get the following error code: \"INVALID_POINTER_READ_c0000005_atidxx64.dll\". </div><div> </div><div>Some users may also experience performance issues with the lock screen or the ShellExperienceHost. (The lock screen hosts widgets, and the ShellExperienceHost is responsible for assorted shell functionality.) </div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4487044\" target=\"_blank\">KB4487044</a>, and the block was removed.</div><br><a href ='#168msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487044' target='_blank'>KB4487044</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='160msgdesc'></div><b>F5 VPN clients losing network connectivity </b><div><strong>Upgrade block:</strong> After updating to Windows 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4482887\" target=\"_blank\">KB4482887</a> and the upgrade block removed. </div><br><a href ='#160msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4482887' target='_blank'>KB4482887</a></td><td>Resolved:<br>March 01, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='168msgdesc'></div><b>Issues with lock screen and Microsoft Edge tabs for certain AMD Radeon video cards</b><div><strong>Note:</strong> AMD no longer supports Radeon HD2000 and HD4000 series graphic processor units (GPUs).</div><div> </div><div><strong>Upgrade block:</strong> After updating to Windows 10, version 1809, Microsoft Edge tabs may stop working when a device is configured with AMD Radeon HD2000 or HD4000 series video cards. Customers may get the following error code: \"INVALID_POINTER_READ_c0000005_atidxx64.dll\". </div><div> </div><div>Some users may also experience performance issues with the lock screen or the ShellExperienceHost. (The lock screen hosts widgets, and the ShellExperienceHost is responsible for assorted shell functionality.) </div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019</li></ul><div></div><div><strong>Resolution:</strong> This issue was resolved in <a href=\"https://support.microsoft.com/help/4487044\" target=\"_blank\">KB4487044</a>, and the block was removed.</div><br><a href ='#168msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = 'https://support.microsoft.com/help/4487044' target='_blank'>KB4487044</a></td><td>Resolved:<br>February 12, 2019 <br>10:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
<tr><td style='border-left-width:1px;border-right-width:1px;border-bottom-width:1px;'><div id='166msgdesc'></div><b>Trend Micro OfficeScan and Worry-Free Business Security AV software not compatible</b><div><strong>Upgrade block:</strong> Microsoft and Trend Micro have identified a compatibility issue with Trend Micro's OfficeScan and Worry-Free Business Security software when attempting to update to Windows 10, version 1809.</div><div><br></div><div><strong>Affected platforms:</strong></div><ul><li>Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019</li><li>Server: Windows Server, version 1809; Windows Server 2019 </li></ul><div></div><div><strong>Resolution:</strong> Trend Micro has released a new version of these products that resolves the issue. To download them, please visit the <a href=\"https://success.trendmicro.com/solution/1121159\" target=\"_blank\">Trend Micro Business Support Portal</a>.</div><div><br></div><div>Once you have updated your version of Trend Micro's OfficeScan or Worry-Free Business Security software, you will be offered Windows 10, version 1809 automatically. </div><br><a href ='#166msg'>Back to top</a></td><td>OS Build 17763.134<br><br>November 13, 2018<br><a href ='https://support.microsoft.com/help/4467708' target='_blank'>KB4467708</a></td><td>Resolved<br><a href = '' target='_blank'></a></td><td>Resolved:<br>February 01, 2019 <br>09:00 AM PT<br><br>Opened:<br>November 13, 2018 <br>10:00 AM PT</td></tr>
|
||||
</table>
|
||||
"
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user