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

Merge branch 'MicrosoftDocs:main' into add_link_to_main_LAPS_docs

Browse Source
This commit is contained in:
Thomas Raya 2022-09-22 09:14:47 -07:00 committed by GitHub
commit 2b113fa1ab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
21 changed files with 80 additions and 75 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
education/windows/windows-11-se-overview.md
View File

@ -112,7 +112,8 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| Kite Student Portal | 8.0.3.0 | Win32 | Dynamic Learning Maps | | Kite Student Portal | 8.0.3.0 | Win32 | Dynamic Learning Maps |
| Kortext | 2.3.433.0 | Store | Kortext | | Kortext | 2.3.433.0 | Store | Kortext |
| Kurzweil 3000 Assistive Learning | 20.13.0000 | Win32 | Kurzweil Educational Systems | | Kurzweil 3000 Assistive Learning | 20.13.0000 | Win32 | Kurzweil Educational Systems |
| LanSchool | 9.1.0.46 | Win32 | Stoneware | | LanSchool | 9.1.0.46 | Win32 | Lenovo Software, Inc. |
| LanSchool Air | 2.0.13312 | Win32 | Lenovo Software, Inc. |
| Lightspeed Smart Agent | 1.9.1 | Win32 | Lightspeed Systems | | Lightspeed Smart Agent | 1.9.1 | Win32 | Lightspeed Systems |
| MetaMoJi ClassRoom | 3.12.4.0 | Store | MetaMoJi Corporation | | MetaMoJi ClassRoom | 3.12.4.0 | Store | MetaMoJi Corporation |
| Microsoft Connect | 10.0.22000.1 | Store | Microsoft | | Microsoft Connect | 10.0.22000.1 | Store | Microsoft |

6
windows/deployment/update/update-compliance-configuration-manual.md
View File

@ -1,11 +1,11 @@
--- ---
title: Manually configuring devices for Update Compliance title: Manually configuring devices for Update Compliance
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: Manually configuring devices for Update Compliance description: Manually configuring devices for Update Compliance
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.localizationpriority: medium ms.localizationpriority: medium
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article

40
windows/deployment/update/update-compliance-configuration-mem.md
View File

@ -1,11 +1,11 @@
--- ---
title: Configuring Microsoft Endpoint Manager devices for Update Compliance title: Configuring Microsoft Endpoint Manager devices for Update Compliance
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: Configuring devices that are enrolled in Endpoint Manager for Update Compliance description: Configuring devices that are enrolled in Endpoint Manager for Update Compliance
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.localizationpriority: medium ms.localizationpriority: medium
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
@ -21,62 +21,64 @@ ms.topic: article
This article is specifically targeted at configuring devices enrolled to [Microsoft Endpoint Manager](/mem/endpoint-manager-overview) for Update Compliance, within Microsoft Endpoint Manager itself. Configuring devices for Update Compliance in Microsoft Endpoint Manager breaks down to the following steps: This article is specifically targeted at configuring devices enrolled to [Microsoft Endpoint Manager](/mem/endpoint-manager-overview) for Update Compliance, within Microsoft Endpoint Manager itself. Configuring devices for Update Compliance in Microsoft Endpoint Manager breaks down to the following steps:
1. [Create a configuration profile](#create-a-configuration-profile) for devices you want to enroll, that contains settings for all the MDM policies that must be configured. 1. [Create a configuration profile](#create-a-configuration-profile) for devices you want to enroll, that contains settings for all the MDM policies that must be configured.
2. [Deploy the configuration script](#deploy-the-configuration-script) as a Win32 app to those same devices, so additional checks can be performed to ensure devices are correctly configured. 1. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. You can learn more about this in the broad section on [enrolling devices to Update Compliance](update-compliance-get-started.md#enroll-devices-in-update-compliance).
3. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. You can learn more about this in the broad section on [enrolling devices to Update Compliance](update-compliance-get-started.md#enroll-devices-in-update-compliance).
> [!TIP]
> If you need to troubleshoot client enrollment, consider deploying the [configuration script](#deploy-the-configuration-script) as a Win32 app to a few devices and reviewing the logs it creates. Additional checks are performed with the script to ensure devices are correctly configured.
## Create a configuration profile ## Create a configuration profile
Take the following steps to create a configuration profile that will set required policies for Update Compliance: Take the following steps to create a configuration profile that will set required policies for Update Compliance:
1. Go to the Admin portal in Endpoint Manager and navigate to **Devices/Windows/Configuration profiles**. 1. Go to the Admin portal in Endpoint Manager and navigate to **Devices/Windows/Configuration profiles**.
2. On the **Configuration profiles** view, select **Create a profile**. 1. On the **Configuration profiles** view, select **Create a profile**.
3. Select **Platform**="Windows 10 and later" and **Profile type**="Templates". 1. Select **Platform**="Windows 10 and later" and **Profile type**="Templates".
4. For **Template name**, select **Custom**, and then press **Create**. 1. For **Template name**, select **Custom**, and then press **Create**.
5. You are now on the Configuration profile creation screen. On the **Basics** tab, give a **Name** and **Description**. 1. You are now on the Configuration profile creation screen. On the **Basics** tab, give a **Name** and **Description**.
6. On the **Configuration settings** page, you will be adding multiple OMA-URI Settings that correspond to the policies described in [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md). 1. On the **Configuration settings** page, you will be adding multiple OMA-URI Settings that correspond to the policies described in [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md).
1. If you don't already have it, get your Commercial ID. For steps, see [Get your CommmercialID](update-compliance-get-started.md#get-your-commercialid). 1. If you don't already have it, get your Commercial ID. For steps, see [Get your CommmercialID](update-compliance-get-started.md#get-your-commercialid).
2. Add a setting for **Commercial ID** with the following values: 1. Add a setting for **Commercial ID** with the following values:
- **Name**: Commercial ID - **Name**: Commercial ID
- **Description**: Sets the Commercial ID that corresponds to the Update Compliance Log Analytics workspace. - **Description**: Sets the Commercial ID that corresponds to the Update Compliance Log Analytics workspace.
- **OMA-URI**: `./Vendor/MSFT/DMClient/Provider/ProviderID/CommercialID` - **OMA-URI**: `./Vendor/MSFT/DMClient/Provider/ProviderID/CommercialID`
- **Data type**: String - **Data type**: String
- **Value**: *Set this to your Commercial ID* - **Value**: *Set this to your Commercial ID*
2. Add a setting configuring the **Windows Diagnostic Data level** for devices: 1. Add a setting configuring the **Windows Diagnostic Data level** for devices:
- **Name**: Allow Telemetry - **Name**: Allow Telemetry
- **Description**: Sets the maximum allowed diagnostic data to be sent to Microsoft, required for Update Compliance. - **Description**: Sets the maximum allowed diagnostic data to be sent to Microsoft, required for Update Compliance.
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowTelemetry` - **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowTelemetry`
- **Data type**: Integer - **Data type**: Integer
- **Value**: 1 (*all that is required is 1, but it can be safely set to a higher value*). - **Value**: 1 (*all that is required is 1, but it can be safely set to a higher value*).
3. (*Recommended, but not required*) Add a setting for **disabling devices' Diagnostic Data opt-in settings interface**. If this is not disabled, users of each device can potentially override the diagnostic data level of devices such that data will not be available for those devices in Update Compliance: 1. (*Recommended, but not required*) Add a setting for **disabling devices' Diagnostic Data opt-in settings interface**. If this is not disabled, users of each device can potentially override the diagnostic data level of devices such that data will not be available for those devices in Update Compliance:
- **Name**: Disable Telemetry opt-in interface - **Name**: Disable Telemetry opt-in interface
- **Description**: Disables the ability for end-users of devices can adjust diagnostic data to levels lower than defined by the Allow Telemetry setting. - **Description**: Disables the ability for end-users of devices can adjust diagnostic data to levels lower than defined by the Allow Telemetry setting.
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/ConfigureTelemetryOptInSettingsUx` - **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/ConfigureTelemetryOptInSettingsUx`
- **Data type**: Integer - **Data type**: Integer
- **Value**: 1 - **Value**: 1
4. Add a setting to **Allow device name in diagnostic data**; otherwise, there will be no device name in Update Compliance: 1. Add a setting to **Allow device name in diagnostic data**; otherwise, there will be no device name in Update Compliance:
- **Name**: Allow device name in Diagnostic Data - **Name**: Allow device name in Diagnostic Data
- **Description**: Allows device name in Diagnostic Data. - **Description**: Allows device name in Diagnostic Data.
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowDeviceNameInDiagnosticData` - **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowDeviceNameInDiagnosticData`
- **Data type**: Integer - **Data type**: Integer
- **Value**: 1 - **Value**: 1
5. Add a setting to **Allow Update Compliance processing**; this policy is required for Update Compliance: 1. Add a setting to **Allow Update Compliance processing**; this policy is required for Update Compliance:
- **Name**: Allow Update Compliance Processing - **Name**: Allow Update Compliance Processing
- **Description**: Opts device data into Update Compliance processing. Required to see data. - **Description**: Opts device data into Update Compliance processing. Required to see data.
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowUpdateComplianceProcessing` - **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowUpdateComplianceProcessing`
- **Data type**: Integer - **Data type**: Integer
- **Value**: 16 - **Value**: 16
6. Add a setting to **Allow commercial data pipeline**; this policy is required for Update Compliance: 1. Add a setting to **Allow commercial data pipeline**; this policy is required for Update Compliance:
- **Name**: Allow commercial data pipeline - **Name**: Allow commercial data pipeline
- **Description**: Configures Microsoft to be the processor of the Windows diagnostic data collected from an Azure Active Directory-joined device. - **Description**: Configures Microsoft to be the processor of the Windows diagnostic data collected from an Azure Active Directory-joined device.
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowCommercialDataPipeline` - **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowCommercialDataPipeline`
- **Data type**: Integer - **Data type**: Integer
- **Value**: 1 - **Value**: 1
7. Proceed through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll. 1. Proceed through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
8. Review and select **Create**. 1. Review and select **Create**.
## Deploy the configuration script ## Deploy the configuration script
The [Update Compliance Configuration Script](update-compliance-configuration-script.md) is an important component of properly enrolling devices in Update Compliance, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management). The [Update Compliance Configuration Script](update-compliance-configuration-script.md) is a useful tool for properly enrolling devices in Update Compliance, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Update Compliance](update-compliance-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management).
When you deploy the configuration script as a Win32 app, you won't be able to retrieve the results of logs on the device without having access to the device, or saving results of the logs to a shared filesystem. We recommend deploying the script in Pilot mode to a set of devices that you do have access to, or have a way to access the resultant log output the script provides, with as similar of a configuration profile as other devices which will be enrolled to Update Compliance, and analyzing the logs for any potential issues. Following this, you can deploy the configuration script in Deployment mode as a Win32 app to all Update Compliance devices. When you deploy the configuration script as a Win32 app, you won't be able to retrieve the results of logs on the device without having access to the device, or saving results of the logs to a shared filesystem. We recommend deploying the script in Pilot mode to a set of devices that you do have access to, or have a way to access the resultant log output the script provides, with as similar of a configuration profile as other devices which will be enrolled to Update Compliance, and analyzing the logs for any potential issues. Following this, you can deploy the configuration script in Deployment mode as a Win32 app to all Update Compliance devices.

2
windows/deployment/update/update-compliance-configuration-script.md
View File

@ -1,7 +1,7 @@
--- ---
title: Update Compliance Configuration Script title: Update Compliance Configuration Script
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: Downloading and using the Update Compliance Configuration Script description: Downloading and using the Update Compliance Configuration Script
ms.prod: w10 ms.prod: w10
author: mestew author: mestew

8
windows/deployment/update/update-compliance-delivery-optimization.md
View File

@ -1,11 +1,11 @@
--- ---
title: Delivery Optimization in Update Compliance title: Delivery Optimization in Update Compliance
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: Learn how the Update Compliance solution provides you with information about your Delivery Optimization configuration. description: Learn how the Update Compliance solution provides you with information about your Delivery Optimization configuration.
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.localizationpriority: medium ms.localizationpriority: medium
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
@ -46,7 +46,7 @@ The table breaks down the number of bytes from each download source into specifi
The download sources that could be included are: The download sources that could be included are:
- LAN Bytes: Bytes downloaded from LAN Peers which are other devices on the same local network - LAN Bytes: Bytes downloaded from LAN Peers which are other devices on the same local network
- Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the "Group" download mode is used) - Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the "Group" download mode is used)
- HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or an Configuration Manager Distribution Point for Express Updates. - HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or a Configuration Manager Distribution Point for Express Updates.
<!--Using include file, waas-delivery-optimization-monitor.md, for shared content on DO monitoring--> <!--Using include file, waas-delivery-optimization-monitor.md, for shared content on DO monitoring-->
[!INCLUDE [Monitor Delivery Optimization](../do/includes/waas-delivery-optimization-monitor.md)] [!INCLUDE [Monitor Delivery Optimization](../do/includes/waas-delivery-optimization-monitor.md)]

6
windows/deployment/update/update-compliance-feature-update-status.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance - Feature Update Status report title: Update Compliance - Feature Update Status report
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: Learn how the Feature Update Status report provides information about the status of feature updates across all devices. description: Learn how the Feature Update Status report provides information about the status of feature updates across all devices.
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
ms.custom: seo-marvel-apr2020 ms.custom: seo-marvel-apr2020

6
windows/deployment/update/update-compliance-get-started.md
View File

@ -1,10 +1,10 @@
--- ---
title: Get started with Update Compliance title: Get started with Update Compliance
manager: dougeby manager: aczechowski
description: Prerequisites, Azure onboarding, and configuring devices for Update Compliance description: Prerequisites, Azure onboarding, and configuring devices for Update Compliance
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.localizationpriority: medium ms.localizationpriority: medium
ms.collection: ms.collection:
- M365-analytics - M365-analytics

6
windows/deployment/update/update-compliance-monitor.md
View File

@ -1,11 +1,11 @@
--- ---
title: Monitor Windows Updates and Microsoft Defender AV with Update Compliance title: Monitor Windows Updates and Microsoft Defender AV with Update Compliance
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: You can use Update Compliance in Azure portal to monitor the progress of updates and key anti-malware protection features on devices in your network. description: You can use Update Compliance in Azure portal to monitor the progress of updates and key anti-malware protection features on devices in your network.
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.localizationpriority: medium ms.localizationpriority: medium
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article

6
windows/deployment/update/update-compliance-need-attention.md
View File

@ -1,9 +1,9 @@
--- ---
title: Update Compliance - Need Attention! report title: Update Compliance - Need Attention! report
manager: dougeby manager: aczechowski
description: Learn how the Need attention! section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance. description: Learn how the Need attention! section provides a breakdown of all Windows 10 device and update issues detected by Update Compliance.
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
ms.prod: w10 ms.prod: w10

6
windows/deployment/update/update-compliance-privacy.md
View File

@ -1,11 +1,11 @@
--- ---
title: Privacy in Update Compliance title: Privacy in Update Compliance
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: an overview of the Feature Update Status report description: an overview of the Feature Update Status report
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
--- ---

6
windows/deployment/update/update-compliance-safeguard-holds.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance - Safeguard Holds report title: Update Compliance - Safeguard Holds report
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: Learn how the Safeguard Holds report provides information about safeguard holds in your population. description: Learn how the Safeguard Holds report provides information about safeguard holds in your population.
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
ms.custom: seo-marvel-apr2020 ms.custom: seo-marvel-apr2020

6
windows/deployment/update/update-compliance-schema-waasdeploymentstatus.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance Schema - WaaSDeploymentStatus title: Update Compliance Schema - WaaSDeploymentStatus
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: WaaSDeploymentStatus schema description: WaaSDeploymentStatus schema
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
--- ---

6
windows/deployment/update/update-compliance-schema-waasinsiderstatus.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance Schema - WaaSInsiderStatus title: Update Compliance Schema - WaaSInsiderStatus
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: WaaSInsiderStatus schema description: WaaSInsiderStatus schema
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
--- ---

6
windows/deployment/update/update-compliance-schema-waasupdatestatus.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance Schema - WaaSUpdateStatus title: Update Compliance Schema - WaaSUpdateStatus
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: WaaSUpdateStatus schema description: WaaSUpdateStatus schema
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
--- ---

6
windows/deployment/update/update-compliance-schema-wudoaggregatedstatus.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance Schema - WUDOAggregatedStatus title: Update Compliance Schema - WUDOAggregatedStatus
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: WUDOAggregatedStatus schema description: WUDOAggregatedStatus schema
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
--- ---

6
windows/deployment/update/update-compliance-schema-wudostatus.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance Schema - WUDOStatus title: Update Compliance Schema - WUDOStatus
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: WUDOStatus schema description: WUDOStatus schema
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
--- ---

8
windows/deployment/update/update-compliance-schema.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance Data Schema title: Update Compliance Data Schema
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: an overview of Update Compliance data schema description: an overview of Update Compliance data schema
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
--- ---
@ -21,7 +21,7 @@ The table below summarizes the different tables that are part of the Update Comp
|Table |Category |Description | |Table |Category |Description |
|--|--|--| |--|--|--|
|[**WaaSUpdateStatus**](update-compliance-schema-waasupdatestatus.md) |Device record |This table houses device-centric data and acts as the device record for Update Compliance. Each record provided in daily snapshots map to a single device in a single tenant. This table has data such as the current device's installed version of Windows, whether it is on the latest available updates, and whether the device needs attention. | |[**WaaSUpdateStatus**](update-compliance-schema-waasupdatestatus.md) |Device record |This table houses device-centric data and acts as the device record for Update Compliance. Each record provided in daily snapshots maps to a single device in a single tenant. This table has data such as the current device's installed version of Windows, whether it is on the latest available updates, and whether the device needs attention. |
|[**WaaSInsiderStatus**](update-compliance-schema-waasinsiderstatus.md) |Device record |This table houses device-centric data specifically for devices enrolled to the Windows Insider Program. Devices enrolled to the Windows Insider Program do not currently have any WaaSDeploymentStatus records, so do not have Update Session data to report on update deployment progress. | |[**WaaSInsiderStatus**](update-compliance-schema-waasinsiderstatus.md) |Device record |This table houses device-centric data specifically for devices enrolled to the Windows Insider Program. Devices enrolled to the Windows Insider Program do not currently have any WaaSDeploymentStatus records, so do not have Update Session data to report on update deployment progress. |
|[**WaaSDeploymentStatus**](update-compliance-schema-waasdeploymentstatus.md) |Update Session record |This table tracks a specific update on a specific device. Multiple WaaSDeploymentStatus records can exist simultaneously for a given device, as each record is specific to a given update and its type. For example, a device can have both a WaaSDeploymentStatus tracking a Windows Feature Update, as well as one tracking a Windows Quality Update, at the same time. | |[**WaaSDeploymentStatus**](update-compliance-schema-waasdeploymentstatus.md) |Update Session record |This table tracks a specific update on a specific device. Multiple WaaSDeploymentStatus records can exist simultaneously for a given device, as each record is specific to a given update and its type. For example, a device can have both a WaaSDeploymentStatus tracking a Windows Feature Update, as well as one tracking a Windows Quality Update, at the same time. |
|[**WUDOStatus**](update-compliance-schema-wudostatus.md) |Delivery Optimization record |This table provides information, for a single device, on their bandwidth utilization across content types in the event they use [Delivery Optimization](https://support.microsoft.com/help/4468254/windows-update-delivery-optimization-faq). | |[**WUDOStatus**](update-compliance-schema-wudostatus.md) |Delivery Optimization record |This table provides information, for a single device, on their bandwidth utilization across content types in the event they use [Delivery Optimization](https://support.microsoft.com/help/4468254/windows-update-delivery-optimization-faq). |

6
windows/deployment/update/update-compliance-security-update-status.md
View File

@ -1,11 +1,11 @@
--- ---
title: Update Compliance - Security Update Status report title: Update Compliance - Security Update Status report
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: Learn how the Security Update Status section provides information about security updates across all devices. description: Learn how the Security Update Status section provides information about security updates across all devices.
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article
ms.custom: seo-marvel-apr2020 ms.custom: seo-marvel-apr2020

6
windows/deployment/update/update-compliance-using.md
View File

@ -1,11 +1,11 @@
--- ---
title: Using Update Compliance title: Using Update Compliance
ms.reviewer: ms.reviewer:
manager: dougeby manager: aczechowski
description: Learn how to use Update Compliance to monitor your device's Windows updates. description: Learn how to use Update Compliance to monitor your device's Windows updates.
ms.prod: w10 ms.prod: w10
author: aczechowski author: mestew
ms.author: aaroncz ms.author: mstewart
ms.localizationpriority: medium ms.localizationpriority: medium
ms.collection: M365-analytics ms.collection: M365-analytics
ms.topic: article ms.topic: article

8
windows/deployment/update/update-compliance-v2-configuration-mem.md
View File

@ -24,8 +24,10 @@ ms.date: 08/24/2022
This article is specifically targeted at configuring devices enrolled to [Microsoft Endpoint Manager](/mem/endpoint-manager-overview) for Update Compliance, within Microsoft Endpoint Manager itself. Configuring devices for Update Compliance in Microsoft Endpoint Manager breaks down to the following steps: This article is specifically targeted at configuring devices enrolled to [Microsoft Endpoint Manager](/mem/endpoint-manager-overview) for Update Compliance, within Microsoft Endpoint Manager itself. Configuring devices for Update Compliance in Microsoft Endpoint Manager breaks down to the following steps:
1. [Create a configuration profile](#create-a-configuration-profile) for devices you want to enroll. The configuration profile contains settings for all the Mobile Device Management (MDM) policies that must be configured. 1. [Create a configuration profile](#create-a-configuration-profile) for devices you want to enroll. The configuration profile contains settings for all the Mobile Device Management (MDM) policies that must be configured.
2. [Deploy the configuration script](#deploy-the-configuration-script) as a Win32 app to those same devices, so additional checks can be performed to ensure devices are correctly configured. 1. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. For more information, see [Use Update Compliance](update-compliance-v2-use.md).
3. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. For more information, see [Use Update Compliance](update-compliance-v2-use.md).
> [!TIP]
> If you need to troubleshoot client enrollment, consider deploying the [configuration script](#deploy-the-configuration-script) as a Win32 app to a few devices and reviewing the logs it creates. Additional checks are performed with the script to ensure devices are correctly configured.
## Create a configuration profile ## Create a configuration profile
@ -105,7 +107,7 @@ Create a configuration profile that will set the required policies for Update Co
## Deploy the configuration script ## Deploy the configuration script
The [Update Compliance Configuration Script](update-compliance-v2-configuration-script.md) is an important component of properly enrolling devices in Update Compliance, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Update Compliance](update-compliance-v2-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management). The [Update Compliance Configuration Script](update-compliance-v2-configuration-script.md) is a useful tool for properly enrolling devices in Update Compliance, though it isn't strictly necessary. It checks to ensure that devices have the required services running and checks connectivity to the endpoints detailed in the section on [Manually configuring devices for Update Compliance](update-compliance-v2-configuration-manual.md). You can deploy the script as a Win32 app. For more information, see [Win32 app management in Microsoft Intune](/mem/intune/apps/apps-win32-app-management).
When you deploy the configuration script as a Win32 app, you won't be able to retrieve the results of logs on the device without having access to the device, or saving results of the logs to a shared filesystem. We recommend deploying the script in pilot mode to a set of devices that you do have access to, or have a way to access the resultant log output the script provides, with as similar of a configuration profile as other devices which will be enrolled to Update Compliance, and analyzing the logs for any potential issues. Following this, you can deploy the configuration script in deployment mode as a Win32 app to all Update Compliance devices. When you deploy the configuration script as a Win32 app, you won't be able to retrieve the results of logs on the device without having access to the device, or saving results of the logs to a shared filesystem. We recommend deploying the script in pilot mode to a set of devices that you do have access to, or have a way to access the resultant log output the script provides, with as similar of a configuration profile as other devices which will be enrolled to Update Compliance, and analyzing the logs for any potential issues. Following this, you can deploy the configuration script in deployment mode as a Win32 app to all Update Compliance devices.

2
windows/whats-new/whats-new-windows-11-version-22H2.md
View File

@ -43,7 +43,7 @@ For more information, see [Enhanced Phishing Protection in Microsoft Defender Sm
<!-- 6286281--> <!-- 6286281-->
**Smart App Control** adds significant protection from malware, including new and emerging threats, by blocking apps that are malicious or untrusted. **Smart App Control** also helps to block potentially unwanted apps, which are apps that may cause your device to run slowly, display unexpected ads, offer extra software you didn't want, or do other things you don't expect. **Smart App Control** adds significant protection from malware, including new and emerging threats, by blocking apps that are malicious or untrusted. **Smart App Control** also helps to block potentially unwanted apps, which are apps that may cause your device to run slowly, display unexpected ads, offer extra software you didn't want, or do other things you don't expect.
For more information, see [Smart App Control](/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md#wdac-and-smart-app-control). For more information, see [Smart App Control](/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control#wdac-and-smart-app-control).
## Credential Guard ## Credential Guard
<!--6289166--> <!--6289166-->