mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Merge branch 'main' into ADO-9517656-Update-for-Business
This commit is contained in:
Gary Moore
commit
3db8e0bb06
@ -1684,6 +1684,11 @@
|
||||
"source_path": "windows/deployment/planning/windows-10-deployment-considerations.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/windows-10/deployment/planning/windows-10-deployment-considerations",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopatch/monitor/windows-autopatch-reliability-report.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopatch/monitor/windows-autopatch-windows-quality-and-feature-update-reports-overview",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Use Set up School PCs app
|
||||
description: Learn how to use the Set up School PCs app and apply the provisioning package.
|
||||
ms.topic: how-to
|
||||
ms.date: 07/09/2024
|
||||
ms.date: 02/25/2025
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
|
||||
|
||||
@ -20,13 +20,3 @@ The following table lists the Windows editions that support Assigned Access:
|
||||
|IoT Enterprise LTSC|✅|
|
||||
|Pro Education|✅|
|
||||
|Pro|✅|
|
||||
|
||||
<!--
|
||||
Assigned Access license entitlements are granted by the following licenses:
|
||||
|
||||
|Windows Pro/Pro Education/SE|Windows Enterprise E3|Windows Enterprise E5|Windows Education A3|Windows Education A5|
|
||||
|:---:|:---:|:---:|:---:|:---:|
|
||||
|Yes|Yes|Yes|Yes|Yes|
|
||||
|
||||
For more information about Windows licensing, see [Windows licensing overview](/windows/whats-new/windows-licensing).
|
||||
-->
|
||||
@ -20,14 +20,4 @@ The following table lists the Windows editions that support Shell Launcher:
|
||||
|IoT Enterprise LTSC|✅|
|
||||
|Pro Education|❌|
|
||||
|Pro|❌|
|
||||
|
||||
<!--
|
||||
Shell Launcher license entitlements are granted by the following licenses:
|
||||
|
||||
|Windows Pro/Pro Education/SE|Windows Enterprise E3|Windows Enterprise E5|Windows Education A3|Windows Education A5|
|
||||
|:---:|:---:|:---:|:---:|:---:|
|
||||
|No|Yes|Yes|Yes|Yes|
|
||||
|
||||
For more information about Windows licensing, see [Windows licensing overview](/windows/whats-new/windows-licensing).
|
||||
|
||||
-->
|
||||
|Home|❌|
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Bulk enrollment
|
||||
description: Bulk enrollment is an efficient way to set up an MDM server to manage a large number of devices without the need to reimage the devices.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 07/08/2024
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Certificate authentication device enrollment
|
||||
description: This section provides an example of the mobile device enrollment protocol using certificate authentication policy.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 07/08/2024
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Certificate Renewal
|
||||
description: Learn how to find all the resources that you need to provide continuous access to client certificates.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 07/08/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Windows default media removal policy
|
||||
description: Manage default media removal policy in Windows.
|
||||
ms.date: 07/01/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
# Manage default media removal policy
|
||||
|
||||
@ -3,7 +3,7 @@ title: Connect to remote Microsoft Entra joined device
|
||||
description: Learn how to use Remote Desktop Connection to connect to a Microsoft Entra joined device.
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/01/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Manage Device Installation with Group Policy
|
||||
description: Find out how to manage Device Installation Restrictions with Group Policy.
|
||||
ms.date: 07/01/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
# Manage Device Installation with Group Policy
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Manage the Settings app with Group Policy
|
||||
description: Find out how to manage the Settings app with Group Policy so you can hide specific pages from users.
|
||||
ms.date: 07/01/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
# Manage the Settings app with Group Policy
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Create mandatory user profiles
|
||||
description: A mandatory user profile is a special type of preconfigured roaming user profile that administrators can use to specify settings for users.
|
||||
ms.date: 07/01/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
# Create mandatory user profiles
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Use Quick Assist to help users
|
||||
description: Learn how IT Pros can use Quick Assist to help users.
|
||||
ms.date: 07/01/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier1
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows Libraries
|
||||
description: All about Windows Libraries, which are containers for users' content, such as Documents and Pictures.
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.date: 07/01/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: What version of Windows am I running?
|
||||
description: Discover which version of Windows you're running to determine whether or not your device is enrolled in the Long-Term Servicing Channel or General Availability Channel.
|
||||
ms.date: 07/01/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
# What version of Windows am I running?
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Enable ADMX policies in MDM
|
||||
description: Use this step-by-step guide to configure a selected set of Group Policy administrative templates (ADMX policies) in Mobile Device Management (MDM).
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/08/2024
|
||||
---
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Enroll a Windows device automatically using Group Policy
|
||||
description: Learn how to use a Group Policy to trigger autoenrollment to MDM for Active Directory (AD) domain-joined devices.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 07/08/2024
|
||||
ms.collection:
|
||||
- highpri
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Support for Windows Information Protection (WIP) on Windows
|
||||
description: Learn about implementing the Windows version of Windows Information Protection (WIP), which is a lightweight solution for managing company data access and security on personal devices.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 07/08/2024
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Collect MDM logs
|
||||
description: Learn how to collect MDM logs. Examining these logs can help diagnose enrollment or device management issues in Windows devices managed by an MDM server.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 07/08/2024
|
||||
ms.collection:
|
||||
- highpri
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: MDM enrollment of Windows devices
|
||||
description: Learn about mobile device management (MDM) enrollment of Windows devices to simplify access to your organization's resources.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
|
||||
@ -13,7 +13,7 @@ This article lists the OMA DM device description framework (DDF) files for vario
|
||||
|
||||
As of December 2022, DDF XML schema was updated to include additional information such as OS build applicability. DDF v2 XML files for Windows 10 and Windows 11 are combined, and provided in a single download:
|
||||
|
||||
- [DDF v2 Files, September 2024](https://download.microsoft.com/download/a/a/a/aaadc008-67d4-4dcd-b864-70c479baf7d6/DDFv2September24.zip)
|
||||
- [DDF v2 Files, February 2025](https://download.microsoft.com/download/a8922fbe-20a9-431d-b24f-9d5344dda25e/DDFv2Feb25.zip)
|
||||
|
||||
## DDF v2 schema
|
||||
|
||||
@ -574,6 +574,7 @@ DDF v2 XML schema definition is listed below along with the schema definition fo
|
||||
## Older DDF files
|
||||
|
||||
You can download the older DDF files for various CSPs from the links below:
|
||||
- [Download all the DDF files for Windows 10 and 11 September 2024](https://download.microsoft.com/download/a/a/a/aaadc008-67d4-4dcd-b864-70c479baf7d6/DDFv2September24.zip)
|
||||
- [Download all the DDF files for Windows 10 and 11 May 2024](https://download.microsoft.com/download/f/6/1/f61445f7-1d38-45f7-bc8c-609b86e4aabc/DDFv2May24.zip)
|
||||
- [Download all the DDF files for Windows 10 and 11 September 2023](https://download.microsoft.com/download/0/e/c/0ec027e5-8971-49a2-9230-ec9352bc3ead/DDFv2September2023.zip)
|
||||
- [Download all the DDF files for Windows 10 and 11 December 2022](https://download.microsoft.com/download/7/4/c/74c6daca-983e-4f16-964a-eef65b553a37/DDFv2December2022.zip)
|
||||
|
||||
@ -2926,7 +2926,8 @@ This policy setting controls whether or not exclusions are visible to local admi
|
||||
<!-- Device-Configuration-HideExclusionsFromLocalAdmins-Editable-Begin -->
|
||||
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
|
||||
> [!NOTE]
|
||||
> Applying this setting won't remove exclusions from the device registry, it will only prevent them from being applied/used. This is reflected in Get-MpPreference.
|
||||
> Applying this setting won't remove exclusions from the device registry. They will be applied and enforced, but they will not be visible via the Defender manageability tools like Get-MpPreference nor by the registry editor to the Defender owned registry hive.
|
||||
|
||||
<!-- Device-Configuration-HideExclusionsFromLocalAdmins-Editable-End -->
|
||||
|
||||
<!-- Device-Configuration-HideExclusionsFromLocalAdmins-DFProperties-Begin -->
|
||||
|
||||
@ -174,7 +174,7 @@ This policy setting allows you to specify which DNS host names and which DNS suf
|
||||
<!-- HostToRealm-Editable-Begin -->
|
||||
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
|
||||
> [!NOTE]
|
||||
> The list of DNS host names and DNS suffixes has a 2048 character limit. This policy would not apply if you exceed this limit.
|
||||
> The list of DNS host names and DNS suffixes has a 2048 character limit. This policy would not apply if you exceed this limit. For more information, see [Kerberos realm to host mapping policy string-length limitations](https://support.microsoft.com/topic/e86856c2-1e02-43fe-9c58-d7c9d6386f01).
|
||||
<!-- HostToRealm-Editable-End -->
|
||||
|
||||
<!-- HostToRealm-DFProperties-Begin -->
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Push notification support for device management
|
||||
description: The DMClient CSP supports the ability to configure push-initiated device management sessions.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 07/08/2024
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Structure of OMA DM provisioning files
|
||||
description: Learn about the structure of OMA DM provisioning files, for example how each message is composed of a header, specified by the SyncHdr element, and a message body.
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 07/08/2024
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Understanding ADMX policies
|
||||
description: You can use ADMX policies for Windows mobile device management (MDM) across Windows devices.
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
ms.date: 07/08/2024
|
||||
---
|
||||
|
||||
|
||||
@ -149,7 +149,7 @@ Example:
|
||||
<App AppUserModelId="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" />
|
||||
<App DesktopAppPath="C:\Windows\system32\cmd.exe" />
|
||||
<App DesktopAppPath="%windir%\explorer.exe" />
|
||||
<App AppUserModelId="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
<App DesktopAppPath="C:\Windows\System32\notepad.exe" rs5:AutoLaunch="true" rs5:AutoLaunchArguments="%windir%\setuperr.log" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
|
||||
@ -23,7 +23,7 @@ ms.topic: include
|
||||
<App DesktopAppPath="%windir%\System32\WindowsPowerShell\v1.0\Powershell.exe" />
|
||||
<App DesktopAppPath="%windir%\explorer.exe" />
|
||||
<App AppUserModelId="windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" />
|
||||
<App AppUserModelId="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<rs5:FileExplorerNamespaceRestrictions>
|
||||
@ -81,7 +81,7 @@ ms.topic: include
|
||||
<App DesktopAppPath="%windir%\System32\WindowsPowerShell\v1.0\Powershell.exe" />
|
||||
<App DesktopAppPath="%windir%\explorer.exe" />
|
||||
<App AppUserModelId="windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" />
|
||||
<App AppUserModelId="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<rs5:FileExplorerNamespaceRestrictions>
|
||||
|
||||
@ -11,7 +11,7 @@ ms.topic: include
|
||||
POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations
|
||||
Content-Type: application/json
|
||||
|
||||
{ "id": "00-0000-0000-0000-000000000000", "displayName": "_MSLearn_Example_Restricted_User_Experience - Assigned Access - Windows 10", "description": "This is a sample policy created from an article on learn.microsoft.com.", "roleScopeTagIds": [ "0" ], "@odata.type": "#microsoft.graph.windows10CustomConfiguration", "omaSettings": [ { "@odata.type": "#microsoft.graph.omaSettingString", "displayName": "AssignedAccess_Configuration", "description": null, "omaUri": "./Vendor/MSFT/AssignedAccess/Configuration", "secretReferenceValueId": null, "isEncrypted": true, "value": "<?xml version=\"1.0\" encoding=\"utf-8\" ?>\n<AssignedAccessConfiguration\n xmlns:xs=\"http://www.w3.org/2001/XMLSchema\"\n xmlns=\"http://schemas.microsoft.com/AssignedAccess/2017/config\"\n xmlns:default=\"http://schemas.microsoft.com/AssignedAccess/2017/config\"\n xmlns:rs5=\"http://schemas.microsoft.com/AssignedAccess/201810/config\"\n xmlns:v3=\"http://schemas.microsoft.com/AssignedAccess/2020/config\">\n <Profiles>\n <Profile Id=\"{9A2A490F-10F6-4764-974A-43B19E722C23}\">\n <AllAppsList>\n <AllowedApps>\n <App AppUserModelId=\"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App\" />\n <App AppUserModelId=\"Microsoft.Windows.Photos_8wekyb3d8bbwe!App\" />\n <App AppUserModelId=\"Microsoft.BingWeather_8wekyb3d8bbwe!App\" />\n <App DesktopAppPath=\"C:\\Windows\\system32\\cmd.exe\" />\n <App DesktopAppPath=\"%windir%\\System32\\WindowsPowerShell\\v1.0\\Powershell.exe\" />\n <App DesktopAppPath=\"%windir%\\explorer.exe\" />\n <App AppUserModelId=\"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\" />\n <App AppUserModelId=\"%ProgramFiles(x86)%\\Microsoft\\Edge\\Application\\msedge.exe\" />\n </AllowedApps>\n </AllAppsList>\n <rs5:FileExplorerNamespaceRestrictions>\n <rs5:AllowedNamespace Name=\"Downloads\"/>\n <v3:AllowRemovableDrives/>\n </rs5:FileExplorerNamespaceRestrictions>\n <StartLayout>\n <![CDATA[\n <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\">\n <LayoutOptions StartTileGroupCellWidth=\"6\" />\n <DefaultLayoutOverride>\n <StartLayoutCollection>\n <defaultlayout:StartLayout GroupCellWidth=\"6\">\n <start:Group Name=\"\">\n <start:Tile Size=\"2x2\" Column=\"0\" Row=\"4\" AppUserModelID=\"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\" />\n <start:DesktopApplicationTile Size=\"2x2\" Column=\"2\" Row=\"4\" DesktopApplicationLinkPath=\"%ALLUSERSPROFILE%\\Microsoft\\Windows\\Start Menu\\Programs\\Microsoft Edge.lnk\" />\n <start:Tile Size=\"2x2\" Column=\"4\" Row=\"0\" AppUserModelID=\"Microsoft.BingWeather_8wekyb3d8bbwe!App\" />\n <start:DesktopApplicationTile Size=\"2x2\" Column=\"4\" Row=\"2\" DesktopApplicationLinkPath=\"%APPDATA%\\Microsoft\\Windows\\Start Menu\\Programs\\System Tools\\File Explorer.lnk\" />\n <start:DesktopApplicationTile Size=\"2x2\" Column=\"2\" Row=\"2\" DesktopApplicationLinkPath=\"%APPDATA%\\Microsoft\\Windows\\Start Menu\\Programs\\Windows PowerShell\\Windows PowerShell.lnk\" />\n <start:Tile Size=\"2x2\" Column=\"2\" Row=\"0\" AppUserModelID=\"Microsoft.Windows.Photos_8wekyb3d8bbwe!App\" />\n <start:Tile Size=\"2x2\" Column=\"0\" Row=\"0\" AppUserModelID=\"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App\" />\n <start:DesktopApplicationTile Size=\"2x2\" Column=\"0\" Row=\"2\" DesktopApplicationLinkPath=\"%APPDATA%\\Microsoft\\Windows\\Start Menu\\Programs\\System Tools\\Command Prompt.lnk\" />\n </start:Group>\n </defaultlayout:StartLayout>\n </StartLayoutCollection>\n </DefaultLayoutOverride>\n </LayoutModificationTemplate>\n ]]>\n </StartLayout>\n <Taskbar ShowTaskbar=\"true\"/>\n </Profile>\n </Profiles>\n <Configs>\n <Config>\n <AutoLogonAccount rs5:DisplayName=\"MS Learn Example\"/>\n <DefaultProfile Id=\"{9A2A490F-10F6-4764-974A-43B19E722C23}\"/>\n </Config>\n </Configs>\n</AssignedAccessConfiguration>" } ] }
|
||||
{ "id": "00-0000-0000-0000-000000000000", "displayName": "_MSLearn_Example_Restricted_User_Experience - Assigned Access - Windows 10", "description": "This is a sample policy created from an article on learn.microsoft.com.", "roleScopeTagIds": [ "0" ], "@odata.type": "#microsoft.graph.windows10CustomConfiguration", "omaSettings": [ { "@odata.type": "#microsoft.graph.omaSettingString", "displayName": "AssignedAccess_Configuration", "description": null, "omaUri": "./Vendor/MSFT/AssignedAccess/Configuration", "secretReferenceValueId": null, "isEncrypted": true, "value": "<?xml version=\"1.0\" encoding=\"utf-8\" ?>\n<AssignedAccessConfiguration\n xmlns:xs=\"http://www.w3.org/2001/XMLSchema\"\n xmlns=\"http://schemas.microsoft.com/AssignedAccess/2017/config\"\n xmlns:default=\"http://schemas.microsoft.com/AssignedAccess/2017/config\"\n xmlns:rs5=\"http://schemas.microsoft.com/AssignedAccess/201810/config\"\n xmlns:v3=\"http://schemas.microsoft.com/AssignedAccess/2020/config\">\n <Profiles>\n <Profile Id=\"{9A2A490F-10F6-4764-974A-43B19E722C23}\">\n <AllAppsList>\n <AllowedApps>\n <App AppUserModelId=\"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App\" />\n <App AppUserModelId=\"Microsoft.Windows.Photos_8wekyb3d8bbwe!App\" />\n <App AppUserModelId=\"Microsoft.BingWeather_8wekyb3d8bbwe!App\" />\n <App DesktopAppPath=\"C:\\Windows\\system32\\cmd.exe\" />\n <App DesktopAppPath=\"%windir%\\System32\\WindowsPowerShell\\v1.0\\Powershell.exe\" />\n <App DesktopAppPath=\"%windir%\\explorer.exe\" />\n <App AppUserModelId=\"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\" />\n <App DesktopAppPath=\"%ProgramFiles(x86)%\\Microsoft\\Edge\\Application\\msedge.exe\" />\n </AllowedApps>\n </AllAppsList>\n <rs5:FileExplorerNamespaceRestrictions>\n <rs5:AllowedNamespace Name=\"Downloads\"/>\n <v3:AllowRemovableDrives/>\n </rs5:FileExplorerNamespaceRestrictions>\n <StartLayout>\n <![CDATA[\n <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\">\n <LayoutOptions StartTileGroupCellWidth=\"6\" />\n <DefaultLayoutOverride>\n <StartLayoutCollection>\n <defaultlayout:StartLayout GroupCellWidth=\"6\">\n <start:Group Name=\"\">\n <start:Tile Size=\"2x2\" Column=\"0\" Row=\"4\" AppUserModelID=\"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\" />\n <start:DesktopApplicationTile Size=\"2x2\" Column=\"2\" Row=\"4\" DesktopApplicationLinkPath=\"%ALLUSERSPROFILE%\\Microsoft\\Windows\\Start Menu\\Programs\\Microsoft Edge.lnk\" />\n <start:Tile Size=\"2x2\" Column=\"4\" Row=\"0\" AppUserModelID=\"Microsoft.BingWeather_8wekyb3d8bbwe!App\" />\n <start:DesktopApplicationTile Size=\"2x2\" Column=\"4\" Row=\"2\" DesktopApplicationLinkPath=\"%APPDATA%\\Microsoft\\Windows\\Start Menu\\Programs\\System Tools\\File Explorer.lnk\" />\n <start:DesktopApplicationTile Size=\"2x2\" Column=\"2\" Row=\"2\" DesktopApplicationLinkPath=\"%APPDATA%\\Microsoft\\Windows\\Start Menu\\Programs\\Windows PowerShell\\Windows PowerShell.lnk\" />\n <start:Tile Size=\"2x2\" Column=\"2\" Row=\"0\" AppUserModelID=\"Microsoft.Windows.Photos_8wekyb3d8bbwe!App\" />\n <start:Tile Size=\"2x2\" Column=\"0\" Row=\"0\" AppUserModelID=\"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App\" />\n <start:DesktopApplicationTile Size=\"2x2\" Column=\"0\" Row=\"2\" DesktopApplicationLinkPath=\"%APPDATA%\\Microsoft\\Windows\\Start Menu\\Programs\\System Tools\\Command Prompt.lnk\" />\n </start:Group>\n </defaultlayout:StartLayout>\n </StartLayoutCollection>\n </DefaultLayoutOverride>\n </LayoutModificationTemplate>\n ]]>\n </StartLayout>\n <Taskbar ShowTaskbar=\"true\"/>\n </Profile>\n </Profiles>\n <Configs>\n <Config>\n <AutoLogonAccount rs5:DisplayName=\"MS Learn Example\"/>\n <DefaultProfile Id=\"{9A2A490F-10F6-4764-974A-43B19E722C23}\"/>\n </Config>\n </Configs>\n</AssignedAccessConfiguration>" } ] }
|
||||
```
|
||||
|
||||
::: zone-end
|
||||
@ -22,7 +22,7 @@ Content-Type: application/json
|
||||
POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations
|
||||
Content-Type: application/json
|
||||
|
||||
{ "id": "00-0000-0000-0000-000000000000", "displayName": "_MSLearn_Example_Restricted_User_Experience - Assigned Access - Windows 11", "description": "This is a sample policy created from an article on learn.microsoft.com.", "roleScopeTagIds": [ "0" ], "@odata.type": "#microsoft.graph.windows10CustomConfiguration", "omaSettings": [ { "@odata.type": "#microsoft.graph.omaSettingString", "displayName": "AssignedAccess_Configuration", "description": null, "omaUri": "./Vendor/MSFT/AssignedAccess/Configuration", "secretReferenceValueId": null, "isEncrypted": true, "value": "<?xml version=\"1.0\" encoding=\"utf-8\" ?>\n<AssignedAccessConfiguration\n xmlns:xs=\"http://www.w3.org/2001/XMLSchema\"\n xmlns=\"http://schemas.microsoft.com/AssignedAccess/2017/config\"\n xmlns:default=\"http://schemas.microsoft.com/AssignedAccess/2017/config\"\n xmlns:rs5=\"http://schemas.microsoft.com/AssignedAccess/201810/config\"\n xmlns:v3=\"http://schemas.microsoft.com/AssignedAccess/2020/config\"\n xmlns:v5=\"http://schemas.microsoft.com/AssignedAccess/2022/config\">\n <Profiles>\n <Profile Id=\"{9A2A490F-10F6-4764-974A-43B19E722C23}\">\n <AllAppsList>\n <AllowedApps>\n <App AppUserModelId=\"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App\" />\n <App AppUserModelId=\"Microsoft.Windows.Photos_8wekyb3d8bbwe!App\" />\n <App AppUserModelId=\"Microsoft.BingWeather_8wekyb3d8bbwe!App\" />\n <App DesktopAppPath=\"C:\\Windows\\system32\\cmd.exe\" />\n <App DesktopAppPath=\"%windir%\\System32\\WindowsPowerShell\\v1.0\\Powershell.exe\" />\n <App DesktopAppPath=\"%windir%\\explorer.exe\" />\n <App AppUserModelId=\"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\" />\n <App AppUserModelId=\"%ProgramFiles(x86)%\\Microsoft\\Edge\\Application\\msedge.exe\" />\n </AllowedApps>\n </AllAppsList>\n <rs5:FileExplorerNamespaceRestrictions>\n <rs5:AllowedNamespace Name=\"Downloads\"/>\n <v3:AllowRemovableDrives/>\n </rs5:FileExplorerNamespaceRestrictions>\n <v5:StartPins>\n <![CDATA[{\n \"pinnedList\":[\n {\"packagedAppId\":\"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App\"},\n {\"packagedAppId\":\"Microsoft.Windows.Photos_8wekyb3d8bbwe!App\"},\n {\"packagedAppId\":\"Microsoft.BingWeather_8wekyb3d8bbwe!App\"},\n {\"desktopAppLink\":\"%APPDATA%\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\System Tools\\\\Command Prompt.lnk\"},\n {\"desktopAppLink\":\"%APPDATA%\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\Windows PowerShell\\\\Windows PowerShell.lnk\"},\n {\"desktopAppLink\":\"%APPDATA%\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\File Explorer.lnk\"},\n {\"packagedAppId\": \"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\"},\n {\"desktopAppLink\": \"%ALLUSERSPROFILE%\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\Microsoft Edge.lnk\"}\n ]\n }]]>\n </v5:StartPins>\n <Taskbar ShowTaskbar=\"true\"/>\n </Profile>\n </Profiles>\n <Configs>\n <Config>\n <AutoLogonAccount rs5:DisplayName=\"MS Learn Example\"/>\n <DefaultProfile Id=\"{9A2A490F-10F6-4764-974A-43B19E722C23}\"/>\n </Config>\n </Configs>\n</AssignedAccessConfiguration>" } ] }
|
||||
{ "id": "00-0000-0000-0000-000000000000", "displayName": "_MSLearn_Example_Restricted_User_Experience - Assigned Access - Windows 11", "description": "This is a sample policy created from an article on learn.microsoft.com.", "roleScopeTagIds": [ "0" ], "@odata.type": "#microsoft.graph.windows10CustomConfiguration", "omaSettings": [ { "@odata.type": "#microsoft.graph.omaSettingString", "displayName": "AssignedAccess_Configuration", "description": null, "omaUri": "./Vendor/MSFT/AssignedAccess/Configuration", "secretReferenceValueId": null, "isEncrypted": true, "value": "<?xml version=\"1.0\" encoding=\"utf-8\" ?>\n<AssignedAccessConfiguration\n xmlns:xs=\"http://www.w3.org/2001/XMLSchema\"\n xmlns=\"http://schemas.microsoft.com/AssignedAccess/2017/config\"\n xmlns:default=\"http://schemas.microsoft.com/AssignedAccess/2017/config\"\n xmlns:rs5=\"http://schemas.microsoft.com/AssignedAccess/201810/config\"\n xmlns:v3=\"http://schemas.microsoft.com/AssignedAccess/2020/config\"\n xmlns:v5=\"http://schemas.microsoft.com/AssignedAccess/2022/config\">\n <Profiles>\n <Profile Id=\"{9A2A490F-10F6-4764-974A-43B19E722C23}\">\n <AllAppsList>\n <AllowedApps>\n <App AppUserModelId=\"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App\" />\n <App AppUserModelId=\"Microsoft.Windows.Photos_8wekyb3d8bbwe!App\" />\n <App AppUserModelId=\"Microsoft.BingWeather_8wekyb3d8bbwe!App\" />\n <App DesktopAppPath=\"C:\\Windows\\system32\\cmd.exe\" />\n <App DesktopAppPath=\"%windir%\\System32\\WindowsPowerShell\\v1.0\\Powershell.exe\" />\n <App DesktopAppPath=\"%windir%\\explorer.exe\" />\n <App AppUserModelId=\"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\" />\n <App DesktopAppPath=\"%ProgramFiles(x86)%\\Microsoft\\Edge\\Application\\msedge.exe\" />\n </AllowedApps>\n </AllAppsList>\n <rs5:FileExplorerNamespaceRestrictions>\n <rs5:AllowedNamespace Name=\"Downloads\"/>\n <v3:AllowRemovableDrives/>\n </rs5:FileExplorerNamespaceRestrictions>\n <v5:StartPins>\n <![CDATA[{\n \"pinnedList\":[\n {\"packagedAppId\":\"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App\"},\n {\"packagedAppId\":\"Microsoft.Windows.Photos_8wekyb3d8bbwe!App\"},\n {\"packagedAppId\":\"Microsoft.BingWeather_8wekyb3d8bbwe!App\"},\n {\"desktopAppLink\":\"%APPDATA%\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\System Tools\\\\Command Prompt.lnk\"},\n {\"desktopAppLink\":\"%APPDATA%\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\Windows PowerShell\\\\Windows PowerShell.lnk\"},\n {\"desktopAppLink\":\"%APPDATA%\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\File Explorer.lnk\"},\n {\"packagedAppId\": \"windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\"},\n {\"desktopAppLink\": \"%ALLUSERSPROFILE%\\\\Microsoft\\\\Windows\\\\Start Menu\\\\Programs\\\\Microsoft Edge.lnk\"}\n ]\n }]]>\n </v5:StartPins>\n <Taskbar ShowTaskbar=\"true\"/>\n </Profile>\n </Profiles>\n <Configs>\n <Config>\n <AutoLogonAccount rs5:DisplayName=\"MS Learn Example\"/>\n <DefaultProfile Id=\"{9A2A490F-10F6-4764-974A-43B19E722C23}\"/>\n </Config>\n </Configs>\n</AssignedAccessConfiguration>" } ] }
|
||||
```
|
||||
|
||||
::: zone-end
|
||||
@ -22,7 +22,7 @@ $assignedAccessConfiguration = @"
|
||||
<App DesktopAppPath="%windir%\System32\WindowsPowerShell\v1.0\Powershell.exe" />
|
||||
<App DesktopAppPath="%windir%\explorer.exe" />
|
||||
<App AppUserModelId="windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" />
|
||||
<App AppUserModelId="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<rs5:FileExplorerNamespaceRestrictions>
|
||||
@ -88,7 +88,7 @@ $assignedAccessConfiguration = @"
|
||||
<App DesktopAppPath="%windir%\System32\WindowsPowerShell\v1.0\Powershell.exe" />
|
||||
<App DesktopAppPath="%windir%\explorer.exe" />
|
||||
<App AppUserModelId="windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" />
|
||||
<App AppUserModelId="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<rs5:FileExplorerNamespaceRestrictions>
|
||||
|
||||
@ -21,7 +21,7 @@ ms.topic: include
|
||||
<App DesktopAppPath="%windir%\System32\WindowsPowerShell\v1.0\Powershell.exe" />
|
||||
<App DesktopAppPath="%windir%\explorer.exe" />
|
||||
<App AppUserModelId="windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" />
|
||||
<App AppUserModelId="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<rs5:FileExplorerNamespaceRestrictions>
|
||||
@ -79,7 +79,7 @@ ms.topic: include
|
||||
<App DesktopAppPath="%windir%\System32\WindowsPowerShell\v1.0\Powershell.exe" />
|
||||
<App DesktopAppPath="%windir%\explorer.exe" />
|
||||
<App AppUserModelId="windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" />
|
||||
<App AppUserModelId="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" />
|
||||
</AllowedApps>
|
||||
</AllAppsList>
|
||||
<rs5:FileExplorerNamespaceRestrictions>
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Assigned Access policy settings
|
||||
description: Learn about the policy settings enforced on a device configured with Assigned Access.
|
||||
ms.topic: reference
|
||||
ms.date: 10/31/2024
|
||||
ms.date: 02/25/2025
|
||||
---
|
||||
|
||||
# Assigned Access policy settings
|
||||
@ -20,6 +20,7 @@ The following policy settings are applied at the device level when you deploy a
|
||||
|
||||
| Type | Path | Name/Description |
|
||||
|---------|----------------------------------------------------------------------------|---------------------------------------------------------------------------|
|
||||
| **CSP** | `./Vendor/MSFT/Policy/Config/Settings/AllowOnlineTips` | Allow Online Tips |
|
||||
| **CSP** | `./Vendor/MSFT/Policy/Config/Experience/AllowCortana` | Disable Cortana |
|
||||
| **CSP** | `./Vendor/MSFT/Policy/Config/Start/AllowPinnedFolderDocuments` | Disable Start documents icon |
|
||||
| **CSP** | `./Vendor/MSFT/Policy/Config/Start/AllowPinnedFolderDownloads` | Disable Start downloads icon |
|
||||
@ -45,8 +46,9 @@ The following policy settings are applied to targeted user accounts when you dep
|
||||
|---------|----------------------------------------------------------------------------------|-------------------------------------------------------------------|
|
||||
| **CSP** | `./User/Vendor/MSFT/Policy/Config/Start/DisableContextMenus` | Disable Context Menu for Start menu apps |
|
||||
| **CSP** | `./User/Vendor/MSFT/Policy/Config/Start/HidePeopleBar` | Hide People Bar from appearing on taskbar |
|
||||
| **CSP** | `./User/Vendor/MSFT/Policy/Config/Start/HideRecentlyAddedApps` | Hide recently added apps from appearing on the Start menu |
|
||||
| **CSP** | `./User/Vendor/MSFT/Policy/Config/Start/HideRecentJumplists` | Hide recent jumplists from appearing on the Start menu/taskbar |
|
||||
| **CSP** | `./User/Vendor/MSFT/Policy/Config/Start/HideRecentlyAddedApps` | Hide recently added apps from appearing on the Start menu |
|
||||
| **CSP** | User Configuration\Administrative Templates\Windows Components\Windows Copilot | Turn off Windows Copilot |
|
||||
| **GPO** | User Configuration\Administrative Templates\Desktop | Hide and disable all items on the desktop |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Clear history of recently opened documents on exit |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Disable showing balloon notifications as toasts |
|
||||
@ -54,7 +56,7 @@ The following policy settings are applied to targeted user accounts when you dep
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Do not allow pinning programs to the Taskbar |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Do not display or track items in Jump Lists from remote locations |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Hide and disable all items on the desktop |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Hide the Task View button |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Hide the TaskView button |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Lock all taskbar settings |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Lock the Taskbar |
|
||||
| **GPO** | User Configuration\Administrative Templates\Start Menu and Taskbar | Prevent users from adding or removing toolbars |
|
||||
@ -81,6 +83,7 @@ The following policy settings are applied to targeted user accounts when you dep
|
||||
| **GPO** | User Configuration\Administrative Templates\Windows Components\File Explorer | Remove *Map network drive* and *Disconnect Network Drive* |
|
||||
| **GPO** | User Configuration\Administrative Templates\Windows Components\File Explorer | Remove File Explorer's default context menu |
|
||||
| **GPO** | User Configuration\Administrative Templates\Windows Components\Windows Copilot | Turn off Windows Copilot |
|
||||
| **GPO** | User Configuration\Administrative Templates\WindowsComponents\File Explorer | Prevent access to drives from My Computer |
|
||||
|
||||
The following policy settings are applied to the kiosk account when you configure a kiosk experience with Microsoft Edge:
|
||||
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
---
|
||||
title: WEDL\_AssignedAccess
|
||||
description: WEDL\_AssignedAccess
|
||||
ms.date: 05/20/2024
|
||||
title: WEDL_AssignedAccess
|
||||
description: WEDL_AssignedAccess
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
# WEDL\_AssignedAccess
|
||||
# WEDL_AssignedAccess
|
||||
|
||||
This Windows Management Instrumentation (WMI) provider class configures settings for assigned access.
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/assigned-access.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -129,13 +131,3 @@ if ($AssignedAccessConfig) {
|
||||
"Could not set up assigned access account."
|
||||
}
|
||||
```
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting
|
||||
description: WESL_UserSetting
|
||||
ms.date: 05/02/2017
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -9,6 +9,8 @@ ms.topic: reference
|
||||
|
||||
This class configures which application Shell Launcher starts based on the security identifier (SID) of the signed in user, and also configures the set of return codes and return actions that Shell Launcher performs when the application exits.
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/shell-launcher.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -158,17 +160,3 @@ $ShellLauncherClass.RemoveCustomShell($Admins_SID)
|
||||
|
||||
$ShellLauncherClass.RemoveCustomShell($Cashier_SID)
|
||||
```
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Shell Launcher](index.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.GetCustomShell
|
||||
description: WESL_UserSetting.GetCustomShell
|
||||
ms.date: 05/20/2024
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -9,6 +9,8 @@ ms.topic: reference
|
||||
|
||||
This method retrieves the Shell Launcher configuration for a specific user or group, based on the security identifier (SID).
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/shell-launcher.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -60,18 +62,3 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
|
||||
Shell Launcher uses the *CustomReturnCodes* and *CustomReturnCodesAction* arrays to determine the system behavior when the shell application exits, based on the return value of the application.
|
||||
|
||||
If the return value does not exist in *CustomReturnCodes*, or if the corresponding action defined in *CustomReturnCodesAction* is not a valid value, Shell Launcher uses *DefaultAction* to determine system behavior. If *DefaultAction* is not defined, or is not a valid value, Shell Launcher restarts the shell application.
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [WESL_UserSetting](wesl-usersetting.md)
|
||||
- [Shell Launcher](index.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.GetDefaultShell
|
||||
description: WESL_UserSetting.GetDefaultShell
|
||||
ms.date: 05/20/2024
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -9,6 +9,8 @@ ms.topic: reference
|
||||
|
||||
This method retrieves the default Shell Launcher configuration.
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/shell-launcher.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -40,18 +42,3 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
|
||||
## Remarks
|
||||
|
||||
Shell Launcher uses the default configuration when the security identifier (SID) of the user who is currently signed in does not match any custom defined Shell Launcher configurations.
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [WESL_UserSetting](wesl-usersetting.md)
|
||||
- [Shell Launcher](index.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.IsEnabled
|
||||
description: WESL_UserSetting.IsEnabled
|
||||
ms.date: 05/20/2024
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -9,6 +9,8 @@ ms.topic: reference
|
||||
|
||||
This method retrieves a value that indicates if Shell Launcher is enabled or disabled.
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/shell-launcher.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -24,18 +26,3 @@ This method retrieves a value that indicates if Shell Launcher is enabled or dis
|
||||
## Return Value
|
||||
|
||||
Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-non-error-constants) or a [WMI error](/windows/win32/wmisdk/wmi-error-constants).
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [WESL_UserSetting](wesl-usersetting.md)
|
||||
- [Shell Launcher](index.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.RemoveCustomShell
|
||||
description: WESL_UserSetting.RemoveCustomShell
|
||||
ms.date: 05/20/2024
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -9,6 +9,8 @@ ms.topic: reference
|
||||
|
||||
This method removes a Shell Launcher configuration for a specific user or group, based on the security identifier (SID).
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/shell-launcher.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -28,18 +30,3 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
|
||||
## Remarks
|
||||
|
||||
You must restart your device for the changes to take effect.
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [WESL_UserSetting](wesl-usersetting.md)
|
||||
- [Shell Launcher](index.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetCustomShell
|
||||
description: WESL_UserSetting.SetCustomShell
|
||||
ms.date: 05/20/2024
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -9,6 +9,8 @@ ms.topic: reference
|
||||
|
||||
This method configures Shell Launcher for a specific user or group, based on the security identifier (SID).
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/shell-launcher.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -60,18 +62,3 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
|
||||
Shell Launcher uses the *CustomReturnCodes* and *CustomReturnCodesAction* arrays to determine the system behavior when the shell application exits, based on the return value of the shell application.
|
||||
|
||||
If the return value does not exist in *CustomReturnCodes*, or if the corresponding action defined in *CustomReturnCodesAction* is not a valid value, Shell Launcher uses *DefaultAction* to determine system behavior. If *DefaultAction* is not defined, or is not a valid value, Shell Launcher restarts the shell application.
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [WESL_UserSetting](wesl-usersetting.md)
|
||||
- [Shell Launcher](index.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetDefaultShell
|
||||
description: WESL_UserSetting.SetDefaultShell
|
||||
ms.date: 05/20/2024
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -9,6 +9,8 @@ ms.topic: reference
|
||||
|
||||
This method sets the default Shell Launcher configuration.
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/shell-launcher.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -40,18 +42,3 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
|
||||
## Remarks
|
||||
|
||||
Shell Launcher uses the default configuration when the security identifier (SID) of the user who is currently signed in does not match any custom defined Shell Launcher configurations.
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [WESL_UserSetting](wesl-usersetting.md)
|
||||
- [Shell Launcher](index.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WESL_UserSetting.SetEnabled
|
||||
description: WESL_UserSetting.SetEnabled
|
||||
ms.date: 05/20/2024
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: reference
|
||||
---
|
||||
|
||||
@ -9,6 +9,8 @@ ms.topic: reference
|
||||
|
||||
This method enables or disables Shell Launcher.
|
||||
|
||||
[!INCLUDE [shell-launcher](../../../includes/licensing/shell-launcher.md)]
|
||||
|
||||
## Syntax
|
||||
|
||||
```powershell
|
||||
@ -30,18 +32,3 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
|
||||
This method enables or disables Shell Launcher by modifying the **Shell** value in the registry key `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon`. If Unified Write Filter (UWF) is enabled, you may need to disable UWF or commit this registry key by using [UWF_RegistryFilter.CommitRegistry](../unified-write-filter/uwf-registryfiltercommitregistry.md) in order to enable or disable Shell Launcher.
|
||||
|
||||
Enabling or disabling Shell Launcher does not take effect until a user signs in.
|
||||
|
||||
## Requirements
|
||||
|
||||
| Windows Edition | Supported |
|
||||
|:-----------------------|:---------:|
|
||||
| Windows Home | No |
|
||||
| Windows Pro | No |
|
||||
| Windows Enterprise | Yes |
|
||||
| Windows Education | Yes |
|
||||
| Windows IoT Enterprise | Yes |
|
||||
|
||||
## Related topics
|
||||
|
||||
- [WESL_UserSetting](wesl-usersetting.md)
|
||||
- [Shell Launcher](index.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 04/10/2024
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
@ -9,14 +9,8 @@ ms.topic: include
|
||||
|
||||
With this policy setting, you can prevent the Start menu from displaying a list of recently installed applications:
|
||||
|
||||
- If **enabled**, the Start menu doesn't display the **Recently added** list. The corresponding option in Settings can't be configured (grayed out).
|
||||
- If **disabled** or **not configured**, the Start menu displays the **Recently added** list. The corresponding option in Settings can be configured.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Starting in Windows 11, version 22H2 with [KB5048685](https://support.microsoft.com/topic/4602-ea3736d3-6948-4fd7-9faf-8d732ac2ed59), the policy setting behavior changed.
|
||||
>
|
||||
> - If **enabled**, the corresponding option in Settings can't be configured (grayed out). The policy setting doesn't affect the display of recently installed applications in the Recommended section of the Start menu.
|
||||
> - If **disabled** or **not configured**, the corresponding option in Settings can be configured.
|
||||
- If **enabled**, the Start menu doesn't display the **Recently added** list. The corresponding option in Settings can't be configured (grayed out)
|
||||
- If **disabled** or **not configured**, the Start menu displays the **Recently added** list. The corresponding option in Settings can be configured
|
||||
|
||||
| | Path |
|
||||
|--|--|
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Start policy settings
|
||||
description: Learn about the policy settings to configure the Windows Start menu.
|
||||
ms.topic: reference
|
||||
ms.date: 07/10/2024
|
||||
ms.date: 02/25/2025
|
||||
appliesto:
|
||||
zone_pivot_groups: windows-versions-11-10
|
||||
---
|
||||
|
||||
@ -0,0 +1,23 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
### Show notification bell icon
|
||||
|
||||
This policy setting allows you to show the notification bell icon in the system tray:
|
||||
|
||||
- If you enable this policy setting, the notification icon is always displayed
|
||||
- If you disable or don't configure this policy setting, the notification icon is only displayed when there's a special status (for example, when *do not disturb* is turned on)
|
||||
|
||||
> [!NOTE]
|
||||
> A reboot is required for this policy setting to take effect.
|
||||
|
||||
| | Path |
|
||||
|--|--|
|
||||
| **CSP** |- `./User/Vendor/MSFT/Policy/Config/Start/`[AlwaysShowNotificationIcon](/windows/client-management/mdm/policy-csp-start#AlwaysShowNotificationIcon) |
|
||||
| **GPO** |- **User Configuration** > **Administrative Templates** > **Start Menu and Taskbar** |
|
||||
|
||||
<!-- not linked yet as it's in Insider>
|
||||
@ -0,0 +1,22 @@
|
||||
---
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
ms.date: 02/25/2025
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
### Turn off abbreviated time and date format
|
||||
|
||||
This policy setting allows you to show the longer time and date format in the system tray:
|
||||
|
||||
- If you enable this policy setting, the time format will include the AM/PM time marker and the date will include the year.
|
||||
|
||||
> [!NOTE]
|
||||
> A reboot is required for this policy setting to take effect.
|
||||
|
||||
| | Path |
|
||||
|--|--|
|
||||
| **CSP** |- `./User/Vendor/MSFT/Policy/Config/Start/`[TurnOffAbbreviatedDateTimeFormat](/windows/client-management/mdm/policy-csp-start#TurnOffAbbreviatedDateTimeFormat) |
|
||||
| **GPO** |- **User Configuration** > **Administrative Templates** > **Start Menu and Taskbar** |
|
||||
|
||||
<!-- not linked yet as it's in Insider>
|
||||
@ -7,7 +7,7 @@ ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
author: frankroj
|
||||
ms.topic: install-set-up-deploy
|
||||
ms.date: 02/13/2024
|
||||
ms.date: 02/27/2025
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -16,7 +16,7 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 07/23/2024
|
||||
ms.date: 02/27/2025
|
||||
---
|
||||
|
||||
# Configure Delivery Optimization (DO) for Windows
|
||||
@ -232,7 +232,12 @@ Delivery Optimization is integrated with both Microsoft Endpoint Manager and Con
|
||||
|
||||
## Monitor Delivery Optimization
|
||||
|
||||
Whether you opt for the default Delivery Optimization configurations or tailor them to suit your environment, you'll want to track the outcomes to see how they improve your efficiency. [Learn more](waas-delivery-optimization-monitor.md) about the monitoring options for Delivery Optimization.
|
||||
Whether you opt for the default Delivery Optimization configurations or tailor them to suit your environment, you'll want to track the outcomes to see how they improve your efficiency. The following options are available to monitor Delivery Optimization:
|
||||
|
||||
- On clients, review the activity monitor, which displays a breakdown of downloads by source, average speed, and upload stats for the current month
|
||||
- **Windows 11**: Settings > Windows Update > Advanced Options > Delivery Optimization > Activity Monitor
|
||||
- **Windows 10**: Settings > Update & Security > Delivery Optimization > Activity Monitor
|
||||
- Windows Update for Business reports offers a Delivery Optimization report. For more information, see [Monitor Delivery Optimization](waas-delivery-optimization-monitor.md).
|
||||
|
||||
## Troubleshoot Delivery Optimization
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
ms.date: 10/30/2024
|
||||
ms.date: 02/28/2025
|
||||
---
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education Overview
|
||||
@ -57,7 +57,7 @@ Customers may have office spaces, data centers, or Azure deployments that meet s
|
||||
- Have Azure VMs and/or Azure Virtual Desktop deployed
|
||||
- Have limited internet bandwidth (T1 or T3 lines)
|
||||
|
||||
To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 or Ubuntu 22.04.
|
||||
To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 (or later) or Ubuntu 24.04.
|
||||
|
||||
See [Connected Cache node host machine requirements](mcc-ent-prerequisites.md) for recommended host machine specifications in each configuration.
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ manager: naengler
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
ms.date: 10/30/2024
|
||||
ms.date: 02/28/2025
|
||||
---
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education Requirements
|
||||
@ -43,7 +43,7 @@ This article details the requirements and recommended specifications for using M
|
||||
|
||||
### Additional requirements for Windows host machines
|
||||
|
||||
- The Windows host machine must be using Windows 11 or Windows Server 2022 with the latest cumulative update applied.
|
||||
- The Windows host machine must be using Windows 11 or Windows Server 2022 (or later) with the latest cumulative update applied.
|
||||
- Windows 11 must have [OS Build 22631.3296](https://support.microsoft.com/topic/march-12-2024-kb5035853-os-builds-22621-3296-and-22631-3296-a69ac07f-e893-4d16-bbe1-554b7d9dd39b) or later
|
||||
- Windows Server 2022 must have [OS Build 20348.2227](https://support.microsoft.com/topic/january-9-2024-kb5034129-os-build-20348-2227-6958a36f-efaf-4ef5-a576-c5931072a89a) or later
|
||||
- The Windows host machine must support nested virtualization. Ensure that any security settings that may restrict nested virtualization are not enabled, such as ["Trusted launch" in Azure VMs](/azure/virtual-machines/trusted-launch-portal).
|
||||
@ -52,7 +52,7 @@ This article details the requirements and recommended specifications for using M
|
||||
### Additional requirements for Linux host machines
|
||||
|
||||
- The Linux host machine must be using one of the following operating systems:
|
||||
- Ubuntu 22.04
|
||||
- Ubuntu 24.04
|
||||
- Red Hat Enterprise Linux (RHEL) 8.* or 9.*
|
||||
- If using RHEL, the default container engine (Podman) must be replaced with [Moby](https://github.com/moby/moby#readme)
|
||||
|
||||
|
||||
@ -11,18 +11,49 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ Supported Linux distributions
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
ms.date: 10/30/2024
|
||||
ms.date: 02/28/2025
|
||||
---
|
||||
|
||||
# Release Notes for Microsoft Connected Cache for Enterprise and Education
|
||||
|
||||
This article contains details about the latest releases of Connected Cache. Since Connected Cache is a preview service, some releases may contain breaking changes.
|
||||
|
||||
## Install script v2.0.0.2
|
||||
## February 2025 Release
|
||||
|
||||
Released on **3/03/2025**
|
||||
|
||||
This release contains improvements that can only be applied by redeploying your cache nodes using the updated installation script.
|
||||
|
||||
### New Connected Cache container version
|
||||
|
||||
- v1.2.1.2083_E
|
||||
|
||||
### New Linux-hosted installation script version
|
||||
|
||||
- v1.08
|
||||
|
||||
### New Windows-hosted installation script version
|
||||
|
||||
- v2.0.0.3
|
||||
|
||||
### Improvements to Windows-hosted cache nodes
|
||||
|
||||
- **Connected Cache WSL distribution now uses Ubuntu 24.04**: The Windows Subsystem for Linux (WSL) distribution used by Connected Cache has been updated to Ubuntu 24.04 (was 22.04). This change ensures that the WSL distribution is up-to-date with the latest security patches and features.
|
||||
- **Connected Cache container now uses Ubuntu 24.04 Docker environment**: The Connected Cache container now runs using an Ubuntu 24.04 Docker environment (was 22.04). This change ensures that the container environment is up-to-date with the latest security patches and features.
|
||||
- **TLS-inspecting proxies no longer cause IoT Edge error during Connected Cache installation**: Fixed a bug that was causing proxy certificate path string to be improperly handled, leading to IoT Edge errors during Connected Cache installation.
|
||||
- **Security improvements**: Kept intentionally vague to protect previous versions of Connected Cache.
|
||||
|
||||
### Improvements to Linux-hosted cache nodes
|
||||
|
||||
- **Connected Cache container now uses Ubuntu 24.04 Docker environment**: The Connected Cache container now runs using an Ubuntu 24.04 Docker environment (was 22.04). This change ensures that the container environment is up-to-date with the latest security patches and features.
|
||||
- **TLS-inspecting proxies no longer cause IoT Edge error during Connected Cache installation**: Fixed a bug that was causing proxy certificate path string to be improperly handled, leading to IoT Edge errors during Connected Cache installation.
|
||||
- **Security improvements**: Kept intentionally vague to protect previous versions of Connected Cache.
|
||||
|
||||
## Windows-hosted install script v2.0.0.2
|
||||
|
||||
Released on **2/7/2025**
|
||||
|
||||
These changes only affect the installation scripts for Connected Cache. To take advantage of these changes, you'll need to redeploy your existing cache nodes using the updated installation script.
|
||||
This release only contains changes to the Windows-hosted installation scripts for Connected Cache. To take advantage of these changes, you need to redeploy your existing cache nodes using the updated installation script.
|
||||
|
||||
### Improvements
|
||||
|
||||
@ -31,11 +62,15 @@ These changes only affect the installation scripts for Connected Cache. To take
|
||||
- **Changes install error codes from decimal to hex code**: Install error codes for Windows-hosted cache nodes are now displayed in hex code format, improving error code readability.
|
||||
- **Uses configured proxy to perform install**: If a proxy was configured for the Windows-hosted cache node in Azure portal, the cache node uses the specified proxy during installation.
|
||||
|
||||
## Release v1.2.1.2076_E (public preview launch)
|
||||
## Public Preview Release
|
||||
|
||||
The public preview released on **10/30/2024**
|
||||
Released on **10/30/2024**
|
||||
|
||||
For customers that installed earlier versions of Connected Cache, this release contains breaking changes that affect both Linux and Windows host machines. See the [early preview documentation page](mcc-ent-early-preview.md) for more details.
|
||||
For customers that installed earlier versions of Connected Cache, this release contains breaking changes that affect both Linux-hosted and Windows-hosted cache nodes. See the [early preview documentation page](mcc-ent-early-preview.md) for more details.
|
||||
|
||||
### New Connected Cache container version
|
||||
|
||||
- v1.2.1.2076_E
|
||||
|
||||
### Feature updates
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ Supported Linux distributions
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>
|
||||
ms.date: 01/15/2025
|
||||
ms.date: 02/28/2025
|
||||
---
|
||||
|
||||
|
||||
@ -97,7 +97,7 @@ If the Connected Cache installation is failing due to WSL-related issues, try ru
|
||||
Once the Connected Cache software has been successfully deployed to the Windows host machine, you can check if the cache node is running properly by doing the following on the Windows host machine:
|
||||
|
||||
1. Launch a PowerShell process as the account specified as the runtime account during the Connected Cache install
|
||||
1. Run `wsl -d Ubuntu-22.04-Mcc-Base` to access the Linux distribution that hosts the Connected Cache container
|
||||
1. Run `wsl -d Ubuntu-24.04-Mcc-Base` to access the Linux distribution that hosts the Connected Cache container
|
||||
1. Run `sudo iotedge list` to show which containers are running within the IoT Edge runtime
|
||||
|
||||
If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs -- -f`.
|
||||
|
||||
@ -17,7 +17,7 @@ metadata:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/en-us/windows/release-health/windows-server-release-info target=_blank>Windows Server 2019, and later</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 10/15/2024
|
||||
ms.date: 02/27/2025
|
||||
title: Frequently Asked Questions about Delivery Optimization
|
||||
summary: |
|
||||
This article answers frequently asked questions about Delivery Optimization.
|
||||
@ -50,7 +50,7 @@ summary: |
|
||||
|
||||
**Device resources questions**:
|
||||
- [Delivery Optimization is using device resources and I can't tell why?](#delivery-optimization-is-using-device-resources-and-i-can-t-tell-why)
|
||||
|
||||
- [How do I clear the Delivery Optimization cache?](#how-do-i-clear-the-delivery-optimization-cache)
|
||||
sections:
|
||||
- name: General questions
|
||||
questions:
|
||||
@ -179,3 +179,10 @@ sections:
|
||||
- question: Delivery Optimization is using device resources and I can't tell why?
|
||||
answer: |
|
||||
Delivery Optimization is used by most content providers from Microsoft. A complete list can be found [here](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization). Often customers may not realize the vast application of Delivery Optimization and how it's used across different apps. Content providers have the option to run downloads in the foreground or background. It's good to check any apps running in the background to see what is running. Also note that depending on the app, closing the app may not necessarily stop the download.
|
||||
- question: How do I clear the Delivery Optimization cache?
|
||||
answer: |
|
||||
Delivery Optimization in Windows clears its cache automatically. Files are removed from the cache after a short time period or when its contents take up too much disk space. However, if you need more disk space on your PC, you can manually clear the cache.
|
||||
1. In the search box on the taskbar, type **Disk Cleanup**, and then select it from the list of results.
|
||||
1. On the **Disk Cleanup** tab, select the **Delivery Optimization Files** check box.
|
||||
1. Select **OK**. On the dialog that appears, select **Delete Files**.
|
||||
|
||||
|
||||
@ -47,6 +47,9 @@ The following table lists the minimum Windows 10 version that supports Delivery
|
||||
|
||||
#### Windows Client
|
||||
|
||||
> [!NOTE]
|
||||
> Starting March 4, 2025, Edge Browser updates will temporarily not utilize Delivery Optimization for downloads. We are actively working to resolve this issue.
|
||||
|
||||
| Windows Client | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache |
|
||||
|------------------|---------------|----------------|----------|----------------|
|
||||
| Windows Update ([feature updates quality updates, language packs, drivers](../update/get-started-updates-channels-tools.md#types-of-updates)) | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
@ -55,7 +58,7 @@ The following table lists the minimum Windows 10 version that supports Delivery
|
||||
| Windows Defender definition updates | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Intune Win32 apps| Windows 10 1709, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Microsoft 365 Apps and updates | Windows 10 1709, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Edge Browser Updates | Windows 10 1809, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Edge Browser Updates | Windows 10 1809, Windows 11 | | | |
|
||||
| Configuration Manager Express updates| Windows 10 1709 + Configuration Manager version 1711, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Dynamic updates| Windows 10 1903, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| MDM Agent | Windows 11 | :heavy_check_mark: | | |
|
||||
|
||||
@ -3,7 +3,7 @@ title: Checkpoint cumulative updates and the Microsoft Update Catalog
|
||||
description: This article describes how to handle checkpoint cumulative updates when you use the Microsoft Update Catalog to update devices and images.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Evaluate infrastructure and tools
|
||||
description: Review the steps to ensure your infrastructure is ready to deploy updates to clients in your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Windows client updates, channels, and tools
|
||||
description: Brief summary of the kinds of Windows updates, the channels they're served through, and the tools for managing them
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: How Windows Update works
|
||||
description: In this article, learn about the process Windows Update uses to download and install updates on Windows client devices.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Migrating and acquiring optional Windows content
|
||||
description: How to keep language resources and Features on Demand during operating system updates for your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Define readiness criteria
|
||||
description: Identify important roles and figure out how to classify apps so you can plan and manage your deployment
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Define update strategy
|
||||
description: Example of using a calendar-based approach to achieve consistent update installation in your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Update release cycle for Windows clients
|
||||
description: Learn about the release cycle for updates so Windows clients in your organization stay productive and protected.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Safeguard holds for Windows
|
||||
description: What are safeguard holds? How to can you tell if a safeguard hold is in effect, and what to do about it.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Opt out of safeguard holds
|
||||
description: How to install an update in your organization even when a safeguard hold for a known issue has been applied to it.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Servicing stack updates
|
||||
description: In this article, learn how servicing stack updates improve the code that installs the other updates.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Windows 10 Update Baseline
|
||||
description: Use an update baseline to optimize user experience and meet monthly update goals in your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -3,7 +3,7 @@ title: Policies for update compliance and user experience
|
||||
description: Explanation and recommendations for update compliance, activity, and user experience for your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
@ -94,7 +94,7 @@ options must be **Disabled** in order to take advantage of intelligent active ho
|
||||
If you do set active hours, we recommend setting the following policies to **Disabled** in order to increase update
|
||||
velocity:
|
||||
|
||||
- [Delay automatic reboot](waas-restart.md#delay-automatic-restart). While it's possible to set the system to delay restarts for users who are logged in, this setting might delay an update indefinitely if a user is always either logged in or shut down. Instead, we recommend setting the following polices to **Disabled**:
|
||||
- [Delay automatic reboot](waas-restart.md#delay-automatic-restart). While it's possible to set the system to delay restarts for users who are logged in, this setting might delay an update indefinitely if a user is always either logged in or shut down. Instead, we recommend setting the following policies to **Disabled**:
|
||||
- **Turn off auto-restart during active hours**
|
||||
- **No auto-restart with logged on users for scheduled automatic updates**
|
||||
|
||||
@ -183,7 +183,7 @@ As administrators, you have set up and expect certain behaviors, so we expressly
|
||||
> expected. For example, if a device is not reacting to your MDM policy changes, check to see if a similar
|
||||
> policy is set in Group Policy with a differing value.
|
||||
> If you find that update velocity is not as high as you expect or if some devices are slower than others, it might be
|
||||
> time to clear all polices and settings and specify only the recommended update policies. See the Policy and settings reference for a consolidated list of recommended polices.
|
||||
> time to clear all policies and settings and specify only the recommended update policies. See the Policy and settings reference for a consolidated list of recommended policies.
|
||||
|
||||
The following are policies that you might want to disable because they could decrease update velocity or there are better policies to use that might conflict:
|
||||
- **Defer Feature Updates Period in Days**. For maximum update velocity, it's best to set this to **0** (no
|
||||
|
||||
@ -3,7 +3,7 @@ title: Configure BranchCache for Windows client updates
|
||||
description: In this article, learn how to use BranchCache to optimize network bandwidth during update deployment.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -6,7 +6,7 @@ ms.service: windows-client
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-updates
|
||||
ms.collection:
|
||||
- tier1
|
||||
|
||||
@ -3,7 +3,7 @@ title: Quick guide to Windows as a service
|
||||
description: In Windows 10, Microsoft has streamlined servicing to make operating system updates simpler to test, manage, and deploy.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -4,7 +4,7 @@ manager: aaroncz
|
||||
description: Overview of the security for Windows Update including security for the metadata exchange and content download.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
appliesto:
|
||||
|
||||
@ -4,7 +4,7 @@ titleSuffix: Windows Update client policies
|
||||
description: This article contains information on how to enforce compliance deadlines using Windows Update client policies.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mstewart
|
||||
|
||||
@ -5,7 +5,7 @@ manager: aaroncz
|
||||
description: Microsoft admin center populates Windows Update for Business reports data into the software updates page.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -4,7 +4,7 @@ titleSuffix: Windows Update for Business reports
|
||||
description: How to get and use the Windows Update for Business reports configuration script to configure devices for Windows Update for Business reports.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -4,7 +4,7 @@ titleSuffix: Windows Update for Business reports
|
||||
description: This article provides information about Delivery Optimization data in Windows Update for Business reports.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -4,7 +4,7 @@ titleSuffix: Windows Update for Business reports
|
||||
description: List of prerequisites for enabling and using Windows Update for Business reports in your organization.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: article
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
|
||||
@ -6,7 +6,7 @@ ms.author: frankroj
|
||||
manager: aaroncz
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 02/13/2024
|
||||
ms.date: 02/27/2025
|
||||
ms.topic: article
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
|
||||
@ -116,8 +116,6 @@
|
||||
href: monitor/windows-autopatch-windows-quality-update-status-report.md
|
||||
- name: Quality update trending report
|
||||
href: monitor/windows-autopatch-windows-quality-update-trending-report.md
|
||||
- name: Reliability report
|
||||
href: monitor/windows-autopatch-reliability-report.md
|
||||
- name: Hotpatch quality update report
|
||||
href: monitor/windows-autopatch-hotpatch-quality-update-report.md
|
||||
- name: Windows feature and quality update device alerts
|
||||
|
||||
@ -1,122 +0,0 @@
|
||||
---
|
||||
title: Reliability report
|
||||
description: This article describes the reliability score for each Windows quality update cycle based on stop error codes detected on managed devices.
|
||||
ms.date: 04/09/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: how-to
|
||||
ms.localizationpriority: medium
|
||||
author: tiaraquan
|
||||
ms.author: tiaraquan
|
||||
manager: aaroncz
|
||||
ms.reviewer: hathind
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier1
|
||||
---
|
||||
|
||||
# Reliability report (public preview)
|
||||
|
||||
[!INCLUDE [windows-autopatch-enterprise-e3-f3-licenses](../includes/windows-autopatch-enterprise-e3-f3-licenses.md)]
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This feature is in **public preview**. It's being actively developed, and might not be complete.
|
||||
|
||||
The Reliability report provides a reliability score for each Windows quality update cycle based on [stop error codes](/troubleshoot/windows-client/performance/stop-error-or-blue-screen-error-troubleshooting) detected on managed devices. Scores are determined at both the service and tenant level. Details on modules associated with stop error codes at the tenant level are provided to better understand how devices are affected.
|
||||
|
||||
> [!NOTE]
|
||||
> **The Reliability report applies to quality updates only**. The Reliability report doesn't currently support Windows feature updates.<p>Scores used in this report are calculated based on devices running both Windows 10 and Windows 11 versions.</p>
|
||||
|
||||
With this feature, IT admins can access the following information:
|
||||
|
||||
| Information type | Description |
|
||||
| ----- | ----- |
|
||||
| Your score | **Your score** is a calculated tenant reliability score based on stop error codes detected on managed devices that updated successfully during the current update cycle. **Your score** is the latest single-day score in the current Windows quality update cycle. The monthly score values can be viewed under the **Trending** tab. |
|
||||
| Baseline | Use the **Baseline** to compare your score with past quality update cycles. You can choose the desired historical record from the **Comparison baseline** dropdown menu at the top of the page. **Baseline** is a single-day score calculated the same number of days from the start of patching as your score. |
|
||||
| Service-level | Use the **Service-level** to compare **your score** with a score computed across tenants in the Azure Data Scale Unit covering your geographic region. **Service-level** is a single-day score calculated the same number of days from the start of patching as **your score**. |
|
||||
| Score details | **Score details** provides information about specific modules associated with stop error code occurrence, occurrence rate, and affected devices. View single-day or multi-day results by selecting from the **Duration** menu. Data can be exported for offline reference. |
|
||||
| Trending | **Trending** provides a graphical visualization of reliability scores at both tenant and service level on a customizable timeline of 1 - 12 months. Monthly scores represent the aggregated value for a complete update cycle (second Tuesday of the month). |
|
||||
| Insights | **Insights** identifies noteworthy trends that might be useful in implementing reliability improvement opportunities. |
|
||||
| Affected devices | **Affected devices** are the number of unique devices associated with stop error code events. |
|
||||
|
||||
## Report availability
|
||||
|
||||
The Reliability report relies on device policies being configured properly. It's important to confirm that the minimum requirements are met to access the full Reliability report.
|
||||
|
||||
| Data collection policies set | Devices registered in Autopatch | Devices updated | Report availability |
|
||||
| ----- | ------ | ----- | ----- |
|
||||
| No | - | - | No report available.<p>In this state, a ribbon appears on the landing page alerting the user that the diagnostic data needed to generate a report appears to be turned off. The report is available 24 and 48 hours after the following conditions are met:<ul><li>[Diagnostic data device configuration policies enabled](../references/windows-autopatch-changes-to-tenant.md#device-configuration-policies)</li><li>At least 100 devices registered in Autopatch</li><li>At least 100 of these registered devices completed a quality update in the current update cycle (second Tuesday of the month)</li></ul></p> |
|
||||
| Yes | 0 | - | The report includes only the historical comparison baseline and service-level score. The tenant and module impact scores are unavailable until 100 devices are updated. |
|
||||
| Yes | 0 < n < 100 | 0 < n < 100 | The report includes module failure details, historical comparison baseline, and service-level score. The tenant score is unavailable until 100 devices are updated. |
|
||||
| Yes | n >= 100 | 0 < n < 100 | The report includes module failure details, historical comparison baseline score, and service-level score. The tenant and module impact scores are unavailable until 100 devices are updated. |
|
||||
| Yes | n >= 100 | n >= 100 | Full reporting available |
|
||||
|
||||
## View the Reliability report
|
||||
|
||||
**To view the Reliability report:**
|
||||
|
||||
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. Navigate to **Reports** > **Windows Autopatch** > **Windows quality updates**.
|
||||
3. Select the **Reports** tab.
|
||||
4. Select **Reliability report**.
|
||||
|
||||
> [!NOTE]
|
||||
> To use the Reliability report capability, ensure that at least 100 devices are registered in the Windows Autopatch service and capable of successfully completing a quality update. The report relies on device stop error code data being available to Microsoft (transmission of this data may take up to 24 hours).<p>A score is generated when:<ul><li>100 or more devices have completed updating to the latest quality update</li><li>Windows Autopatch receives the stop error code data related to that update cycle</li></ul><p>Windows Autopatch data collection must be enabled according to the [configuration policies](../references/windows-autopatch-changes-to-tenant.md#device-configuration-policies) set during tenant onboarding. For more information about data collection, see [Privacy](../overview/windows-autopatch-privacy.md)</p></p>
|
||||
|
||||
## Report information
|
||||
|
||||
The following information is available as default columns in the Reliability report:
|
||||
|
||||
> [!NOTE]
|
||||
> The report is refreshed no more than once every 24 hours with data received from your Windows Autopatch managed devices. Manual data refresh is not supported. The last refreshed date and time can be found at the top of the page. For more information about how often Windows Autopatch receives data from your managed devices, see [Data latency](../operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md#about-data-latency).
|
||||
|
||||
### Score details
|
||||
|
||||
| Column | Description |
|
||||
| ----- | ----- |
|
||||
| Module name | Name of module associated with stop error code detection. |
|
||||
| Version | Version of module associated with stop error code detection. |
|
||||
| Unique devices | Number of unique devices seeing a stop error code occurrence associated with a specific module name and version. This information is hyperlinked to the **Devices affected** flyout. |
|
||||
| Total events | Total number of stop error codes detected associated with a specific module name and version. |
|
||||
| Module score impact | **Your score** associated with specific module name and version. |
|
||||
| Timeline | This information is hyperlinked to **Module details** flyout. |
|
||||
|
||||
### Export file
|
||||
|
||||
| Column | Description |
|
||||
| ----- | ----- |
|
||||
| DeviceName | Device name |
|
||||
| MicrosoftEntraDeviceId | Microsoft Entra device ID |
|
||||
| Model | Device model |
|
||||
| Manufacturer | Device manufacturer |
|
||||
| AutopatchGroup | Autopatch group assignment for the affected device |
|
||||
| LatestOccurrence | Time of the most recent reported failure |
|
||||
| WindowsVersion | Windows version (Windows 10 or Windows 11) |
|
||||
| OSVersion | OS version |
|
||||
| ModuleName | Name of the module associated with stop error code detection |
|
||||
| Version | Version of the module associated with stop error code detection |
|
||||
| BugCheckCode | Bug check code associated with stop error code |
|
||||
| TenantId | Your Microsoft Entra tenant ID |
|
||||
|
||||
### Devices affected
|
||||
|
||||
| Column | Description |
|
||||
| ----- | ----- |
|
||||
| Device name | Device name |
|
||||
| Microsoft Entra device ID | Microsoft Entra device ID |
|
||||
| Model | Device model |
|
||||
| Manufacturer | Device manufacturer |
|
||||
| Autopatch group | Autopatch group assignment for the affected device |
|
||||
| Latest occurrence | Time of the most recent reported failure |
|
||||
|
||||
### Module details
|
||||
|
||||
| Display selection | Description |
|
||||
| ----- | ----- |
|
||||
| Unique devices | Number of unique devices affected by module failure and the associated version |
|
||||
| Total events | Number of occurrences by module failure and the associated version |
|
||||
| Module impact | Score impact by module and version representing the relative importance of module failure. Higher positive values describe module failures that have a greater impact on the tenant and should be addressed with higher priority. Negative values describe module failures that have a lower-than-average impact on the tenant and thus can be treated with lower priority. Values around `0` describe module failures with average impact on the tenant. |
|
||||
|
||||
## Known limitations
|
||||
|
||||
The Reliability report supports tenant and service-level score data going back to September 2023. Data before that date isn't supported. A full 12 months of score data are available to select from the menu dropdowns in September 2024.
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows quality and feature update reports overview
|
||||
description: This article details the types of reports available and info about update device eligibility, device update health, device update trends in Windows Autopatch.
|
||||
ms.date: 11/20/2024
|
||||
ms.date: 03/03/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: overview
|
||||
@ -19,6 +19,15 @@ ms.collection:
|
||||
|
||||
[!INCLUDE [windows-autopatch-enterprise-e3-f3-licenses](../includes/windows-autopatch-enterprise-e3-f3-licenses.md)]
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Windows Autopatch requires, and uses Windows diagnostic data to display device update statuses in Autopatch reports.
|
||||
|
||||
- Service state and substate data are included for all devices configured for Windows quality and feature updates. No data collection configuration is required.
|
||||
- Client and substate data are collected from devices only if Windows data collection data is properly configured.
|
||||
|
||||
This data collection configuration method using Windows diagnostic data in Intune is shared across Autopatch reports. To support Autopatch reporting, you must configure the [Enable Windows diagnostic data collection settings](/windows/privacy/configure-windows-diagnostic-data-in-your-organization#diagnostic-data-settings) from devices at the **Required** or higher level.
|
||||
|
||||
## Windows quality update reports
|
||||
|
||||
The Windows quality reports provide you with information about:
|
||||
@ -35,7 +44,6 @@ The Windows quality report types are organized into the following focus areas:
|
||||
| ----- | ----- |
|
||||
| Organizational | The [Summary dashboard](../operate/windows-autopatch-groups-windows-quality-update-summary-dashboard.md) provide the current update status summary for all devices.<p>The [Quality update status report](../operate/windows-autopatch-groups-windows-quality-update-status-report.md) provides the current update status of all devices at the device level. |
|
||||
| Device trends | The [Quality update trending report](../operate/windows-autopatch-groups-windows-quality-update-trending-report.md) provides the update status trend of all devices over the last 90 days. |
|
||||
| [Reliability report](../operate/windows-autopatch-reliability-report.md) | The Reliability report provides a reliability score for each Windows quality update cycle based on stop error codes detected on managed devices. |
|
||||
|
||||
## Windows feature update reports
|
||||
|
||||
@ -87,7 +95,7 @@ Up to date devices are devices that meet all of the following prerequisites:
|
||||
- Applied the current monthly cumulative updates
|
||||
|
||||
> [!NOTE]
|
||||
> Device that are [Up to Date](#up-to-date-devices) will remain with the **In Progress** status until either the current monthly cumulative update is applied, or an [alert](../operate/windows-autopatch-device-alerts.md) is received. If the device receives an alert, the device's status will change to [Not up to Date](#not-up-to-date-devices).
|
||||
> Devices that are [Up to Date](#up-to-date-devices) remain with the **In Progress** status until either the current monthly cumulative update is applied, or an [alert](../operate/windows-autopatch-device-alerts.md) is received. If the device receives an alert, the device's status changes to [Not up to Date](#not-up-to-date-devices).
|
||||
|
||||
#### Up to Date sub statuses
|
||||
|
||||
|
||||
@ -174,15 +174,18 @@ You can add the *Device configurations* permission with one or more rights to yo
|
||||
|
||||
### [Windows Enterprise E3+ and F3](#tab/windows-enterprise-e3-f3-intune-permissions)
|
||||
|
||||
Your account must be assigned an [Intune role-based access control](/mem/intune/fundamentals/role-based-access-control) (RBAC) role that includes the following permissions:
|
||||
|
||||
- **Device configurations**:
|
||||
- Assign
|
||||
- Create
|
||||
- Delete
|
||||
- View Reports
|
||||
- Update
|
||||
- Read
|
||||
|
||||
After you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md#activate-windows-autopatch-features), use the Intune Service Administrator role to register devices, manage your update deployments, and reporting tasks.
|
||||
|
||||
If you want to assign less-privileged user accounts to perform specific tasks in the Windows Autopatch portal, such as register devices with the service, you can add these user accounts into one of the two Microsoft Entra groups created during the [Start using Windows Autopatch](../prepare/windows-autopatch-feature-activation.md) process:
|
||||
|
||||
| Microsoft Entra group name | Discover devices | Modify columns | Refresh device list | Export to .CSV | Device actions |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Modern Workplace Roles - Service Administrator | Yes | Yes | Yes | Yes | Yes |
|
||||
| Modern Workplace Roles - Service Reader | No | Yes | Yes | Yes | Yes |
|
||||
|
||||
For more information, see [Microsoft Entra built-in roles](/entra/identity/role-based-access-control/permissions-reference) and [Role-based access control (RBAC) with Microsoft Intune](/mem/intune/fundamentals/role-based-access-control).
|
||||
|
||||
> [!TIP]
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Changes made at feature activation
|
||||
description: This reference article details the changes made to your tenant when you activate Windows Autopatch
|
||||
ms.date: 09/16/2024
|
||||
ms.date: 03/03/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: concept-article
|
||||
@ -49,14 +49,6 @@ The following groups target Windows Autopatch configurations to devices and mana
|
||||
| Modern Workplace Devices-Windows Autopatch-Fast | Fast deployment ring for quick rollout and adoption |
|
||||
| Modern Workplace Devices-WindowsAutopatch-Broad | Final deployment ring for broad rollout into the organization |
|
||||
|
||||
## Device configuration policies
|
||||
|
||||
- Windows Autopatch - Data Collection
|
||||
|
||||
| Policy name | Policy description | Properties | Value |
|
||||
| ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch - Data Collection | Windows Autopatch and Telemetry settings processes diagnostic data from the Windows device.<p>Assigned to:<ul><li>Modern Workplace Devices-Windows Autopatch-Test</li><li>Modern Workplace Devices-Windows Autopatch-First</li><li>Modern Workplace Devices-Windows Autopatch-Fast</li><li>Modern Workplace Devices-Windows Autopatch-Broad</li></ul>|<ol><li>[Allow Telemetry](/windows/client-management/mdm/policy-csp-system#system-allowtelemetry)</li><li>[Limit Enhanced Diagnostic Data Windows Analytics](/windows/client-management/mdm/policy-csp-system#system-limitenhanceddiagnosticdatawindowsanalytics)</li><li>[Limit Dump Collection](/windows/client-management/mdm/policy-csp-system#system-limitdumpcollection)</li><li>[Limit Diagnostic Log Collection](/windows/client-management/mdm/policy-csp-system#system-limitdiagnosticlogcollection)</li></ol>|<ol><li>Full</li><li>Enabled</li><li>Enabled</li><li>Enabled</li></ol> |
|
||||
|
||||
## Windows feature update policies
|
||||
|
||||
- Windows Autopatch - Global DSS Policy
|
||||
@ -68,7 +60,7 @@ The following groups target Windows Autopatch configurations to devices and mana
|
||||
## Microsoft Office update policies
|
||||
|
||||
> [!IMPORTANT]
|
||||
> By default, these policies are not deployed. You can opt-in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update Microsoft Office, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle the must be set to [**Allow**](../manage/windows-autopatch-microsoft-365-apps-enterprise.md#allow-or-block-microsoft-365-app-updates).</p>
|
||||
> By default, these policies aren't deployed. You can opt in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update Microsoft Office, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle must be set to [**Allow**](../manage/windows-autopatch-microsoft-365-apps-enterprise.md#allow-or-block-microsoft-365-app-updates).</p>
|
||||
|
||||
- Windows Autopatch - Office Configuration
|
||||
- Windows Autopatch - Office Update Configuration [Test]
|
||||
@ -87,7 +79,7 @@ The following groups target Windows Autopatch configurations to devices and mana
|
||||
## Microsoft Edge update policies
|
||||
|
||||
> [!IMPORTANT]
|
||||
> By default, these policies are not deployed. You can opt-in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update Microsoft Edge, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle the must be set to [**Allow**](../manage/windows-autopatch-edge.md#allow-or-block-microsoft-edge-updates).</p>
|
||||
> By default, these policies aren't deployed. You can opt in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update Microsoft Edge, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle must be set to [**Allow**](../manage/windows-autopatch-edge.md#allow-or-block-microsoft-edge-updates).</p>
|
||||
|
||||
- Windows Autopatch - Edge Update Channel Stable
|
||||
- Windows Autopatch - Edge Update Channel Beta
|
||||
@ -100,7 +92,7 @@ The following groups target Windows Autopatch configurations to devices and mana
|
||||
## Driver updates for Windows 10 and later
|
||||
|
||||
> [!IMPORTANT]
|
||||
> By default, these policies are not deployed. You can opt-in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update drivers and firmware, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle the must be set to [**Allow**](../manage/windows-autopatch-manage-autopatch-groups.md#create-an-autopatch-group).</p>
|
||||
> By default, these policies aren't deployed. You can opt in to deploy these policies when you [activate Windows Autopatch features](../prepare/windows-autopatch-feature-activation.md).<p>To update drivers and firmware, you must [create at least one Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md) and the toggle must be set to [**Allow**](../manage/windows-autopatch-manage-autopatch-groups.md#create-an-autopatch-group).</p>
|
||||
|
||||
- Windows Autopatch - Driver Update Policy [Test]
|
||||
- Windows Autopatch - Driver Update Policy [First]
|
||||
|
||||
@ -70,7 +70,6 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
| ----- | ----- |
|
||||
| [MC678305](https://admin.microsoft.com/adminportal/home#/MessageCenter) | September 2023 Windows Autopatch baseline configuration update |
|
||||
| [MC678303](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Windows Autopatch availability within Microsoft Intune Admin Center |
|
||||
| [MC674422](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Public Preview: Windows Autopatch Reliability Report |
|
||||
| [MC672750](https://admin.microsoft.com/adminportal/home#/MessageCenter) | August 2023 Windows Autopatch baseline configuration update |
|
||||
|
||||
## August 2023
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2024
|
||||
description: This article lists the 2024 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 11/19/2024
|
||||
ms.date: 02/27/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: whats-new
|
||||
@ -37,14 +37,6 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
| ----- | ----- |
|
||||
| All articles | Windows Update for Business deployment service (WUfB-DS) unified under Windows Autopatch. Unification is going through a gradual rollout over the next several weeks. If your experience looks different from the documentation, you didn't receive the unified experience yet. Review [Prerequisites](../prepare/windows-autopatch-prerequisites.md) and [Features and capabilities](../overview/windows-autopatch-overview.md#features-and-capabilities) to understand licensing and feature entitlement.|
|
||||
|
||||
## March 2024
|
||||
|
||||
### March feature releases or updates
|
||||
|
||||
| Article | Description |
|
||||
| ----- | ----- |
|
||||
| [Reliability report](../operate/windows-autopatch-reliability-report.md) | Added the [Reliability report](../operate/windows-autopatch-reliability-report.md) feature |
|
||||
|
||||
## February 2024
|
||||
|
||||
## February service releases
|
||||
|
||||
@ -7,7 +7,7 @@ author: frankroj
|
||||
ms.service: windows-client
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: install-set-up-deploy
|
||||
ms.date: 02/13/2024
|
||||
ms.date: 02/27/2025
|
||||
ms.subservice: itpro-deploy
|
||||
appliesto:
|
||||
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
|
||||
@ -7,7 +7,7 @@ author: frankroj
|
||||
ms.author: frankroj
|
||||
manager: aaroncz
|
||||
ms.topic: how-to
|
||||
ms.date: 03/28/2024
|
||||
ms.date: 02/27/2025
|
||||
ms.subservice: itpro-deploy
|
||||
zone_pivot_groups: windows-versions-11-10
|
||||
appliesto:
|
||||
|
||||
@ -3,7 +3,7 @@ title: Create your App Control for Business AppId Tagging Policies
|
||||
description: Create your App Control for Business AppId tagging policies for Windows devices.
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/23/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
# Creating your App Control AppId Tagging Policies
|
||||
@ -21,7 +21,7 @@ You can use the App Control for Business Wizard and the PowerShell commands to c
|
||||
:::image type="content" alt-text="Configuring the policy base and template." source="../images/appid-appcontrol-wizard-1.png" lightbox="../images/appid-appcontrol-wizard-1.png":::
|
||||
|
||||
> [!NOTE]
|
||||
> If your AppId Tagging Policy does build off the base templates or does not allow Windows in-box processes, you will notice significant performance regressions, especially during boot. For this reason, it is strongly recommended to build off the base templates. For more information on the issue, see the [AppId Tagging Known Issue](../operations/known-issues.md#slow-boot-and-performance-with-custom-policies).
|
||||
> If your AppId Tagging Policy does not build off the base templates or does not allow Windows in-box processes, you will notice significant performance regressions, especially during boot. For this reason, it is strongly recommended to build off the base templates. For more information on the issue, see the [AppId Tagging Known Issue](../operations/known-issues.md#slow-boot-and-performance-with-custom-policies).
|
||||
|
||||
2. Set the following rule-options using the Wizard toggles:
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@ title: App Control and AppLocker Overview
|
||||
description: Compare Windows application control technologies.
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/11/2024
|
||||
ms.topic: conceptual
|
||||
ms.topic: concept-article
|
||||
---
|
||||
|
||||
# App Control for Business and AppLocker Overview
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Administer AppLocker
|
||||
description: This article for IT professionals provides links to specific procedures to use when administering AppLocker policies.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Configure an AppLocker policy for audit only
|
||||
description: This article for IT professionals describes how to set AppLocker policies to Audit only within your IT environment by using AppLocker.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Configure an AppLocker policy for enforce rules
|
||||
description: This article for IT professionals describes the steps to enable the AppLocker policy enforcement setting.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Add exceptions for an AppLocker rule
|
||||
description: This article for IT professionals describes the steps to specify which apps can or can't run as exceptions to an AppLocker rule.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Configure the AppLocker reference device
|
||||
description: This article for the IT professional describes the steps to create an AppLocker policy platform structure on a reference computer.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Configure the Application Identity service
|
||||
description: This article for IT professionals shows how to configure the Application Identity service to start automatically or manually.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Create a rule for packaged apps
|
||||
description: This article for IT professionals shows how to create an AppLocker rule for packaged apps with a publisher condition.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Create a rule that uses a file hash condition
|
||||
description: This article for IT professionals shows how to create an AppLocker rule with a file hash condition.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Create a rule that uses a path condition
|
||||
description: This article for IT professionals shows how to create an AppLocker rule with a path condition.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Create a rule that uses a publisher condition
|
||||
description: This article for IT professionals shows how to create an AppLocker rule with a publisher condition.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Create AppLocker default rules
|
||||
description: This article for IT professionals describes the steps to create a standard set of AppLocker rules that allow Windows system files to run.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Create Your AppLocker policies
|
||||
description: This overview article for the IT professional describes the steps to create an AppLocker policy and prepare it for deployment.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Create Your AppLocker rules
|
||||
description: This article for the IT professional describes what you need to know about AppLocker rules and the methods that you can to create rules.
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
ms.date: 09/11/2024
|
||||
---
|
||||
|
||||
|
||||
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