Merge branch 'main' into pm-20230105-cleanup-win-configuration
@ -83,6 +83,10 @@ For more information, see:
|
|||||||
|
|
||||||
When your apps are ready, you can add or deploy these apps to your Windows devices. This section lists some common options.
|
When your apps are ready, you can add or deploy these apps to your Windows devices. This section lists some common options.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> Microsoft Store for Business and Microsoft Store for Education will be retired on March 31, 2023. Customers may continue to use the current capabilities for free apps until that time. There will be no support for Microsoft Store for Business and Education for Windows 11.
|
||||||
|
>Visit [Evolving the Microsoft Store for Business and Education](https://aka.ms/windows/msfb_evolution) for more information about the new Microsoft Store experience for both Windows 11 and Windows 10, and learn about other options for getting and managing apps.
|
||||||
|
|
||||||
- **Manually install**: On your devices, users can install apps from the Microsoft Store, from the internet, and from an organization shared drive. These apps, and more, are listed in **Settings** > **Apps** > **Apps and Features**.
|
- **Manually install**: On your devices, users can install apps from the Microsoft Store, from the internet, and from an organization shared drive. These apps, and more, are listed in **Settings** > **Apps** > **Apps and Features**.
|
||||||
|
|
||||||
If you want to prevent users from downloading apps on organization owned devices, use an MDM provider, like Microsoft Intune. For example, you can create a policy that allows or prevents users from sideloading apps, only allow the private store, and more. For more information on the features you can restrict, see [Windows client device settings to allow or restrict features using Intune](/mem/intune/configuration/device-restrictions-windows-10).
|
If you want to prevent users from downloading apps on organization owned devices, use an MDM provider, like Microsoft Intune. For example, you can create a policy that allows or prevents users from sideloading apps, only allow the private store, and more. For more information on the features you can restrict, see [Windows client device settings to allow or restrict features using Intune](/mem/intune/configuration/device-restrictions-windows-10).
|
||||||
|
@ -18,6 +18,7 @@ ms.date: 08/01/2022
|
|||||||
- [ApplicationManagement/AllowAllTrustedApps](policy-csp-applicationmanagement.md#applicationmanagement-allowalltrustedapps)
|
- [ApplicationManagement/AllowAllTrustedApps](policy-csp-applicationmanagement.md#applicationmanagement-allowalltrustedapps)
|
||||||
- [ApplicationManagement/AllowAppStoreAutoUpdate](policy-csp-applicationmanagement.md#applicationmanagement-allowappstoreautoupdate)
|
- [ApplicationManagement/AllowAppStoreAutoUpdate](policy-csp-applicationmanagement.md#applicationmanagement-allowappstoreautoupdate)
|
||||||
- [ApplicationManagement/AllowDeveloperUnlock](policy-csp-applicationmanagement.md#applicationmanagement-allowdeveloperunlock)
|
- [ApplicationManagement/AllowDeveloperUnlock](policy-csp-applicationmanagement.md#applicationmanagement-allowdeveloperunlock)
|
||||||
|
- [ApplicationManagement/RequirePrivateStoreOnly](policy-csp-applicationmanagement.md#applicationmanagement-requireprivatestoreonly) <sup>11</sup>
|
||||||
- [Authentication/AllowFastReconnect](policy-csp-authentication.md#authentication-allowfastreconnect)
|
- [Authentication/AllowFastReconnect](policy-csp-authentication.md#authentication-allowfastreconnect)
|
||||||
- [Authentication/PreferredAadTenantDomainName](policy-csp-authentication.md#authentication-preferredaadtenantdomainname)
|
- [Authentication/PreferredAadTenantDomainName](policy-csp-authentication.md#authentication-preferredaadtenantdomainname)
|
||||||
- [Bluetooth/AllowDiscoverableMode](policy-csp-bluetooth.md#bluetooth-allowdiscoverablemode)
|
- [Bluetooth/AllowDiscoverableMode](policy-csp-bluetooth.md#bluetooth-allowdiscoverablemode)
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Understanding ADMX policies
|
title: Understanding ADMX policies
|
||||||
description: In Windows 10, you can use ADMX policies for Windows 10 mobile device management (MDM) across Windows 10 devices.
|
description: You can use ADMX policies for Windows mobile device management (MDM) across Windows devices.
|
||||||
ms.author: vinpa
|
ms.author: vinpa
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
ms.prod: windows-client
|
ms.prod: windows-client
|
||||||
@ -237,7 +237,7 @@ Below is the internal OS mapping of a Group Policy to an MDM area and name. This
|
|||||||
|
|
||||||
`./[Device|User]/Vendor/MSFT/Policy/Config/[config|result]/<area>/<policy>`
|
`./[Device|User]/Vendor/MSFT/Policy/Config/[config|result]/<area>/<policy>`
|
||||||
|
|
||||||
The data payload of the SyncML needs to be encoded so that it doesn't conflict with the boilerplate SyncML XML tags. Use this online tool for encoding and encoding the policy data [Coder's Toolbox](http://coderstoolbox.net/string/#!encoding=xml&action=encode&charset=us_ascii)
|
The data payload of the SyncML needs to be encoded so that it doesn't conflict with the boilerplate SyncML XML tags. Use this online tool for encoding and decoding the policy data [Coder's Toolbox](https://coderstoolbox.net/string/#!encoding=xml&action=encode&charset=us_ascii).
|
||||||
|
|
||||||
**Snippet of manifest for AppVirtualization area:**
|
**Snippet of manifest for AppVirtualization area:**
|
||||||
|
|
||||||
|
@ -1,15 +1,15 @@
|
|||||||
---
|
---
|
||||||
title: Add or remove pinned apps on the Start menu in Windows 11 | Microsoft Docs
|
title: Add or remove pinned apps on the Start menu in Windows 11
|
||||||
description: Export Start layout to LayoutModification.json with pinned apps, and add or remove pinned apps. Use the JSON text in an MDM policy to deploy a custom Start menu layout to Windows 11 devices.
|
description: Export Start layout to LayoutModification.json with pinned apps, and add or remove pinned apps. Use the JSON text in an MDM policy to deploy a custom Start menu layout to Windows 11 devices.
|
||||||
manager: aaroncz
|
manager: aaroncz
|
||||||
|
author: lizgt2000
|
||||||
ms.author: lizlong
|
ms.author: lizlong
|
||||||
ms.reviewer: ericpapa
|
ms.reviewer: ericpapa
|
||||||
ms.prod: windows-client
|
ms.prod: windows-client
|
||||||
author: lizgt2000
|
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
ms.collection: highpri
|
ms.collection: highpri
|
||||||
ms.technology: itpro-configure
|
ms.technology: itpro-configure
|
||||||
ms.date: 12/31/2017
|
ms.date: 01/10/2023
|
||||||
ms.topic: article
|
ms.topic: article
|
||||||
---
|
---
|
||||||
|
|
||||||
@ -31,9 +31,11 @@ This article shows you how to export an existing Start menu layout, and use the
|
|||||||
|
|
||||||
## Before you begin
|
## Before you begin
|
||||||
|
|
||||||
- When you customize the Start layout, you overwrite the entire full layout. A partial Start layout isn't available. Users can pin and unpin apps, and uninstall apps from Start. You can't prevent users from changing the layout.
|
- When you customize the Start layout, you overwrite the entire full layout. A partial Start layout isn't available. Users can pin and unpin apps, and uninstall apps from Start. When a user signs in or Explorer restarts, Windows reapplies the MDM policy. This action restores the specified layout and doesn't retain any user changes.
|
||||||
|
|
||||||
- It's recommended to use a Mobile Device Management (MDM) provider. MDM providers help manage your devices, and help manage apps on your devices. You can use Microsoft Intune. Intune is a family of products that include Microsoft Intune, which is a cloud service, and Configuration Manager, which is on-premises.
|
To prevent users from making any changes to the Start menu layout, see the [NoChangeStartMenu](/windows/client-management/mdm/policy-csp-admx-startmenu#admx-startmenu-nochangestartmenu) policy.
|
||||||
|
|
||||||
|
- It's recommended to use a mobile device management (MDM) provider. MDM providers help manage your devices, and help manage apps on your devices. You can use Microsoft Intune. Intune is a family of products that include Microsoft Intune, which is a cloud service, and Configuration Manager, which is on-premises.
|
||||||
|
|
||||||
In this article, we mention these services. If you're not managing your devices using an MDM provider, the following resources may help you get started:
|
In this article, we mention these services. If you're not managing your devices using an MDM provider, the following resources may help you get started:
|
||||||
|
|
||||||
|
@ -10,7 +10,7 @@ ms.topic: article
|
|||||||
ms.collection: highpri
|
ms.collection: highpri
|
||||||
date: 09/22/2022
|
date: 09/22/2022
|
||||||
ms.technology: itpro-updates
|
ms.technology: itpro-updates
|
||||||
ms.date: 12/31/2017
|
ms.date: 01/06/2023
|
||||||
---
|
---
|
||||||
|
|
||||||
# Manage additional Windows Update settings
|
# Manage additional Windows Update settings
|
||||||
@ -156,7 +156,7 @@ Enables the IT admin to manage automatic update behavior to scan, download, and
|
|||||||
|
|
||||||
#### Configuring Automatic Updates by using Group Policy
|
#### Configuring Automatic Updates by using Group Policy
|
||||||
|
|
||||||
Under **Computer Configuration\Administrative Templates\Windows Components\Windows update\Configure Automatic Updates**, you must select one of the four options:
|
Under **Computer Configuration\Administrative Templates\Windows Components\Windows update\Configure Automatic Updates**, you must select one of the following options:
|
||||||
|
|
||||||
**2 - Notify for download and auto install** - When Windows finds updates that apply to this device, users will be notified that updates are ready to be downloaded. After going to **Settings > Update & security > Windows Update**, users can download and install any available updates.
|
**2 - Notify for download and auto install** - When Windows finds updates that apply to this device, users will be notified that updates are ready to be downloaded. After going to **Settings > Update & security > Windows Update**, users can download and install any available updates.
|
||||||
|
|
||||||
@ -164,11 +164,13 @@ Under **Computer Configuration\Administrative Templates\Windows Components\Windo
|
|||||||
|
|
||||||
**4 - Auto download and schedule the install** - Specify the schedule using the options in the Group Policy Setting. For more information about this setting, see [Schedule update installation](waas-restart.md#schedule-update-installation).
|
**4 - Auto download and schedule the install** - Specify the schedule using the options in the Group Policy Setting. For more information about this setting, see [Schedule update installation](waas-restart.md#schedule-update-installation).
|
||||||
|
|
||||||
**5 - Allow local admin to choose setting** - With this option, local administrators will be allowed to use the settings app to select a configuration option of their choice. Local administrators will not be allowed to disable the configuration for Automatic Updates.
|
**5 - Allow local admin to choose setting** - With this option, local administrators will be allowed to use the settings app to select a configuration option of their choice. Local administrators will not be allowed to disable the configuration for Automatic Updates. This option is not available in any Windows 10 or later versions.
|
||||||
|
|
||||||
If this setting is set to *Disabled*, any updates that are available on Windows Update must be downloaded and installed manually. To do this, users must go to **Settings > Update & security > Windows Update**.
|
**7 - Notify for install and notify for restart** (Windows Server 2016 and later only) - With this option, when Windows finds updates that apply to this device, they will be downloaded, then users will be notified that updates are ready to be installed. Once updates are installed, a notification will be displayed to users to restart the device.
|
||||||
|
|
||||||
If this setting is set to *Not Configured*, an administrator can still configure Automatic Updates through the settings app, under **Settings > Update & security > Windows Update > Advanced options**.
|
If this setting is set to **Disabled**, any updates that are available on Windows Update must be downloaded and installed manually. To do this, users must go to **Settings > Update & security > Windows Update**.
|
||||||
|
|
||||||
|
If this setting is set to **Not Configured**, an administrator can still configure Automatic Updates through the settings app, under **Settings > Update & security > Windows Update > Advanced options**.
|
||||||
|
|
||||||
#### Configuring Automatic Updates by editing the registry
|
#### Configuring Automatic Updates by editing the registry
|
||||||
|
|
||||||
@ -205,6 +207,10 @@ To do this, follow these steps:
|
|||||||
|
|
||||||
* **4**: Automatically download and scheduled installation.
|
* **4**: Automatically download and scheduled installation.
|
||||||
|
|
||||||
|
* **5**: Allow local admin to select the configuration mode. This option is not available for Windows 10 or later versions.
|
||||||
|
|
||||||
|
* **7**: Notify for install and notify for restart. (Windows Server 2016 and later only)
|
||||||
|
|
||||||
* ScheduledInstallDay (REG_DWORD):
|
* ScheduledInstallDay (REG_DWORD):
|
||||||
|
|
||||||
* **0**: Every day.
|
* **0**: Every day.
|
||||||
|
@ -103,5 +103,7 @@
|
|||||||
- name: What's new
|
- name: What's new
|
||||||
href:
|
href:
|
||||||
items:
|
items:
|
||||||
|
- name: What's new 2023
|
||||||
|
href: whats-new/windows-autopatch-whats-new-2023.md
|
||||||
- name: What's new 2022
|
- name: What's new 2022
|
||||||
href: whats-new/windows-autopatch-whats-new-2022.md
|
href: whats-new/windows-autopatch-whats-new-2022.md
|
Before Width: | Height: | Size: 52 KiB After Width: | Height: | Size: 86 KiB |
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 60 KiB |
Before Width: | Height: | Size: 168 KiB After Width: | Height: | Size: 1.5 MiB |
Before Width: | Height: | Size: 57 KiB After Width: | Height: | Size: 66 KiB |
Before Width: | Height: | Size: 168 KiB After Width: | Height: | Size: 818 KiB |
Before Width: | Height: | Size: 297 KiB After Width: | Height: | Size: 1001 KiB |
Before Width: | Height: | Size: 258 KiB After Width: | Height: | Size: 1.5 MiB |
Before Width: | Height: | Size: 259 KiB After Width: | Height: | Size: 828 KiB |
Before Width: | Height: | Size: 1006 KiB After Width: | Height: | Size: 1008 KiB |
@ -31,7 +31,7 @@ For a device to be eligible for Windows feature updates as a part of Windows Aut
|
|||||||
| Internet connectivity | Devices must have a steady internet connection, and access to Windows [update endpoints](../prepare/windows-autopatch-configure-network.md). |
|
| Internet connectivity | Devices must have a steady internet connection, and access to Windows [update endpoints](../prepare/windows-autopatch-configure-network.md). |
|
||||||
| Windows edition | Devices must be on a Windows edition supported by Windows Autopatch. For more information, see [Prerequisites](../prepare/windows-autopatch-prerequisites.md). |
|
| Windows edition | Devices must be on a Windows edition supported by Windows Autopatch. For more information, see [Prerequisites](../prepare/windows-autopatch-prerequisites.md). |
|
||||||
| Mobile device management (MDM) policy conflict | Devices must not have deployed any policies that would prevent device management. For more information, see [Conflicting and unsupported policies](../operate/windows-autopatch-wqu-unsupported-policies.md). |
|
| Mobile device management (MDM) policy conflict | Devices must not have deployed any policies that would prevent device management. For more information, see [Conflicting and unsupported policies](../operate/windows-autopatch-wqu-unsupported-policies.md). |
|
||||||
| Group policy conflict | Devices must not have group policies deployed which would prevent device management. For more information, see [Group policy](windows-autopatch-wqu-unsupported-policies.md#group-policy-and-other-policy-managers) |
|
| Group policy conflict | Devices must not have group policies deployed which would prevent device management. For more information, see [Group policy](windows-autopatch-wqu-unsupported-policies.md#group-policy-and-other-policy-managers). |
|
||||||
|
|
||||||
## Windows feature update releases
|
## Windows feature update releases
|
||||||
|
|
||||||
@ -101,6 +101,6 @@ Windows Autopatch doesn't support the rollback of feature updates.
|
|||||||
|
|
||||||
## Incidents and outages
|
## Incidents and outages
|
||||||
|
|
||||||
If devices in your tenant aren't meeting the [service level objective](#service-level-objective) for Windows feature updates, Autopatch will raise an incident will be raised. The Windows Autopatch Service Engineering Team will work to bring those devices onto the latest version of Windows.
|
If devices in your tenant don't meet the [service level objective](#service-level-objective) for Windows feature updates, Autopatch will raise an incident will be raised. The Windows Autopatch Service Engineering Team will work to bring those devices onto the latest version of Windows.
|
||||||
|
|
||||||
If you're experiencing other issues related to Windows feature updates, [submit a support request](../operate/windows-autopatch-support-request.md).
|
If you're experiencing other issues related to Windows feature updates, [submit a support request](../operate/windows-autopatch-support-request.md).
|
||||||
|
@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
title: Submit a support request
|
title: Submit a support request
|
||||||
description: Details how to contact the Windows Autopatch Service Engineering Team and submit support requests
|
description: Details how to contact the Windows Autopatch Service Engineering Team and submit support requests
|
||||||
ms.date: 05/30/2022
|
ms.date: 01/06/2023
|
||||||
ms.prod: windows-client
|
ms.prod: windows-client
|
||||||
ms.technology: itpro-updates
|
ms.technology: itpro-updates
|
||||||
ms.topic: how-to
|
ms.topic: how-to
|
||||||
@ -19,6 +19,20 @@ msreviewer: hathind
|
|||||||
|
|
||||||
You can submit support tickets to Microsoft using the Windows Autopatch admin center. Email is the recommended approach to interact with the Windows Autopatch Service Engineering Team.
|
You can submit support tickets to Microsoft using the Windows Autopatch admin center. Email is the recommended approach to interact with the Windows Autopatch Service Engineering Team.
|
||||||
|
|
||||||
|
## Premier and Unified support options
|
||||||
|
|
||||||
|
As a customer with a **Premier** or **Unified** support contract, you can specify the severity of your issue, and schedule a support callback for a specific day and time. These options are available when you open or submit a new issue and when you edit an active support case.
|
||||||
|
|
||||||
|
Depending on your support contract, the following severity options are available:
|
||||||
|
|
||||||
|
| Support contract | Severity options |
|
||||||
|
| ----- | ----- |
|
||||||
|
| Premier | Severity A, B or C |
|
||||||
|
| Unified | Critical or non-critical |
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> Selecting either severity **A** or **Critical** issue limits you to a phone support case. This is the fastest support option.
|
||||||
|
|
||||||
## Submit a new support request
|
## Submit a new support request
|
||||||
|
|
||||||
Support requests are triaged and responded to as they're received.
|
Support requests are triaged and responded to as they're received.
|
||||||
|
@ -12,7 +12,7 @@ manager: dougeby
|
|||||||
msreviewer: hathind
|
msreviewer: hathind
|
||||||
---
|
---
|
||||||
|
|
||||||
# Windows quality update communications
|
# Windows quality and feature update communications
|
||||||
|
|
||||||
There are three categories of communication that are sent out during a Windows quality and feature update:
|
There are three categories of communication that are sent out during a Windows quality and feature update:
|
||||||
|
|
||||||
@ -29,8 +29,8 @@ Communications are posted to Message center, Service health dashboard, and the W
|
|||||||
| Communication | Location | Timing | Description |
|
| Communication | Location | Timing | Description |
|
||||||
| ----- | ----- | ----- | ----- |
|
| ----- | ----- | ----- | ----- |
|
||||||
| Release schedule | <ul><li>Message center</li><li>Messages blade</li><li>Email sent to your specified [admin contacts](../deploy/windows-autopatch-admin-contacts.md)</li><ul> | At least seven days prior to the second Tuesday of the month| Notification of the planned release window for each ring. |
|
| Release schedule | <ul><li>Message center</li><li>Messages blade</li><li>Email sent to your specified [admin contacts](../deploy/windows-autopatch-admin-contacts.md)</li><ul> | At least seven days prior to the second Tuesday of the month| Notification of the planned release window for each ring. |
|
||||||
| Release start | Same as release schedule | The second Tuesday of every month | Notification that the update is now being released into your environment. |
|
| Release start | Same as release schedule | The second Tuesday of every month. | Notification that the update is now being released into your environment. |
|
||||||
| Release summary | Same as release schedule | The fourth Tuesday of every month | Informs you of the percentage of eligible devices that were patched during the release. |
|
| Release summary | Same as release schedule | The fourth Tuesday of every month. | Informs you of the percentage of eligible devices that were patched during the release. |
|
||||||
|
|
||||||
## Communications during release
|
## Communications during release
|
||||||
|
|
||||||
|
@ -73,7 +73,7 @@ For each [deployment ring](windows-autopatch-update-management.md#windows-autopa
|
|||||||
|
|
||||||
Threat and vulnerability information about a new revision of Windows becomes available on the second Tuesday of each month. Windows Autopatch assesses that information shortly afterwards. If the service determines that it's critical to security, it may be expedited. The quality update is also evaluated on an ongoing basis throughout the release and Windows Autopatch may choose to expedite at any time during the release.
|
Threat and vulnerability information about a new revision of Windows becomes available on the second Tuesday of each month. Windows Autopatch assesses that information shortly afterwards. If the service determines that it's critical to security, it may be expedited. The quality update is also evaluated on an ongoing basis throughout the release and Windows Autopatch may choose to expedite at any time during the release.
|
||||||
|
|
||||||
When running an expedited release, the regular goal of 95% of devices in 21 days no longer applies. Instead, Windows Autopatch greatly accelerates the release schedule of the release to update the environment more quickly. This approach requires an updated schedule for all devices outside of the Test ring since those devices are already getting the update as quickly.
|
When running an expedited release, the regular goal of 95% of devices in 21 days no longer applies. Instead, Windows Autopatch greatly accelerates the release schedule of the release to update the environment more quickly. This approach requires an updated schedule for all devices outside of the Test ring since those devices are already getting the update quickly.
|
||||||
|
|
||||||
| Release type | Group | Deferral | Deadline | Grace period |
|
| Release type | Group | Deferral | Deadline | Grace period |
|
||||||
| ----- | ----- | ----- | ----- | ----- |
|
| ----- | ----- | ----- | ----- | ----- |
|
||||||
@ -84,7 +84,7 @@ When running an expedited release, the regular goal of 95% of devices in 21 days
|
|||||||
|
|
||||||
Windows Autopatch provides the option to turn off of service-driven expedited quality updates.
|
Windows Autopatch provides the option to turn off of service-driven expedited quality updates.
|
||||||
|
|
||||||
By default, the service expedites quality updates as needed. For those organizations seeking greater control, you can disable expedited quality updates for Microsoft Managed Desktop-enrolled devices using Microsoft Intune.
|
By default, the service expedites quality updates as needed. For those organizations seeking greater control, you can disable expedited quality updates for Windows Autopatch-enrolled devices using Microsoft Intune.
|
||||||
|
|
||||||
**To turn off service-driven expedited quality updates:**
|
**To turn off service-driven expedited quality updates:**
|
||||||
|
|
||||||
@ -116,8 +116,8 @@ There are two statuses associated with paused quality updates, **Service Paused*
|
|||||||
|
|
||||||
| Status | Description |
|
| Status | Description |
|
||||||
| ----- | ------ |
|
| ----- | ------ |
|
||||||
| Service Paused | If the Microsoft Managed Desktop service has paused an update, the release will have the **Service Paused** status. You must [submit a support request](windows-autopatch-support-request.md) to resume the update. |
|
| Service Paused | If the Windows Autopatch service has paused an update, the release will have the **Service Paused** status. You must [submit a support request](windows-autopatch-support-request.md) to resume the update. |
|
||||||
| Customer Paused | If you've paused an update, the release will have the **Customer Paused** status. The Microsoft Managed Desktop service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
|
| Customer Paused | If you've paused an update, the release will have the **Customer Paused** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
|
||||||
|
|
||||||
## Incidents and outages
|
## Incidents and outages
|
||||||
|
|
||||||
|
@ -22,7 +22,7 @@ If there's a scenario that is critical to your business, which isn't monitored b
|
|||||||
|
|
||||||
Before being released to the Test ring, Windows Autopatch reviews several data sources to determine if we need to send any customer advisories or need to pause the update. Situations where Windows Autopatch doesn't release an update to the Test ring are seldom occurrences.
|
Before being released to the Test ring, Windows Autopatch reviews several data sources to determine if we need to send any customer advisories or need to pause the update. Situations where Windows Autopatch doesn't release an update to the Test ring are seldom occurrences.
|
||||||
|
|
||||||
| Text | Text |
|
| Pre-release signal | Description |
|
||||||
| ----- | ----- |
|
| ----- | ----- |
|
||||||
| Windows Payload Review | The contents of the B release are reviewed to help focus your update testing on areas that have changed. If any relevant changes are detected, a [customer advisory](../operate/windows-autopatch-wqu-communications.md#communications-during-release) will be sent out. |
|
| Windows Payload Review | The contents of the B release are reviewed to help focus your update testing on areas that have changed. If any relevant changes are detected, a [customer advisory](../operate/windows-autopatch-wqu-communications.md#communications-during-release) will be sent out. |
|
||||||
| C-Release Review - Internal Signals | Windows Autopatch reviews active incidents associated with the previous C release to understand potential risks in the B release. |
|
| C-Release Review - Internal Signals | Windows Autopatch reviews active incidents associated with the previous C release to understand potential risks in the B release. |
|
||||||
@ -50,12 +50,12 @@ Autopatch monitors the following reliability signals:
|
|||||||
|
|
||||||
| Device reliability signal | Description |
|
| Device reliability signal | Description |
|
||||||
| ----- | ----- |
|
| ----- | ----- |
|
||||||
| Blue screens | These events are highly disruptive to end users so are closely watched. |
|
| Blue screens | These events are highly disruptive to end users. These events are closely monitored. |
|
||||||
| Overall app reliability | Tracks the total number of app crashes and freezes on a device. A known limitation with this measure is that if one app becomes 10% more reliable and another becomes 10% less reliable then it shows up as a flat line in the measure. |
|
| Overall app reliability | Tracks the total number of app crashes and freezes on a device. A known limitation with this measure is that if one app becomes 10% more reliable and another becomes 10% less reliable then it shows up as a flat line in the measure. |
|
||||||
| Microsoft Office reliability | Tracks the number of Office crashes and freezes per application per device. |
|
| Microsoft Office reliability | Tracks the number of Office crashes and freezes per application per device. |
|
||||||
| Microsoft Edge reliability | Tracks the number of Microsoft Edge crashes and freezes per device. |
|
| Microsoft Edge reliability | Tracks the number of Microsoft Edge crashes and freezes per device. |
|
||||||
| Microsoft Teams reliability | Tracks the number of Microsoft Teams crashes and freezes per device. |
|
| Microsoft Teams reliability | Tracks the number of Microsoft Teams crashes and freezes per device. |
|
||||||
|
|
||||||
When the update is released to the First ring, the service crosses the 500 device threshold. Therefore, Autopatch is able to detect regressions, which are common to all customers. At this point in the release, we'll decide if we need to change the release schedule or pause for all customers.
|
When the update is released to the First ring, the service crosses the 500 device threshold. Therefore, Autopatch can to detect regressions, which are common to all customers. At this point in the release, we'll decide if we need to change the release schedule or pause for all customers.
|
||||||
|
|
||||||
Once your tenant reaches 500 devices, Windows Autopatch starts generating recommendations specific to your devices. Based on this information, the service starts developing insights specific to your tenant allowing a customized response to what's happening in your environment.
|
Once your tenant reaches 500 devices, Windows Autopatch starts generating recommendations specific to your devices. Based on this information, the service starts developing insights specific to your tenant allowing a customized response to what's happening in your environment.
|
||||||
|
@ -79,7 +79,7 @@ Windows Autopatch creates and uses guest accounts using just-in-time access func
|
|||||||
| Account name | Usage | Mitigating controls |
|
| Account name | Usage | Mitigating controls |
|
||||||
| ----- | ----- | -----|
|
| ----- | ----- | -----|
|
||||||
| MsAdmin@tenantDomain.onmicrosoft.com | <ul><li>This account is a limited-service account with administrator privileges. This account is used as an Intune and User administrator to define and configure the tenant for Windows Autopatch devices.</li><li>This account doesn't have interactive sign-in permissions. The account performs operations only through the service.</li></ul> | Audited sign-ins |
|
| MsAdmin@tenantDomain.onmicrosoft.com | <ul><li>This account is a limited-service account with administrator privileges. This account is used as an Intune and User administrator to define and configure the tenant for Windows Autopatch devices.</li><li>This account doesn't have interactive sign-in permissions. The account performs operations only through the service.</li></ul> | Audited sign-ins |
|
||||||
| MsAdminInt@tenantDomain.onmicrosoft.com |<ul><li>This account is an Intune and User administrator account used to define and configure the tenant for Windows Autopatch devices.</li><li>This account is used for interactive login to the customer’s tenant.</li><li>The use of this account is limited as most operations are exclusively through MsAdmin (non-interactive) account.</li></ul> | <ul><li>Restricted to be accessed only from defined secure access workstations (SAWs) through a conditional access policy</li><li>Audited sign-ins</li</ul> |
|
| MsAdminInt@tenantDomain.onmicrosoft.com |<ul><li>This account is an Intune and User administrator account used to define and configure the tenant for Windows Autopatch devices.</li><li>This account is used for interactive login to the customer’s tenant.</li><li>The use of this account is limited as most operations are exclusively through MsAdmin (non-interactive) account.</li></ul> | <ul><li>Restricted to be accessed only from defined secure access workstations (SAWs) through a conditional access policy</li><li>Audited sign-ins</li></ul> |
|
||||||
| MsTest@tenantDomain.onmicrosoft.com | This account is a standard account used as a validation account for initial configuration and roll out of policy, application, and device compliance settings. | Audited sign-ins |
|
| MsTest@tenantDomain.onmicrosoft.com | This account is a standard account used as a validation account for initial configuration and roll out of policy, application, and device compliance settings. | Audited sign-ins |
|
||||||
|
|
||||||
## Microsoft Windows Update for Business
|
## Microsoft Windows Update for Business
|
||||||
|
@ -1,10 +1,10 @@
|
|||||||
---
|
---
|
||||||
title: What's new
|
title: What's new 2022
|
||||||
description: This article lists the new feature releases and any corresponding Message center post numbers.
|
description: This article lists the 2022 feature releases and any corresponding Message center post numbers.
|
||||||
ms.date: 12/09/2022
|
ms.date: 12/09/2022
|
||||||
ms.prod: windows-client
|
ms.prod: windows-client
|
||||||
ms.technology: itpro-updates
|
ms.technology: itpro-updates
|
||||||
ms.topic: how-to
|
ms.topic: whats-new
|
||||||
ms.localizationpriority: medium
|
ms.localizationpriority: medium
|
||||||
author: tiaraquan
|
author: tiaraquan
|
||||||
ms.author: tiaraquan
|
ms.author: tiaraquan
|
||||||
|
@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
title: What's new 2023
|
||||||
|
description: This article lists the 2023 feature releases and any corresponding Message center post numbers.
|
||||||
|
ms.date: 01/09/2023
|
||||||
|
ms.prod: windows-client
|
||||||
|
ms.technology: itpro-updates
|
||||||
|
ms.topic: whats-new
|
||||||
|
ms.localizationpriority: medium
|
||||||
|
author: tiaraquan
|
||||||
|
ms.author: tiaraquan
|
||||||
|
manager: dougeby
|
||||||
|
msreviewer: hathind
|
||||||
|
---
|
||||||
|
|
||||||
|
# What's new 2023
|
||||||
|
|
||||||
|
This article lists new and updated feature releases, and service releases, with their corresponding Message center post numbers (if applicable).
|
||||||
|
|
||||||
|
Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||||
|
|
||||||
|
## January 2023
|
||||||
|
|
||||||
|
### January feature releases or updates
|
||||||
|
|
||||||
|
| Article | Description |
|
||||||
|
| ----- | ----- |
|
||||||
|
| [Submit a support request](../operate/windows-autopatch-support-request.md) | Added Premier and Unified support options section |
|
||||||
|
|
||||||
|
### January service release
|
||||||
|
|
||||||
|
| Message center post number | Description |
|
||||||
|
| ----- | ----- |
|
||||||
|
| [MC494386](https://admin.microsoft.com/adminportal/home#/MessageCenter) | January 2023 (2023.01 B) Windows quality update deployment |
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Devices: Restrict floppy access to locally logged-on user only
|
# Devices: Restrict floppy access to locally logged-on user only
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Devices: Restrict floppy access to locally logged-on user only** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Devices: Restrict floppy access to locally logged-on user only** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Domain member: Digitally encrypt or sign secure channel data (always)
|
# Domain member: Digitally encrypt or sign secure channel data (always)
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Domain member: Digitally encrypt or sign secure channel data (always)** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Domain member: Digitally encrypt or sign secure channel data (always)** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Domain member: Digitally encrypt secure channel data (when possible)
|
# Domain member: Digitally encrypt secure channel data (when possible)
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Domain member: Digitally encrypt secure channel data (when possible)** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Domain member: Digitally encrypt secure channel data (when possible)** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Domain member: Digitally sign secure channel data (when possible)
|
# Domain member: Digitally sign secure channel data (when possible)
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Domain member: Digitally sign secure channel data (when possible)** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Domain member: Digitally sign secure channel data (when possible)** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Domain member: Disable machine account password changes
|
# Domain member: Disable machine account password changes
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Domain member: Disable machine account password changes** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Domain member: Disable machine account password changes** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Domain member: Maximum machine account password age
|
# Domain member: Maximum machine account password age
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Domain member: Maximum machine account password age** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Domain member: Maximum machine account password age** security policy setting.
|
||||||
|
@ -20,7 +20,8 @@ ms.technology: itpro-security
|
|||||||
# Domain member: Require strong (Windows 2000 or later) session key
|
# Domain member: Require strong (Windows 2000 or later) session key
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 11
|
||||||
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Domain member: Require strong (Windows 2000 or later) session key** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Domain member: Require strong (Windows 2000 or later) session key** security policy setting.
|
||||||
|
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Display user information when the session is locked
|
# Interactive logon: Display user information when the session is locked
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Interactive logon: Display user information when the session is locked** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Interactive logon: Display user information when the session is locked** security policy setting.
|
||||||
|
@ -19,7 +19,8 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Don't display last signed-in
|
# Interactive logon: Don't display last signed-in
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10
|
- Windows 11
|
||||||
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Interactive logon: Don't display last signed-in** security policy setting. Before Windows 10 version 1703, this policy setting was named **Interactive logon:Do not display last user name.**
|
Describes the best practices, location, values, and security considerations for the **Interactive logon: Don't display last signed-in** security policy setting. Before Windows 10 version 1703, this policy setting was named **Interactive logon:Do not display last user name.**
|
||||||
|
|
||||||
|
@ -19,6 +19,7 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Do not require CTRL+ALT+DEL
|
# Interactive logon: Do not require CTRL+ALT+DEL
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Interactive logon: Do not require CTRL+ALT+DEL** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Interactive logon: Do not require CTRL+ALT+DEL** security policy setting.
|
||||||
|
@ -20,7 +20,9 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Don't display username at sign-in
|
# Interactive logon: Don't display username at sign-in
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
- Windows 10, Windows Server 2019
|
- Windows 11
|
||||||
|
- Windows 10
|
||||||
|
- Windows Server 2019
|
||||||
|
|
||||||
Describes the best practices, location, values, and security considerations for the **Interactive logon: Don't display username at sign-in** security policy setting.
|
Describes the best practices, location, values, and security considerations for the **Interactive logon: Don't display username at sign-in** security policy setting.
|
||||||
|
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Machine account lockout threshold
|
# Interactive logon: Machine account lockout threshold
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, management, and security considerations for the **Interactive logon: Machine account lockout threshold** security policy setting.
|
Describes the best practices, location, values, management, and security considerations for the **Interactive logon: Machine account lockout threshold** security policy setting.
|
||||||
|
@ -22,6 +22,7 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Machine inactivity limit
|
# Interactive logon: Machine inactivity limit
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, management, and security considerations for the **Interactive logon: Machine inactivity limit** security policy setting.
|
Describes the best practices, location, values, management, and security considerations for the **Interactive logon: Machine inactivity limit** security policy setting.
|
||||||
|
@ -21,6 +21,7 @@ ms.technology: itpro-security
|
|||||||
|
|
||||||
**Applies to:**
|
**Applies to:**
|
||||||
|
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, management, and security considerations for the **Interactive logon: Message text for users attempting to log on** security policy setting.
|
Describes the best practices, location, values, management, and security considerations for the **Interactive logon: Message text for users attempting to log on** security policy setting.
|
||||||
|
@ -21,6 +21,7 @@ ms.technology: itpro-security
|
|||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, policy management and security considerations for the **Interactive logon: Message title for users attempting to log on** security policy setting.
|
Describes the best practices, location, values, policy management and security considerations for the **Interactive logon: Message title for users attempting to log on** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Number of previous logons to cache (in case domain controller is not available)
|
# Interactive logon: Number of previous logons to cache (in case domain controller is not available)
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, policy management, and security considerations for the **Interactive logon: Number of previous logons to cache (in case domain controller is not available)** security policy setting.
|
Describes the best practices, location, values, policy management, and security considerations for the **Interactive logon: Number of previous logons to cache (in case domain controller is not available)** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Interactive log on: Prompt the user to change passwords before expiration
|
# Interactive log on: Prompt the user to change passwords before expiration
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
This article describes the best practices, location, values, policy management, and security considerations for the **Interactive logon: Prompt user to change password before expiration** security policy setting.
|
This article describes the best practices, location, values, policy management, and security considerations for the **Interactive logon: Prompt user to change password before expiration** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Require Domain Controller authentication to unlock workstation
|
# Interactive logon: Require Domain Controller authentication to unlock workstation
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the best practices, location, values, policy management, and security considerations for the **Interactive logon: Require Domain Controller authentication to unlock workstation** security policy setting.
|
Describes the best practices, location, values, policy management, and security considerations for the **Interactive logon: Require Domain Controller authentication to unlock workstation** security policy setting.
|
||||||
|
@ -20,6 +20,7 @@ ms.technology: itpro-security
|
|||||||
# Interactive logon: Smart card removal behavior
|
# Interactive logon: Smart card removal behavior
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
|
|
||||||
Describes the recommended practices, location, values, policy management, and security considerations for the **Interactive logon: Smart card removal behavior** security policy setting.
|
Describes the recommended practices, location, values, policy management, and security considerations for the **Interactive logon: Smart card removal behavior** security policy setting.
|
||||||
|
@ -19,6 +19,7 @@ ms.topic: conceptual
|
|||||||
# Microsoft network client: Digitally sign communications (always)
|
# Microsoft network client: Digitally sign communications (always)
|
||||||
|
|
||||||
**Applies to**
|
**Applies to**
|
||||||
|
- Windows 11
|
||||||
- Windows 10
|
- Windows 10
|
||||||
- Windows Server
|
- Windows Server
|
||||||
|
|
||||||
|
@ -31,7 +31,7 @@ Before you deploy your WDAC policies, you must first convert the XML to its bina
|
|||||||
|
|
||||||
```powershell
|
```powershell
|
||||||
## Update the path to your WDAC policy XML
|
## Update the path to your WDAC policy XML
|
||||||
$WDACPolicyXMLFile = $env:USERPROFILE"\Desktop\MyWDACPolicy.xml"
|
$WDACPolicyXMLFile = $env:USERPROFILE + "\Desktop\MyWDACPolicy.xml"
|
||||||
[xml]$WDACPolicy = Get-Content -Path $WDACPolicyXMLFile
|
[xml]$WDACPolicy = Get-Content -Path $WDACPolicyXMLFile
|
||||||
if (($WDACPolicy.SiPolicy.PolicyID) -ne $null) ## Multiple policy format (For Windows builds 1903+ only, including Server 2022)
|
if (($WDACPolicy.SiPolicy.PolicyID) -ne $null) ## Multiple policy format (For Windows builds 1903+ only, including Server 2022)
|
||||||
{
|
{
|
||||||
|
@ -23,10 +23,12 @@ Each version of Windows client adds new features and functionality. Occasionally
|
|||||||
|
|
||||||
For more information about features in Windows 11, see [Feature deprecations and removals](https://www.microsoft.com/windows/windows-11-specifications#table3).
|
For more information about features in Windows 11, see [Feature deprecations and removals](https://www.microsoft.com/windows/windows-11-specifications#table3).
|
||||||
|
|
||||||
To understand the distinction between _deprecation_ and _removal_, see [Windows client features lifecycle](feature-lifecycle.md).
|
To understand the distinction between *deprecation* and *removal*, see [Windows client features lifecycle](feature-lifecycle.md).
|
||||||
|
|
||||||
The features in this article are no longer being actively developed, and might be removed in a future update. Some features have been replaced with other features or functionality and some are now available from other sources.
|
The features in this article are no longer being actively developed, and might be removed in a future update. Some features have been replaced with other features or functionality and some are now available from other sources.
|
||||||
|
|
||||||
|
## Deprecated features
|
||||||
|
|
||||||
**The following list is subject to change and might not include every affected feature or functionality.**
|
**The following list is subject to change and might not include every affected feature or functionality.**
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
@ -34,6 +36,7 @@ The features in this article are no longer being actively developed, and might b
|
|||||||
|
|
||||||
|Feature | Details and mitigation | Deprecation announced |
|
|Feature | Details and mitigation | Deprecation announced |
|
||||||
| ----------- | --------------------- | ---- |
|
| ----------- | --------------------- | ---- |
|
||||||
|
| Universal Windows Platform (UWP) Applications for 32-bit Arm <!--7116112-->| This change is applicable only to devices with an Arm processor, for example Snapdragon processors from Qualcomm. If you have a PC built with a processor from Intel or AMD, this content is not applicable. If you are not sure which type of processor you have, check **Settings** > **System** > **About**.</br> </br> Support for 32-bit Arm versions of applications will be removed in a future release of Windows 11. After this change, for the small number of applications affected, app features might be different and you might notice a difference in performance. For more technical details about this change, see [Update app architecture from Arm32 to Arm64](/windows/arm/arm32-to-arm64). | January 2023 |
|
||||||
| Update Compliance <!--7260188-->| [Update Compliance](/windows/deployment/update/update-compliance-monitor), a cloud-based service for the Windows client, is no longer being developed. This service has been replaced with [Windows Update for Business reports](/windows/deployment/update/wufb-reports-overview), which provides reporting on client compliance with Microsoft updates from the Azure portal. | November 2022|
|
| Update Compliance <!--7260188-->| [Update Compliance](/windows/deployment/update/update-compliance-monitor), a cloud-based service for the Windows client, is no longer being developed. This service has been replaced with [Windows Update for Business reports](/windows/deployment/update/wufb-reports-overview), which provides reporting on client compliance with Microsoft updates from the Azure portal. | November 2022|
|
||||||
| Windows Information Protection <!-- 6010051 --> | [Windows Information Protection](/windows/security/information-protection/windows-information-protection/protect-enterprise-data-using-wip) will no longer be developed in future versions of Windows. For more information, see [Announcing sunset of Windows Information Protection (WIP)](https://go.microsoft.com/fwlink/?linkid=2202124).<br> <br>For your data protection needs, Microsoft recommends that you use [Microsoft Purview Information Protection](/microsoft-365/compliance/information-protection) and [Microsoft Purview Data Loss Prevention](/microsoft-365/compliance/dlp-learn-about-dlp). | July 2022 |
|
| Windows Information Protection <!-- 6010051 --> | [Windows Information Protection](/windows/security/information-protection/windows-information-protection/protect-enterprise-data-using-wip) will no longer be developed in future versions of Windows. For more information, see [Announcing sunset of Windows Information Protection (WIP)](https://go.microsoft.com/fwlink/?linkid=2202124).<br> <br>For your data protection needs, Microsoft recommends that you use [Microsoft Purview Information Protection](/microsoft-365/compliance/information-protection) and [Microsoft Purview Data Loss Prevention](/microsoft-365/compliance/dlp-learn-about-dlp). | July 2022 |
|
||||||
| BitLocker To Go Reader | **Note: BitLocker to Go as a feature is still supported.**<br>Reading of BitLocker-protected removable drives ([BitLocker To Go](/windows/security/information-protection/bitlocker/bitlocker-to-go-faq)) from Windows XP or Windows Vista in later operating systems is deprecated and might be removed in a future release of Windows client.<br>The following items might not be available in a future release of Windows client:<br>- ADMX policy: **Allow access to BitLocker-protected removable data drives from earlier versions of Windows**<br>- Command line parameter: [`manage-bde -DiscoveryVolumeType`](/windows-server/administration/windows-commands/manage-bde-on) (-dv)<br>- Catalog file: **c:\windows\BitLockerDiscoveryVolumeContents**<br>- BitLocker 2 Go Reader app: **bitlockertogo.exe** and associated files | 21H1 |
|
| BitLocker To Go Reader | **Note: BitLocker to Go as a feature is still supported.**<br>Reading of BitLocker-protected removable drives ([BitLocker To Go](/windows/security/information-protection/bitlocker/bitlocker-to-go-faq)) from Windows XP or Windows Vista in later operating systems is deprecated and might be removed in a future release of Windows client.<br>The following items might not be available in a future release of Windows client:<br>- ADMX policy: **Allow access to BitLocker-protected removable data drives from earlier versions of Windows**<br>- Command line parameter: [`manage-bde -DiscoveryVolumeType`](/windows-server/administration/windows-commands/manage-bde-on) (-dv)<br>- Catalog file: **c:\windows\BitLockerDiscoveryVolumeContents**<br>- BitLocker 2 Go Reader app: **bitlockertogo.exe** and associated files | 21H1 |
|
||||||
|