mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 13:57:22 +00:00
Merging changes synced from https://github.com/MicrosoftDocs/windows-docs-pr (branch live)
This commit is contained in:
officedocspr
commit
2c7fc2e42a
@ -14652,9 +14652,9 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/basic-level-windows-diagnostic-events-and-fields.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/privacy/basic-level-windows-diagnostic-events-and-fields-1903",
|
||||
"redirect_document_id": true
|
||||
"source_path": "windows/privacy/basic-level-windows-diagnostic-events-and-fields.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/privacy/required-windows-diagnostic-events-and-fields-2005",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/basic-level-windows-diagnostic-events-and-fields-1703.md",
|
||||
|
||||
@ -18,7 +18,7 @@
|
||||
## [Getting around HoloLens (1st gen)](hololens1-basic-usage.md)
|
||||
## [HoloLens (1st Gen) release notes](hololens1-release-notes.md)
|
||||
|
||||
# Deploy HoloLens and mixed-reality apps in commercial environments
|
||||
# Deploy HoloLens and mixed reality apps in commercial environments
|
||||
## [Commercial features](hololens-commercial-features.md)
|
||||
## [Deploy HoloLens in a commercial environment](hololens-requirements.md)
|
||||
## [Determine what licenses you need](hololens-licenses-requirements.md)
|
||||
@ -29,13 +29,13 @@
|
||||
## [Manage HoloLens updates](hololens-updates.md)
|
||||
## [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md)
|
||||
|
||||
# Navigating Windows Holographic
|
||||
## [Start menu and mixed reality home](holographic-home.md)
|
||||
## [Use your voice with HoloLens](hololens-cortana.md)
|
||||
# Navigate the Windows Holographic environment
|
||||
## [Use the Start menu and mixed reality home](holographic-home.md)
|
||||
## [Use your voice to operate HoloLens](hololens-cortana.md)
|
||||
## [Find, open, and save files](holographic-data.md)
|
||||
## [Create mixed reality photos and videos](holographic-photos-and-videos.md)
|
||||
|
||||
# User management and access management
|
||||
# Manage users and access
|
||||
## [Manage user identity and sign-in for HoloLens](hololens-identity.md)
|
||||
## [Share your HoloLens with multiple people](hololens-multiple-users.md)
|
||||
## [Set up HoloLens as a kiosk](hololens-kiosk.md)
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Start menu and mixed reality home
|
||||
title: Use the Start menu and mixed reality home
|
||||
description: Navigate the mixed reality home in Windows Holographic.
|
||||
ms.assetid: 742bc126-7996-4f3a-abb2-cf345dff730c
|
||||
ms.date: 08/07/2019
|
||||
@ -15,7 +15,7 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Start menu and mixed reality home
|
||||
# Use the Start menu and mixed reality home
|
||||
|
||||
Just like the Windows PC experience starts with the desktop, Windows Holographic starts with mixed reality home. Using the Start menu you can open and place app windows, immersive app launchers, and 3D content in mixed reality home, and their placement in your physical space will be remembered.
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Use your voice with HoloLens
|
||||
title: Use your voice to operate HoloLens
|
||||
description: Cortana can help you do all kinds of things on your HoloLens
|
||||
ms.assetid: fd96fb0e-6759-4dbe-be1f-58bedad66fed
|
||||
ms.date: 03/10/2020
|
||||
@ -17,7 +17,7 @@ appliesto:
|
||||
- HoloLens 2
|
||||
---
|
||||
|
||||
# Use your voice with HoloLens
|
||||
# Use your voice to operate HoloLens
|
||||
|
||||
You can use your voice to do almost anything on HoloLens, such as taking a quick photo or opening an app. Many voice commands are built into HoloLens, while others are available through Cortana.
|
||||
|
||||
@ -34,14 +34,14 @@ Get around HoloLens faster with these basic commands. In order to use these, you
|
||||
|
||||
### General speech commands
|
||||
|
||||
Use these commands throughout Windows Mixed Reality to get around faster. Some commands use the gaze cursor, which you bring up by saying “select.”
|
||||
Use these commands throughout Windows Mixed Reality to get around faster. Some commands use the gaze cursor, which you bring up by saying "select."
|
||||
|
||||
> [!NOTE]
|
||||
> Hand rays are not supported on HoloLens (1st Gen).
|
||||
|
||||
| Say this | To do this |
|
||||
| - | - |
|
||||
| "Select" | Say "select" to bring up the gaze cursor. Then, turn your head to position the cursor on the thing you want to select, and say “select” again. |
|
||||
| "Select" | Say "select" to bring up the gaze cursor. Then, turn your head to position the cursor on the thing you want to select, and say "select" again. |
|
||||
|Open the Start menu | "Go to Start" |
|
||||
|Close the Start menu | "Close" |
|
||||
|Leave an immersive app | Say "Go to Start" to bring up the quick actions menu, then say "Mixed reality home." |
|
||||
|
||||
@ -185,24 +185,7 @@ The Enrollment Status Page (ESP) displays the status of the complete device conf
|
||||
|
||||
|
||||
|
||||
### 8. Configure a custom configuration profile for HoloLens devices (known issue)
|
||||
|
||||
1. In [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com), select **Devices** > **Configuration profiles** > **Create profile**.
|
||||
1. For **Platform**, specify **Windows 10 and later**, and for **Profile**, select **Custom**.
|
||||
1. Select **Create**.
|
||||
1. Enter a name for the profile, and then select **Settings** > **Configure**.
|
||||
|
||||
|
||||
1. Select **Add**, and then specify the following information:
|
||||
|
||||
- **Name**: SidecarPath
|
||||
- **OMA-URI**: ./images/Device/Vendor/MSFT/EnrollmentStatusTracking/DevicePreparation/PolicyProviders/Sidecar/InstallationState
|
||||
- **Data type**: Integer
|
||||
- **Value**: 2
|
||||
1. Select **OK** two times, and then select **Create** to create the profile.
|
||||
1. After Intune creates the configuration profile, assign the configuration profile to the device group for the HoloLens devices.
|
||||
|
||||
### 9. Verify the profile status of the HoloLens devices
|
||||
### 8. Verify the profile status of the HoloLens devices
|
||||
|
||||
1. In Microsoft Endpoint Manager Admin Center, select **Devices** > **Windows** > **Windows enrollment** > **Devices**.
|
||||
1. Verify that the HoloLens devices are listed, and that their profile status is **Assigned**.
|
||||
@ -234,7 +217,7 @@ At the end of OOBE, you can sign in to the device by using your user name and pa
|
||||
|
||||
## Known Issues
|
||||
|
||||
- The list of supported languages for Autopilot deployment profiles includes languages that HoloLens does not support. Select a language that [HoloLens supports](hololens2-language-support.md).
|
||||
- You cannot install applications that use the device security context.
|
||||
|
||||
## Feedback
|
||||
|
||||
|
||||
@ -53,7 +53,7 @@ appliesto:
|
||||
| [HoloLens user management](hololens-multiple-users.md) | Multiple users can share a HoloLens device by using their Azure Active Directory accounts. |
|
||||
| [HoloLens application access management](hololens-kiosk.md) | Manage application access for different user groups. |
|
||||
| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) | Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary. |
|
||||
| [Contact Support](https://support.microsoft.com/supportforbusiness/productselection) | Create a new support request for the business support team. |
|
||||
| [Contact Support](https://support.microsoft.com/supportforbusiness/productselection?sapid=e9391227-fa6d-927b-0fff-f96288631b8f) | Create a new support request for the business support team. |
|
||||
| [More support options](https://support.microsoft.com/products/hololens) | Connect with Microsoft support resources for HoloLens in the enterprise. |
|
||||
|
||||
## Related resources
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Create Surface Hub 2S device account"
|
||||
description: "This page describes the procedure for creating the Surface Hub 2S device account."
|
||||
title: Create Surface Hub 2S device account
|
||||
description: This page describes the procedure for creating the Surface Hub 2S device account.
|
||||
keywords: separate values with commas
|
||||
ms.prod: surface-hub
|
||||
ms.sitesec: library
|
||||
@ -15,15 +15,18 @@ ms.localizationpriority: Medium
|
||||
|
||||
# Create Surface Hub 2S device account
|
||||
|
||||
Creating a Surface Hub device account (also known as a Room mailbox) allows Surface Hub 2S to receive, approve, or decline meeting requests and join meetings using Microsoft Teams or Skype for Business. Configure the device account during OOBE setup. If needed you can change it later (without going through OOBE setup).
|
||||
Creating a Surface Hub device account (also known as a Room mailbox) allows Surface Hub 2S to receive, approve, or decline meeting requests and join meetings using either Microsoft Teams or Skype for Business. Configure the device account during Out-of-Box Experience (OOBE) setup. If needed, you can change it later (without going through OOBE setup).
|
||||
|
||||
Unlike standard Room mailboxes that remain disabled by default, you need to enable the Surface Hub 2S device account to sign on to Microsoft Teams and Skype for Business. Surface Hub 2S relies on Exchange ActiveSync, which requires an ActiveSync mailbox policy on the device account. Apply the default ActiveSync mailbox policy that comes with Exchange Online.
|
||||
|
||||
Create the account using the Microsoft 365 admin center or by using PowerShell. You can use Exchange Online PowerShell to configure specific features including:
|
||||
Create the account by using the Microsoft 365 admin center or by using PowerShell. You can use Exchange Online PowerShell to configure specific features including:
|
||||
|
||||
- Calendar processing for every Surface Hub device account.
|
||||
- Custom auto replies to scheduling requests.
|
||||
- If the default ActiveSync mailbox policy has already been modified by someone else or another process, you will likely have to create and assign a new ActiveSync mailbox policy
|
||||
- If the default ActiveSync mailbox policy has already been modified by someone else or by another process, you will likely have to create and assign a new ActiveSync mailbox policy.
|
||||
|
||||
> [!NOTE]
|
||||
> The Surface Hub device account doesn’t support third-party Federated Identity Providers (FIPs) and must be a standard Active Directory or Azure Active Directory account.
|
||||
|
||||
## Create account using Microsoft 365 admin center
|
||||
|
||||
@ -31,17 +34,17 @@ Create the account using the Microsoft 365 admin center or by using PowerShell.
|
||||
|
||||
2. Provide a name and email address for the device account. Leave remaining settings unchanged in the default state.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
3. Set the password for the device account. To set the password, choose **Users** and then select **Active Users**. Now search for the newly created user to set the password. Ensure that you **do not** select the option **Make this user change their password when they first sign in.**
|
||||
|
||||
|
||||
|
||||
|
||||
4. Assign the room with an Office 365 license. It’s recommended to assign the Office 365 **Meeting Room** license, a new option that automatically enables the account for Skype for Business Online and Microsoft Teams.
|
||||
|
||||
|
||||
|
||||
|
||||
### Finalize setup via PowerShell
|
||||
|
||||
@ -50,6 +53,7 @@ Create the account using the Microsoft 365 admin center or by using PowerShell.
|
||||
- **Microsoft Teams and Skype for Business Calendar:** Set [**Calendar Auto processing**](https://docs.microsoft.com/surface-hub/surface-hub-2s-account?source=docs#set-calendar-auto-processing) for this account.
|
||||
|
||||
## Create account using PowerShell
|
||||
|
||||
Instead of using the Microsoft Admin Center portal, you can create the account using PowerShell.
|
||||
|
||||
### Connect to Exchange Online PowerShell
|
||||
@ -59,13 +63,13 @@ $365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
|
||||
$ImportResults = Import-PSSession $365Session
|
||||
```
|
||||
|
||||
### Create a new Room Mailbox
|
||||
### Create a new Room mailbox
|
||||
|
||||
```powershell
|
||||
New-Mailbox -MicrosoftOnlineServicesID account@YourDomain.com -Alias SurfaceHub2S -Name SurfaceHub2S -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String "<Enter Strong Password>" -AsPlainText -Force)
|
||||
```
|
||||
|
||||
### Set Calendar Auto processing
|
||||
### Set Calendar auto-processing
|
||||
|
||||
```powershell
|
||||
Set-CalendarProcessing -Identity "account@YourDomain.com" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This room is equipped with a Surface Hub"
|
||||
@ -81,7 +85,7 @@ Set-MsolUserLicense -UserPrincipalName "account@YourDomain.com" -AddLicenses "co
|
||||
|
||||
## Connect to Skype for Business Online using PowerShell
|
||||
|
||||
### Install prerequisites
|
||||
### Install pre-requisites
|
||||
|
||||
- [Visual C++ 2017 Redistributable](https://aka.ms/vs/15/release/vc_redist.x64.exe)
|
||||
- [Skype for Business Online PowerShell Module](https://www.microsoft.com/download/confirmation.aspx?id=39366)
|
||||
|
||||
@ -9,11 +9,11 @@ ms.sitesec: library
|
||||
author: coveminer
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
ms.reviewer: scottmca
|
||||
ms.reviewer: hachidan
|
||||
manager: laurawi
|
||||
ms.localizationpriority: medium
|
||||
audience: itpro
|
||||
ms.date: 05/11/2020
|
||||
ms.date: 05/26/2020
|
||||
---
|
||||
|
||||
# Microsoft Surface Enterprise Management Mode
|
||||
@ -228,14 +228,27 @@ create a reset package using PowerShell to reset SEMM.
|
||||
|
||||
## Version History
|
||||
|
||||
The latest version of SEMM released May 11, 2020 includes:
|
||||
### Version 2.71.139.0
|
||||
|
||||
This version of SEMM adds support for Surface Dock 2 management features for Surface Book 3, Surface Laptop 3, and Surface Pro 7 including:
|
||||
|
||||
- Enabling audio (locking/unlocking), Ethernet and USB ports
|
||||
- Ability to create dock packages for both authenticated and unauthenticated hosts
|
||||
|
||||
### Version 2.70.130.0
|
||||
|
||||
This version of SEMM includes:
|
||||
|
||||
- Support for Surface Go 2
|
||||
- Support for Surface Book 3
|
||||
- Bug fixes
|
||||
|
||||
### Version 2.59.
|
||||
* Support to Surface Pro 7, Surface Pro X, and Surface Laptop 3 13.5" and 15" models with Intel processor. Note: Surface Laptop 3 15" AMD processor is not supported.
|
||||
- Support to Wake on Power feature
|
||||
|
||||
### Version 2.59.139.0
|
||||
|
||||
* Support for Surface Pro 7, Surface Pro X, and Surface Laptop 3 13.5" and 15" models with Intel processor. Note: Surface Laptop 3 15" AMD processor is not supported.
|
||||
|
||||
- Support for Wake on Power feature
|
||||
|
||||
### Version 2.54.139.0
|
||||
* Support to Surface Hub 2S
|
||||
|
||||
@ -33,7 +33,7 @@ There are a few things to be aware of before you start using Cortana in Windows
|
||||
|
||||
- **Troubleshooting tips.** If you run into issues, check out these [troubleshooting tips](https://go.microsoft.com/fwlink/p/?LinkId=620763).
|
||||
|
||||
### Turn on Cortana enterprise services on employees devices
|
||||
### Turn on Cortana enterprise services on employees' devices
|
||||
Your employees must connect Cortana to their Microsoft 365 account to be able to use skills like email and calendar.
|
||||
|
||||
#### Turn on Cortana enterprise services
|
||||
@ -51,6 +51,6 @@ Cortana in Windows 10, versions 1909 and earlier can only access data in your Mi
|
||||
|
||||
2. Select the app launcher icon in the upper-left and choose **Admin**.
|
||||
|
||||
3. Expand **Settings** and select **Settings**.
|
||||
3. Expand **Settings** and select **Org Settings**.
|
||||
|
||||
4. Select **Cortana** to toggle Cortana's access to Microsoft 365 data off.
|
||||
@ -34,7 +34,7 @@ Cortana requires a PC running Windows 10, version 1703 or later, as well as the
|
||||
|
||||
|**Software** |**Minimum version** |
|
||||
|---------|---------|
|
||||
|Client operating system | Desktop: <br> - Windows 10, version 2004 (recommended) <br> <br> - Windows 10, version 1703 (legacy version of Cortana) <br> <br> Mobile: Windows 10 mobile, version 1703 (legacy version of Cortana) <br> <br> For more information on the differences between Cortana in Windows 10, version 2004 and earlier versions, see **How is my data processed by Cortana** below. |
|
||||
|Client operating system | Desktop: <br> - Windows 10, version 2004 (recommended) <br> <br> - Windows 10, version 1703 (legacy version of Cortana) <br> <br> Mobile: Windows 10 mobile, version 1703 (legacy version of Cortana) <br> <br> For more information on the differences between Cortana in Windows 10, version 2004 and earlier versions, see [**How is my data processed by Cortana**](https://docs.microsoft.com/en-us/windows/configuration/cortana-at-work/cortana-at-work-overview#how-is-my-data-processed-by-cortana) below. |
|
||||
|Azure Active Directory (Azure AD) | While all employees signing into Cortana need an Azure AD account, an Azure AD premium tenant isn’t required. |
|
||||
|Additional policies (Group Policy and Mobile Device Management (MDM)) |There is a rich set of policies that can be used to manage various aspects of Cortana. Most of these policies will limit the abilities of Cortana but won't turn Cortana off. For example, if you turn **Speech** off, your employees won't be able to use the wake word (“Cortana”) for hands-free activation or voice commands to easily ask for help. |
|
||||
|
||||
@ -65,6 +65,9 @@ The table below describes the data handling for Cortana enterprise services.
|
||||
|
||||
#### How does the wake word (Cortana) work? If I enable it, is Cortana always listening?
|
||||
|
||||
>[!NOTE]
|
||||
>The wake word has been temporarily disabled in the latest version of Cortana in Windows but will be restored soon. You can still click on the microphone button to use your voice with Cortana.
|
||||
|
||||
Cortana only begins listening for commands or queries when the wake word is detected, or the microphone button has been selected.
|
||||
|
||||
First, the user must enable the wake word from within Cortana settings. Once it has been enabled, a component of Windows called the [Windows Multiple Voice Assistant platform](https://docs.microsoft.com/windows-hardware/drivers/audio/voice-activation-mva#voice-activation) will start listening for the wake word. No audio is processed by speech recognition unless two local wake word detectors and a server-side one agree with high confidence that the wake word was heard.
|
||||
@ -85,4 +88,4 @@ Cortana is covered under the [Microsoft Privacy Statement](https://privacy.micro
|
||||
|
||||
## See also
|
||||
|
||||
- [What is Cortana?](https://go.microsoft.com/fwlink/p/?LinkId=746818)
|
||||
- [What is Cortana?](https://go.microsoft.com/fwlink/p/?LinkId=746818)
|
||||
@ -14,6 +14,9 @@ manager: dansimp
|
||||
|
||||
# Test scenario 1 – Sign into Azure AD, enable the wake word, and try a voice query
|
||||
|
||||
>[!NOTE]
|
||||
>The wake word has been temporarily disabled in the latest version of Cortana in Windows but will be restored soon.
|
||||
|
||||
1. Select the **Cortana** icon in the task bar and sign in using your Azure AD account.
|
||||
|
||||
2. Select the "…" menu and select **Talking to Cortana**.
|
||||
|
||||
@ -268,7 +268,7 @@
|
||||
#### [Conclusion](update/feature-update-conclusion.md)
|
||||
### [Deploy updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](update/waas-mobile-updates.md)
|
||||
### Use Windows Update for Business
|
||||
#### [Deploy updates using Windows Update for Business](update/waas-manage-updates-wufb.md)
|
||||
#### [What is Windows Update for Business?](update/waas-manage-updates-wufb.md)
|
||||
#### [Configure Windows Update for Business](update/waas-configure-wufb.md)
|
||||
#### [Enforcing compliance deadlines for updates](update/wufb-compliancedeadlines.md)
|
||||
#### [Integrate Windows Update for Business with management solutions](update/waas-integrate-wufb.md)
|
||||
|
||||
@ -50,8 +50,8 @@ See [Deploy Windows 10 with Microsoft 365](deploy-m365.md) for an overview, whic
|
||||
## Windows 10 servicing and support
|
||||
|
||||
- [**Delivery Optimization**](https://docs.microsoft.com/windows/deployment/update/waas-delivery-optimization): Improved Peer Efficiency for enterprises and educational institutions with complex networks is enabled with of [new policies](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-deliveryoptimization). This now supports Microsoft 365 Apps for enterprise updates, and Intune content, with Microsoft Endpoint Configuration Manager content coming soon!
|
||||
- [**Automatic Restart Sign-on (ARSO)**](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#automatic-restart-and-sign-on-arso-for-enterprises-build-18305): Windows will automatically logon as the user and lock their device in order to complete the update, ensuring that when the user returns and unlocks the device, the update will be completed.
|
||||
- [**Windows Update for Business**](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523): There will now be a single, common start date for phased deployments (no more SAC-T designation). In addition, there will a new notification and reboot scheduling experience for end users, the ability to enforce update installation and reboot deadlines, and the ability to provide end user control over reboots for a specific time period.
|
||||
- [**Automatic Restart Sign-on (ARSO)**](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#automatic-restart-and-sign-on-arso-for-enterprises-build-18305): Windows will automatically log on as the user and lock their device in order to complete the update, ensuring that when the user returns and unlocks the device, the update will be completed.
|
||||
- [**Windows Update for Business**](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523): There will now be a single, common start date for phased deployments (no more SAC-T designation). In addition, there will be a new notification and reboot scheduling experience for end users, the ability to enforce update installation and reboot deadlines, and the ability to provide end user control over reboots for a specific time period.
|
||||
- **Update rollback improvements**: You can now automatically recover from startup failures by removing updates if the startup failure was introduced after the installation of recent driver or quality updates. When a device is unable to start up properly after the recent installation of Quality of driver updates, Windows will now automatically uninstall the updates to get the device back up and running normally.
|
||||
- **Pause updates**: We have extended the ability to pause updates for both feature and monthly updates. This extension ability is for all editions of Windows 10, including Home. You can pause both feature and monthly updates for up to 35 days (seven days at a time, up to five times). Once the 35-day pause period is reached, you will need to update your device before pausing again.
|
||||
- **Improved update notifications**: When there’s an update requiring you to restart your device, you’ll see a colored dot on the Power button in the Start menu and on the Windows icon in your taskbar.
|
||||
|
||||
140
windows/deployment/update/create-deployment-plan.md
Normal file
140
windows/deployment/update/create-deployment-plan.md
Normal file
@ -0,0 +1,140 @@
|
||||
---
|
||||
title: Create a deployment plan
|
||||
description: Devise the number of deployment rings you need and how you want to populate them
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Create a deployment plan
|
||||
|
||||
A service management mindset means that the devices in your organization fall into a continuum, with the software update process being constantly planned, deployed, monitored, and optimized. And once this process is used for feature updates, quality updates become a lightweight procedure that is simple and fast to execute, ultimately increasing velocity.
|
||||
|
||||
When you move to a service management model, you need effective ways of rolling out updates to representative groups of devices, and we’ve found that ring-based deployment is a methodology that works well for us at Microsoft and many other organizations across the globe. Deployment rings in Windows 10 are similar to the deployment groups most organizations constructed for previous major revision upgrades--they are simply a method by which to separate devices into a deployment timeline.
|
||||
|
||||
At the highest level, each “ring” comprise a group of users or devices that receive a particular update concurrently. For each ring, IT administrators set criteria to control deferral time or adoption (completion) that should be met before deployment to the next broader ring of devices or users can occur.
|
||||
|
||||
A common ring structure comprises three deployment groups:
|
||||
|
||||
- Preview: Planning and development
|
||||
- Limited: Pilot and validation
|
||||
- Broad: Wide deployment
|
||||
|
||||
> [!NOTE]
|
||||
> Organizations often use different names for their “rings," for example:
|
||||
> - First > Fast > Broad
|
||||
> - Canaries > Early Adopters > Users
|
||||
> - Preview > Broad > Critical
|
||||
|
||||
|
||||
## How many rings should I have?
|
||||
|
||||
There are no definite rules for exactly how many rings to have for your deployments. As mentioned previously, you might want to ensure zero downtime for mission-critical devices by putting them in their own ring. If you have a large
|
||||
organization, you might want to consider assigning devices to rings based on geographic location or the size of rings so that helpdesk resources are more available. Consider the needs of your business and introduce rings that make sense for your organization.
|
||||
|
||||
## Advancing between rings
|
||||
|
||||
There are basically two strategies for moving deployments from one ring to the next. One is service based, the other project based.
|
||||
|
||||
- "Red button" (service based): Assumes that content is good until proven bad. Content flows until an issue is discovered, at which point the IT administrator presses the “red button” to stop further distribution.
|
||||
- Green button (project based): Assumes that content is bad until proven good. Once all validation has passed, the IT administrator presses the “green button” to push the content to the next ring.
|
||||
|
||||
When it comes to deployments, having manual steps in the process usually impedes update velocity, so a "red button" strategy is better when that is your goal.
|
||||
|
||||
## Preview ring
|
||||
|
||||
The purpose of the Preview ring is to evaluate the new features of the update. This is specifically *not* for broad parts of the organization but is limited to the people who are responsible for knowing what is coming next,
|
||||
generally IT administrators. Ultimately, this is the time the design and planning work happens so that when the public update is actually shipped, you can have greater confidence in the update.
|
||||
|
||||
> [!NOTE]
|
||||
> Being part of the [Windows Insider Program](https://insider.windows.com/for-business/) gives you early access to Windows releases so that you can use Insider Preview builds in your Preview ring to validate your apps and infrastructure, preparing you for public Windows releases.
|
||||
|
||||
|
||||
### Who goes in the Preview ring?
|
||||
|
||||
The Preview ring users are the most tech savvy and resilient people, who will not lose productivity if something goes wrong. In general, these are IT pros, and perhaps a few people in the business organization.
|
||||
|
||||
During your plan and prepare phases, these are the activities you should focus on:
|
||||
|
||||
- Work with Windows Insider Preview builds.
|
||||
- Identify the features and functionality your organization can or wants to use.
|
||||
- Establish who will use the features and how they will benefit.
|
||||
- Understand why you are putting the update out.
|
||||
- Plan for usage feedback.
|
||||
|
||||
Remember, you are working with pre-release software in the Preview ring and you will be evaluating features and testing the update for a targeted release.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are using Windows Insider (pre-release) releases for your preview ring and you are using WSUS or Windows Update for Business, be sure to set the following policies to allow for Preview builds:
|
||||
> - **Manage Preview Builds: 2 - Enable preview builds**
|
||||
> • Under **Branch Readiness Level**, select **When Preview Builds and Feature Updates are Received: 4--Windows Insider Program Slow**
|
||||
|
||||
## Limited ring
|
||||
|
||||
The purpose of the Limited ring is to validate the update on representative devices across the network. During this period, data, and feedback is generated to enable the decision to move forward to broader deployment. Desktop
|
||||
Analytics can help with defining a good Limited ring of representative devices and assist in monitoring the deployment.
|
||||
|
||||
### Who goes in the Limited ring?
|
||||
|
||||
The most important part of this phase is finding a representative sample of devices and applications across your network. If possible, all hardware and all applications should be represented, and it's important that the people selected for this ring are using their devices regularly in order to generate the data you will need to make a decision for broader deployment across your organization. The IT department, lab devices, and users with the most cutting-edge hardware usually don’t have the applications or device drivers that are truly a representative sample of your network.
|
||||
|
||||
|
||||
During your pilot and validate phases, these are the activities you should focus on:
|
||||
|
||||
- Deploy new innovations.
|
||||
- Assess and act if issues are encountered.
|
||||
- Move forward unless blocked.
|
||||
|
||||
When you deploy to the Limited ring, you’ll be able to gather data and react to incidents happening in the environment, quickly addressing any issues that might arise. Ensure you monitor for sufficient adoption within this ring, because your Limited ring represents your organization across the board, and when you achieve sufficient adoption, you can have confidence that your broader deployment will run more smoothly.
|
||||
|
||||
## Broad deployment
|
||||
|
||||
Once the devices in the Limited ring have had a sufficient stabilization period, it’s time for broad deployment across the network.
|
||||
|
||||
### Who goes in the Broad deployment ring?
|
||||
|
||||
In most businesses, the Broad ring includes the rest of your organization. Because of the work in the previous ring to vet stability and minimize disruption (with diagnostic data to support your decision) broad deployment can occur relatively quickly.
|
||||
|
||||
> [!NOTE]
|
||||
> In some instances, you might hold back on mission critical devices (such as medical devices) until deployment in the Broad ring is complete. Get best practices and recommendations for deploying Windows 10 feature
|
||||
> updates to mission critical devices.
|
||||
|
||||
During the broad deployment phase, these are the activities you should focus on:
|
||||
|
||||
- Deploy to all devices in the organization.
|
||||
- Work through any final unusual issues that were not detected in your Limited ring.
|
||||
|
||||
|
||||
## Ring deployment planning
|
||||
|
||||
Previously, we have provided methods for analyzing your deployments, but these have generally been standalone tools to assess, manage and execute deployments. In other words, you would generate an analysis, make a deployment strategy, and then move to your console for implementation, repeating these steps for each deployment. We have combined many of these tasks, and more, into a single interface with Desktop Analytics.
|
||||
|
||||
|
||||
[Desktop Analytics](https://docs.microsoft.com/mem/configmgr/desktop-analytics/overview) is a cloud-based service and a key tool in [Microsoft Endpoint Manager](https://docs.microsoft.com/mem/configmgr/core/understand/microsoft-endpoint-manager-faq). Using artificial intelligence and machine learning, Desktop Analytics is a powerful tool to give you insights and intelligence to
|
||||
make informed decisions about the readiness of your Windows devices.
|
||||
|
||||
In Windows 10 deployments, we have seen compatibility issues on < 0.5% of apps when using Desktop Analytics. Using Desktop Analytics with Microsoft Endpoint Manager can help you assess app compatibility with the latest
|
||||
feature update and create groups that represent the broadest number of hardware and software configurations on the smallest set of devices across your organization. In addition, Desktop Analytics can provide you with a device and software inventory and identify issues, giving you data that equate to actionable decisions.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Desktop Analytics does not support preview (Windows Insider) builds; use Configuration Manager to deploy to your Preview ring. As noted previously, the Preview ring is a small group of devices represents your ecosystem very well in terms of app, driver, and hardware diversity.
|
||||
|
||||
### Deployment plan options
|
||||
|
||||
There are two ways to implement a ring deployment plan, depending on how you manage your devices:
|
||||
|
||||
- If you are using Configuration Manager: Desktop Analytics provides end-to-end deployment plan integration so that you can also kick off phased deployments within a ring. Learn more about [deployment plans in Desktop Analytics](https://docs.microsoft.com/mem/configmgr/desktop-analytics/about-deployment-plans).
|
||||
- If you are using Microsoft Intune, see [Create deployment plans directly in Intune](https://docs.microsoft.com/mem/intune/fundamentals/planning-guide).
|
||||
|
||||
For more about Desktop Analytics, see these articles:
|
||||
|
||||
- [How to set up Desktop Analytics](https://docs.microsoft.com/mem/configmgr/desktop-analytics/set-up)
|
||||
- [Tutorial: Deploy Windows 10 to Pilot](https://docs.microsoft.com/mem/configmgr/desktop-analytics/tutorial-windows10)
|
||||
- [Desktop Analytics documentation](https://docs.microsoft.com/mem/configmgr/desktop-analytics/overview)
|
||||
- [Intune deployment planning, design, and implementation guide](https://docs.microsoft.com/mem/intune/fundamentals/planning-guide)
|
||||
|
||||
71
windows/deployment/update/eval-infra-tools.md
Normal file
71
windows/deployment/update/eval-infra-tools.md
Normal file
@ -0,0 +1,71 @@
|
||||
---
|
||||
title: Evaluate infrastructure and tools
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description:
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
author: jaimeo
|
||||
ms.topic: article
|
||||
ms.collection: M365-modern-desktop
|
||||
---
|
||||
|
||||
# Evaluate infrastructure and tools
|
||||
|
||||
Before you deploy an update, it's best to assess your deployment infrastucture (that is, tools such as Configuration Manager, Microsoft Intune, or similar) and current configurations (such as security baselines, administrative templates, and policies that affect updates). Then, set some criteria to define your operational readiness.
|
||||
|
||||
## Infrastructure
|
||||
|
||||
Do your deployment tools need updates?
|
||||
|
||||
- If you use Configuration Manager, is it on the Current Branch with the latest release installed. This ensures that it supports the next Windows 10 feature update. Configuration Manager releases are supported for 18 months.
|
||||
- Using a cloud-based management tool like Microsoft Intune reduces support challenges, since no related products need to be updated.
|
||||
- If you use a non-Microsoft tool, check with its product support to make sure you're using the current version and that it supports the next Windows 10 feature update.
|
||||
|
||||
Rely on your experiences and data from previous deployments to help you judge how long infrastructure changes take and identify any problems you've encountered while doing so.
|
||||
|
||||
## Device settings
|
||||
|
||||
Make sure your security basline, administrative templates, and policies have the right settings to support your devices once the new Windows 10 update is installed.
|
||||
|
||||
### Security baseline
|
||||
|
||||
Keep security baslines current to help ensure that your environment is secure and that new security feature in the coming Windows 10 update are set properly.
|
||||
|
||||
- **Microsoft security baselines**: You should implement security baselines from Microsoft. They are included in the [Security Compliance Toolkit](https://www.microsoft.com/download/details.aspx?id=55319), along with tools for managing them.
|
||||
- **Industry- or region-specific baselines**: Your specific industry or region might have particular baselines that you must follow per regulations. Ensure that any new baselines support the version of Windows 10 you are about to deploy.
|
||||
|
||||
### Configuration updates
|
||||
|
||||
There are a number of Windows policies (set by Group Policy, Intune, or other methods) that affect when Windows updates are installed, deferral, end-user experience, and many other aspects. Check these policies to make sure they are set appropriately.
|
||||
|
||||
- **Windows 10 Administrative templates**: Each Windows 10 feature update has a supporting Administrative template (.admx) file. Group Policy tools use Administrative template files to populate policy settings in the user interface. The templates are available in the Download Center, for example, this one for [Windows 10, version 1909](https://www.microsoft.com/download/100591).
|
||||
- **Policies for update compliance and end-user experience**: A number of settings affect when a device installs updates, whether and for how long a user can defer an update, restart behavior after installation, and many other aspects of update behavior. It's especially important to look for existing policies that are out of date or could conflict with new ones. {SET COMPLIANCE and other policies}
|
||||
|
||||
|
||||
## Define operational readiness criteria
|
||||
|
||||
When you’ve deployed an update, you’ll need to make sure the update isn’t introducing new operational issues. And you’ll also ensure that if incidents arise, the needed documentation and processes are available. To achieve this, work with your operations and support team to define acceptable trends and what documents or processes require updating:
|
||||
|
||||
- **Call trend**: Define what percentage increase in calls relating to Windows 10 feature updates are acceptable or can be supported.
|
||||
- **Incident trend**: Define what percentage of increase in calls asking for support relating to Windows 10 feature updates are acceptable or can be supported.
|
||||
- **Support documentation**: Review supporting documentation that requires an update to support new infrastructure tooling or configuration as part of the Windows 10 feature update.
|
||||
- **Process changes:** Define and update any processes that will change as a result of the Windows 10 feature update.
|
||||
|
||||
Your operations and support staff can help you determine if the appropriate information is being tracked at the moment. If it isn't, work out how to get get this information so you can gain the right insight.
|
||||
|
||||
## Tasks
|
||||
|
||||
Finally, you can begin to carry out the work needed to ensure your infrastructure and configuration can support the update. To help you keep track, you can classify the work into the following overarching tasks:
|
||||
|
||||
- **Review infrastructure requirements**: Go over the details of requirements to support the update, and ensure they’ve all been defined.
|
||||
- **Validate infrastructure against requirements**: Compare your infrastructure against the requirements that have been identified for the update.
|
||||
- **Define infrastructure update plan**: Detail how your infrastructure must change to support the update.
|
||||
- **Review current support volume**: Understand the current support volume to understand how much of an effect the update has when it’s been deployed.
|
||||
- **Identify gaps that require attention**: Identify issues that will need to be addressed to successfully deploy the update. For example, will your infrastructure engineer have to research how a new feature that comes with the update might affect the infrastructure?
|
||||
- **Define operational update plan**: Detail how your operational services and processes must change to support the update.
|
||||
204
windows/deployment/update/update-policies.md
Normal file
204
windows/deployment/update/update-policies.md
Normal file
@ -0,0 +1,204 @@
|
||||
---
|
||||
title: Policies for update compliance, activity, and end-user experience
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description:
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
audience: itpro
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
author: jaimeo
|
||||
ms.topic: article
|
||||
ms.collection: M365-modern-desktop
|
||||
---
|
||||
|
||||
# Policies for update compliance, activity, and end-user experience
|
||||
Keeping devices up to date is the best way to keep them working smoothly and securely.
|
||||
|
||||
## Deadlines for update compliance
|
||||
|
||||
You can control how strictly devices must reliably keep to your desired update schedule by using update deadline policies. Windows components adapt based on these deadlines. Also, they can make tradeoffs between user experience and velocity in order to meet your desired update deadlines. For example, they can prioritize user experience well before the
|
||||
deadline approaches, and then prioritize velocity as the deadline nears, while still affording the user some control.
|
||||
|
||||
### Deadlines
|
||||
|
||||
Beginning with Windows 10, version 1903 and with the August 2019 security update for Windows 10, version 1709
|
||||
and late, a new policy was introduced to replace older deadline-like policies: **Specify deadlines for automatic updates and restarts**.
|
||||
|
||||
The older policies started enforcing deadlines once the device reached a “restart pending” state for
|
||||
an update. The new policy starts the countdown for the update installation deadline from when the
|
||||
update is published plus any deferral. In addition, this policy includes a configurable grace period and the option
|
||||
to opt out of automatic restarts until the deadline is reached (although we recommend always allowing automatic
|
||||
restarts for maximum update velocity).
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you use the new **Specify deadlines for automatic updates and restarts** setting in Windows 10,
|
||||
> version 1903, you must disable the [older deadline policies](wufb-compliancedeadlines.md#prior-to-windows-10-version-1709) because they could conflict.
|
||||
|
||||
We recommend you set deadlines as follows:
|
||||
- Quality update deadline, in days: 3
|
||||
- Feature update deadline, in days: 7
|
||||
-
|
||||
Notifications are automatically presented to the user at appropriate times, and users can choose to be reminded
|
||||
later, to reschedule, or to restart immediately, depending on how close the deadline is. We recommend that you
|
||||
do **not** set any notification policies, because they are automatically configured with appropriate defaults. An exception is if you
|
||||
have kiosks or digital signage.
|
||||
|
||||
While three days for quality updates and seven days for feature updates is our recommendation, you might decide
|
||||
you want more or less, depending on your organization and its requirements, and this policy is configurable down
|
||||
to a minimum of two days.
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If the device is unable to reach the Internet, it can't determine when Microsoft
|
||||
> published the update, so it won't be able to enforce the deadline. Learn more about [low activity devices](#device-activity-policies).
|
||||
|
||||
### Grace periods
|
||||
|
||||
You can set a period of days for Windows to find a minimally disruptive automatic restart time before the restart is enforced. This
|
||||
is especially useful in cases where a user has been away for many days (for example, on vacation) so that the device will not
|
||||
be forced to update immediately when the user returns.
|
||||
|
||||
We recommend you set the following:
|
||||
|
||||
- Grace period, in days: 2
|
||||
|
||||
Once the deadline and grace period have passed, updates are applied automatically, and a restart occurs
|
||||
regardless of [active hours](#active-hours).
|
||||
|
||||
|
||||
### Let Windows choose when to restart
|
||||
|
||||
Windows can use user interactions to dynamically identify the least disruptive time for an
|
||||
automatic restart. To take advantage of this feature, ensure **ConfigureDeadlineNoAutoReboot** is set to
|
||||
**Disabled**.
|
||||
|
||||
## Device activity policies
|
||||
|
||||
Windows typically requires that a device is active and connected to the internet for at least six hours, with at least two
|
||||
of continuous activity {HOW DO YOU DEFINE ACTIVITY?}, in order to successfully complete a system update. The device could have other
|
||||
physical circumstances that prevent successful installation of an update--for example, if a laptop is running low
|
||||
on battery power, or the user has shut down the device before active hours end and the device cannot comply
|
||||
with the deadline.
|
||||
|
||||
You can use the settings in this section to ensure that devices are actually available to install updates during the update compliance period.
|
||||
|
||||
### Active hours
|
||||
|
||||
"Active hours" identify the period of time when a device is expected to be in use. Normally, restarts will occur outside of
|
||||
these hours. Windows 10, version 1903 introduced "intelligent active hours," which allow the system to learn active hours based on a user’s activities, rather than you as an administrator having to make decisions for your organization or allowing the user to choose active hours that minimize the period when the system can install an update.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you used the **Configure Active Hours** setting in previous versions of Windows 10, these
|
||||
options must be **Disabled** in order to take advantage of intelligent active hours.
|
||||
|
||||
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-reboot). While it’s possible to set the system to delay restarts for users who are logged
|
||||
in, this 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**:
|
||||
- **Turn off auto-restart during active hours**
|
||||
- **No auto-restart with logged on users for scheduled automatic updates**
|
||||
|
||||
- [Limit restart delays](waas-restart.md#limit-restart-delays). By using compliance deadlines, your users will receive notifications that
|
||||
updates will occur, so we recommend that you set this policy to **Disabled**, to allow compliance deadlines to eliminate the user’s ability to delay a restart outside of compliance deadline settings.
|
||||
|
||||
- **Do not allow users to approve updates and reboots**. Letting users approve or engage with the update process outside of the deadline policies decreases update velocity and increases risk. These policies should be set to **Disabled**:
|
||||
- [Update/RequireUpdateApproval](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-requireupdateapproval)
|
||||
- [Update/EngagedRestartDeadline](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-engagedrestartdeadline)
|
||||
- [Update/EngagedRestartDeadlineForFeatureUpdates](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-engagedrestartdeadlineforfeatureupdates)
|
||||
- [Update/EngagedRestartSnoozeSchedule](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-engagedrestartsnoozeschedule)
|
||||
- [Update/EngagedRestartSnoozeScheduleForFeatureUpdates](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-engagedrestartsnoozescheduleforfeatureupdates)
|
||||
- [Update/EngagedRestartTransitionSchedule](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-engagedrestarttransitionschedule)
|
||||
|
||||
- [Configure automatic update](waas-wu-settings.md#configure-automatic-updates). By properly setting policies to configure automatic updates, you can increase update velocity by having clients contact a Windows Server Update Services (WSUS) server so it can manage them. We recommend that you set this policy to **Disabled**. However, if you need to provide values, ensure that you set downloads to install automatically by setting the [Group Policy](waas-manage-updates-wsus.md#configure-automatic-updates-and-update-service-location) to **4**. If you’re using Microsoft Intune, setting the value to [Reset to Default](https://docs.microsoft.com/mem/intune/protect/windows-update-settings#user-experience-settings).
|
||||
- **Allow auto Windows Update to download over metered networks**. Since more and more devices primarily use cellular data and do not have wi-fi access, consider allowing users to automatically download updates from a metered network. Though the default setting does not allow download over a metered network, setting this value to **1** can increase velocity by enabling users to get updates whether they are connected to the internet or not, provided they have cellular service.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Older versions of Windows don't support intelligent active hours. If your device runs a version of Windows prior to Windows 10, version 1903, we recommend setting the following policies:
|
||||
>- [Configure active hours](waas-restart.md#configure-active-hours). Starting with Windows 10, version 1703, you can specify a maximum active-hour range which is counted from the active hours start time. We recommend setting
|
||||
this value to **10**.
|
||||
>- [Schedule update installation](waas-restart.md#schedule-update-installation). In the **Configure Automatic Updates** settings, there are two ways to control a forced restart after a specified installation time. If you use **schedule update installation**, do not enable both settings because they will most likely conflict.
|
||||
> - **Specify automatic maintenance time**. This setting lets you set broader maintenance windows for updates and ensures that this schedule does not conflict with active hours. We
|
||||
recommend setting this value to **3** (corresponding to 3 AM). If 3:00 AM is in the middle of the work shift, pick another time that is at least a couple hours before your scheduled work time begins.
|
||||
> - **Schedule the install time**. This setting allows you to schedule an installation time for a restart. We do *not* recommend you set this to **Disabled** as it could conflict with active hours.
|
||||
|
||||
### Power policies
|
||||
|
||||
Devices must actually be available during non-active hours in order to an update. They can't do this if power policies prevent them from waking up. In our organization, we strive to set a balance between security and eco-friendly configurations. We recommend the following settings to achieve what we feel are the appropriate tradeoffs:
|
||||
|
||||
To a user, a device is either on or off, but for Windows, there are states that will allow an update to occur (active) and states that do not (inactive). Some states are considered active (sleep), but the user may think the device is off. Also, there are power statuses (plugged in/battery) that Windows checks before starting an update.
|
||||
|
||||
You can override the default settings and prevent users from changing them in order to ensure that devices are available for updates during non-active hours.
|
||||
|
||||
> [!NOTE]
|
||||
> One way to ensure that devices can install updates when you need them to is to educate your users to keep devices plugged in during non-active hours. Even with the best policies, a device that isn't plugged in will not be updated, even in sleep mode.
|
||||
|
||||
We recommend these power management settings:
|
||||
|
||||
- Sleep mode (S1 or S0 Low Power Idle or [Modern Standby](https://docs.microsoft.com/windows-hardware/design/device-experiences/modern-standby)). When a device is in sleep mode, the system
|
||||
appears to be off but if an update is available, it can wake the device up in order to take an update. The
|
||||
power consumption in sleep mode is between working (system fully usable) and hibernate (S4 - lowest
|
||||
power level before shutdown). When a device is not being used, the system will generally move to sleep
|
||||
mode before it goes to hibernate. Issues in velocity arise when the time between sleep and hibernate is
|
||||
too short and Windows does not have time to complete an update. Sleep mode is an important setting
|
||||
because the system can wake the system from sleep in order to start the update process, as long as there
|
||||
is enough power.
|
||||
|
||||
Set the following policies to **Enable** or **Do Not Configure** in order to allow the device to use sleep mode:
|
||||
- [Power/AllowStandbyStatesWhenSleepingOnBattery](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-power#power-allowstandbystateswhensleepingonbattery)
|
||||
- [Power/AllowStandbyWhenSleepingPluggedIn](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-power#power-selectlidcloseactionpluggedin)
|
||||
|
||||
Set the following policies to **1 (Sleep)** so that when a user closes the lid of a device, the system goes to
|
||||
sleep mode and the device has an opportunity to take an update:
|
||||
- [Power/SelectLidCloseActionOnBattery](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-power#power-selectlidcloseactiononbattery)
|
||||
- [Power/SelectLidCloseActionPluggedIn](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-power#power-selectlidcloseactionpluggedin)
|
||||
|
||||
- **Hibernate**. When a device is hibernating, power consumption is very low and the system cannot wake up
|
||||
without user intervention, like pressing the power button. If a device is in this state, it cannot be updated
|
||||
unless it supports an ACPI Time and Alarm Device (TAD). That said, if a device supporting Traditional Sleep
|
||||
(S3) is plugged in, and a Windows update is available, a hibernate state will be delayed until the update is complete.
|
||||
|
||||
> [!NOTE]
|
||||
> This does not apply to devices that support Modern Standby (S0 Low Power Idle). You can check which system sleep state (S3 or S0 Low Power Idle) a device supports by running `powercfg /a` at a command prompt. For more, see [Powercfg options](https://docs.microsoft.com/windows-hardware/design/device-experiences/powercfg-command-line-options#option_availablesleepstates).
|
||||
|
||||
The default timeout on devices that support traditional sleep is set to three hours. We recommend that you do not reduce these policies in order to allow Windows Update the opportunity to restart the device before sending it into hibernation:
|
||||
|
||||
- [Power/HibernateTimeoutOnBattery](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-power#power-hibernatetimeoutonbattery)
|
||||
- [Power/HibernateTimeoutPluggedIn](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-power#power-hibernatetimeoutpluggedin)
|
||||
|
||||
## Old or conflicting policies
|
||||
|
||||
Each release of Windows 10 can introduce new policies to make the experience better for both administrators and their organizations. When we release a new client policy, we either release it purely for that release and later or we backport the policy to make it available on earlier versions.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are using Group Policy, note that we don't update the old ADMX templates and you must use the newer (1903) ADMX template in order to use the newer policy. Also, if you are
|
||||
> using an MDM tool (Microsoft or non-Microsoft), you can't use the new policy until it's available in the tool interface.
|
||||
|
||||
As administrators, you have set up and expect certain behaviors, so we expressly do not remove older policies since they were set up for your particular use cases. However, if you set a new policy without disabling a similar older policy, you could have conflicting behavior and updates might not perform as expected.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> We sometimes find that administrators set devices to get both Group Policy settings and MDM settings from an MDM server such as Microsoft Intune. Policy conflicts are handled differently, depending on how they are ultimately set up:
|
||||
> - Windows updates: Group Policy settings take precedence over MDM.
|
||||
> - Microsoft Intune: If you set different values for the same policy on two different groups, you will
|
||||
> receive an alert and neither policy will be set until the conflict is resolved.
|
||||
> It is crucial that you disable conflicting policies in order for devices in your organization to take updates as
|
||||
> 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.
|
||||
|
||||
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
|
||||
deferral) so that the feature update can complete and monthly security updates will be offered again. Even if there is an urgent quality update that must be quickly deployed, it is best to use **Pause Feature
|
||||
Updates** rather than setting a deferral policy. You can choose a longer period if you don't want to stay up to date with the latest feature update.
|
||||
- **Defer Quality Updates Period in Days**. To minimize risk and maximize update velocity, the maximum time you might want to consider while evaluating the update with a different ring of devices is two to three days.
|
||||
- **Pause Feature Updates Start Time**. Set to **Disabled** unless there is a known issue requiring time for a resolution.
|
||||
- **Pause Quality Updates Start Time**. Set to **Disabled** unless there is a known issue requiring time for a resolution.
|
||||
- **Deadline No Auto Reboot**. Default is **Disabled – Set to 0** . We recommend that devices automatically try to restart when an update is received. Windows uses user interactions to dynamically identify the least disruptive time to restart.
|
||||
|
||||
There are additional policies are no longer supported or have been superseded. See {LINK TO Policies and settings reference guide – Policies to disable or not configure} for more information.
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Deploy updates using Windows Update for Business (Windows 10)
|
||||
title: Windows Update for Business (Windows 10)
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: Windows Update for Business lets you manage when devices received updates from Windows Update.
|
||||
@ -11,24 +11,118 @@ ms.author: jaimeo
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Deploy updates using Windows Update for Business
|
||||
# What is Windows Update for Business?
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
- Windows Server 2019
|
||||
|
||||
Windows Update for Business is a free service that is available for Windows Pro, Enterprise, Pro for Workstation, and Education editions.
|
||||
|
||||
Windows Update for Business is a free service that is available for all premium editions including Windows 10 Pro, Enterprise, Pro for Workstation, and Education editions.
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
|
||||
|
||||
Windows Update for Business enables IT administrators to keep the Windows 10 devices in their organization always up to date with the latest security defenses and Windows features by directly connecting these systems to Windows Update service. You can use Group Policy or MDM solutions such as Microsoft Intune to configure the Windows Update for Business settings that control how and when Windows 10 devices are updated.
|
||||
Windows Update for Business enables IT administrators to keep the Windows 10 devices in their organization always up to date with the latest security defenses and Windows features by directly connecting these systems to Windows Update service. You can use Group Policy or Mobile Device Management (MDM) solutions such as Microsoft Intune to configure the Windows Update for Business settings that control how and when Windows 10 devices are updated.
|
||||
|
||||
Specifically, Windows Update for Business allows for control over update offering and experience to allow for reliability and performance testing on a subset of systems before rolling out updates across the organization as well as a positive update experience for those within your organization.
|
||||
Specifically, Windows Update for Business allows for control over update offerings and experiences to allow for reliability and performance testing on a subset of devices before deploying updates across the organization as well as a positive update experience for those in your organization.
|
||||
|
||||
## What can I do with Windows Update for Business?
|
||||
|
||||
Windows Update for Business enables commercial customers to manage which Windows Updates are received when as well as the experience a device has when it receives them.
|
||||
|
||||
You can control Windows Update for Business policies by using either Mobile Device Management (MDM) tools such as Microsoft Intune or Group Policy management tools such as local group policy or the Group Policy Management Console (GPMC), as well as a variety of other non-Microsoft management tools. MDMs use Configuration Service Provider (CSP) policies instead of Group Policy. Intune additionally uses Cloud Policies. Not all policies are available in all formats (CSP, Group Policy, or Cloud policy).
|
||||
|
||||
|
||||
### Manage deployment of Windows Updates
|
||||
By using Windows Update for Business, you can control which types of Windows Updates are offered to devices in your ecosystem, when updates are applied, and deployment to devices in your organization in waves.
|
||||
|
||||
### Manage which updates are offered
|
||||
Windows Update for Business enables an IT administrator to receive and manage a variety of different types of Windows Updates.
|
||||
|
||||
## Types of updates managed by Windows Update for Business
|
||||
|
||||
Windows Update for Business provides management policies for several types of updates to Windows 10 devices:
|
||||
|
||||
- **Feature updates:** Previously referred to as "upgrades," feature updates contain not only security and quality revisions, but also significant feature additions and changes. Feature updates are released semi-annually in the fall and in the spring.
|
||||
- **Quality updates:** These are traditional operating system updates, typically released on the second Tuesday of each month (though they can be released at any time). These include security, critical, and driver updates. Windows Update for Business also treats non-Windows updates (such as those for Microsoft Office or Visual Studio) as quality updates. These non-Windows Updates are known as "Microsoft updates" and you can set devices to receive such updates (or not) along with their Windows updates.
|
||||
- **Driver updates:** These are non-Microsoft drivers that are applicable to your devices. Driver updates are on by default, but you can use Windows Update for Business policies to turn them off if you prefer.
|
||||
- **Microsoft product updates**: These are updates for other Microsoft products, such as Office. Product updates are off by default. You can turn them on by using Windows Update for Business policies.
|
||||
|
||||
|
||||
## Offering
|
||||
You can control when updates are applied, for example by deferring when an update is installed on a device or by pausing updates for a certain period.
|
||||
|
||||
### Manage when updates are offered
|
||||
You can defer or pause the installation of updates for a set period of time.
|
||||
|
||||
#### Enroll in pre-release updates
|
||||
|
||||
The branch readiness level enables administrators to specify which channel of feature updates they want to receive. Today there are branch readiness level options for both pre-release and released updates:
|
||||
|
||||
- Windows Insider Fast
|
||||
- Windows Insider Slow
|
||||
- Windows Insider Release Preview
|
||||
- Semi-annual Channel
|
||||
|
||||
Prior to Windows 10, version 1903, there are two channels for released updates: Semi-annual Channel and Semi-annual Channel (Targeted). Deferral days are calculated against the release date of the chosen channel. Starting with Windows 10, version 1903 there is only the one release channel: Semi-annual Channel. All deferral days are calculated against a release’s Semi-annual Channel release date. For exact release dates, see [Windows Release Information](https://docs.microsoft.com/windows/release-information/). You can set the branch readiness level by using the **Select when Preview Builds and Feature Updates are Received** policy. To use this policy to manage pre-release builds, first enable preview builds by using the **Manage preview Builds** policy.
|
||||
|
||||
#### Defer an update
|
||||
|
||||
A Windows Update for Business administrator can defer the installation of both feature and quality updates from deploying to devices within a bounded range of time from when those updates are first made available on the Windows Update service. You can use this deferral to allow time to validate deployments as they are pushed to devices. Deferrals work by allowing you to specify the number of days after an update is released before it is offered to a device. That is, if you set a feature update deferral period of 365 days, the device will not install a feature update that has been released for less than 365 days. To defer feature updates use the **Select when Preview Builds and Feature Updates are Received** policy.
|
||||
|
||||
|
||||
|Category |Maximum deferral period |
|
||||
|---------|---------|
|
||||
|Feature updates | 365 days |
|
||||
|Quality updates | 30 days |
|
||||
|Non-deferrable | none |
|
||||
|
||||
<!--Example: Using deferrals to deploy in waves
|
||||
[Insert graphic with the deferrals set to different values showing a feature update rollout)-->
|
||||
|
||||
#### Pause an update
|
||||
|
||||
If you discover a problem while deploying a feature or quality update, the IT administrator can pause the update for 35 days from a specified start date to prevent other devices from installing it until the issue is mitigated.
|
||||
If you pause a feature update, quality updates are still offered to devices to ensure they stay secure. The pause period for both feature and quality updates is calculated from a start date that you set.
|
||||
|
||||
To pause feature updates use the **Select when Preview Builds and Feature Updates are Received** policy and to pause quality updates use the **Select when Quality Updates are Received** policy. For more information, see [Pause feature updates](waas-configure-wufb.md#pause-feature-updates) and [Pause quality updates](waas-configure-wufb.md#pause-quality-updates).
|
||||
|
||||
Built in benefits:
|
||||
When updating from Windows Update you get the added benefits of built in compatibility checks to prevent against a poor update experience for your device as well as a check to prevent repeated rollbacks.
|
||||
|
||||
### Recommendations
|
||||
|
||||
For the best experience with Windows Update, follow these guidelines:
|
||||
|
||||
- Use devices for at least 6 hours per month, including at least 2 hours of continuous use.
|
||||
- Keep devices regularly charged. Plugging in devices overnight enables them to automatically update outside of active hours.
|
||||
- Make sure that devices have at least 10 GB of free space.
|
||||
- Give devices unobstructed access to the Windows Update service.
|
||||
|
||||
### Manage the end-user experience when receiving Windows Updates
|
||||
|
||||
Windows Update for Business provides controls to help meet your organization’s security standards as well as provide a great end-user experience. We do this by enabling you to set automatic updates at times that work well for those in your organization and set deadlines for quality and feature updates. Because Windows Update includes built-in intelligence, it's usually better to use fewer controls to manage the end-user experience.
|
||||
|
||||
#### Recommended experience settings
|
||||
|
||||
Features like the smart busy check (which ensure updates don't happen when a user is signed in) and active hours help provide the best experience for end users while keeping devices more secure and up to date. Follow these steps to take advantage of these features:
|
||||
|
||||
1. Automatically download, install and restart (default if no restart policies are set up or enabled)
|
||||
2. Use the default notifications
|
||||
3. Set update deadlines
|
||||
|
||||
##### Setting deadlines
|
||||
|
||||
A compliance deadline policy (released in June 2019) enables you to set separate deadlines and grace periods for feature and quality updates.
|
||||
|
||||
This policy enables you to specify the number of days from an update's publication date that it must be installed on the device. The policy also includes a configurable grace period that specifies the number of days from when the update is installed on the device until the device is forced to restart. This is extremely beneficial in a vacation scenario as it allows, for example, users who have been away to have a bit of time before being forced to restart their devices when they return from vacation.
|
||||
|
||||
|
||||
|
||||
|
||||
<!--
|
||||
|
||||
>[!NOTE]
|
||||
> To use Windows Update for Business, you must allow devices to access the Windows Update service.
|
||||
@ -120,22 +214,6 @@ For more information about Update Compliance, see [Monitor Windows Updates using
|
||||
|  | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |
|
||||
|  | Deploy updates using Windows Update for Business (this topic) </br>or [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)</br>or [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](waas-manage-updates-configuration-manager.md) |
|
||||
|
||||
## Related topics
|
||||
- [Update Windows 10 in the enterprise](index.md)
|
||||
- [Overview of Windows as a service](waas-overview.md)
|
||||
- [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md)
|
||||
- [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md)
|
||||
- [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md)
|
||||
- [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md)
|
||||
- [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md)
|
||||
- [Configure BranchCache for Windows 10 updates](waas-branchcache.md)
|
||||
- [Deploy updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md)
|
||||
- [Configure Windows Update for Business](waas-configure-wufb.md)
|
||||
- [Integrate Windows Update for Business with management solutions](waas-integrate-wufb.md)
|
||||
- [Walkthrough: use Group Policy to configure Windows Update for Business](waas-wufb-group-policy.md)
|
||||
- [Walkthrough: use Intune to configure Windows Update for Business](https://docs.microsoft.com/intune/windows-update-for-business-configure)
|
||||
- [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)
|
||||
- [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](waas-manage-updates-configuration-manager.md)
|
||||
- [Manage device restarts after updates](waas-restart.md)
|
||||
|
||||
|
||||
|
||||
|
||||
218
windows/deployment/update/waas-wufb-csp-mdm.md
Normal file
218
windows/deployment/update/waas-wufb-csp-mdm.md
Normal file
@ -0,0 +1,218 @@
|
||||
---
|
||||
title: Configure Windows Update for Business by using CSPs and MDM
|
||||
description: Walk-through demonstration of how to configure Windows Update for Business settings using Configuration Service Providers and MDM.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Walkthrough: Use CSPs and MDMs to configure Windows Update for Business
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
|
||||
## Overview
|
||||
|
||||
You can use Configuration Service Provider (CSP) policies to control how Windows Update for Business works by using a Mobile Device Management (MDM) tool. You should consider and devise a deployment strategy for updates before you make changes to the Windows Update for Business settings.
|
||||
|
||||
An IT administrator can set policies for Windows Update for Business by using Microsoft Intune or a non-Microsoft MDM tool.
|
||||
|
||||
To manage updates with Windows Update for Business, you should prepare with these steps, if you haven't already:
|
||||
|
||||
- Create Active Directory security groups that align with the deployment rings you use to phase deployment of updates. See [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) to learn more about deployment rings in Windows 10.
|
||||
- Allow access to the Windows Update service.
|
||||
|
||||
|
||||
## Manage Windows Update offerings
|
||||
|
||||
You can control when updates are applied, for example by deferring when an update is installed on a device or by pausing updates for a certain period of time.
|
||||
|
||||
### Determine which updates you want offered to your devices
|
||||
|
||||
Both Windows 10 feature and quality updates are automatically offered to devices that are connected to Windows Update using Windows Update for Business policies. However, you can choose whether you want the devices to additionally receive other Microsoft Updates or drivers that are applicable to that device.
|
||||
|
||||
To enable Microsoft Updates use [Update/AllwMUUpdateService](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowmuupdateservice).
|
||||
|
||||
Drivers are automatically enabled because they are beneficial to device systems. We recommend that you allow the driver policy to allow drivers to updated on devices (the default), but you can turn this setting off if you prefer to manage drivers manually. If you want to disable driver updates for some reason, use Update/[ExcludeWUDriversInQualityUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-excludewudriversinqualityupdate).
|
||||
|
||||
We also recommend that you allow Microsoft product updates as discussed previously.
|
||||
|
||||
### Set when devices receive feature and quality updates
|
||||
|
||||
#### I want to receive pre-release versions of the next feature update
|
||||
|
||||
1. Ensure that you are enrolled in the Windows Insider Program for Business. This is a completely free program available to commercial customers to aid them in their validation of feature updates before they are released. Joining the program enables you to receive updates prior to their release as well as receive emails and content related to what is coming in the next updates.
|
||||
2. For any of test devices you want to install pre-release builds, use [Update/ManagePreviewBuilds](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-managepreviewbuilds). Set this to **Enable preview builds**.
|
||||
3. Use [Update/BranchReadinessLevel](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-branchreadinesslevel) and select one of the preview Builds. Windows Insider Program Slow is the recommended channel for commercial customers who are using pre-release builds for validation.
|
||||
4. Additionally, you can defer pre-release feature updates the same way as released updates, by setting a deferral period up to 14 days by using [Update/DeferFeatureUpdatesPeriodInDays](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-deferfeatureupdatesperiodindays). If you are testing with Windows Insider Program Slow builds, we recommend that you receive the preview updates to your IT department on day 0, when the update is released, and then have a 7-10 day deferral before rolling out to your group of testers. This ensures that if a problem is discovered, you can pause the rollout of the preview update before it reaches your tests.
|
||||
|
||||
#### I want to manage which released feature update my devices receive
|
||||
|
||||
A Windows Update for Business administrator can defer or pause updates. You can defer feature updates for up to 365 days and defer quality updates for up to 30 days. Deferring simply means that you will not receive the update until it has been released for at least the number of deferral days you specified (offer date = release date + deferral date). You can pause feature or quality updates for up to 35 days from a given start date that you specify.
|
||||
|
||||
- To defer a feature update: [Update/DeferFeatureUpdatesPeriodInDays](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-deferfeatureupdatesperiodindays)
|
||||
- To pause a feature update: [Update/PauseFeatureUpdatesStartTime](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-pausefeatureupdatesstarttime)
|
||||
- To defer a quality update: [Update/DeferQualityUpdatesPeriodInDays](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-deferqualityupdatesperiodindays)
|
||||
- To pause a quality update: [Update/PauseQualityUpdatesStartTime](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-pausequalityupdatesstarttime)
|
||||
|
||||
#### Example
|
||||
|
||||
In this example, there are three rings for quality updates. The first ring ("pilot") has a deferral period of 0 days. The second ring ("fast") has a deferral of five days. The third ring ("slow") has a deferral of ten days.
|
||||
|
||||
|
||||
|
||||
When the quality update is released, it is offered to devices in the pilot ring the next time they scan for updates.
|
||||
|
||||
##### Five days later
|
||||
The devices in the fast ring are offered the quality update the next time they scan for updates.
|
||||
|
||||
|
||||
|
||||
##### Ten days later
|
||||
Ten days after the quality update is released, it is offered to the devices in the slow ring the next time they scan for updates.
|
||||
|
||||
|
||||
|
||||
If no problems occur, all of the devices that scan for updates will be offered the quality update within ten days of its release, in three waves.
|
||||
|
||||
##### What if a problem occurs with the update?
|
||||
|
||||
In this example, some problem is discovered during the deployment of the update to the "pilot" ring.
|
||||
|
||||
|
||||
|
||||
At this point, the IT administrator can set a policy to pause the update. In this example, the admin selects the **Pause quality updates** check box.
|
||||
|
||||
|
||||
|
||||
Now all devices are paused from updating for 35 days. When the pause is removed, they will be offered the *next* quality update, which ideally will not have the same issue. If there is still an issue, the IT admin can pause updates again.
|
||||
|
||||
|
||||
|
||||
|
||||
#### I want to stay on a specific version
|
||||
|
||||
If you need a device to stay on a version beyond the point when deferrals on the next version would elapse or if you need to skip a version (for example, update fall release to fall release) use the **Select the target Feature Update version** setting instead of using the Update/TargetReleaseVersion (or DeployFeatureUpdates in Windows 10, version 1803 and later) setting for feature update deferrals. When you use this policy, specify the version that you want your device(s) to use. If you don't update this before the device reaches end of service, the device will automatically be updated once it is 60 days past end of service for its edition.
|
||||
|
||||
### Manage how users experience updates
|
||||
|
||||
#### I want to manage when devices download, install, and restart after updates
|
||||
|
||||
We recommended that you allow to update automatically--this is the default behavior. If you don't set an automatic update policy, the device will attempt to download, install, and restart at the best times for the user by using built-in intelligence such as intelligent active hours and smart busy check.
|
||||
|
||||
For more granular control, you can set the maximum period of active hours the user can set with [Update/ActiveHoursMaxRange](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-activehoursmaxrange). You could also set specific start and end times for active ours with [Update/ActiveHoursEnd](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-activehoursend) and [Update/ActiveHoursStart](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-activehoursstart).
|
||||
|
||||
It's best to refrain from setting the active hours policy because it's enabled by default when automatic updates are not disabled and provides a better experience when users can set their own active hours.
|
||||
|
||||
To update outside of the active hours, use [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) with Option 2 (which is the default setting). For even more granular control, consider using automatic updates to schedule the install time, day, or week. To do this, use Option 3, and then set the following policies as appropriate for your plan:
|
||||
|
||||
- [Update/ScheduledInstallDay](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstallday)
|
||||
- [Update/ScheduledInstallEveryWeek](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstalleveryweek)
|
||||
- [Update/ScheduledInstallFirstWeek](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstallfirstweek)
|
||||
- [Update/ScheduledInstallFourthWeek](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstallfourthweek)
|
||||
- [Update/ScheduledInstallSecondWeek](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstallsecondweek)
|
||||
- [Update/ScheduledInstallThirdWeek](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstallthirdweek)
|
||||
- [Update/ScheduledInstallTime](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstalltime)
|
||||
|
||||
|
||||
When you set these policies, installation happens automatically at the specified time and the device will restart 15 minutes after installation is complete (unless it's interrupted by the user).
|
||||
|
||||
If you don't want to allow any automatic updates prior to the deadline, set [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate) to Option 5, which turns off automatic updates.
|
||||
|
||||
#### I want to keep devices secure and compliant with update deadlines
|
||||
|
||||
We recommend that you use set specific deadlines for feature and quality updates to ensure that devices stay secure on Windows 10, version 1709 and later. This works by enabling you to specify the number of days that can elapse after an update is offered to a device before it must be installed. Also you can set the number of days that can elapse after a pending restart before the user is forced to restart. Use these settings:
|
||||
|
||||
- [Update/ConfigureDeadlineForFeatureUpdates](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-configuredeadlineforfeatureupdates)
|
||||
- [Update/ConfigureDeadlineForQualityUpdates ](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-configuredeadlineforqualityupdates)
|
||||
- [Update/ConfigureDeadlineGracePeriod](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-configuredeadlinegraceperiod)
|
||||
- [Update/ConfigureDeadlineNoAutoReboot](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-configuredeadlinenoautoreboot)
|
||||
|
||||
These policies also offer an option to opt out of automatic restarts until a deadline is reached by presenting an "engaged restart experience" until the deadline has actually expired. At that point the device will automatically schedule a restart regardles of active hours.
|
||||
|
||||
These notifications are what the user sees depending on the settings you choose:
|
||||
|
||||
When **Specify deadlines for automatic updates and restarts** is set (For Windows 10, version 1709 and later):
|
||||
|
||||
- **While restart is pending, before the deadline occurs:**
|
||||
|
||||
- For the first few days, the user receives a toast notification
|
||||
|
||||
- After this period, the user receives this dialog:
|
||||
|
||||
|
||||
|
||||
- If the user scheduled a restart, or if an auto restart is scheduled, 15 minutes before the scheduled time the user is receives this notification that the restart is about to occur:
|
||||
|
||||
|
||||
|
||||
- **If the restart is still pending after the deadline passes:**
|
||||
|
||||
- Within 12 hours before the deadline passes, the user receives this notification that the deadline is approaching:
|
||||
|
||||
|
||||
|
||||
- Once the deadline has passed, the user is forced to restart to keep their devices in compliance and receives this notification:
|
||||
|
||||
|
||||
|
||||
#### I want to manage the notifications a user sees
|
||||
|
||||
There are additional settings that affect the notifications.
|
||||
|
||||
We recommend that you use the default notifications as they aim to provide the best user experience while adjusting for the compliance policies that you have set. If you do have further needs that are not met by the default notification settings, you can use the [Update/UpdateNotificationLevel](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updatenotificationlevel) policy with these values:
|
||||
|
||||
**0** (default) – Use the default Windows Update notifications
|
||||
**1** – Turn off all notifications, excluding restart warnings
|
||||
**2** – Turn off all notifications, including restart warnings
|
||||
|
||||
> [!NOTE]
|
||||
> Option **2** creates a poor experience for personal devices; it's only recommended for kiosk devices where automatic restarts have been disabled.
|
||||
|
||||
Still more options are available in [Update/ScheduleRestartWarning](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-schedulerestartwarning). This setting allows you to specify the period for auto-restart warning reminder notifications (from 2-24 hours; 4 hours is the default) before the update. You can also specify the period for auto-restart imminent warning notifications with [Update/ScheduleImminentRestartWarning](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduleimminentrestartwarning) (15-60 minutes is the default). We recommend using the default notifications.
|
||||
|
||||
#### I want to manage the update settings a user can access
|
||||
|
||||
Every Windows device provides users with a variety of controls they can use to manage Windows Updates. They can access these controls by Search to find Windows Updates or by going selecting **Updates and Security** in **Settings**. We provide the ability to disable a variety of these controls that are accessible to users.
|
||||
|
||||
Users with access to update pause settings can prevent both feature and quality updates for 7 days. You can prevent users from pausing updates through the Windows Update settings page by using [Update/SetDisablePauseUXAccess](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-setdisablepauseuxaccess).
|
||||
When you disable this setting, users will see **Some settings are managed by your organization** and the update pause settings are greyed out.
|
||||
|
||||
If you use Windows Server Update Server (WSUS), you can prevent users from scanning Windows Update. To do this, use [Update/SetDisableUXWUAccess](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-setdisableuxwuaccess).
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Update Windows 10 in the enterprise](index.md)
|
||||
- [Overview of Windows as a service](waas-overview.md)
|
||||
- [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md)
|
||||
- [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md)
|
||||
- [Assign devices to servicing channels for Windows 10 updates](waas-servicing-channels-windows-10-updates.md)
|
||||
- [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md)
|
||||
- [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md)
|
||||
- [Configure BranchCache for Windows 10 updates](waas-branchcache.md)
|
||||
- [Deploy updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md)
|
||||
- [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md)
|
||||
- [Configure Windows Update for Business](waas-configure-wufb.md)
|
||||
- [Integrate Windows Update for Business with management solutions](waas-integrate-wufb.md)
|
||||
- [Walkthrough: use Intune to configure Windows Update for Business](https://docs.microsoft.com/intune/windows-update-for-business-configure)
|
||||
- [Deploy Windows 10 updates using Windows Server Update Services](waas-manage-updates-wsus.md)
|
||||
- [Deploy Windows 10 updates using Microsoft Endpoint Configuration Manager](waas-manage-updates-configuration-manager.md)
|
||||
- [Manage device restarts after updates](waas-restart.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ You can use Group Policy through the Group Policy Management Console (GPMC) to c
|
||||
|
||||
An IT administrator can set policies for Windows Update for Business by using Group Policy, or they can be set locally (per device). All of the relevant policies are under the path **Computer configuration > Administrative Templates > Windows Components > Windows Update**.
|
||||
|
||||
To manage updates with Windows Update for Business as described in this topic, you should prepare with these steps, if you haven't already:
|
||||
To manage updates with Windows Update for Business as described in this article, you should prepare with these steps, if you haven't already:
|
||||
|
||||
- Create Active Directory security groups that align with the deployment rings you use to phase deployment of updates. See [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) to learn more about deployment rings in Windows 10.
|
||||
- Allow access to the Windows Update service.
|
||||
@ -49,27 +49,34 @@ Follow these steps on a device running the Remote Server Administration Tools or
|
||||
6. In the Group Policy Management Editor, go to **Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Update**. You are now ready to start assigning policies to this ring (group) of devices.
|
||||
|
||||
|
||||
## Offering
|
||||
## Manage Windows Update offerings
|
||||
|
||||
You can control when updates are applied, for example by deferring when an update is installed on a device or by pausing updates for a certain period of time.
|
||||
|
||||
### Manage which updates are offered
|
||||
### Determine which updates you want offered to your devices
|
||||
|
||||
Windows Update for Business offers you the ability to turn on or off both driver and Microsoft product updates.
|
||||
Both Windows 10 feature and quality updates are automatically offered to devices that are connected to Windows Update using Windows Update for Business policies. However, you can choose whether you want the devices to additionally receive other Microsoft Updates or drivers that are applicable to that device.
|
||||
|
||||
- Drivers (on/off): **Computer configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates**
|
||||
- Microsoft product updates (on/off): **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates > Install updates for other Microsoft products**
|
||||
To enable Microsoft Updates use the Group Policy Management Console go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates** and select **Install updates for other Microsoft products**.
|
||||
|
||||
We recommend that you allow the driver policy to allow drivers to updated on devices (the default), but you can turn this setting off if you prefer to manage drivers manually. We also recommend that you leave the "Microsoft product updates" setting on.
|
||||
Drivers are automatically enabled because they are beneficial to device systems. We recommend that you allow the driver policy to allow drivers to updated on devices (the default), but you can turn this setting off if you prefer to manage drivers manually. If you want to disable driver updates for some reason, use the Group Policy Management Console to go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates** and enable the policy.
|
||||
|
||||
### Manage when updates are offered
|
||||
You can defer or pause the installation of updates for a set period of time.
|
||||
We also recommend that you allow Microsoft product updates as discussed previously.
|
||||
|
||||
#### Defer or pause an update
|
||||
### Set when devices receive feature and quality updates
|
||||
|
||||
A Windows Update for Business administrator can defer or pause updates and preview builds. You can defer features updates for up to 365 days. You can pause feature or quality updates for up to 35 days from a given start date that you specify.
|
||||
#### I want to receive pre-release versions of the next feature update
|
||||
|
||||
- Defer or pause a feature update: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are Received**
|
||||
1. Ensure that you are enrolled in the Windows Insider Program for Business. This is a completely free program available to commercial customers to aid them in their validation of feature updates before they are released. Joining the program enables you to receive updates prior to their release as well as receive emails and content related to what is coming in the next updates.
|
||||
2. Use Group Policy Management Console to go to: C**omputer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Manage preview builds** and set the policy to **Enable preview builds** for any of test devices you want to install pre-release builds.
|
||||
3. Use Group Policy Management Console to go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are received**. In the **Options** pane, use the pulldown menu to select one of the preview builds. We recomment **Windows Insider Program Slow** for commercial customers using pre-release builds for validation.
|
||||
4. Select **OK**.
|
||||
|
||||
#### I want to manage which released feature update my devices receive
|
||||
|
||||
A Windows Update for Business administrator can defer or pause updates. You can defer feature updates for up to 365 days and defer quality updates for up to 30 days. Deferring simply means that you will not receive the update until it has been released for at least the number of deferral days you specified (offer date = release date + deferral date). You can pause feature or quality updates for up to 35 days from a given start date that you specify.
|
||||
|
||||
- To defer or pause a feature update: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are Received**
|
||||
- Defer or pause a quality update: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Quality Updates are Received**
|
||||
|
||||
#### Example
|
||||
@ -106,18 +113,80 @@ Now all devices are paused from updating for 35 days. When the pause is removed,
|
||||
|
||||
|
||||
|
||||
#### Set branch readiness level for feature updates
|
||||
|
||||
This policy only applies to feature updates. To enable preview builds for devices in your organization, set the "Enable preview builds" policy and then use the "Select when preview builds and feature updates are received" policy.
|
||||
#### I want to stay on a specific version
|
||||
|
||||
We recommend that you set up a ring to receive preview builds by joining the Windows Insider Program for Business. By having a ring of devices receiving "pre-release slow" builds and learning about commercial pre-release features, you can ensure that any issues you have with the release are fixed before it is ever released and far before you broadly deploy.
|
||||
If you need a device to stay on a version beyond the point when deferrals on the next version would elapse or if you need to skip a version (for example, update fall release to fall release) use the **Select the target Feature Update version** setting instead of using the **Specify when Preview Builds and Feature Updates are received** setting for feature update deferrals. When you use this policy, specify the version that you want your device(s) to use. If you don't update this before the device reaches end of service, the device will automatically be updated once it is 60 days past end of service for its edition.
|
||||
|
||||
- Enable preview builds: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Manage Preview Builds**
|
||||
### Manage how users experience updates
|
||||
|
||||
#### I want to manage when devices download, install, and restart after updates
|
||||
|
||||
We recommend that you allow to update automatically--this is the default behavior. If you don't set an automatic update policy, the device will attempt to download, install, and restart at the best times for the user by using built-in intelligence such as intelligent active hours and smart busy check.
|
||||
|
||||
- Set branch readiness level: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and Feature Updates are Received**
|
||||
For more granular control, you can set the maximum period of active hours the user can set with **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify active hours range for auto restart**.
|
||||
|
||||
It's best to refrain from setting the active hours policy because it's enabled by default when automatic updates are not disabled and provides a better experience when users can set their own active hours. If you do want to set active hours, use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Turn off auto-restart for updates during active hours**.
|
||||
|
||||
To update outside of the active hours, you don't need to set any additional settings: simply don't disable automatic restarts. For even more granular control, consider using automatic updates to schedule the install time, day, or week. To do this, use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates** and select **Auto download and schedule the install**. You can customize this setting to accommodate the time that you want the update to be installed for your devices.
|
||||
|
||||
When you set these policies, installation happens automatically at the specified time and the device will restart 15 minutes after installation is complete (unless it's interrupted by the user).
|
||||
|
||||
#### I want to keep devices secure and compliant with update deadlines
|
||||
|
||||
We recommend that you use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadline for automatic updates and restarts** for feature and quality updates to ensure that devices stay secure on Windows 10, version 1709 and later. This works by enabling you to specify the number of days that can elapse after an update is offered to a device before it must be installed. Also you can set the number of days that can elapse after a pending restart before the user is forced to restart.
|
||||
|
||||
This policies also offers an option to opt out of automatic restarts until a deadline is reached by presenting an "engaged restart experience" until the deadline has actually expired. At that point the device will automatically schedule a restart regardles of active hours.
|
||||
|
||||
These notifications are what the user sees depending on the settings you choose:
|
||||
|
||||
When **Specify deadlines for automatic updates and restarts** is set (For Windows 10, version 1709 and later):
|
||||
|
||||
- **While restart is pending, before the deadline occurs:**
|
||||
|
||||
- For the first few days, the user receives a toast notification
|
||||
|
||||
- After this period, the user receives this dialog:
|
||||
|
||||
|
||||
|
||||
- If the user scheduled a restart, or if an auto restart is scheduled, 15 minutes before the scheduled time the user is receives this notification that the restart is about to occur:
|
||||
|
||||
|
||||
|
||||
- **If the restart is still pending after the deadline passes:**
|
||||
|
||||
- Within 12 hours before the deadline passes, the user receives this notification that the deadline is approaching:
|
||||
|
||||
|
||||
|
||||
- Once the deadline has passed, the user is forced to restart to keep their devices in compliance and receives this notification:
|
||||
|
||||
|
||||
|
||||
#### I want to manage the notifications a user sees
|
||||
|
||||
There are additional settings that affect the notifications.
|
||||
|
||||
We recommend that you use the default notifications as they aim to provide the best user experience while adjusting for the compliance policies that you have set. If you do have further needs that are not met by the default notification settings, you can use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Display options for update notifications** with these values:
|
||||
|
||||
**0** (default) – Use the default Windows Update notifications
|
||||
**1** – Turn off all notifications, excluding restart warnings
|
||||
**2** – Turn off all notifications, including restart warnings
|
||||
|
||||
> [!NOTE]
|
||||
> Option **2** creates a poor experience for personal devices; it's only recommended for kiosk devices where automatic restarts have been disabled.
|
||||
|
||||
Still more options are available in **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure auto-restart restart warning notifications schedule for updates**. This setting allows you to specify the period for auto-restart warning reminder notifications (from 2-24 hours; 4 hours is the default) before the update and to specify the period for auto-restart imminent warning notifications (15-60 minutes is the default). We recommend using the default notifications.
|
||||
|
||||
#### I want to manage the update settings a user can access
|
||||
|
||||
Every Windows device provides users with a variety of controls they can use to manage Windows Updates. They can access these controls by Search to find Windows Updates or by going selecting **Updates and Security** in **Settings**. We provide the ability to disable a variety of these controls that are accessible to users.
|
||||
|
||||
Users with access to update pause settings can prevent both feature and quality updates for 7 days. You can prevent users from pausing updates through the Windows Update settings page by using **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Remove access to “Pause updates**.
|
||||
When you disable this setting, users will see **Some settings are managed by your organization** and the update pause settings are greyed out.
|
||||
|
||||
If you use Windows Server Update Server (WSUS), you can prevent users from scanning Windows Update. To do this, use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Remove access to use all Windows Update features**.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@
|
||||
### [Diagnostic Data Viewer Overview](diagnostic-data-viewer-overview.md)
|
||||
### [Diagnostic Data Viewer for PowerShell Overview](Microsoft-DiagnosticDataViewer.md)
|
||||
## Basic level Windows diagnostic data events and fields
|
||||
### [Windows 10, version 2005 required Windows diagnostic data events and fields](required-windows-diagnostic-data-events-and-fields-2005.md)
|
||||
### [Windows 10, version 1903 and Windows 10, version 1909 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
||||
### [Windows 10, version 1809 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||
### [Windows 10, version 1803 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||
|
||||
@ -13,7 +13,7 @@ manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.date: 01/04/2020
|
||||
ms.date: 03/27/2020
|
||||
ms.reviewer:
|
||||
---
|
||||
|
||||
@ -81,7 +81,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Appraiser.General.DatasourceApplicationFileAdd
|
||||
|
||||
Represents the basic metadata about specific application files installed on the system.
|
||||
This event sends compatibility information about a file to help keep Windows up-to-date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -1323,7 +1323,7 @@ The following fields are available:
|
||||
- **MPNId** Returns the Partner ID/MPN ID from Regkey. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DeployID
|
||||
- **SCCMClientId** This ID correlate systems that send data to Compat Analytics (OMS) and other OMS based systems with systems in a Configuration Manager environment.
|
||||
- **ServerFeatures** Represents the features installed on a Windows Server. This can be used by developers and administrators who need to automate the process of determining the features installed on a set of server computers.
|
||||
- **SystemCenterID** The Microsoft Endpoint Configuration Manager ID is an anonymized one-way hash of the Active Directory Organization identifier.
|
||||
- **SystemCenterID** The SCCM ID is an anonymized one-way hash of the Active Directory Organization identifier.
|
||||
|
||||
|
||||
### Census.Firmware
|
||||
@ -2477,44 +2477,6 @@ The following fields are available:
|
||||
- **InventoryVersion** The version of the inventory file generating the events.
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDevicePnpAdd
|
||||
|
||||
This event represents the basic metadata about a plug and play (PNP) device and its associated driver.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **Class** The device setup class of the driver loaded for the device.
|
||||
- **ClassGuid** The device class unique identifier of the driver package loaded on the device.
|
||||
- **COMPID** The list of “Compatible IDs” for this device. See [COMPID](#compid).
|
||||
- **ContainerId** The system-supplied unique identifier that specifies which group(s) the device(s) installed on the parent (main) device belong to.
|
||||
- **Description** The description of the device.
|
||||
- **DeviceState** Identifies the current state of the parent (main) device.
|
||||
- **DriverId** The unique identifier for the installed driver.
|
||||
- **DriverName** The name of the driver image file.
|
||||
- **DriverPackageStrongName** The immediate parent directory name in the Directory field of InventoryDriverPackage.
|
||||
- **DriverVerDate** The date of the driver loaded for the device
|
||||
- **DriverVerVersion** The version of the driver loaded for the device
|
||||
- **Enumerator** Identifies the bus that enumerated the device.
|
||||
- **HWID** A list of hardware IDs for the device. See [HWID](#hwid).
|
||||
- **Inf** The name of the INF file (possibly renamed by the OS, such as oemXX.inf).
|
||||
- **InstallState** The device installation state. For a list of values, see: https://msdn.microsoft.com/library/windows/hardware/ff543130.aspx
|
||||
- **InventoryVersion** The version number of the inventory process generating the events.
|
||||
- **LowerClassFilters** The identifiers of the Lower Class filters installed for the device.
|
||||
- **LowerFilters** The identifiers of the Lower filters installed for the device.
|
||||
- **Manufacturer** The manufacturer of the device.
|
||||
- **MatchingID** The Hardware ID or Compatible ID that Windows uses to install a device instance.
|
||||
- **Model** Identifies the model of the device.
|
||||
- **ParentId** The Device Instance ID of the parent of the device.
|
||||
- **ProblemCode** The error code currently returned by the device, if applicable.
|
||||
- **Provider** Identifies the device provider.
|
||||
- **Service** The name of the device service.
|
||||
- **STACKID** The list of hardware IDs for the stack. See [STACKID](#stackid).
|
||||
- **UpperClassFilters** The identifiers of the Upper Class filters installed for the device.
|
||||
- **UpperFilters** The identifiers of the Upper filters installed for the device.
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDevicePnpRemove
|
||||
|
||||
This event indicates that the InventoryDevicePnpRemove object is no longer present.
|
||||
@ -2551,7 +2513,7 @@ This event indicates that a new set of InventoryDeviceUsbHubClassAdd events will
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDriverBinaryAdd
|
||||
|
||||
This event provides the basic metadata about driver binaries running on the system.
|
||||
This event sends basic metadata about driver binaries running on the system to help keep Windows up to date.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
@ -3077,6 +3039,56 @@ The following fields are available:
|
||||
- **resetSettingsResult** The return code of the action to correct the known issue.
|
||||
|
||||
|
||||
## Quality Update Assistant events
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Applicability
|
||||
|
||||
This event sends basic info on whether the device should be updated to the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Applicability check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.DeviceReadinessCheck
|
||||
|
||||
This event sends basic info on whether the device is ready to download the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Device readiness check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Download
|
||||
|
||||
This event sends basic info when download of the latest cumulative update begins.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter that indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Download of latest cumulative update payload.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Install
|
||||
|
||||
This event sends basic info on the result of the installation of the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Install of latest cumulative update payload.
|
||||
|
||||
|
||||
## Remediation events
|
||||
|
||||
### Microsoft.Windows.Remediation.Applicable
|
||||
@ -4023,7 +4035,7 @@ This event sends basic metadata about the update installation process generated
|
||||
|
||||
### SetupPlatformTel.SetupPlatformTelEvent
|
||||
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios.
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -5139,7 +5151,7 @@ The following fields are available:
|
||||
- **ReportId** With Windows Update, this is the updateID that is passed to Setup. In media setup, this is the GUID for the install.wim.
|
||||
- **Setup360Extended** Detailed information about the phase/action when the potential failure occurred.
|
||||
- **Setup360Mode** The phase of Setup360. Example: Predownload, Install, Finalize, Rollback.
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that can be used to diagnose errors.
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that can be used used to diagnose errors.
|
||||
- **Setup360Scenario** The Setup360 flow type. Example: Boot, Media, Update, MCT.
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of target OS).
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
@ -6016,7 +6028,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.FlightInapplicable
|
||||
|
||||
This event indicates that the update is no longer applicable to this device.
|
||||
This event sends data on whether the update was applicable to the device, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -6097,7 +6109,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.PostInstall
|
||||
|
||||
This event is sent after a Windows update install completes.
|
||||
This event sends data about lite stack devices (mobile, IOT, anything non-PC) immediately before data migration is launched to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.date: 01/04/2020
|
||||
ms.date: 03/27/2020
|
||||
ms.reviewer:
|
||||
---
|
||||
|
||||
@ -1866,7 +1866,7 @@ The following fields are available:
|
||||
|
||||
### CbsServicingProvider.CbsCapabilityEnumeration
|
||||
|
||||
This event reports on the results of scanning for optional Windows content on Windows Update.
|
||||
This event reports on the results of scanning for optional Windows content on Windows Update to keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -2566,7 +2566,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDriverBinaryAdd
|
||||
|
||||
This event provides the basic metadata about driver binaries running on the system.
|
||||
This event sends basic metadata about driver binaries running on the system to help keep Windows up to date.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
@ -3225,6 +3225,56 @@ The following fields are available:
|
||||
- **resetSettingsResult** The return code of the action to correct the known issue.
|
||||
|
||||
|
||||
## Quality Update Assistant events
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Applicability
|
||||
|
||||
This event sends basic info on whether the device should be updated to the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Applicability check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.DeviceReadinessCheck
|
||||
|
||||
This event sends basic info on whether the device is ready to download the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Device readiness check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Download
|
||||
|
||||
This event sends basic info when download of the latest cumulative update begins.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter that indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Download of latest cumulative update payload.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Install
|
||||
|
||||
This event sends basic info on the result of the installation of the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Install of latest cumulative update payload.
|
||||
|
||||
|
||||
## Remediation events
|
||||
|
||||
### Microsoft.Windows.Remediation.Applicable
|
||||
@ -3970,7 +4020,7 @@ This event sends basic metadata about the update installation process generated
|
||||
|
||||
### SetupPlatformTel.SetupPlatformTelEvent
|
||||
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios.
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -6253,7 +6303,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.FlightInapplicable
|
||||
|
||||
This event indicates that the update is no longer applicable to this device.
|
||||
This event sends data on whether the update was applicable to the device, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -6347,7 +6397,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.PostInstall
|
||||
|
||||
This event is sent after a Windows update install completes.
|
||||
This event sends data about lite stack devices (mobile, IOT, anything non-PC) immediately before data migration is launched to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.date: 01/04/2020
|
||||
ms.date: 03/27/2020
|
||||
ms.reviewer:
|
||||
---
|
||||
|
||||
@ -2044,7 +2044,7 @@ The following fields are available:
|
||||
|
||||
### CbsServicingProvider.CbsCapabilityEnumeration
|
||||
|
||||
This event reports on the results of scanning for optional Windows content on Windows Update.
|
||||
This event reports on the results of scanning for optional Windows content on Windows Update to keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -3528,7 +3528,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDriverBinaryAdd
|
||||
|
||||
This event provides the basic metadata about driver binaries running on the system.
|
||||
This event sends basic metadata about driver binaries running on the system to help keep Windows up to date.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
@ -4091,71 +4091,71 @@ The following fields are available:
|
||||
|
||||
### Aria.160f0649efde47b7832f05ed000fc453.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event, where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
|
||||
|
||||
### Aria.29e24d069f27450385c7acaa2f07e277.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
|
||||
|
||||
### Aria.7005b72804a64fa4b2138faab88f877b.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
|
||||
|
||||
### Aria.754de735ccd546b28d0bfca8ac52c3de.Microsoft.WebBrowser.SystemInfo.Config
|
||||
@ -4164,21 +4164,21 @@ This config event sends basic device connectivity and configuration information
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
|
||||
|
||||
### Aria.af397ef28e484961ba48646a5d38cf54.Microsoft.WebBrowser.Installer.EdgeUpdate.Ping
|
||||
@ -4187,17 +4187,18 @@ This event sends hardware and software inventory information about the Microsoft
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **appAp** Microsoft Edge Update parameters, including channel, architecture, platform, and additional parameters identifying the release of Microsoft Edge to update and how to install it. Example: 'beta-arch_x64-full'. Default: ''.
|
||||
- **appAp** Microsoft Edge Update parameters, including channel, architecture, platform, and additional parameters identifying the release of Microsoft Edge to update and how to install it. Example: 'beta-arch_x64-full'. Default: ''."
|
||||
- **appAppId** The GUID that identifies the product channels such as Edge Canary, Dev, Beta, Stable, and Edge Update.
|
||||
- **appBrandCode** The 4-digit brand code under which the the product was installed, if any. Possible values: 'GGLS' (default), 'GCEU' (enterprise install), and '' (unknown).
|
||||
- **appChannel** An integer indicating the channel of the installation (e.g. Canary or Dev).
|
||||
- **appClientId** A generalized form of the brand code that can accept a wider range of values and is used for similar purposes. Default: ''.
|
||||
- **appClientId** A generalized form of the brand code that can accept a wider range of values and is used for similar purposes. Default: ''.
|
||||
- **appCohort** A machine-readable string identifying the release channel that the app belongs to. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appCohortHint** A machine-readable enum indicating that the client has a desire to switch to a different release cohort. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appCohortName** A stable non-localized human-readable enum indicating which (if any) set of messages the app should display to the user. For example, an app with a cohort name of 'beta' might display beta-specific branding to the user. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appConsentState** Bit flags describing the diagnostic data disclosure and response flow where 1 indicates the affirmative and 0 indicates the negative or unspecified data. Bit 1 indicates consent was given, bit 2 indicates data originated from the download page, bit 18 indicates choice for sending data about how the browser is used, and bit 19 indicates choice for sending data about websites visited.
|
||||
- **appDayOfInstall** The date-based counting equivalent of appInstallTimeDiffSec (the numeric calendar day that the app was installed on). This value is provided by the server in the response to the first request in the installation flow. Default: '-2' (Unknown).
|
||||
- **appExperiments** A semicolon-delimited key/value list of experiment identifiers and treatment groups. This field is unused and always empty in Edge Update. Default: ''.
|
||||
- **appIid** A GUID that identifies a particular installation flow. For example, each download of a product installer is tagged with a unique GUID. Attempts to install using that installer can then be grouped. A client SHOULD NOT persist the IID GUID after the installation flow of a product is complete.
|
||||
- **appInstallTimeDiffSec** The difference between the current time and the install date in seconds. '0' if unknown. Default: '-1'.
|
||||
- **appLang** The language of the product install, in IETF BCP 47 representation. Default: ''.
|
||||
- **appNextVersion** The version of the app that the update attempted to reach, regardless of the success or failure of the update operation. Default: '0.0.0.0'.
|
||||
@ -4208,7 +4209,7 @@ The following fields are available:
|
||||
- **appPingEventDownloadMetricsError** The error code (if any) of the operation, encoded as a signed base-10 integer. Default: '0'.
|
||||
- **appPingEventDownloadMetricsServerIpHint** For events representing a download, the CDN Host IP address that corresponds to the update file server. The CDN host is controlled by Microsoft servers and always maps to IP addresses hosting *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadMetricsTotalBytes** For events representing a download, the number of bytes expected to be downloaded. For events representing an entire update flow, the sum of all such expected bytes over the course of the update flow. Default: '0'.
|
||||
- **appPingEventDownloadMetricsUrl** For events representing a download, the CDN URL provided by the update server for the client to download the update, the URL is controlled by Microsoft servers and always maps back to either *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadMetricsUrl** For events representing a download, the CDN URL provided by the update server for the client to download the update, the URL is controlled by Microsoft servers and always maps back to either *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadTimeMs** For events representing a download, the time elapsed between the start of the download and the end of the download, in milliseconds. For events representing an entire update flow, the sum of all such download times over the course of the update flow. Sent in events that have an event type of '1', '2', '3', and '14' only. Default: '0'.
|
||||
- **appPingEventErrorCode** The error code (if any) of the operation, encoded as a signed, base-10 integer. Default: '0'.
|
||||
- **appPingEventEventResult** An enumeration indicating the result of the event. Common values are '0' (Error) and '1' (Success). Default: '0' (Error).
|
||||
@ -4217,15 +4218,14 @@ The following fields are available:
|
||||
- **appPingEventInstallTimeMs** For events representing an install, the time elapsed between the start of the install and the end of the install, in milliseconds. For events representing an entire update flow, the sum of all such durations. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appPingEventNumBytesDownloaded** The number of bytes downloaded for the specified application. Default: '0'.
|
||||
- **appPingEventSequenceId** An ID that uniquely identifies particular events within one requestId. Since a request can contain multiple ping events, this field is necessary to uniquely identify each possible event.
|
||||
- **appPingEventSourceUrlIndex** For events representing a download, the position of the download URL in the list of URLs supplied by the server in a <urls> tag.
|
||||
- **appPingEventUpdateCheckTimeMs** For events representing an entire update flow, the time elapsed between the start of the update check and the end of the update check, in milliseconds. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appPingEventSourceUrlIndex** For events representing a download, the position of the download URL in the list of URLs supplied by the server in a tag.
|
||||
- **appPingEventUpdateCheckTimeMs** For events representing an entire update flow, the time elapsed between the start of the update check and the end of the update check, in milliseconds. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appUpdateCheckIsUpdateDisabled** The state of whether app updates are restricted by group policy. True if updates have been restricted by group policy or false if they have not.
|
||||
- **appUpdateCheckTargetVersionPrefix** A component-wise prefix of a version number, or a complete version number suffixed with the $ character. The prefix is interpreted a dotted-tuple that specifies the exactly-matching elements; it is not a lexical prefix (for example, '1.2.3' MUST match '1.2.3.4' but MUST NOT match '1.2.34'). Default: ''.
|
||||
- **appUpdateCheckTtToken** An opaque access token that can be used to identify the requesting client as a member of a trusted-tester group. If non-empty, the request is sent over SSL or another secure protocol. This field is unused by Edge Update and always empty. Default: ''.
|
||||
- **appVersion** The version of the product install. Default: '0.0.0.0'.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **eventType** A string representation of appPingEventEventType indicating the type of the event.
|
||||
- **hwHasAvx** '1' if the client's hardware supports the SSE instruction set. '0' if the client's hardware does not support the SSE instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasAvx** '1' if the client's hardware supports the AVX instruction set. '0' if the client's hardware does not support the AVX instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse** '1' if the client's hardware supports the SSE instruction set. '0' if the client's hardware does not support the SSE instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse2** '1' if the client's hardware supports the SSE2 instruction set. '0' if the client's hardware does not support the SSE2 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse3** '1' if the client's hardware supports the SSE3 instruction set. '0' if the client's hardware does not support the SSE3 instruction set. '-1' if unknown. Default: '-1'.
|
||||
@ -4246,9 +4246,9 @@ The following fields are available:
|
||||
- **requestOmahaShellVersion** The version of the Omaha installation folder. Default: ''.
|
||||
- **requestOmahaVersion** The version of the Omaha updater itself (the entity sending this request). Default: '0.0.0.0'.
|
||||
- **requestProtocolVersion** The version of the Omaha protocol. Compatible clients MUST provide a value of '3.0'. Compatible clients MUST always transmit this attribute. Default: undefined.
|
||||
- **requestRequestId** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha request. Default: ''.
|
||||
- **requestRequestId** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha request. Each request attempt SHOULD have (with high probability) a unique request id. Default: ''.
|
||||
- **requestSessionCorrelationVectorBase** A client generated random MS Correlation Vector base code used to correlate the update session with update and CDN servers. Default: ''.
|
||||
- **requestSessionId** A randomly-generated (uniformly distributed) GUID. Each single update flow (e.g. update check, update application, event ping sequence) should have (with high probability) a single unique sessionid. Default: ''.
|
||||
- **requestSessionId** A randomly-generated (uniformly distributed) GUID. Each single update flow (e.g. update check, update application, event ping sequence) SHOULD have (with high probability) a single unique session ID. Default: ''.
|
||||
- **requestTestSource** Either '', 'dev', 'qa', 'prober', 'auto', or 'ossdev'. Any value except '' indicates that the request is a test and should not be counted toward normal metrics. Default: ''.
|
||||
- **requestUid** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha user. Each request attempt should have (with high probability) a unique request id. Default: ''.
|
||||
|
||||
@ -4552,6 +4552,56 @@ The following fields are available:
|
||||
- **resetSettingsResult** The return code of the action to correct the known issue.
|
||||
|
||||
|
||||
## Quality Update Assistant events
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Applicability
|
||||
|
||||
This event sends basic info on whether the device should be updated to the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Applicability check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.DeviceReadinessCheck
|
||||
|
||||
This event sends basic info on whether the device is ready to download the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Device readiness check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Download
|
||||
|
||||
This event sends basic info when download of the latest cumulative update begins.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Download of latest cumulative update payload.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Install
|
||||
|
||||
This event sends basic info on the result of the installation of the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Result** Install of latest cumulative update payload.
|
||||
|
||||
|
||||
## Remediation events
|
||||
|
||||
### Microsoft.Windows.Remediation.Applicable
|
||||
@ -5153,7 +5203,7 @@ This event sends basic metadata about the update installation process generated
|
||||
|
||||
### SetupPlatformTel.SetupPlatformTelEvent
|
||||
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios.
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -7680,7 +7730,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.FlightInapplicable
|
||||
|
||||
This event indicates that the update is no longer applicable to this device.
|
||||
This event sends data on whether the update was applicable to the device, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -7774,7 +7824,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.PostInstall
|
||||
|
||||
This event is sent after a Windows update install completes.
|
||||
This event sends data about lite stack devices (mobile, IOT, anything non-PC) immediately before data migration is launched to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.date: 01/04/2020
|
||||
ms.date: 03/27/2020
|
||||
ms.reviewer:
|
||||
---
|
||||
|
||||
@ -312,6 +312,7 @@ The following fields are available:
|
||||
- **DatasourceApplicationFile_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_RS1** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **DatasourceApplicationFile_RS2** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **DatasourceApplicationFile_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -327,6 +328,7 @@ The following fields are available:
|
||||
- **DatasourceDevicePnp_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_RS1** The total DataSourceDevicePnp objects targeting Windows 10 version 1607 on this device.
|
||||
- **DatasourceDevicePnp_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -342,6 +344,7 @@ The following fields are available:
|
||||
- **DatasourceDriverPackage_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_RS1** The total DataSourceDriverPackage objects targeting Windows 10 version 1607 on this device.
|
||||
- **DatasourceDriverPackage_RS2** The total DataSourceDriverPackage objects targeting Windows 10, version 1703 on this device.
|
||||
- **DatasourceDriverPackage_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -357,6 +360,7 @@ The following fields are available:
|
||||
- **DataSourceMatchingInfoBlock_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_RS1** The total DataSourceMatchingInfoBlock objects targeting Windows 10 version 1607 on this device.
|
||||
- **DataSourceMatchingInfoBlock_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -372,6 +376,7 @@ The following fields are available:
|
||||
- **DataSourceMatchingInfoPassive_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_RS1** The total DataSourceMatchingInfoPassive objects targeting Windows 10 version 1607 on this device.
|
||||
- **DataSourceMatchingInfoPassive_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -387,6 +392,7 @@ The following fields are available:
|
||||
- **DataSourceMatchingInfoPostUpgrade_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_RS1** The total DataSourceMatchingInfoPostUpgrade objects targeting Windows 10 version 1607 on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_RS2** The total DataSourceMatchingInfoPostUpgrade objects targeting Windows 10 version 1703 on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_RS3** The total DataSourceMatchingInfoPostUpgrade objects targeting Windows 10 version 1709 on this device.
|
||||
@ -402,6 +408,7 @@ The following fields are available:
|
||||
- **DatasourceSystemBios_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_RS1** The total DatasourceSystemBios objects targeting Windows 10 version 1607 present on this device.
|
||||
- **DatasourceSystemBios_RS2** The total DatasourceSystemBios objects targeting Windows 10 version 1703 present on this device.
|
||||
- **DatasourceSystemBios_RS3** The total DatasourceSystemBios objects targeting Windows 10 version 1709 present on this device.
|
||||
@ -417,6 +424,7 @@ The following fields are available:
|
||||
- **DecisionApplicationFile_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_RS1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -432,6 +440,7 @@ The following fields are available:
|
||||
- **DecisionDevicePnp_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_RS1** The total DecisionDevicePnp objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionDevicePnp_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -447,6 +456,7 @@ The following fields are available:
|
||||
- **DecisionDriverPackage_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_RS1** The total DecisionDriverPackage objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionDriverPackage_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -462,6 +472,7 @@ The following fields are available:
|
||||
- **DecisionMatchingInfoBlock_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_RS1** The total DecisionMatchingInfoBlock objects targeting Windows 10 version 1607 present on this device.
|
||||
- **DecisionMatchingInfoBlock_RS2** The total DecisionMatchingInfoBlock objects targeting Windows 10 version 1703 present on this device.
|
||||
- **DecisionMatchingInfoBlock_RS3** The total DecisionMatchingInfoBlock objects targeting Windows 10 version 1709 present on this device.
|
||||
@ -477,6 +488,7 @@ The following fields are available:
|
||||
- **DecisionMatchingInfoPassive_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_RS1** The total DecisionMatchingInfoPassive objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionMatchingInfoPassive_RS2** The total DecisionMatchingInfoPassive objects targeting Windows 10 version 1703 on this device.
|
||||
- **DecisionMatchingInfoPassive_RS3** The total DecisionMatchingInfoPassive objects targeting Windows 10 version 1803 on this device.
|
||||
@ -492,6 +504,7 @@ The following fields are available:
|
||||
- **DecisionMatchingInfoPostUpgrade_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_RS1** The total DecisionMatchingInfoPostUpgrade objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_RS2** The total DecisionMatchingInfoPostUpgrade objects targeting Windows 10 version 1703 on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_RS3** The total DecisionMatchingInfoPostUpgrade objects targeting Windows 10 version 1709 on this device.
|
||||
@ -507,6 +520,7 @@ The following fields are available:
|
||||
- **DecisionMediaCenter_19H1Setup** The total DecisionMediaCenter objects targeting the next release of Windows on this device.
|
||||
- **DecisionMediaCenter_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMediaCenter_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMediaCenter_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMediaCenter_RS1** The total DecisionMediaCenter objects targeting Windows 10 version 1607 present on this device.
|
||||
- **DecisionMediaCenter_RS2** The total DecisionMediaCenter objects targeting Windows 10 version 1703 present on this device.
|
||||
- **DecisionMediaCenter_RS3** The total DecisionMediaCenter objects targeting Windows 10 version 1709 present on this device.
|
||||
@ -522,6 +536,7 @@ The following fields are available:
|
||||
- **DecisionSystemBios_19H1Setup** The total DecisionSystemBios objects targeting the next release of Windows on this device.
|
||||
- **DecisionSystemBios_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemBios_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemBios_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemBios_RS1** The total DecisionSystemBios objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionSystemBios_RS2** The total DecisionSystemBios objects targeting Windows 10 version 1703 on this device.
|
||||
- **DecisionSystemBios_RS3** The total DecisionSystemBios objects targeting Windows 10 version 1709 on this device.
|
||||
@ -534,6 +549,7 @@ The following fields are available:
|
||||
- **DecisionSystemBios_TH2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemProcessor_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionTest_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionTest_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionTest_RS1** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **InventoryApplicationFile** The count of the number of this particular object type present on this device.
|
||||
- **InventoryDeviceContainer** A count of device container objects in cache.
|
||||
@ -563,6 +579,7 @@ The following fields are available:
|
||||
- **Wmdrm_19H1Setup** The total Wmdrm objects targeting the next release of Windows on this device.
|
||||
- **Wmdrm_20H1** The count of the number of this particular object type present on this device.
|
||||
- **Wmdrm_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **Wmdrm_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **Wmdrm_RS1** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **Wmdrm_RS2** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **Wmdrm_RS3** An ID for the system, calculated by hashing hardware identifiers.
|
||||
@ -1838,6 +1855,38 @@ The following fields are available:
|
||||
|
||||
## Audio endpoint events
|
||||
|
||||
### MicArrayGeometry
|
||||
|
||||
This event provides information about the layout of the individual microphone elements in the microphone array.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **MicCoords** The location and orientation of the microphone element. See [MicCoords](#miccoords).
|
||||
- **usFrequencyBandHi** The high end of the frequency range for the microphone.
|
||||
- **usFrequencyBandLo** The low end of the frequency range for the microphone.
|
||||
- **usMicArrayType** The type of the microphone array.
|
||||
- **usNumberOfMicrophones** The number of microphones in the array.
|
||||
- **usVersion** The version of the microphone array specification.
|
||||
- **wHorizontalAngleBegin** The horizontal angle of the start of the working volume (reported as radians times 10,000).
|
||||
- **wHorizontalAngleEnd** The horizontal angle of the end of the working volume (reported as radians times 10,000).
|
||||
- **wVerticalAngleBegin** The vertical angle of the start of the working volume (reported as radians times 10,000).
|
||||
- **wVerticalAngleEnd** The vertical angle of the end of the working volume (reported as radians times 10,000).
|
||||
|
||||
|
||||
### MicCoords
|
||||
|
||||
This event provides information about the location and orientation of the microphone element.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **usType** The type of microphone.
|
||||
- **wHorizontalAngle** The horizontal angle of the microphone (reported as radians times 10,000).
|
||||
- **wVerticalAngle** The vertical angle of the microphone (reported as radians times 10,000).
|
||||
- **wXCoord** The x-coordinate of the microphone.
|
||||
- **wYCoord** The y-coordinate of the microphone.
|
||||
- **wZCoord** The z-coordinate of the microphone.
|
||||
|
||||
|
||||
### Microsoft.Windows.Audio.EndpointBuilder.DeviceInfo
|
||||
|
||||
This event logs the successful enumeration of an audio endpoint (such as a microphone or speaker) and provides information about the audio endpoint.
|
||||
@ -1860,22 +1909,6 @@ The following fields are available:
|
||||
- **MicArrayGeometry** Describes the microphone array, including the microphone position, coordinates, type, and frequency range. See [MicArrayGeometry](#micarraygeometry).
|
||||
- **persistentId** A unique ID for this endpoint which is retained across migrations.
|
||||
|
||||
### MicArrayGeometry
|
||||
|
||||
This event provides information about the layout of the individual microphone elements in the microphone array.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **MicCoords** The location and orientation of the microphone element.
|
||||
- **usFrequencyBandHi** The high end of the frequency range for the microphone.
|
||||
- **usFrequencyBandLo** The low end of the frequency range for the microphone.
|
||||
- **usMicArrayType** The type of the microphone array.
|
||||
- **usNumberOfMicrophones** The number of microphones in the array.
|
||||
- **usVersion** The version of the microphone array specification.
|
||||
- **wHorizontalAngleBegin** The horizontal angle of the start of the working volume (reported as radians times 10,000).
|
||||
- **wHorizontalAngleEnd** The horizontal angle of the end of the working volume (reported as radians times 10,000).
|
||||
- **wVerticalAngleBegin** The vertical angle of the start of the working volume (reported as radians times 10,000).
|
||||
- **wVerticalAngleEnd** The vertical angle of the end of the working volume (reported as radians times 10,000).
|
||||
|
||||
## Census events
|
||||
|
||||
@ -2437,6 +2470,7 @@ The following fields are available:
|
||||
- **ext_container** Describes the properties of the container for events logged within a container. See [Common Data Extensions.container](#common-data-extensionscontainer).
|
||||
- **ext_cs** Describes properties related to the schema of the event. See [Common Data Extensions.cs](#common-data-extensionscs).
|
||||
- **ext_device** Describes the device-related fields. See [Common Data Extensions.device](#common-data-extensionsdevice).
|
||||
- **ext_m365a** Describes the Microsoft 365-related fields. See [Common Data Extensions.m365a](#common-data-extensionsm365a).
|
||||
- **ext_os** Describes the operating system properties that would be populated by the client. See [Common Data Extensions.os](#common-data-extensionsos).
|
||||
- **ext_sdk** Describes the fields related to a platform library required for a specific SDK. See [Common Data Extensions.sdk](#common-data-extensionssdk).
|
||||
- **ext_user** Describes the fields related to a user. See [Common Data Extensions.user](#common-data-extensionsuser).
|
||||
@ -2449,6 +2483,14 @@ The following fields are available:
|
||||
- **time** Represents the event date time in Coordinated Universal Time (UTC) when the event was generated on the client. This should be in ISO 8601 format.
|
||||
- **ver** Represents the major and minor version of the extension.
|
||||
|
||||
### Common Data Extensions.m365a
|
||||
|
||||
Describes the Microsoft 365-related fields.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **enrolledTenantId** The enrolled tenant ID.
|
||||
- **msp** A bitmask that lists the active programs.
|
||||
|
||||
### Common Data Extensions.os
|
||||
|
||||
@ -2562,7 +2604,7 @@ The following fields are available:
|
||||
|
||||
### CbsServicingProvider.CbsCapabilityEnumeration
|
||||
|
||||
This event reports on the results of scanning for optional Windows content on Windows Update.
|
||||
This event reports on the results of scanning for optional Windows content on Windows Update to keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -2774,6 +2816,75 @@ The following fields are available:
|
||||
|
||||
## Diagnostic data events
|
||||
|
||||
### TelClientSynthetic.AbnormalShutdown_0
|
||||
|
||||
This event sends data about boot IDs for which a normal clean shutdown was not observed, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **AbnormalShutdownBootId** BootId of the abnormal shutdown being reported by this event.
|
||||
- **AcDcStateAtLastShutdown** Identifies if the device was on battery or plugged in.
|
||||
- **BatteryLevelAtLastShutdown** The last recorded battery level.
|
||||
- **BatteryPercentageAtLastShutdown** The battery percentage at the last shutdown.
|
||||
- **CrashDumpEnabled** Indicates whether crash dumps are enabled.
|
||||
- **CumulativeCrashCount** Cumulative count of operating system crashes since the BootId reset.
|
||||
- **CurrentBootId** BootId at the time the abnormal shutdown event was being reported.
|
||||
- **Firmwaredata->ResetReasonEmbeddedController** The reset reason that was supplied by the firmware.
|
||||
- **Firmwaredata->ResetReasonEmbeddedControllerAdditional** Additional data related to reset reason provided by the firmware.
|
||||
- **Firmwaredata->ResetReasonPch** The reset reason that was supplied by the hardware.
|
||||
- **Firmwaredata->ResetReasonPchAdditional** Additional data related to the reset reason supplied by the hardware.
|
||||
- **Firmwaredata->ResetReasonSupplied** Indicates whether the firmware supplied any reset reason or not.
|
||||
- **FirmwareType** ID of the FirmwareType as enumerated in DimFirmwareType.
|
||||
- **HardwareWatchdogTimerGeneratedLastReset** Indicates whether the hardware watchdog timer caused the last reset.
|
||||
- **HardwareWatchdogTimerPresent** Indicates whether hardware watchdog timer was present or not.
|
||||
- **LastBugCheckBootId** bootId of the last captured crash.
|
||||
- **LastBugCheckCode** Code that indicates the type of error.
|
||||
- **LastBugCheckContextFlags** Additional crash dump settings.
|
||||
- **LastBugCheckOriginalDumpType** The type of crash dump the system intended to save.
|
||||
- **LastBugCheckOtherSettings** Other crash dump settings.
|
||||
- **LastBugCheckParameter1** The first parameter with additional info on the type of the error.
|
||||
- **LastBugCheckProgress** Progress towards writing out the last crash dump.
|
||||
- **LastBugCheckVersion** The version of the information struct written during the crash.
|
||||
- **LastSuccessfullyShutdownBootId** BootId of the last fully successful shutdown.
|
||||
- **LongPowerButtonPressDetected** Identifies if the user was pressing and holding power button.
|
||||
- **OOBEInProgress** Identifies if the Out-Of-Box-Experience is running.
|
||||
- **OSSetupInProgress** Identifies if the operating system setup is running.
|
||||
- **PowerButtonCumulativePressCount** Indicates the number of times the power button has been pressed ("pressed" not to be confused with "released").
|
||||
- **PowerButtonCumulativeReleaseCount** Indicates the number of times the power button has been released ("released" not to be confused with "pressed").
|
||||
- **PowerButtonErrorCount** Indicates the number of times there was an error attempting to record Power Button metrics (e.g.: due to a failure to lock/update the bootstat file).
|
||||
- **PowerButtonLastPressBootId** BootId of the last time the Power Button was detected to have been pressed ("pressed" not to be confused with "released").
|
||||
- **PowerButtonLastPressTime** Date/time of the last time the Power Button was pressed ("pressed" not to be confused with "released").
|
||||
- **PowerButtonLastReleaseBootId** The Boot ID of the last time the Power Button was released ("released" not to be confused with "pressed").
|
||||
- **PowerButtonLastReleaseTime** The date and time the Power Button was most recently released ("released" not to be confused with "pressed").
|
||||
- **PowerButtonPressCurrentCsPhase** Represents the phase of Connected Standby exit when the power button was pressed.
|
||||
- **PowerButtonPressIsShutdownInProgress** Indicates whether a system shutdown was in progress at the last time the power button was pressed.
|
||||
- **PowerButtonPressLastPowerWatchdogStage** The last stage completed when the Power Button was most recently pressed.
|
||||
- **PowerButtonPressPowerWatchdogArmed** Indicates whether or not the watchdog for the monitor was active at the time of the last power button press.
|
||||
- **ShutdownDeviceType** Identifies who triggered a shutdown. Is it because of battery, thermal zones, or through a Kernel API.
|
||||
- **SleepCheckpoint** Provides the last checkpoint when there is a failure during a sleep transition.
|
||||
- **SleepCheckpointSource** Indicates whether the source is the EFI variable or bootstat file.
|
||||
- **SleepCheckpointStatus** Indicates whether the checkpoint information is valid.
|
||||
- **StaleBootStatData** Identifies if the data from bootstat is stale.
|
||||
- **TransitionInfoBootId** The Boot ID of the captured transition information.
|
||||
- **TransitionInfoCSCount** The total number of times the system transitioned from "Connected Standby" mode to "On" when the last marker was saved.
|
||||
- **TransitionInfoCSEntryReason** Indicates the reason the device last entered "Connected Standby" mode ("entered" not to be confused with "exited").
|
||||
- **TransitionInfoCSExitReason** Indicates the reason the device last exited "Connected Standby" mode ("exited" not to be confused with "entered").
|
||||
- **TransitionInfoCSInProgress** Indicates whether the system was in or entering Connected Standby mode when the last marker was saved.
|
||||
- **TransitionInfoLastReferenceTimeChecksum** The checksum of TransitionInfoLastReferenceTimestamp.
|
||||
- **TransitionInfoLastReferenceTimestamp** The date and time that the marker was last saved.
|
||||
- **TransitionInfoLidState** Describes the state of the laptop lid.
|
||||
- **TransitionInfoPowerButtonTimestamp** The most recent date and time when the Power Button was pressed (collected via a different mechanism than PowerButtonLastPressTime).
|
||||
- **TransitionInfoSleepInProgress** Indicates whether the system was in or entering Sleep mode when the last marker was saved.
|
||||
- **TransitionInfoSleepTranstionsToOn** The total number of times the system transitioned from Sleep mode to on, when the last marker was saved.
|
||||
- **TransitionInfoSystemRunning** Indicates whether the system was running when the last marker was saved.
|
||||
- **TransitionInfoSystemShutdownInProgress** Indicates whether a device shutdown was in progress when the power button was pressed.
|
||||
- **TransitionInfoUserShutdownInProgress** Indicates whether a user shutdown was in progress when the power button was pressed.
|
||||
- **TransitionLatestCheckpointId** Represents a unique identifier for a checkpoint during the device state transition.
|
||||
- **TransitionLatestCheckpointSeqNumber** Represents the chronological sequence number of the checkpoint.
|
||||
- **TransitionLatestCheckpointType** Represents the type of the checkpoint, which can be the start of a phase, end of a phase, or just informational.
|
||||
- **VirtualMachineId** If the operating system is on a virtual Machine, it gives the virtual Machine ID (GUID) that can be used to correlate events on the host.
|
||||
|
||||
|
||||
### TelClientSynthetic.AuthorizationInfo_RuntimeTransition
|
||||
|
||||
This event sends data indicating that a device has undergone a change of telemetry opt-in level detected at UTC startup, to help keep Windows up to date. The telemetry opt-in level signals what data we are allowed to collect.
|
||||
@ -3642,26 +3753,27 @@ The following fields are available:
|
||||
- **ComputePreemptionLevel** The maximum preemption level supported by GPU for compute payload.
|
||||
- **DDIInterfaceVersion** The device driver interface version.
|
||||
- **DedicatedSystemMemoryB** The amount of system memory dedicated for GPU use (in bytes).
|
||||
- **DedicatedVideoMemo** Amount of dedicated video memory in bytes.
|
||||
- **DedicatedVideoMemoryB** The amount of dedicated VRAM of the GPU (in bytes).
|
||||
- **DisplayAdapterLuid** The display adapter LUID.
|
||||
- **DriverDate** The date of the display driver.
|
||||
- **DriverRank** The rank of the display driver.
|
||||
- **DriverVersion** The display driver version.
|
||||
- **DriverWorkarounds** Bitfield data for specific driver workarounds enabled for this device.
|
||||
- **DriverWorkarounds.Length** The length of the DriverWorkarounds bitfield.
|
||||
- **DriverWorkarounds** Numeric value indicating the driver workarounds that are enabled for this device.
|
||||
- **DX10UMDFilePath** The file path to the location of the DirectX 10 Display User Mode Driver in the Driver Store.
|
||||
- **DX11UMDFilePath** The file path to the location of the DirectX 11 Display User Mode Driver in the Driver Store.
|
||||
- **DX12U** File path to the location of the DirectX 12 Display User Mode Driver in the Driver Store.
|
||||
- **DX12UMDFilePath** The file path to the location of the DirectX 12 Display User Mode Driver in the Driver Store.
|
||||
- **DX9UMDFilePath** The file path to the location of the DirectX 9 Display User Mode Driver in the Driver Store.
|
||||
- **GPUDeviceID** The GPU device ID.
|
||||
- **GPUPreemptionLevel** The maximum preemption level supported by GPU for graphics payload.
|
||||
- **GPURevisionID** The GPU revision ID.
|
||||
- **GPUVendorID** The GPU vendor ID.
|
||||
- **InterfaceFuncPointersProvided1** The number of device driver interface function pointers provided.
|
||||
- **InterfaceFuncPointersProvided2** The number of device driver interface function pointers provided.
|
||||
- **InterfaceFuncPointersProvided1** Number of device driver interface function pointers provided.
|
||||
- **InterfaceFuncPointersProvided2** Number of device driver interface function pointers provided.
|
||||
- **InterfaceId** The GPU interface ID.
|
||||
- **IsDisplayDevice** Does the GPU have displaying capabilities?
|
||||
- **IsHwSchEnabled** Indicates whether Hardware Scheduling is enabled.
|
||||
- **IsHwSchEnabled** Boolean value indicating whether hardware scheduling is enabled.
|
||||
- **IsHwSchSupported** Indicates whether the adapter supports hardware scheduling.
|
||||
- **IsHybridDiscrete** Does the GPU have discrete GPU capabilities in a hybrid device?
|
||||
- **IsHybridIntegrated** Does the GPU have integrated GPU capabilities in a hybrid device?
|
||||
@ -4216,7 +4328,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDriverBinaryAdd
|
||||
|
||||
This event provides the basic metadata about driver binaries running on the system.
|
||||
This event sends basic metadata about driver binaries running on the system to help keep Windows up to date.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
@ -4276,9 +4388,11 @@ The following fields are available:
|
||||
- **Date** The driver package date.
|
||||
- **Directory** The path to the driver package.
|
||||
- **DriverInBox** Is the driver included with the operating system?
|
||||
- **FlightIds** Driver Flight IDs.
|
||||
- **Inf** The INF name of the driver package.
|
||||
- **InventoryVersion** The version of the inventory file generating the events.
|
||||
- **Provider** The provider for the driver package.
|
||||
- **RecoveryIds** Driver recovery IDs.
|
||||
- **SubmissionId** The HLK submission ID for the driver package.
|
||||
- **Version** The version of the driver package.
|
||||
|
||||
@ -4804,71 +4918,79 @@ The following fields are available:
|
||||
|
||||
### Aria.160f0649efde47b7832f05ed000fc453.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_sample_rate** A number representing how often the client sends telemetry, expressed as a percentage. Low values indicate that said client sends more events and high values indicate that said client sends fewer events.
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event, where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **reconsentConfigs** A comma separated list of all reconsent configurations the current installation has received. Each configuration follows a well-defined format: 2DigitMonth-2DigitYear-3LetterKeyword.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Aria.29e24d069f27450385c7acaa2f07e277.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Aria.7005b72804a64fa4b2138faab88f877b.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Aria.754de735ccd546b28d0bfca8ac52c3de.Microsoft.WebBrowser.SystemInfo.Config
|
||||
@ -4877,21 +4999,24 @@ This config event sends basic device connectivity and configuration information
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_sample_rate** A number representing how often the client sends telemetry, expressed as a percentage. Low values indicate that said client sends more events and high values indicate that said client sends fewer events.
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Aria.af397ef28e484961ba48646a5d38cf54.Microsoft.WebBrowser.Installer.EdgeUpdate.Ping
|
||||
@ -4965,28 +5090,76 @@ The following fields are available:
|
||||
- **requestTestSource** Either '', 'dev', 'qa', 'prober', 'auto', or 'ossdev'. Any value except '' indicates that the request is a test and should not be counted toward normal metrics. Default: ''.
|
||||
- **requestUid** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha user. Each request attempt should have (with high probability) a unique request id. Default: ''.
|
||||
|
||||
### Microsoft.WebBrowser.Installer.EdgeUpdate.Ping
|
||||
|
||||
### Aria.f4a7d46e472049dfba756e11bdbbc08f.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This event sends hardware and software inventory information about the Microsoft Edge Update service, Microsoft Edge applications, and the current system environment, including app configuration, update configuration, and hardware capabilities. It's used to measure the reliability and performance of the EdgeUpdate service and if Microsoft Edge applications are up to date
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **appAp** Microsoft Edge Update parameters, including channel, architecture, platform, and additional parameters identifying the release of Microsoft Edge to update and how to install it. Example: 'beta-arch_x64-full'. Default: ''."
|
||||
- **appAppId** The GUID that identifies the product channels such as Edge Canary, Dev, Beta, Stable, and Edge Update.
|
||||
- **appBrandCode** The 4-digit brand code under which the the product was installed, if any. Possible values: 'GGLS' (default), 'GCEU' (enterprise install), and '' (unknown).
|
||||
- **appChannel** An integer indicating the channel of the installation (e.g. Canary or Dev).
|
||||
- **appClientId** A generalized form of the brand code that can accept a wider range of values and is used for similar purposes. Default: ''.
|
||||
- **appCohort** A machine-readable string identifying the release channel that the app belongs to. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appCohortHint** A machine-readable enum indicating that the client has a desire to switch to a different release cohort. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appCohortName** A stable non-localized human-readable enum indicating which (if any) set of messages the app should display to the user. For example, an app with a cohort name of 'beta' might display beta-specific branding to the user. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appConsentState** Bit flags describing the diagnostic data disclosure and response flow where 1 indicates the affirmative and 0 indicates the negative or unspecified data. Bit 1 indicates consent was given, bit 2 indicates data originated from the download page, bit 18 indicates choice for sending data about how the browser is used, and bit 19 indicates choice for sending data about websites visited.
|
||||
- **appDayOfInstall** The date-based counting equivalent of appInstallTimeDiffSec (the numeric calendar day that the app was installed on). This value is provided by the server in the response to the first request in the installation flow. Default: '-2' (Unknown).
|
||||
- **appExperiments** A semicolon-delimited key/value list of experiment identifiers and treatment groups. This field is unused and always empty in Edge Update. Default: ''.
|
||||
- **appIid** A GUID that identifies a particular installation flow. For example, each download of a product installer is tagged with a unique GUID. Attempts to install using that installer can then be grouped. A client SHOULD NOT persist the IID GUID after the installation flow of a product is complete.
|
||||
- **appInstallTimeDiffSec** The difference between the current time and the install date in seconds. '0' if unknown. Default: '-1'.
|
||||
- **appLang** The language of the product install, in IETF BCP 47 representation. Default: ''.
|
||||
- **appNextVersion** The version of the app that the update attempted to reach, regardless of the success or failure of the update operation. Default: '0.0.0.0'.
|
||||
- **appPingEventAppSize** The total number of bytes of all downloaded packages. Default: '0'.
|
||||
- **appPingEventDownloadMetricsDownloadedBytes** For events representing a download, the number of bytes expected to be downloaded. For events representing an entire update flow, the sum of all such expected bytes over the course of the update flow. Default: '0'.
|
||||
- **appPingEventDownloadMetricsDownloader** A string identifying the download algorithm and/or stack. Example values include: 'bits', 'direct', 'winhttp', 'p2p'. Sent in events that have an event type of '14' only. Default: ''.
|
||||
- **appPingEventDownloadMetricsDownloadTimeMs** For events representing a download, the time elapsed between the start of the download and the end of the download, in milliseconds. For events representing an entire update flow, the sum of all such download times over the course of the update flow. Sent in events that have an event type of '1', '2', '3', and '14' only. Default: '0'.
|
||||
- **appPingEventDownloadMetricsError** The error code (if any) of the operation, encoded as a signed base-10 integer. Default: '0'.
|
||||
- **appPingEventDownloadMetricsServerIpHint** For events representing a download, the CDN Host IP address that corresponds to the update file server. The CDN host is controlled by Microsoft servers and always maps to IP addresses hosting *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadMetricsTotalBytes** For events representing a download, the number of bytes expected to be downloaded. For events representing an entire update flow, the sum of all such expected bytes over the course of the update flow. Default: '0'.
|
||||
- **appPingEventDownloadMetricsUrl** For events representing a download, the CDN URL provided by the update server for the client to download the update, the URL is controlled by Microsoft servers and always maps back to either *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadTimeMs** For events representing a download, the time elapsed between the start of the download and the end of the download, in milliseconds. For events representing an entire update flow, the sum of all such download times over the course of the update flow. Sent in events that have an event type of '1', '2', '3', and '14' only. Default: '0'.
|
||||
- **appPingEventErrorCode** The error code (if any) of the operation, encoded as a signed, base-10 integer. Default: '0'.
|
||||
- **appPingEventEventResult** An enumeration indicating the result of the event. Common values are '0' (Error) and '1' (Success). Default: '0' (Error).
|
||||
- **appPingEventEventType** An enumeration indicating the type of the event and the event stage. Default: '0' (Unknown).
|
||||
- **appPingEventExtraCode1** Additional numeric information about the operation's result, encoded as a signed, base-10 integer. Default: '0'.
|
||||
- **appPingEventInstallTimeMs** For events representing an install, the time elapsed between the start of the install and the end of the install, in milliseconds. For events representing an entire update flow, the sum of all such durations. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appPingEventNumBytesDownloaded** The number of bytes downloaded for the specified application. Default: '0'.
|
||||
- **appPingEventSequenceId** An ID that uniquely identifies particular events within one requestId. Since a request can contain multiple ping events, this field is necessary to uniquely identify each possible event.
|
||||
- **appPingEventSourceUrlIndex** For events representing a download, the position of the download URL in the list of URLs supplied by the server in a tag.
|
||||
- **appPingEventUpdateCheckTimeMs** For events representing an entire update flow, the time elapsed between the start of the update check and the end of the update check, in milliseconds. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appUpdateCheckIsUpdateDisabled** The state of whether app updates are restricted by group policy. True if updates have been restricted by group policy or false if they have not.
|
||||
- **appUpdateCheckTargetVersionPrefix** A component-wise prefix of a version number, or a complete version number suffixed with the $ character. The prefix is interpreted a dotted-tuple that specifies the exactly-matching elements; it is not a lexical prefix (for example, '1.2.3' MUST match '1.2.3.4' but MUST NOT match '1.2.34'). Default: ''.
|
||||
- **appUpdateCheckTtToken** An opaque access token that can be used to identify the requesting client as a member of a trusted-tester group. If non-empty, the request is sent over SSL or another secure protocol. This field is unused by Edge Update and always empty. Default: ''.
|
||||
- **appVersion** The version of the product install. Default: '0.0.0.0'.
|
||||
- **eventType** A string representation of appPingEventEventType indicating the type of the event.
|
||||
- **hwHasAvx** '1' if the client's hardware supports the AVX instruction set. '0' if the client's hardware does not support the AVX instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse** '1' if the client's hardware supports the SSE instruction set. '0' if the client's hardware does not support the SSE instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse2** '1' if the client's hardware supports the SSE2 instruction set. '0' if the client's hardware does not support the SSE2 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse3** '1' if the client's hardware supports the SSE3 instruction set. '0' if the client's hardware does not support the SSE3 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse41** '1' if the client's hardware supports the SSE4.1 instruction set. '0' if the client's hardware does not support the SSE4.1 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse42** '1' if the client's hardware supports the SSE4.2 instruction set. '0' if the client's hardware does not support the SSE4.2 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSsse3** '1' if the client's hardware supports the SSSE3 instruction set. '0' if the client's hardware does not support the SSSE3 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwPhysmemory** The physical memory available to the client, truncated down to the nearest gibibyte. '-1' if unknown. This value is intended to reflect the maximum theoretical storage capacity of the client, not including any hard drive or paging to a hard drive or peripheral. Default: '-1'.
|
||||
- **isMsftDomainJoined** '1' if the client is a member of a Microsoft domain. '0' otherwise. Default: '0'.
|
||||
- **osArch** The architecture of the operating system (e.g. 'x86', 'x64', 'arm'). '' if unknown. Default: ''.
|
||||
- **osPlatform** The operating system family that the within which the Omaha client is running (e.g. 'win', 'mac', 'linux', 'ios', 'android'). '' if unknown. The operating system name should be transmitted in lowercase with minimal formatting. Default: ''.
|
||||
- **osServicePack** The secondary version of the operating system. '' if unknown. Default: ''.
|
||||
- **osVersion** The primary version of the operating system. '' if unknown. Default: ''.
|
||||
- **requestCheckPeriodSec** The update interval in seconds. The value is read from the registry. Default: '-1'.
|
||||
- **requestDlpref** A comma-separated list of values specifying the preferred download URL behavior. The first value is the highest priority, further values reflect secondary, tertiary, et cetera priorities. Legal values are '' (in which case the entire list must be empty, indicating unknown or no-preference) or 'cacheable' (the server should prioritize sending URLs that are easily cacheable). Default: ''.
|
||||
- **requestDomainJoined** '1' if the device is part of a managed enterprise domain. Otherwise '0'.
|
||||
- **requestInstallSource** A string specifying the cause of the update flow. For example: 'ondemand', or 'scheduledtask'. Default: ''.
|
||||
- **requestIsMachine** '1' if the client is known to be installed with system-level or administrator privileges. '0' otherwise. Default: '0'.
|
||||
- **requestOmahaShellVersion** The version of the Omaha installation folder. Default: ''.
|
||||
- **requestOmahaVersion** The version of the Omaha updater itself (the entity sending this request). Default: '0.0.0.0'.
|
||||
- **requestProtocolVersion** The version of the Omaha protocol. Compatible clients MUST provide a value of '3.0'. Compatible clients MUST always transmit this attribute. Default: undefined.
|
||||
- **requestRequestId** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha request. Each request attempt SHOULD have (with high probability) a unique request id. Default: ''.
|
||||
- **requestSessionCorrelationVectorBase** A client generated random MS Correlation Vector base code used to correlate the update session with update and CDN servers. Default: ''.
|
||||
- **requestSessionId** A randomly-generated (uniformly distributed) GUID. Each single update flow (e.g. update check, update application, event ping sequence) SHOULD have (with high probability) a single unique session ID. Default: ''.
|
||||
- **requestTestSource** Either '', 'dev', 'qa', 'prober', 'auto', or 'ossdev'. Any value except '' indicates that the request is a test and should not be counted toward normal metrics. Default: ''.
|
||||
- **requestUid** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha user. Each request attempt SHOULD have (with high probability) a unique request id. Default: ''.
|
||||
|
||||
|
||||
## Migration events
|
||||
@ -5258,8 +5431,8 @@ The following fields are available:
|
||||
- **originatingContextName** The name of the originating call context that resulted in the failure.
|
||||
- **threadId** The ID of the thread on which the activity is executing.
|
||||
|
||||
## Privacy notifier events
|
||||
|
||||
## Privacy notifier events
|
||||
|
||||
### Microsoft.Windows.Shell.PrivacyNotifierLogging.PrivacyNotifierCompleted
|
||||
|
||||
@ -5276,6 +5449,85 @@ The following fields are available:
|
||||
- **resetSettingsResult** The return code of the action to correct the known issue.
|
||||
|
||||
|
||||
## Quality Update Assistant events
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Applicability
|
||||
|
||||
This event sends basic info on whether the device should be updated to the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **dayspendingrebootafterfu** Number of days that have elapsed since the device reached ready to reboot for a Feature Update that is still actively pending reboot.
|
||||
- **ExecutionRequestId** Identifier of the Execution Request that launched the QualityUpdateAssistant process.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **IsApplicable** Indicates whether the update is applicable to this device.
|
||||
- **KBNumber** KBNumber of the update being installed.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Reason** Provides information on reasons why the update is not applicable to the device.
|
||||
- **Result** Applicability check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.DeviceReadinessCheck
|
||||
|
||||
This event sends basic info on whether the device is ready to download the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **ExecutionRequestId** Identifier of the Execution Request that launched the QualityUpdateAssistant process.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **KBNumber** KBNumber of the update being installed.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **QualityUpdateReadinessProcessorMaxSpeed** Processor max speed.
|
||||
- **Reason** Indicates why the device did not pass the readiness check.
|
||||
- **Result** Device readiness check for quality update assistant.
|
||||
- **VirtualMemoryUsedByCurrentProcess** Virtual memory in use by the Quality Update Assistant process.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Download
|
||||
|
||||
This event sends basic info when download of the latest cumulative update begins.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **DODownloadHResult** Result code from Delivery Optimization when used to download the quality update.
|
||||
- **DownloadMode** Indicates how the quality update was downloaded.
|
||||
- **ExecutionRequestId** Identifier of the Execution Request that launched the QualityUpdateAssistant process.
|
||||
- **GlobalEventCounter** Client side counter that indicates ordering of events sent by this device.
|
||||
- **HttpsDownloadHResult** Result code when HTTPS is used to download the quality update.
|
||||
- **InstallMode** Indicates which installation method was used to attempt the install of the quality update.
|
||||
- **KBNumber** KBNumber of the update being installed.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **QualityUpdateDeviceHasMinimumUptime** Indicates whether the device has the minimum uptime required to install a quality update.
|
||||
- **Result** Download of latest cumulative update payload.
|
||||
- **Scenario** Indicates if the installation step succeeded or failed.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Install
|
||||
|
||||
This event sends basic info on the result of the installation of the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **DismInstallHResult** Internal result code from DISM when used to install the quality update.
|
||||
- **ExecutionRequestId** Identifier of the Execution Request that launched the QualityUpdateAssistant process.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **InstallMode** Indicates which installation method was used to attempt the install of the quality update.
|
||||
- **KBNumber** KBNumber of the update being installed.
|
||||
- **launchretrycounter** Count of the number of times the install has been retried in the event of a non-successful installation attempt.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **QualityUpdateDismErrorCode** Error code returned when DISM is used to install the quality update.
|
||||
- **QualityUpdatePendingRebootAfterInstallStage** Indicates if the device is pending reboot after install is complete.
|
||||
- **QualityUpdateSecondsInstallStage** Time spent installing the quality update.
|
||||
- **QualityUpdateWusaErrorCode** Error code returned when WUSA is used to install the quality update.
|
||||
- **Result** Install of latest cumulative update payload.
|
||||
- **Scenario** Indicates if the installation step succeeded or failed.
|
||||
- **WusaInstallHResult** Internal result code from WUSA when used to install the quality update.
|
||||
|
||||
|
||||
## Remediation events
|
||||
|
||||
### Microsoft.Windows.Remediation.Applicable
|
||||
@ -5789,7 +6041,7 @@ This event sends basic metadata about the update installation process generated
|
||||
|
||||
### SetupPlatformTel.SetupPlatformTelEvent
|
||||
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios.
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -7650,7 +7902,7 @@ The following fields are available:
|
||||
- **groupConnectionCount** The total number of connections made to peers in the same group.
|
||||
- **internetConnectionCount** The total number of connections made to peers not in the same LAN or the same group.
|
||||
- **isEncrypted** TRUE if the file is encrypted and will be decrypted after download.
|
||||
- **isThrottled** Indicates the Event Rate was throttled (event represent aggregated data).
|
||||
- **isThrottled** Event Rate throttled (event represents aggregated data).
|
||||
- **isVpn** Is the device connected to a Virtual Private Network?
|
||||
- **jobID** Identifier for the Windows Update job.
|
||||
- **lanConnectionCount** The total number of connections made to peers in the same LAN.
|
||||
@ -8230,7 +8482,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.FlightInapplicable
|
||||
|
||||
This event indicates that the update is no longer applicable to this device.
|
||||
This event sends data on whether the update was applicable to the device, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -8316,7 +8568,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.PostInstall
|
||||
|
||||
This event is sent after a Windows update install completes.
|
||||
This event sends data about lite stack devices (mobile, IOT, anything non-PC) immediately before data migration is launched to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -8623,6 +8875,22 @@ The following fields are available:
|
||||
- **wuDeviceid** The Windows Update device GUID.
|
||||
|
||||
|
||||
### Microsoft.Windows.UpdateHealthTools.UpdateHealthToolsPushNotificationStatus
|
||||
|
||||
This event is received when there is status on a push notification.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
||||
- **PackageVersion** Current package version of UpdateHealthTools.
|
||||
- **UpdateHealthToolsDeviceUri** The URI to be used for push notifications on this device.
|
||||
- **UpdateHealthToolsEnterpriseActionType** Enum describing the type of action requested by the push.
|
||||
- **UpdateHealthToolsPushCurrentRequestId** The request ID for the push.
|
||||
- **UpdateHealthToolsPushCurrentResults** The results from the push request.
|
||||
- **UpdateHealthToolsPushCurrentStep** The current step for the push notification
|
||||
|
||||
|
||||
## Windows Update mitigation events
|
||||
|
||||
### Mitigation360Telemetry.MitigationCustom.CleanupSafeOsImages
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
description: Use this article to learn more about what Windows diagnostic data is gathered at the basic level. Specific to Windows 10, version 1903.
|
||||
title: Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields (Windows 10)
|
||||
description: Use this article to learn more about what required Windows diagnostic data is gathered.
|
||||
title: Windows 10, version 1909 and Windows 10, version 1903 required diagnostic events and fields (Windows 10)
|
||||
keywords: privacy, telemetry
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -13,11 +13,16 @@ manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.date: 12/10/2019
|
||||
ms.date: 03/27/2020
|
||||
---
|
||||
|
||||
|
||||
# Windows 10, version 1903 and Windows 10, version 1909 basic level Windows diagnostic events and fields
|
||||
# Windows 10, version 1909 and Windows 10, version 1903 required Windows diagnostic events and fields
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Windows is moving to classifying the data collected from customer’s devices as either *Required* or *Optional*.
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
@ -25,9 +30,9 @@ ms.date: 12/10/2019
|
||||
- Windows 10, version 1903
|
||||
|
||||
|
||||
The Basic level gathers a limited set of information that is critical for understanding the device and its configuration including: basic device information, quality-related information, app compatibility, and Microsoft Store. When the level is set to Basic, it also includes the Security level information.
|
||||
Required diagnostic data gathers a limited set of information that is critical for understanding the device and its configuration including: basic device information, quality-related information, app compatibility, and Microsoft Store.
|
||||
|
||||
The Basic level helps to identify problems that can occur on a particular device hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a particular driver version. This helps Microsoft fix operating system or app problems.
|
||||
Required diagnostic data helps to identify problems that can occur on a particular device hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a particular driver version. This helps Microsoft fix operating system or app problems.
|
||||
|
||||
Use this article to learn about diagnostic events, grouped by event area, and the fields within each event. A brief description is provided for each field. Every event generated includes common data, which collects device data.
|
||||
|
||||
@ -269,6 +274,8 @@ The following fields are available:
|
||||
- **DatasourceApplicationFile_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceApplicationFile_RS1** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **DatasourceApplicationFile_RS2** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **DatasourceApplicationFile_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -280,6 +287,8 @@ The following fields are available:
|
||||
- **DatasourceDevicePnp_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_RS1** The total DataSourceDevicePnp objects targeting Windows 10 version 1607 on this device.
|
||||
- **DatasourceDevicePnp_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDevicePnp_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -294,6 +303,8 @@ The following fields are available:
|
||||
- **DatasourceDriverPackage_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceDriverPackage_RS1** The total DataSourceDriverPackage objects targeting Windows 10 version 1607 on this device.
|
||||
- **DatasourceDriverPackage_RS2** The total DataSourceDriverPackage objects targeting Windows 10, version 1703 on this device.
|
||||
- **DatasourceDriverPackage_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -308,6 +319,8 @@ The following fields are available:
|
||||
- **DataSourceMatchingInfoBlock_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_RS1** The total DataSourceMatchingInfoBlock objects targeting Windows 10 version 1607 on this device.
|
||||
- **DataSourceMatchingInfoBlock_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoBlock_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -319,6 +332,8 @@ The following fields are available:
|
||||
- **DataSourceMatchingInfoPassive_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_RS1** The total DataSourceMatchingInfoPassive objects targeting Windows 10 version 1607 on this device.
|
||||
- **DataSourceMatchingInfoPassive_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -326,11 +341,12 @@ The following fields are available:
|
||||
- **DataSourceMatchingInfoPassive_RS5** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_TH1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPassive_TH2** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPoltUpgrade_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_19H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_RS1** The total DataSourceMatchingInfoPostUpgrade objects targeting Windows 10 version 1607 on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_RS2** The total DataSourceMatchingInfoPostUpgrade objects targeting Windows 10 version 1703 on this device.
|
||||
- **DataSourceMatchingInfoPostUpgrade_RS3** The total DataSourceMatchingInfoPostUpgrade objects targeting Windows 10 version 1709 on this device.
|
||||
@ -343,6 +359,8 @@ The following fields are available:
|
||||
- **DatasourceSystemBios_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DatasourceSystemBios_RS1** The total DatasourceSystemBios objects targeting Windows 10 version 1607 present on this device.
|
||||
- **DatasourceSystemBios_RS2** The total DatasourceSystemBios objects targeting Windows 10 version 1703 present on this device.
|
||||
- **DatasourceSystemBios_RS3** The total DatasourceSystemBios objects targeting Windows 10 version 1709 present on this device.
|
||||
@ -357,6 +375,8 @@ The following fields are available:
|
||||
- **DecisionApplicationFile_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_RS1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionApplicationFile_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -368,6 +388,8 @@ The following fields are available:
|
||||
- **DecisionDevicePnp_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_RS1** The total DecisionDevicePnp objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionDevicePnp_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDevicePnp_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -382,6 +404,8 @@ The following fields are available:
|
||||
- **DecisionDriverPackage_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_RS1** The total DecisionDriverPackage objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionDriverPackage_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionDriverPackage_RS3** The count of the number of this particular object type present on this device.
|
||||
@ -396,6 +420,8 @@ The following fields are available:
|
||||
- **DecisionMatchingInfoBlock_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoBlock_RS1** The total DecisionMatchingInfoBlock objects targeting Windows 10 version 1607 present on this device.
|
||||
- **DecisionMatchingInfoBlock_RS2** The total DecisionMatchingInfoBlock objects targeting Windows 10 version 1703 present on this device.
|
||||
- **DecisionMatchingInfoBlock_RS3** The total DecisionMatchingInfoBlock objects targeting Windows 10 version 1709 present on this device.
|
||||
@ -407,6 +433,8 @@ The following fields are available:
|
||||
- **DecisionMatchingInfoPassive_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_RS1** The total DecisionMatchingInfoPassive objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionMatchingInfoPassive_RS2** The total DecisionMatchingInfoPassive objects targeting Windows 10 version 1703 on this device.
|
||||
- **DecisionMatchingInfoPassive_RS3** The total DecisionMatchingInfoPassive objects targeting Windows 10 version 1803 on this device.
|
||||
@ -414,11 +442,12 @@ The following fields are available:
|
||||
- **DecisionMatchingInfoPassive_RS5** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_TH1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPassive_TH2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPoltUpgrade_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_19H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_19H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_RS1** The total DecisionMatchingInfoPostUpgrade objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_RS2** The total DecisionMatchingInfoPostUpgrade objects targeting Windows 10 version 1703 on this device.
|
||||
- **DecisionMatchingInfoPostUpgrade_RS3** The total DecisionMatchingInfoPostUpgrade objects targeting Windows 10 version 1709 on this device.
|
||||
@ -430,6 +459,8 @@ The following fields are available:
|
||||
- **DecisionMediaCenter_19H1Setup** The total DecisionMediaCenter objects targeting the next release of Windows on this device.
|
||||
- **DecisionMediaCenter_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMediaCenter_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMediaCenter_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMediaCenter_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionMediaCenter_RS1** The total DecisionMediaCenter objects targeting Windows 10 version 1607 present on this device.
|
||||
- **DecisionMediaCenter_RS2** The total DecisionMediaCenter objects targeting Windows 10 version 1703 present on this device.
|
||||
- **DecisionMediaCenter_RS3** The total DecisionMediaCenter objects targeting Windows 10 version 1709 present on this device.
|
||||
@ -442,6 +473,8 @@ The following fields are available:
|
||||
- **DecisionSystemBios_19H1Setup** The total DecisionSystemBios objects targeting the next release of Windows on this device.
|
||||
- **DecisionSystemBios_20H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemBios_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemBios_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemBios_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemBios_RS1** The total DecisionSystemBios objects targeting Windows 10 version 1607 on this device.
|
||||
- **DecisionSystemBios_RS2** The total DecisionSystemBios objects targeting Windows 10 version 1703 on this device.
|
||||
- **DecisionSystemBios_RS3** The total DecisionSystemBios objects targeting Windows 10 version 1709 on this device.
|
||||
@ -454,6 +487,8 @@ The following fields are available:
|
||||
- **DecisionSystemBios_TH2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionSystemProcessor_RS2** The count of the number of this particular object type present on this device.
|
||||
- **DecisionTest_20H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionTest_21H1** The count of the number of this particular object type present on this device.
|
||||
- **DecisionTest_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **DecisionTest_RS1** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **InventoryApplicationFile** The count of the number of this particular object type present on this device.
|
||||
- **InventoryDeviceContainer** A count of device container objects in cache.
|
||||
@ -482,6 +517,8 @@ The following fields are available:
|
||||
- **Wmdrm_19H1Setup** The total Wmdrm objects targeting the next release of Windows on this device.
|
||||
- **Wmdrm_20H1** The count of the number of this particular object type present on this device.
|
||||
- **Wmdrm_20H1Setup** The total Wmdrm objects targeting the next release of Windows on this device.
|
||||
- **Wmdrm_21H1** The count of the number of this particular object type present on this device.
|
||||
- **Wmdrm_21H1Setup** The count of the number of this particular object type present on this device.
|
||||
- **Wmdrm_RS1** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **Wmdrm_RS2** An ID for the system, calculated by hashing hardware identifiers.
|
||||
- **Wmdrm_RS3** An ID for the system, calculated by hashing hardware identifiers.
|
||||
@ -616,6 +653,7 @@ This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedevic
|
||||
The following fields are available:
|
||||
|
||||
- **AppraiserVersion** The version of the appraiser file generating the events.
|
||||
- **ResolveAttempted** This will always be an empty string when sending diagnostic data.
|
||||
|
||||
|
||||
### Microsoft.Windows.Appraiser.General.DataSourceMatchingInfoBlockStartSync
|
||||
@ -847,10 +885,12 @@ The following fields are available:
|
||||
- **AppraiserVersion** The version of the appraiser file generating the events.
|
||||
- **BlockingApplication** Are there are any application issues that interfere with upgrade due to matching info blocks?
|
||||
- **DisplayGenericMessage** Will a generic message be shown for this block?
|
||||
- **NeedsDismissAction** Will the file cause an action that can be dismissed?
|
||||
- **NeedsUninstallAction** Does the user need to take an action in setup due to a matching info block?
|
||||
- **SdbBlockUpgrade** Is a matching info block blocking upgrade?
|
||||
- **SdbBlockUpgradeCanReinstall** Is a matching info block blocking upgrade, but has the can reinstall tag?
|
||||
- **SdbBlockUpgradeUntilUpdate** Is a matching info block blocking upgrade but has the until update tag?
|
||||
- **SdbReinstallUpgradeWarn** The file is tagged as needing to be reinstalled after upgrade with a warning in the SDB. It does not block upgrade.
|
||||
|
||||
|
||||
### Microsoft.Windows.Appraiser.General.DecisionMatchingInfoBlockStartSync
|
||||
@ -1732,6 +1772,7 @@ The following fields are available:
|
||||
- **IsDomainJoined** Indicates whether a machine is joined to a domain.
|
||||
- **IsEDPEnabled** Represents if Enterprise data protected on the device.
|
||||
- **IsMDMEnrolled** Whether the device has been MDM Enrolled or not.
|
||||
- **MDMServiceProvider** A hash of the specific MDM authority, such as Microsoft Intune, that is managing the device.
|
||||
- **MPNId** Returns the Partner ID/MPN ID from Regkey. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DeployID
|
||||
- **SCCMClientId** This ID correlate systems that send data to Compat Analytics (OMS) and other OMS based systems with systems in a Configuration Manager environment.
|
||||
- **ServerFeatures** Represents the features installed on a Windows Server. This can be used by developers and administrators who need to automate the process of determining the features installed on a set of server computers.
|
||||
@ -1781,6 +1822,7 @@ The following fields are available:
|
||||
- **DeviceName** The device name that is set by the user.
|
||||
- **DigitizerSupport** Is a digitizer supported?
|
||||
- **DUID** The device unique ID.
|
||||
- **EnclosureKind** Windows.Devices.Enclosure.EnclosureKind enum values representing each unique enclosure posture kind.
|
||||
- **Gyroscope** Indicates whether the device has a gyroscope (a mechanical component that measures and maintains orientation).
|
||||
- **InventoryId** The device ID used for compatibility testing.
|
||||
- **Magnetometer** Indicates whether the device has a magnetometer (a mechanical component that works like a compass).
|
||||
@ -1965,10 +2007,14 @@ The following fields are available:
|
||||
- **HVCIRunning** Hypervisor Code Integrity (HVCI) enables Device Guard to help protect kernel mode processes and drivers from vulnerability exploits and zero days. HVCI uses the processor’s functionality to force all software running in kernel mode to safely allocate memory. This field tells if HVCI is running.
|
||||
- **IsSawGuest** Indicates whether the device is running as a Secure Admin Workstation Guest.
|
||||
- **IsSawHost** Indicates whether the device is running as a Secure Admin Workstation Host.
|
||||
- **IsWdagFeatureEnabled** Indicates whether Windows Defender Application Guard is enabled.
|
||||
- **RequiredSecurityProperties** Describes the required security properties to enable virtualization-based security.
|
||||
- **SecureBootCapable** Systems that support Secure Boot can have the feature turned off via BIOS. This field tells if the system is capable of running Secure Boot, regardless of the BIOS setting.
|
||||
- **SModeState** The Windows S mode trail state.
|
||||
- **SystemGuardState** Indicates the SystemGuard state. NotCapable (0), Capable (1), Enabled (2), Error (0xFF).
|
||||
- **TpmReadyState** Indicates the TPM ready state. NotReady (0), ReadyForStorage (1), ReadyForAttestation (2), Error (0xFF).
|
||||
- **VBSState** Virtualization-based security (VBS) uses the hypervisor to help protect the kernel and other parts of the operating system. Credential Guard and Hypervisor Code Integrity (HVCI) both depend on VBS to isolate/protect secrets, and kernel-mode code integrity validation. VBS has a tri-state that can be Disabled, Enabled, or Running.
|
||||
- **WdagPolicyValue** The Windows Defender Application Guard policy.
|
||||
|
||||
|
||||
### Census.Speech
|
||||
@ -2109,7 +2155,7 @@ The following fields are available:
|
||||
- **IsVirtualDevice** Retrieves that when the Hypervisor is Microsoft's Hyper-V Hypervisor or other Hv#1 Hypervisor, this field will be set to FALSE for the Hyper-V host OS and TRUE for any guest OS's. This field should not be relied upon for non-Hv#1 Hypervisors.
|
||||
- **SLATSupported** Represents whether Second Level Address Translation (SLAT) is supported by the hardware.
|
||||
- **VirtualizationFirmwareEnabled** Represents whether virtualization is enabled in the firmware.
|
||||
- **VMId** A string that uniquely identifies a virtual machine.
|
||||
- **VMId** A string that identifies a virtual machine.
|
||||
|
||||
|
||||
### Census.WU
|
||||
@ -2197,6 +2243,7 @@ The following fields are available:
|
||||
- **ext_app** Describes the properties of the running application. This extension could be populated by either a client app or a web app. See [Common Data Extensions.app](#common-data-extensionsapp).
|
||||
- **ext_container** Describes the properties of the container for events logged within a container. See [Common Data Extensions.container](#common-data-extensionscontainer).
|
||||
- **ext_device** Describes the device-related fields. See [Common Data Extensions.device](#common-data-extensionsdevice).
|
||||
- **ext_m365a** Describes the Microsoft 365-related fields. See [Common Data Extensions.m365a](#common-data-extensionsm365a).
|
||||
- **ext_mscv** Describes the correlation vector-related fields. See [Common Data Extensions.mscv](#common-data-extensionsmscv).
|
||||
- **ext_os** Describes the operating system properties that would be populated by the client. See [Common Data Extensions.os](#common-data-extensionsos).
|
||||
- **ext_sdk** Describes the fields related to a platform library required for a specific SDK. See [Common Data Extensions.sdk](#common-data-extensionssdk).
|
||||
@ -2208,6 +2255,14 @@ The following fields are available:
|
||||
- **time** Represents the event date time in Coordinated Universal Time (UTC) when the event was generated on the client. This should be in ISO 8601 format.
|
||||
- **ver** Represents the major and minor version of the extension.
|
||||
|
||||
### Common Data Extensions.m365a
|
||||
|
||||
Describes the Microsoft 365-related fields.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **enrolledTenantId** The enrolled tenant ID.
|
||||
- **msp** A bitmask that lists the active programs.
|
||||
|
||||
### Common Data Extensions.mscv
|
||||
|
||||
@ -2276,6 +2331,7 @@ The following fields are available:
|
||||
- **providerGuid** The ETW provider ID associated with the provider name.
|
||||
- **raId** Represents the ETW Related ActivityId. Logged via TraceLogging or directly via ETW.
|
||||
- **seq** Represents the sequence field used to track absolute order of uploaded events. It is an incrementing identifier for each event added to the upload queue. The Sequence helps track how many events were fired and how many events were uploaded and enables identification of data lost during upload and de-duplication of events on the ingress server.
|
||||
- **sqmId** The Windows SQM (Software Quality Metrics—a precursor of Windows 10 Diagnostic Data collection) device identifier.
|
||||
- **stId** Represents the Scenario Entry Point ID. This is a unique GUID for each event in a diagnostic scenario. This used to be Scenario Trigger ID.
|
||||
- **wcmp** The Windows Shell Composer ID.
|
||||
- **wPId** The Windows Core OS product ID.
|
||||
@ -2325,7 +2381,7 @@ The following fields are available:
|
||||
|
||||
### CbsServicingProvider.CbsCapabilityEnumeration
|
||||
|
||||
This event reports on the results of scanning for optional Windows content on Windows Update.
|
||||
This event reports on the results of scanning for optional Windows content on Windows Update to keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -2610,6 +2666,22 @@ The following fields are available:
|
||||
- **RestrictedNetworkTime** Retrieves the time spent on a metered (cost restricted) network in seconds.
|
||||
|
||||
|
||||
### TelClientSynthetic.EventMonitor_0
|
||||
|
||||
This event provides statistics for specific diagnostic events.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ConsumerCount** The number of instances seen in the Event Tracing for Windows consumer.
|
||||
- **EventName** The name of the event being monitored.
|
||||
- **EventSnFirst** The expected first event serial number.
|
||||
- **EventSnLast** The expected last event serial number.
|
||||
- **EventStoreCount** The number of events reaching the event store.
|
||||
- **MonitorSn** The serial number of the monitor.
|
||||
- **TriggerCount** The number of events reaching the trigger buffer.
|
||||
- **UploadedCount** The number of events uploaded.
|
||||
|
||||
|
||||
### TelClientSynthetic.GetFileInfoAction_FilePathNotApproved_0
|
||||
|
||||
This event occurs when the DiagTrack escalation fails due to the scenario requesting a path that is not approved for GetFileInfo actions.
|
||||
@ -2809,6 +2881,22 @@ This event is a low latency health alert that is part of the 4Nines device healt
|
||||
|
||||
|
||||
|
||||
## Direct to update events
|
||||
|
||||
### Microsoft.Windows.DirectToUpdate.DTUHandlerCheckApplicabilityGenericFailure
|
||||
|
||||
This event indicates that we have received an unexpected error in the Direct to Update (DTU) Handler CheckApplicability call.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CampaignID** Campaign ID being run
|
||||
- **ClientID** Client ID being run
|
||||
- **CoordinatorVersion** Coordinator version of DTU
|
||||
- **CV** Correlation vector
|
||||
- **CV_new** New correlation vector
|
||||
- **hResult** HRESULT of the failure
|
||||
|
||||
|
||||
## DISM events
|
||||
|
||||
### Microsoft.Windows.StartRepairCore.DISMLatestInstalledLCU
|
||||
@ -3007,12 +3095,12 @@ The following fields are available:
|
||||
- **ComputePreemptionLevel** The maximum preemption level supported by GPU for compute payload.
|
||||
- **DedicatedSystemMemoryB** The amount of system memory dedicated for GPU use (in bytes).
|
||||
- **DedicatedVideoMemoryB** The amount of dedicated VRAM of the GPU (in bytes).
|
||||
- **Display1UMDFilePath** File path to the location of the Display User Mode Driver in the Driver Store.
|
||||
- **Display1UMDFilePath** The file path to the location of the Display User Mode Driver in the Driver Store.
|
||||
- **DisplayAdapterLuid** The display adapter LUID.
|
||||
- **DriverDate** The date of the display driver.
|
||||
- **DriverRank** The rank of the display driver.
|
||||
- **DriverVersion** The display driver version.
|
||||
- **DriverWorkarounds** Numeric value indicating the driver workarounds enabled for this device.
|
||||
- **DriverWorkarounds** Numeric value indicating the driver workarounds that are enabled for this device.
|
||||
- **DX10UMDFilePath** The file path to the location of the DirectX 10 Display User Mode Driver in the Driver Store.
|
||||
- **DX11UMDFilePath** The file path to the location of the DirectX 11 Display User Mode Driver in the Driver Store.
|
||||
- **DX12UMDFilePath** The file path to the location of the DirectX 12 Display User Mode Driver in the Driver Store.
|
||||
@ -3203,21 +3291,6 @@ The following fields are available:
|
||||
|
||||
## Holographic events
|
||||
|
||||
### Microsoft.Windows.Analog.Spectrum.TelemetryHolographicDeviceAdded
|
||||
|
||||
This event indicates Windows Mixed Reality device state. This event is also used to count WMR device.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ClassGuid** Windows Mixed Reality device class GUID.
|
||||
- **DeviceInterfaceId** Windows Mixed Reality device interface ID.
|
||||
- **DeviceName** Windows Mixed Reality device name.
|
||||
- **DriverVersion** Windows Mixed Reality device driver version.
|
||||
- **FirmwareVersion** Windows Mixed Reality firmware version.
|
||||
- **Manufacturer** Windows Mixed Reality device manufacturer.
|
||||
- **ModelName** Windows Mixed Reality device model name.
|
||||
- **SerialNumber** Windows Mixed Reality device serial number.
|
||||
|
||||
### Microsoft.Windows.Holographic.Coordinator.HoloShellStateUpdated
|
||||
|
||||
This event indicates Windows Mixed Reality HoloShell State. This event is also used to count WMR device.
|
||||
@ -3327,7 +3400,6 @@ The following fields are available:
|
||||
- **InventoryMiscellaneousOfficeVBA** A count of office vba objects in cache
|
||||
- **InventoryMiscellaneousOfficeVBARuleViolations** A count of office vba rule violations objects in cache
|
||||
- **InventoryMiscellaneousUUPInfo** A count of uup info objects in cache
|
||||
- **InventoryVersion** The version of the inventory file generating the events.
|
||||
- **Metadata** A count of metadata objects in cache.
|
||||
- **Orphan** A count of orphan file objects in cache.
|
||||
- **Programs** A count of program objects in cache.
|
||||
@ -3702,7 +3774,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDriverBinaryAdd
|
||||
|
||||
This event provides the basic metadata about driver binaries running on the system.
|
||||
This event sends basic metadata about driver binaries running on the system to help keep Windows up to date.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
@ -3762,9 +3834,11 @@ The following fields are available:
|
||||
- **Date** The driver package date.
|
||||
- **Directory** The path to the driver package.
|
||||
- **DriverInBox** Is the driver included with the operating system?
|
||||
- **FlightIds** Driver Flight IDs.
|
||||
- **Inf** The INF name of the driver package.
|
||||
- **InventoryVersion** The version of the inventory file generating the events.
|
||||
- **Provider** The provider for the driver package.
|
||||
- **RecoveryIds** Driver recovery IDs.
|
||||
- **SubmissionId** The HLK submission ID for the driver package.
|
||||
- **Version** The version of the driver package.
|
||||
|
||||
@ -4301,71 +4375,84 @@ The following fields are available:
|
||||
|
||||
### Aria.160f0649efde47b7832f05ed000fc453.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_sample_rate** A number representing how often the client sends telemetry, expressed as a percentage. Low values indicate that said client sends more events and high values indicate that said client sends fewer events.
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event, where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **reconsentConfigs** A comma separated list of all reconsent configurations the current installation has received. Each configuration follows a well-defined format: 2DigitMonth-2DigitYear-3LetterKeyword.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Aria.29e24d069f27450385c7acaa2f07e277.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_sample_rate** A number representing how often the client sends telemetry, expressed as a percentage. Low values indicate that said client sends more events and high values indicate that said client sends fewer events.
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **reconsentConfigs** A comma separated list of all reconsent configurations the current installation has received. Each configuration follows a well-defined format: 2DigitMonth-2DigitYear-3LetterKeyword.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Aria.7005b72804a64fa4b2138faab88f877b.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_env** The environment from which the event was logged when testing; otherwise, the field is omitted or left blank.
|
||||
- **app_sample_rate** A number representing how often the client sends telemetry, expressed as a percentage. Low values indicate that said client sends more events and high values indicate that said client sends fewer events.
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **reconsentConfigs** A comma separated list of all reconsent configurations the current installation has received. Each configuration follows a well-defined format: 2DigitMonth-2DigitYear-3LetterKeyword.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Aria.754de735ccd546b28d0bfca8ac52c3de.Microsoft.WebBrowser.SystemInfo.Config
|
||||
@ -4374,21 +4461,25 @@ This config event sends basic device connectivity and configuration information
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_version** The internal Microsoft Edge build version string.
|
||||
- **appConsentState** Bit flags that describe the consent for data collection on the device, or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **app_sample_rate** A number representing how often the client sends telemetry, expressed as a percentage. Low values indicate that said client sends more events and high values indicate that said client sends fewer events.
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A non-durable unique identifier with which all other diagnostic client data is associated. This value is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. Possible values: Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth
|
||||
- **container_client_id** The client ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **container_session_id** The session ID of the container if the device is in Windows Defender Application Guard mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. There is not value in this field is the device is at the Basic diagnostic data level.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event. Possible values: 1 -- Basic, 2 -- Enhanced, 3 -- Full
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation. Possible values: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with. Possible values: 0 -- Unknown, 1 -- Stability, 2 -- On-going, 3 -- Independent, 4 -- UKM, or 5 -- Instance level
|
||||
- **session_id** An ordered identifier that is guaranteed to be greater than the previous session identifier each time the user launches the application, reset on subsequent launch after client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **reconsentConfigs** A comma separated list of all reconsent configurations the current installation has received. Each configuration follows a well-defined format: 2DigitMonth-2DigitYear-3LetterKeyword.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Aria.af397ef28e484961ba48646a5d38cf54.Microsoft.WebBrowser.Installer.EdgeUpdate.Ping
|
||||
@ -4397,17 +4488,118 @@ This event sends hardware and software inventory information about the Microsoft
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **appAp** Microsoft Edge Update parameters, including channel, architecture, platform, and additional parameters identifying the release of Microsoft Edge to update and how to install it. Example: 'beta-arch_x64-full'. Default: ''.
|
||||
- **appAp** Any additional parameters for the specified application. Default: ''.
|
||||
- **appAppId** The GUID that identifies the product. Compatible clients must transmit this attribute. Please see the wiki for additional information. Default: undefined.
|
||||
- **appBrandCode** The brand code under which the product was installed, if any. A brand code is a short (4-character) string used to identify installations that took place as a result of partner deals or website promotions. Default: ''.
|
||||
- **appChannel** An integer indicating the channel of the installation (i.e. Canary or Dev).
|
||||
- **appClientId** A generalized form of the brand code that can accept a wider range of values and is used for similar purposes. Default: ''.
|
||||
- **appCohort** A machine-readable string identifying the release cohort (channel) that the app belongs to. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appCohortHint** A machine-readable enum indicating that the client has a desire to switch to a different release cohort. The exact legal values are app-specific and should be shared between the server and app implementations. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appCohortName** A stable non-localized human-readable enum indicating which (if any) set of messages the app should display to the user. For example, an app with a cohort Name of 'beta' might display beta-specific branding to the user. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appConsentState** Bit flags describing the diagnostic data disclosure and response flow where 1 indicates the affirmative and 0 indicates the negative or unspecified data. Bit 1 indicates consent was given, bit 2 indicates data originated from the download page, bit 18 indicates choice for sending data about how the browser is used, and bit 19 indicates choice for sending data about websites visited.
|
||||
- **appDayOfInstall** The date-based counting equivalent of appInstallTimeDiffSec (the numeric calendar day that the app was installed on). This value is provided by the server in the response to the first request in the installation flow. The client MAY fuzz this value to the week granularity (e.g. send '0' for 0 through 6, '7' for 7 through 13, etc.). The first communication to the server should use a special value of '-1'. A value of '-2' indicates that this value is not known. Please see the wiki for additional information. Default: '-2'.
|
||||
- **appExperiments** A key/value list of experiment identifiers. Experiment labels are used to track membership in different experimental groups, and may be set at install or update time. The experiments string is formatted as a semicolon-delimited concatenation of experiment label strings. An experiment label string is an experiment Name, followed by the '=' character, followed by an experimental label value. For example: 'crdiff=got_bsdiff;optimized=O3'. The client should not transmit the expiration date of any experiments it has, even if the server previously specified a specific expiration date. Default: ''.
|
||||
- **appInstallTimeDiffSec** The difference between the current time and the install date in seconds. '0' if unknown. Default: '-1'.
|
||||
- **appLang** The language of the product install, in IETF BCP 47 representation. Default: ''.
|
||||
- **appNextVersion** The version of the app that the update flow to which this event belongs attempted to reach, regardless of the success or failure of the update operation. Please see the wiki for additional information. Default: '0.0.0.0'.
|
||||
- **appPingEventAppSize** The total number of bytes of all downloaded packages. Default: '0'.
|
||||
- **appPingEventDownloadMetricsDownloadedBytes** For events representing a download, the number of bytes expected to be downloaded. For events representing an entire update flow, the sum of all such expected bytes over the course of the update flow. Default: '0'.
|
||||
- **appPingEventDownloadMetricsDownloader** A string identifying the download algorithm and/or stack. Example values include: 'bits', 'direct', 'winhttp', 'p2p'. Sent in events that have an event type of '14' only. Default: ''.
|
||||
- **appPingEventDownloadMetricsDownloadTimeMs** For events representing a download, the time elapsed between the start of the download and the end of the download, in milliseconds. For events representing an entire update flow, the sum of all such download times over the course of the update flow. Sent in events that have an event type of '1', '2', '3', and '14' only. Default: '0'.
|
||||
- **appPingEventDownloadMetricsError** The error code (if any) of the operation, encoded as a signed base-10 integer. Default: '0'.
|
||||
- **appPingEventDownloadMetricsServerIpHint** For events representing a download, the CDN Host IP address that corresponds to the update file server. The CDN host is controlled by Microsoft servers and always maps to IP addresses hosting *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadMetricsTotalBytes** For events representing a download, the number of bytes expected to be downloaded. For events representing an entire update flow, the sum of all such expected bytes over the course of the update flow. Default: '0'.
|
||||
- **appPingEventDownloadMetricsUrl** For events representing a download, the CDN URL provided by the update server for the client to download the update, the URL is controlled by Microsoft servers and always maps back to either *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadTimeMs** For events representing a download, the time elapsed between the start of the download and the end of the download, in milliseconds. For events representing an entire update flow, the sum of all such download times over the course of the update flow. Sent in events that have an event type of '1', '2', '3', and '14' only. Default: '0'.
|
||||
- **appPingEventErrorCode** The error code (if any) of the operation, encoded as a signed, base-10 integer. Default: '0'.
|
||||
- **appPingEventEventResult** An enum indicating the result of the event. Please see the wiki for additional information. Default: '0'.
|
||||
- **appPingEventEventType** An enum indicating the type of the event. Compatible clients MUST transmit this attribute. Please see the wiki for additional information.
|
||||
- **appPingEventExtraCode1** Additional numeric information about the operation's result, encoded as a signed, base-10 integer. Default: '0'.
|
||||
- **appPingEventInstallTimeMs** For events representing an install, the time elapsed between the start of the install and the end of the install, in milliseconds. For events representing an entire update flow, the sum of all such durations. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appPingEventNumBytesDownloaded** The number of bytes downloaded for the specified application. Default: '0'.
|
||||
- **appPingEventSequenceId** An id that uniquely identifies particular events within one requestId. Since a request can contain multiple ping events, this field is necessary to uniquely identify each possible event.
|
||||
- **appPingEventSourceUrlIndex** For events representing a download, the position of the download URL in the list of URLs supplied by the server in a "urls" tag.
|
||||
- **appPingEventUpdateCheckTimeMs** For events representing an entire update flow, the time elapsed between the start of the update check and the end of the update check, in milliseconds. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appUpdateCheckIsUpdateDisabled** The state of whether app updates are restricted by group policy. True if updates have been restricted by group policy or false if they have not.
|
||||
- **appUpdateCheckTargetVersionPrefix** A component-wise prefix of a version number, or a complete version number suffixed with the $ character. The server should not return an update instruction to a version number that does not match the prefix or complete version number. The prefix is interpreted a dotted-tuple that specifies the exactly-matching elements; it is not a lexical prefix (for example, '1.2.3' must match '1.2.3.4' but must not match '1.2.34'). Default: ''.
|
||||
- **appUpdateCheckTtToken** An opaque access token that can be used to identify the requesting client as a member of a trusted-tester group. If non-empty, the request should be sent over SSL or another secure protocol. Default: ''.
|
||||
- **appVersion** The version of the product install. Please see the wiki for additional information. Default: '0.0.0.0'.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **eventType** A string indicating the type of the event. Please see the wiki for additional information.
|
||||
- **hwHasAvx** '1' if the client's hardware supports the AVX instruction set. '0' if the client's hardware does not support the AVX instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse** '1' if the client's hardware supports the SSE instruction set. '0' if the client's hardware does not support the SSE instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse2** '1' if the client's hardware supports the SSE2 instruction set. '0' if the client's hardware does not support the SSE2 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse3** '1' if the client's hardware supports the SSE3 instruction set. '0' if the client's hardware does not support the SSE3 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse41** '1' if the client's hardware supports the SSE4.1 instruction set. '0' if the client's hardware does not support the SSE4.1 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse42** '1' if the client's hardware supports the SSE4.2 instruction set. '0' if the client's hardware does not support the SSE4.2 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSsse3** '1' if the client's hardware supports the SSSE3 instruction set. '0' if the client's hardware does not support the SSSE3 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwPhysmemory** The physical memory available to the client, truncated down to the nearest gibibyte. '-1' if unknown. This value is intended to reflect the maximum theoretical storage capacity of the client, not including any hard drive or paging to a hard drive or peripheral. Default: '-1'.
|
||||
- **isMsftDomainJoined** '1' if the client is a member of a Microsoft domain. '0' otherwise. Default: '0'.
|
||||
- **osArch** The architecture of the operating system (e.g. 'x86', 'x64', 'arm'). '' if unknown. Default: ''.
|
||||
- **osPlatform** The operating system family that the within which the Omaha client is running (e.g. 'win', 'mac', 'linux', 'ios', 'android'). '' if unknown. The operating system Name should be transmitted in lowercase with minimal formatting. Default: ''.
|
||||
- **osServicePack** The secondary version of the operating system. '' if unknown. Default: ''.
|
||||
- **osVersion** The primary version of the operating system. '' if unknown. Default: ''.
|
||||
- **requestCheckPeriodSec** The update interval in seconds. The value is read from the registry. Default: '-1'.
|
||||
- **requestDlpref** A comma-separated list of values specifying the preferred download URL behavior. The first value is the highest priority, further values reflect secondary, tertiary, et cetera priorities. Legal values are '' (in which case the entire list must be empty, indicating unknown or no-preference) or 'cacheable' (the server should prioritize sending URLs that are easily cacheable). Default: ''.
|
||||
- **requestDomainJoined** '1' if the machine is part of a managed enterprise domain. Otherwise '0'.
|
||||
- **requestInstallSource** A string specifying the cause of the update flow. For example: 'ondemand', or 'scheduledtask'. Default: ''.
|
||||
- **requestIsMachine** '1' if the client is known to be installed with system-level or administrator privileges. '0' otherwise. Default: '0'.
|
||||
- **requestOmahaShellVersion** The version of the Omaha installation folder. Default: ''.
|
||||
- **requestOmahaVersion** The version of the Omaha updater itself (the entity sending this request). Default: '0.0.0.0'.
|
||||
- **requestProtocolVersion** The version of the Omaha protocol. Compatible clients MUST provide a value of '3.0'. Compatible clients must always transmit this attribute. Default: undefined.
|
||||
- **requestRequestId** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha request. Each request attempt should have (with high probability) a unique request id. Default: ''.
|
||||
- **requestSessionCorrelationVectorBase** A client generated random MS Correlation Vector base code used to correlate the update session with update and CDN servers. Default: ''.
|
||||
- **requestSessionId** A randomly-generated (uniformly distributed) GUID. Each single update flow (e.g. update check, update application, event ping sequence) should have (with high probability) a single unique session ID. Default: ''.
|
||||
- **requestTestSource** Either '', 'dev', 'qa', 'prober', 'auto', or 'ossdev'. Any value except '' indicates that the request is a test and should not be counted toward normal metrics. Default: ''.
|
||||
- **requestUid** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha user. Each request attempt SHOULD have (with high probability) a unique request id. Default: ''.
|
||||
|
||||
|
||||
### Aria.f4a7d46e472049dfba756e11bdbbc08f.Microsoft.WebBrowser.SystemInfo.Config
|
||||
|
||||
This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **app_env** The environment from which the event was logged when testing; otherwise, the field is omitted or left blank.
|
||||
- **app_sample_rate** A number representing how often the client sends telemetry, expressed as a percentage. Low values indicate that said client sends more events and high values indicate that said client sends fewer events.
|
||||
- **app_version** The internal Edge build version string, taken from the UMA metrics field system_profile.app_version.
|
||||
- **appConsentState** Bit flags describing consent for data collection on the machine or zero if the state was not retrieved. The following are true when the associated bit is set: consent was granted (0x1), consent was communicated at install (0x2), diagnostic data consent granted (0x20000), browsing data consent granted (0x40000).
|
||||
- **Channel** An integer indicating the channel of the installation (Canary or Dev).
|
||||
- **client_id** A unique identifier with which all other diagnostic client data is associated, taken from the UMA metrics provider. This ID is effectively unique per device, per OS user profile, per release channel (e.g. Canary/Dev/Beta/Stable). client_id is not durable, based on user preferences. client_id is initialized on the first application launch under each OS user profile. client_id is linkable, but not unique across devices or OS user profiles. client_id is reset whenever UMA data collection is disabled, or when the application is uninstalled.
|
||||
- **ConnectionType** The first reported type of network connection currently connected. This can be one of Unknown, Ethernet, WiFi, 2G, 3G, 4G, None, or Bluetooth.
|
||||
- **container_client_id** The client ID of the container, if in WDAG mode. This will be different from the UMA log client ID, which is the client ID of the host in WDAG mode.
|
||||
- **container_session_id** The session ID of the container, if in WDAG mode. This will be different from the UMA log session ID, which is the session ID of the host in WDAG mode.
|
||||
- **Etag** Etag is an identifier representing all service applied configurations and experiments for the current browser session. This field is left empty when Windows diagnostic level is set to Basic or lower or when consent for diagnostic data has been denied.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **install_date** The date and time of the most recent installation in seconds since midnight on January 1, 1970 UTC, rounded down to the nearest hour.
|
||||
- **installSource** An enumeration representing the source of this installation: source was not retrieved (0), unspecified source (1), website installer (2), enterprise MSI (3), Windows update (4), Edge updater (5), scheduled or timed task (6, 7), uninstall (8), Edge about page (9), self-repair (10), other install command line (11), reserved (12), unknown source (13).
|
||||
- **PayloadClass** The base class used to serialize and deserialize the Protobuf binary payload.
|
||||
- **PayloadGUID** A random identifier generated for each original monolithic Protobuf payload, before the payload is potentially broken up into manageably-sized chunks for transmission.
|
||||
- **PayloadLogType** The log type for the event correlating with 0 for unknown, 1 for stability, 2 for on-going, 3 for independent, 4 for UKM, or 5 for instance level.
|
||||
- **pop_sample** A value indicating how the device's data is being sampled.
|
||||
- **reconsentConfigs** A comma separated list of all reconsent configurations the current installation has received. Each configuration follows a well-defined format: 2DigitMonth-2DigitYear-3LetterKeyword.
|
||||
- **session_id** An identifier that is incremented each time the user launches the application, irrespective of any client_id changes. session_id is seeded during the initial installation of the application. session_id is effectively unique per client_id value. Several other internal identifier values, such as window or tab IDs, are only meaningful within a particular session. The session_id value is forgotten when the application is uninstalled, but not during an upgrade.
|
||||
- **utc_flags** Event Tracing for Windows (ETW) flags required for the event as part of the data collection process.
|
||||
|
||||
|
||||
### Microsoft.WebBrowser.Installer.EdgeUpdate.Ping
|
||||
|
||||
This event sends hardware and software inventory information about the Microsoft Edge Update service, Microsoft Edge applications, and the current system environment, including app configuration, update configuration, and hardware capabilities. It's used to measure the reliability and performance of the EdgeUpdate service and if Microsoft Edge applications are up to date
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **appAp** Microsoft Edge Update parameters, including channel, architecture, platform, and additional parameters identifying the release of Microsoft Edge to update and how to install it. Example: 'beta-arch_x64-full'. Default: ''."
|
||||
- **appAppId** The GUID that identifies the product channels such as Edge Canary, Dev, Beta, Stable, and Edge Update.
|
||||
- **appBrandCode** The 4-digit brand code under which the the product was installed, if any. Possible values: 'GGLS' (default), 'GCEU' (enterprise install), and '' (unknown).
|
||||
- **appChannel** An integer indicating the channel of the installation (e.g. Canary or Dev).
|
||||
- **appClientId** A generalized form of the brand code that can accept a wider range of values and is used for similar purposes. Default: ''.
|
||||
- **appClientId** A generalized form of the brand code that can accept a wider range of values and is used for similar purposes. Default: ''.
|
||||
- **appCohort** A machine-readable string identifying the release channel that the app belongs to. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appCohortHint** A machine-readable enum indicating that the client has a desire to switch to a different release cohort. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appCohortName** A stable non-localized human-readable enum indicating which (if any) set of messages the app should display to the user. For example, an app with a cohort name of 'beta' might display beta-specific branding to the user. Limited to ASCII characters 32 to 127 (inclusive) and a maximum length of 1024 characters. Default: ''.
|
||||
- **appConsentState** Bit flags describing the diagnostic data disclosure and response flow where 1 indicates the affirmative and 0 indicates the negative or unspecified data. Bit 1 indicates consent was given, bit 2 indicates data originated from the download page, bit 18 indicates choice for sending data about how the browser is used, and bit 19 indicates choice for sending data about websites visited.
|
||||
- **appDayOfInstall** The date-based counting equivalent of appInstallTimeDiffSec (the numeric calendar day that the app was installed on). This value is provided by the server in the response to the first request in the installation flow. Default: '-2' (Unknown).
|
||||
- **appExperiments** A semicolon-delimited key/value list of experiment identifiers and treatment groups. This field is unused and always empty in Edge Update. Default: ''.
|
||||
- **appIid** A GUID that identifies a particular installation flow. For example, each download of a product installer is tagged with a unique GUID. Attempts to install using that installer can then be grouped. A client SHOULD NOT persist the IID GUID after the installation flow of a product is complete.
|
||||
- **appInstallTimeDiffSec** The difference between the current time and the install date in seconds. '0' if unknown. Default: '-1'.
|
||||
- **appLang** The language of the product install, in IETF BCP 47 representation. Default: ''.
|
||||
- **appNextVersion** The version of the app that the update attempted to reach, regardless of the success or failure of the update operation. Default: '0.0.0.0'.
|
||||
@ -4418,7 +4610,7 @@ The following fields are available:
|
||||
- **appPingEventDownloadMetricsError** The error code (if any) of the operation, encoded as a signed base-10 integer. Default: '0'.
|
||||
- **appPingEventDownloadMetricsServerIpHint** For events representing a download, the CDN Host IP address that corresponds to the update file server. The CDN host is controlled by Microsoft servers and always maps to IP addresses hosting *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadMetricsTotalBytes** For events representing a download, the number of bytes expected to be downloaded. For events representing an entire update flow, the sum of all such expected bytes over the course of the update flow. Default: '0'.
|
||||
- **appPingEventDownloadMetricsUrl** For events representing a download, the CDN URL provided by the update server for the client to download the update, the URL is controlled by Microsoft servers and always maps back to either *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadMetricsUrl** For events representing a download, the CDN URL provided by the update server for the client to download the update, the URL is controlled by Microsoft servers and always maps back to either *.delivery.mp.microsoft.com or msedgesetup.azureedge.net. Default: ''.
|
||||
- **appPingEventDownloadTimeMs** For events representing a download, the time elapsed between the start of the download and the end of the download, in milliseconds. For events representing an entire update flow, the sum of all such download times over the course of the update flow. Sent in events that have an event type of '1', '2', '3', and '14' only. Default: '0'.
|
||||
- **appPingEventErrorCode** The error code (if any) of the operation, encoded as a signed, base-10 integer. Default: '0'.
|
||||
- **appPingEventEventResult** An enumeration indicating the result of the event. Common values are '0' (Error) and '1' (Success). Default: '0' (Error).
|
||||
@ -4427,15 +4619,14 @@ The following fields are available:
|
||||
- **appPingEventInstallTimeMs** For events representing an install, the time elapsed between the start of the install and the end of the install, in milliseconds. For events representing an entire update flow, the sum of all such durations. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appPingEventNumBytesDownloaded** The number of bytes downloaded for the specified application. Default: '0'.
|
||||
- **appPingEventSequenceId** An ID that uniquely identifies particular events within one requestId. Since a request can contain multiple ping events, this field is necessary to uniquely identify each possible event.
|
||||
- **appPingEventSourceUrlIndex** For events representing a download, the position of the download URL in the list of URLs supplied by the server in a <urls> tag.
|
||||
- **appPingEventUpdateCheckTimeMs** For events representing an entire update flow, the time elapsed between the start of the update check and the end of the update check, in milliseconds. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appPingEventSourceUrlIndex** For events representing a download, the position of the download URL in the list of URLs supplied by the server in a tag.
|
||||
- **appPingEventUpdateCheckTimeMs** For events representing an entire update flow, the time elapsed between the start of the update check and the end of the update check, in milliseconds. Sent in events that have an event type of '2' and '3' only. Default: '0'.
|
||||
- **appUpdateCheckIsUpdateDisabled** The state of whether app updates are restricted by group policy. True if updates have been restricted by group policy or false if they have not.
|
||||
- **appUpdateCheckTargetVersionPrefix** A component-wise prefix of a version number, or a complete version number suffixed with the $ character. The prefix is interpreted a dotted-tuple that specifies the exactly-matching elements; it is not a lexical prefix (for example, '1.2.3' MUST match '1.2.3.4' but MUST NOT match '1.2.34'). Default: ''.
|
||||
- **appUpdateCheckTtToken** An opaque access token that can be used to identify the requesting client as a member of a trusted-tester group. If non-empty, the request is sent over SSL or another secure protocol. This field is unused by Edge Update and always empty. Default: ''.
|
||||
- **appVersion** The version of the product install. Default: '0.0.0.0'.
|
||||
- **EventInfo.Level** The minimum Windows diagnostic data level required for the event where 1 is basic, 2 is enhanced, and 3 is full.
|
||||
- **eventType** A string representation of appPingEventEventType indicating the type of the event.
|
||||
- **hwHasAvx** '1' if the client's hardware supports the SSE instruction set. '0' if the client's hardware does not support the SSE instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasAvx** '1' if the client's hardware supports the AVX instruction set. '0' if the client's hardware does not support the AVX instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse** '1' if the client's hardware supports the SSE instruction set. '0' if the client's hardware does not support the SSE instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse2** '1' if the client's hardware supports the SSE2 instruction set. '0' if the client's hardware does not support the SSE2 instruction set. '-1' if unknown. Default: '-1'.
|
||||
- **hwHasSse3** '1' if the client's hardware supports the SSE3 instruction set. '0' if the client's hardware does not support the SSE3 instruction set. '-1' if unknown. Default: '-1'.
|
||||
@ -4456,9 +4647,9 @@ The following fields are available:
|
||||
- **requestOmahaShellVersion** The version of the Omaha installation folder. Default: ''.
|
||||
- **requestOmahaVersion** The version of the Omaha updater itself (the entity sending this request). Default: '0.0.0.0'.
|
||||
- **requestProtocolVersion** The version of the Omaha protocol. Compatible clients MUST provide a value of '3.0'. Compatible clients MUST always transmit this attribute. Default: undefined.
|
||||
- **requestRequestId** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha request. Default: ''.
|
||||
- **requestRequestId** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha request. Each request attempt SHOULD have (with high probability) a unique request id. Default: ''.
|
||||
- **requestSessionCorrelationVectorBase** A client generated random MS Correlation Vector base code used to correlate the update session with update and CDN servers. Default: ''.
|
||||
- **requestSessionId** A randomly-generated (uniformly distributed) GUID. Each single update flow (e.g. update check, update application, event ping sequence) should have (with high probability) a single unique sessionid. Default: ''.
|
||||
- **requestSessionId** A randomly-generated (uniformly distributed) GUID. Each single update flow (e.g. update check, update application, event ping sequence) SHOULD have (with high probability) a single unique session ID. Default: ''.
|
||||
- **requestTestSource** Either '', 'dev', 'qa', 'prober', 'auto', or 'ossdev'. Any value except '' indicates that the request is a test and should not be counted toward normal metrics. Default: ''.
|
||||
- **requestUid** A randomly-generated (uniformly distributed) GUID, corresponding to the Omaha user. Each request attempt should have (with high probability) a unique request id. Default: ''.
|
||||
|
||||
@ -4596,6 +4787,24 @@ The following fields are available:
|
||||
- **WFD2Supported** Indicates if the Miracast receiver supports WFD2 protocol.
|
||||
|
||||
|
||||
## Mixed Reality events
|
||||
|
||||
### Microsoft.Windows.Analog.Spectrum.TelemetryHolographicDeviceAdded
|
||||
|
||||
This event indicates Windows Mixed Reality device state. This event is also used to count WMR device.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ClassGuid** Windows Mixed Reality device class GUID.
|
||||
- **DeviceInterfaceId** Windows Mixed Reality device interface ID.
|
||||
- **DeviceName** Windows Mixed Reality device name.
|
||||
- **DriverVersion** Windows Mixed Reality device driver version.
|
||||
- **FirmwareVersion** Windows Mixed Reality firmware version.
|
||||
- **Manufacturer** Windows Mixed Reality device manufacturer.
|
||||
- **ModelName** Windows Mixed Reality device model name.
|
||||
- **SerialNumber** Windows Mixed Reality device serial number.
|
||||
|
||||
|
||||
## OneDrive events
|
||||
|
||||
### Microsoft.OneDrive.Sync.Setup.OSUpgradeInstallationOperation
|
||||
@ -4613,6 +4822,7 @@ The following fields are available:
|
||||
- **SourceOSBuildNumber** The source build number of the operating system.
|
||||
- **SourceOSVersion** The source version of the operating system.
|
||||
|
||||
|
||||
## Privacy consent logging events
|
||||
|
||||
### Microsoft.Windows.Shell.PrivacyConsentLogging.PrivacyConsentCompleted
|
||||
@ -4749,6 +4959,7 @@ The following fields are available:
|
||||
- **apiName** Name of the API command that completed.
|
||||
- **errorCode** Error code if an error occurred during the API call.
|
||||
- **sessionID** The ID of this push-button reset session.
|
||||
- **succeeded** Indicates whether the operation is successfully completed.
|
||||
- **success** Indicates whether the API call was successful.
|
||||
- **timestamp** Timestamp of this push-button reset event.
|
||||
|
||||
@ -4818,6 +5029,7 @@ This event is sent when construction of the operation queue for push-button rese
|
||||
The following fields are available:
|
||||
|
||||
- **error** The result code for operation queue construction.
|
||||
- **errorCode** Represents any error code during the API call.
|
||||
- **sessionID** The ID of this push-button reset session.
|
||||
- **succeeded** Indicates whether the operation successfully completed.
|
||||
- **timestamp** Timestamp of this push-button reset event.
|
||||
@ -4856,6 +5068,18 @@ The following fields are available:
|
||||
- **SPPhase** The last phase of the Setup Platform operation.
|
||||
|
||||
|
||||
### Microsoft.Windows.PBR.PBRCreateNewSystemReconstructionSucceed
|
||||
|
||||
This event is sent when the push-button reset operation succeeds in constructing a new copy of the operating system.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CBSPackageCount** The Component Based Servicing package count.
|
||||
- **CustomizationPackageCount** The Customization package count.
|
||||
- **PBRType** The type of push-button reset.
|
||||
- **SessionID** The ID of this push-button reset session.
|
||||
|
||||
|
||||
### Microsoft.Windows.PBR.PBRFailed
|
||||
|
||||
This event is sent when the push-button reset operation fails and rolls back to the previous state.
|
||||
@ -4881,6 +5105,34 @@ The following fields are available:
|
||||
- **SessionID** The ID of this push-button reset session.
|
||||
|
||||
|
||||
### Microsoft.Windows.PBR.PBRFormatOSVolumeSucceed
|
||||
|
||||
This event is sent when the operation to format the operating system volume succeeds during push-button reset (PBR).
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **JustDeleteFiles** Indicates whether disk formatting was skipped.
|
||||
- **SessionID** The ID of this push-button reset session.
|
||||
|
||||
|
||||
### Microsoft.Windows.PBR.PBRIOCTLErasureSucceed
|
||||
|
||||
This event is sent when the erasure operation succeeds during push-button reset (PBR).
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **SessionID** The ID of this push-button reset session.
|
||||
|
||||
|
||||
### Microsoft.Windows.PBR.PBRLayoutImageFailed
|
||||
|
||||
This event is sent when push-button reset fails to create a new image of Windows.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **SessionID** The ID of this push-button reset session.
|
||||
|
||||
|
||||
### Microsoft.Windows.PBR.PBROEM1Failed
|
||||
|
||||
This event is sent when the first OEM extensibility operation is successfully completed.
|
||||
@ -5191,6 +5443,7 @@ This event returns data when System Info Sense is finished.
|
||||
The following fields are available:
|
||||
|
||||
- **error** The error code if an error occurred while querying for system information.
|
||||
- **errorCode** Represents any error code during the API call.
|
||||
- **sessionID** The ID of this push-button reset session.
|
||||
- **succeeded** Indicates whether the query for system information was successful.
|
||||
- **timestamp** The timestamp of this push-button reset event.
|
||||
@ -5259,6 +5512,81 @@ The following fields are available:
|
||||
- **timestamp** The timestamp for this push-button reset event.
|
||||
|
||||
|
||||
## Quality Update Assistant events
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Applicability
|
||||
|
||||
This event sends basic info on whether the device should be updated to the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **dayspendingrebootafterfu** Number of days that have elapsed since the device reached ready to reboot for a Feature Update that is still actively pending reboot.
|
||||
- **ExecutionRequestId** Identifier of the Execution Request that launched the QualityUpdateAssistant process.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **KBNumber** KBNumber of the update being installed.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Reason** Provides information on reasons why the update is not applicable to the device.
|
||||
- **Result** Applicability check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.DeviceReadinessCheck
|
||||
|
||||
This event sends basic info on whether the device is ready to download the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **ExecutionRequestId** Identifier of the Execution Request that launched the QualityUpdateAssistant process.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **KBNumber** KBNumber of the update being installed.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **Reason** Indicates why the device did not pass the readiness check.
|
||||
- **Result** Device readiness check for quality update assistant.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Download
|
||||
|
||||
This event sends basic info when download of the latest cumulative update begins.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **DODownloadHResult** Result code from Delivery Optimization when used to download the quality update.
|
||||
- **DownloadMode** Indicates how the quality update was downloaded.
|
||||
- **ExecutionRequestId** Identifier of the Execution Request that launched the QualityUpdateAssistant process.
|
||||
- **GlobalEventCounter** Client side counter that indicates ordering of events sent by this device.
|
||||
- **HttpsDownloadHResult** Result code when HTTPS is used to download the quality update.
|
||||
- **KBNumber** KBNumber of the update being installed.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **QualityUpdateDeviceHasMinimumUptime** Indicates whether the device has the minimum uptime required to install a quality update.
|
||||
- **Result** Download of latest cumulative update payload.
|
||||
- **Scenario** Indicates if the installation step succeeded or failed.
|
||||
|
||||
|
||||
### Microsoft.Windows.QualityUpdateAssistant.Install
|
||||
|
||||
This event sends basic info on the result of the installation of the latest cumulative update.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **DismInstallHResult** Internal result code from DISM when used to install the quality update.
|
||||
- **ExecutionRequestId** Identifier of the Execution Request that launched the QualityUpdateAssistant process.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this device.
|
||||
- **InstallMode** Indicates which installation method was used to attempt the install of the quality update.
|
||||
- **KBNumber** KBNumber of the update being installed.
|
||||
- **launchretrycounter** Count of the number of times the install has been retried in the event of a non-successful installation attempt.
|
||||
- **PackageVersion** Current package version of quality update assistant.
|
||||
- **QualityUpdateDismErrorCode** Error code returned when DISM is used to install the quality update.
|
||||
- **QualityUpdatePendingRebootAfterInstallStage** Indicates if the device is pending reboot after install is complete.
|
||||
- **QualityUpdateSecondsInstallStage** Time spent installing the quality update.
|
||||
- **QualityUpdateWusaErrorCode** Error code returned when WUSA is used to install the quality update.
|
||||
- **Result** Install of latest cumulative update payload.
|
||||
- **Scenario** Indicates if the installation step succeeded or failed.
|
||||
- **WusaInstallHResult** Internal result code from WUSA when used to install the quality update.
|
||||
|
||||
|
||||
## Sediment events
|
||||
|
||||
### Microsoft.Windows.Sediment.Info.DetailedState
|
||||
@ -5315,7 +5643,7 @@ This event sends basic metadata about the update installation process generated
|
||||
|
||||
### SetupPlatformTel.SetupPlatformTelEvent
|
||||
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios.
|
||||
This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -5374,6 +5702,7 @@ The following fields are available:
|
||||
- **IsWUfBDualScanEnabled** Indicates if Windows Update for Business dual scan is enabled on the device.
|
||||
- **IsWUfBEnabled** Indicates if Windows Update for Business is enabled on the device.
|
||||
- **IsWUfBFederatedScanDisabled** Indicates if Windows Update for Business federated scan is disabled on the device.
|
||||
- **IsWUfBTargetVersionEnabled** Flag that indicates if the WU-for-Business target version policy is enabled on the device.
|
||||
- **MetadataIntegrityMode** The mode of the update transport metadata integrity check. 0-Unknown, 1-Ignoe, 2-Audit, 3-Enforce
|
||||
- **MSIError** The last error that was encountered during a scan for updates.
|
||||
- **NetworkConnectivityDetected** Indicates the type of network connectivity that was detected. 0 - IPv4, 1 - IPv6
|
||||
@ -5406,6 +5735,7 @@ The following fields are available:
|
||||
- **SystemBIOSMajorRelease** Major version of the BIOS.
|
||||
- **SystemBIOSMinorRelease** Minor version of the BIOS.
|
||||
- **TargetMetadataVersion** For self-initiated healing, this is the target version of the SIH engine to download (if needed). If not, the value is null.
|
||||
- **TargetReleaseVersion** The value selected for the target release version policy.
|
||||
- **TotalNumMetadataSignatures** The total number of metadata signatures checks done for new metadata that was synced down.
|
||||
- **WebServiceRetryMethods** Web service method requests that needed to be retried to complete operation.
|
||||
- **WUDeviceID** The unique identifier of a specific device, used to identify how many devices are encountering success or a particular issue.
|
||||
@ -5497,6 +5827,7 @@ The following fields are available:
|
||||
- **IsDependentSet** Indicates whether a driver is a part of a larger System Hardware/Firmware Update
|
||||
- **IsWUfBDualScanEnabled** Indicates if Windows Update for Business dual scan is enabled on the device.
|
||||
- **IsWUfBEnabled** Indicates if Windows Update for Business is enabled on the device.
|
||||
- **IsWUfBTargetVersionEnabled** Flag that indicates if the WU-for-Business target version policy is enabled on the device.
|
||||
- **NetworkCost** A flag indicating the cost of the network (congested, fixed, variable, over data limit, roaming, etc.) used for downloading the update content.
|
||||
- **NetworkCostBitMask** Indicates what kind of network the device is connected to (roaming, metered, over data cap, etc.)
|
||||
- **NetworkRestrictionStatus** More general version of NetworkCostBitMask, specifying whether Windows considered the current network to be "metered."
|
||||
@ -5630,6 +5961,7 @@ The following fields are available:
|
||||
- **IsSuccessFailurePostReboot** Indicates whether the update succeeded and then failed after a restart.
|
||||
- **IsWUfBDualScanEnabled** Indicates whether Windows Update for Business dual scan is enabled on the device.
|
||||
- **IsWUfBEnabled** Indicates whether Windows Update for Business is enabled on the device.
|
||||
- **IsWUfBTargetVersionEnabled** Flag that indicates if the WU-for-Business target version policy is enabled on the device.
|
||||
- **MergedUpdate** Indicates whether the OS update and a BSP update merged for installation.
|
||||
- **MsiAction** The stage of MSI installation where it failed.
|
||||
- **MsiProductCode** The unique identifier of the MSI installer.
|
||||
@ -5686,6 +6018,7 @@ The following fields are available:
|
||||
- **IsSuccessFailurePostReboot** Indicates whether an initial success was a failure after a reboot.
|
||||
- **IsWUfBDualScanEnabled** Flag indicating whether WU-for-Business dual scan is enabled on the device.
|
||||
- **IsWUfBEnabled** Flag indicating whether WU-for-Business is enabled on the device.
|
||||
- **IsWUfBTargetVersionEnabled** Flag that indicates if the WU-for-Business target version policy is enabled on the device.
|
||||
- **MergedUpdate** Indicates whether an OS update and a BSP update were merged for install.
|
||||
- **ProcessName** Process name of the caller who initiated API calls into the software distribution client.
|
||||
- **QualityUpdatePause** Indicates whether quality OS updates are paused on the device.
|
||||
@ -6820,7 +7153,7 @@ The following fields are available:
|
||||
|
||||
- **AggregatedPackageFullNames** Includes a set of package full names for each app that is part of an atomic set.
|
||||
- **AttemptNumber** The total number of attempts to acquire this product.
|
||||
- **BundleId** The identity of the test build (flight) associated with this product.
|
||||
- **BundleId** The bundle ID
|
||||
- **CategoryId** The identity of the package or packages being installed.
|
||||
- **ClientAppId** The identity of the app that initiated this operation.
|
||||
- **HResult** HResult code to show the result of the operation (success/failure).
|
||||
@ -6830,7 +7163,7 @@ The following fields are available:
|
||||
- **IsRemediation** Is this repairing a previous installation?
|
||||
- **IsRestore** Is this happening after a device restore?
|
||||
- **IsUpdate** Is this an update?
|
||||
- **ParentBundleId** The product identifier of the parent if this product is part of a bundle.
|
||||
- **ParentBundleId** The parent bundle ID (if it's part of a bundle).
|
||||
- **PFN** Product Family Name of the product being installed.
|
||||
- **ProductId** The Store Product ID for the product being installed.
|
||||
- **SystemAttemptNumber** The number of attempts by the system to acquire this product.
|
||||
@ -7242,7 +7575,7 @@ The following fields are available:
|
||||
- **groupConnectionCount** The total number of connections made to peers in the same group.
|
||||
- **internetConnectionCount** The total number of connections made to peers not in the same LAN or the same group.
|
||||
- **isEncrypted** TRUE if the file is encrypted and will be decrypted after download.
|
||||
- **isThrottled** Indicates the Event Rate was throttled (event represent aggregated data).
|
||||
- **isThrottled** Event Rate throttled (event represents aggregated data).
|
||||
- **isVpn** Is the device connected to a Virtual Private Network?
|
||||
- **jobID** Identifier for the Windows Update job.
|
||||
- **lanConnectionCount** The total number of connections made to peers in the same LAN.
|
||||
@ -7743,7 +8076,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.FlightInapplicable
|
||||
|
||||
This event indicates that the update is no longer applicable to this device.
|
||||
This event sends data on whether the update was applicable to the device, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -7973,13 +8306,13 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.UniversalOrchestratorScheduleWorkInvalidCmd
|
||||
|
||||
Event to indicate a critical error with the callback binary requested by the updater
|
||||
This event indicates a critical error with the callback binary requested by the updater.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **updaterCmdLine** The callback executable for the updater.
|
||||
- **updaterId** The ID of the updater.
|
||||
- **wuDeviceid** The Windows Update device identifier.
|
||||
- **updaterCmdLine** The command line requested by the updater.
|
||||
- **updaterId** The ID of the updater that requested the work.
|
||||
- **wuDeviceid** WU device ID.
|
||||
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.UnstickUpdate
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
60
windows/privacy/stub.md
Normal file
60
windows/privacy/stub.md
Normal file
@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Stub topic
|
||||
description: Use this topic to test localization e2e.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 10/11/2019
|
||||
ms.reviewer:
|
||||
---
|
||||
# Stub topic
|
||||
|
||||
Applies to:
|
||||
- Windows 10, version 1809
|
||||
- Windows 10, version 1803
|
||||
- Windows 10, version 1709
|
||||
- Windows 10, version 1703
|
||||
- Windows 10 Team Edition, version 1703 for Surface Hub
|
||||
- Windows Server 2019
|
||||
- Windows Server 2016
|
||||
- Windows Analytics
|
||||
|
||||
This topic provides IT Decision Makers with a basic understanding of the relationship between users in an organization and Microsoft in the context of the GDPR (General Data Protection Regulation). You will also learn what role an IT organization plays for that relationship.
|
||||
|
||||
For more information about the GDPR, see:
|
||||
* [Microsoft GDPR Overview](https://aka.ms/GDPROverview)
|
||||
* [Microsoft Trust Center FAQs about the GDPR](https://aka.ms/gdpr-faq)
|
||||
* [Microsoft Service Trust Portal (STP)](https://aka.ms/stp)
|
||||
* [Get Started: Support for GDPR Accountability](https://servicetrust.microsoft.com/ViewPage/GDPRGetStarted)
|
||||
|
||||
## GDPR fundamentals
|
||||
|
||||
Here are some GDPR fundamentals:
|
||||
|
||||
* On May 25, 2018, this EU data privacy law is implemented. It sets a new global bar for data privacy rights, security, and compliance.
|
||||
* The GDPR is fundamentally about protecting and enabling the privacy rights of individuals – both customers and employees.
|
||||
* The European law establishes strict global data privacy requirements governing how organizations manage and protect personal data while respecting individual choice – no matter where data is sent, processed, or stored.
|
||||
* A request by an individual to an organization to take an action on their personal data is referred to here as a *data subject request*, or *DSR*.
|
||||
|
||||
Microsoft believes data privacy is a fundamental right, and that the GDPR is an important step forward for clarifying and enabling individual privacy rights. We also recognize that the GDPR required significant changes by organizations all over the world with regard to the discovery, management, protection, and reporting of personal data that is collected, processed, and stored within an organization.
|
||||
|
||||
### What is personal data under the GDPR?
|
||||
|
||||
Article 4 (1) of [the GDPR](http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679&from=en) defines personal data as any information relating to an identified or identifiable person. There is no distinction between a person’s private, public, or work roles. As defined by the GDPR, personal data includes, but is not limited to:
|
||||
* Name
|
||||
* Email address
|
||||
* Credit card numbers
|
||||
* IP addresses
|
||||
* Social media posts
|
||||
* Location information
|
||||
* Handwriting patterns
|
||||
* Voice input to cloud-based speech services
|
||||
|
||||
@ -145,7 +145,7 @@ Appendix section in this document for the URLs Whitelisting or on
|
||||
Docs](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection#enable-access-to-windows-defender-atp-service-urls-in-the-proxy-server).
|
||||
|
||||
> [!NOTE]
|
||||
> For a detailed list of URLs that need to be whitelisted, please see [this article](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus).
|
||||
> For a detailed list of URLs that need to be whitelisted, please see [this article](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus).
|
||||
|
||||
**Manual static proxy configuration:**
|
||||
|
||||
|
||||
@ -1,4 +1,5 @@
|
||||
# [What's new in Windows 10](index.md)
|
||||
## [What's new in Windows 10, version 2004](whats-new-windows-10-version-2004.md)
|
||||
## [What's new in Windows 10, version 1909](whats-new-windows-10-version-1909.md)
|
||||
## [What's new in Windows 10, version 1903](whats-new-windows-10-version-1903.md)
|
||||
## [What's new in Windows 10, version 1809](whats-new-windows-10-version-1809.md)
|
||||
|
||||
BIN
windows/whats-new/images/system-guard2.png
Normal file
BIN
windows/whats-new/images/system-guard2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 94 KiB |
@ -18,6 +18,7 @@ Windows 10 provides IT professionals with advanced protection against modern sec
|
||||
|
||||
## In this section
|
||||
|
||||
- [What's new in Windows 10, version 2004](whats-new-windows-10-version-2004.md)
|
||||
- [What's new in Windows 10, version 1909](whats-new-windows-10-version-1909.md)
|
||||
- [What's new in Windows 10, version 1903](whats-new-windows-10-version-1903.md)
|
||||
- [What's new in Windows 10, version 1809](whats-new-windows-10-version-1809.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in Windows 10, versions 1507 and 1511 (Windows 10)
|
||||
description: This topic lists new and updated topics in the What's new in Windows 10 documentation for Windows 10 (versions 1507 and 1511) and Windows 10 Mobile.
|
||||
description: What's new in Windows 10 for Windows 10 (versions 1507 and 1511) and Windows 10 Mobile.
|
||||
ms.assetid: 75F285B0-09BE-4821-9B42-37B9BE54CEC6
|
||||
ms.reviewer:
|
||||
ms.prod: w10
|
||||
@ -13,7 +13,7 @@ ms.localizationpriority: high
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# What's new in Windows 10, versions 1507 and 1511
|
||||
# What's new in Windows 10, versions 1507 and 1511 for IT Pros
|
||||
|
||||
Below is a list of some of the new and updated features included in the initial release of Windows 10 (version 1507) and the Windows 10 update to version 1511.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in Windows 10, version 1607 (Windows 10)
|
||||
description: This topic lists new and updated topics in the What's new in Windows 10 documentation for Windows 10 (version 1607) and Windows 10 Mobile.
|
||||
description: What's new in Windows 10 for Windows 10 (version 1607) and Windows 10 Mobile.
|
||||
keywords: ["What's new in Windows 10", "Windows 10", "anniversary update"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,7 +13,7 @@ ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# What's new in Windows 10, version 1607
|
||||
# What's new in Windows 10, version 1607 for IT Pros
|
||||
|
||||
Below is a list of some of the new and updated features in Windows 10, version 1607 (also known as the Anniversary Update).
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in Windows 10, version 1703
|
||||
description: New and updated IT pro content about new features in Windows 10, version 1703 (also known as the Creators Updated).
|
||||
description: New and updated features in Windows 10, version 1703 (also known as the Creators Updated).
|
||||
keywords: ["What's new in Windows 10", "Windows 10", "creators update"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,7 +14,7 @@ ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# What's new in Windows 10, version 1703 IT pro content
|
||||
# What's new in Windows 10, version 1703 for IT Pros
|
||||
|
||||
Below is a list of some of what's new in Information Technology (IT) pro features in Windows 10, version 1703 (also known as the Creators Update).
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in Windows 10, version 1709
|
||||
description: New and updated IT Pro content about new features in Windows 10, version 1709 (also known as the Fall Creators Update).
|
||||
description: New and updated features in Windows 10, version 1709 (also known as the Fall Creators Update).
|
||||
keywords: ["What's new in Windows 10", "Windows 10", "Fall Creators Update"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,7 +13,7 @@ ms.localizationpriority: high
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# What's new in Windows 10, version 1709 IT Pro content
|
||||
# What's new in Windows 10, version 1709 for IT Pros
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1709
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in Windows 10, version 1803
|
||||
description: New and updated IT Pro content about new features in Windows 10, version 1803 (also known as the Windows 10 April 2018 Update).
|
||||
description: New and updated features in Windows 10, version 1803 (also known as the Windows 10 April 2018 Update).
|
||||
keywords: ["What's new in Windows 10", "Windows 10", "April 2018 Update"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,7 +13,7 @@ ms.localizationpriority: high
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# What's new in Windows 10, version 1803 IT Pro content
|
||||
# What's new in Windows 10, version 1803 for IT Pros
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1803
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in Windows 10, version 1903
|
||||
description: New and updated IT Pro content about new features in Windows 10, version 1903 (also known as the Windows 10 May 2019 Update).
|
||||
description: New and updated features in Windows 10, version 1903 (also known as the Windows 10 May 2019 Update).
|
||||
keywords: ["What's new in Windows 10", "Windows 10", "May 2019 Update"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,7 +13,7 @@ ms.localizationpriority: high
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# What's new in Windows 10, version 1903 IT Pro content
|
||||
# What's new in Windows 10, version 1903 for IT Pros
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1903
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: What's new in Windows 10, version 1909
|
||||
description: New and updated IT Pro content about new features in Windows 10, version 1909 (also known as the Windows 10 November 2019 Update).
|
||||
description: New and updated features in Windows 10, version 1909 (also known as the Windows 10 November 2019 Update).
|
||||
keywords: ["What's new in Windows 10", "Windows 10", "November 2019 Update"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,7 +13,7 @@ ms.localizationpriority: high
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# What's new in Windows 10, version 1909 IT Pro content
|
||||
# What's new in Windows 10, version 1909 for IT Pros
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1909
|
||||
|
||||
246
windows/whats-new/whats-new-windows-10-version-2004.md
Normal file
246
windows/whats-new/whats-new-windows-10-version-2004.md
Normal file
@ -0,0 +1,246 @@
|
||||
---
|
||||
title: What's new in Windows 10, version 2004
|
||||
description: New and updated features in Windows 10, version 2004 (also known as the Windows 10 May 2020 Update).
|
||||
keywords: ["What's new in Windows 10", "Windows 10", "May 2020 Update"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.author: greglin
|
||||
manager: laurawi
|
||||
ms.localizationpriority: high
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# What's new in Windows 10, version 2004 for IT Pros
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 2004
|
||||
|
||||
This article lists new and updated features and content that are of interest to IT Pros for Windows 10, version 2004, also known as the Windows 10 May 2020 Update. This update also contains all features and fixes included in previous cumulative updates to Windows 10, version 1909.
|
||||
|
||||
> [!NOTE]
|
||||
> The month indicator for this release is 04 instead of 03 to avoid confusion with Windows releases in the year 2003.
|
||||
|
||||
## Security
|
||||
|
||||
### Windows Hello
|
||||
|
||||
- Windows Hello is now supported as Fast Identity Online 2 (FIDO2) authenticator across all major browsers including Chrome and Firefox.
|
||||
- You can now enable passwordless sign-in for Microsoft accounts on your Windows 10 device by going to **Settings > Accounts > Sign-in options**, and selecting **On** under **Make your device passwordless**. Enabling passwordless sign in will switch all Microsoft accounts on your Windows 10 device to modern authentication with Windows Hello Face, Fingerprint, or PIN.
|
||||
- Windows Hello PIN sign-in support is [added to Safe mode](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#windows-hello-pin-in-safe-mode-build-18995).
|
||||
- Windows Hello for Business now has Hybrid Azure Active Directory support and phone number sign-in (MSA). FIDO2 security key support is expanded to Azure Active Directory hybrid environments, enabling enterprises with hybrid environments to take advantage of [passwordless authentication](https://docs.microsoft.com/azure/active-directory/authentication/howto-authentication-passwordless-security-key-on-premises). For more information, see [Expanding Azure Active Directory support for FIDO2 preview to hybrid environments](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/expanding-azure-active-directory-support-for-fido2-preview-to/ba-p/981894).
|
||||
|
||||
### Windows Defender System Guard
|
||||
|
||||
In this release, [Windows Defender System Guard](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows) enables an even *higher* level of [System Management Mode](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows#system-management-mode-smm-protection) (SMM) Firmware Protection that goes beyond checking the OS memory and secrets to additional resources like registers and IO.
|
||||
|
||||
With this improvement, the OS can detect a higher level of SMM compliance, enabling devices to be even more hardened against SMM exploits and vulnerabilities. This feature is forward-looking and currently requires new hardware available soon.
|
||||
|
||||
|
||||
|
||||
### Windows Defender Application Guard
|
||||
|
||||
[Windows Defender Application Guard](https://docs.microsoft.com/deployedge/microsoft-edge-security-windows-defender-application-guard) has been available for Chromium-based Edge since early 2020.
|
||||
|
||||
Note: [Application Guard for Office](https://support.office.com/article/application-guard-for-office-9e0fb9c2-ffad-43bf-8ba3-78f785fdba46) is coming soon.
|
||||
|
||||
## Deployment
|
||||
|
||||
### Windows Setup
|
||||
|
||||
Improvements in Windows Setup with this release include:
|
||||
- Reduced offline time during feature updates
|
||||
- Improved controls for reserved storage
|
||||
- Improved controls and diagnostics
|
||||
- New recovery options
|
||||
|
||||
For more information, see Windows Setup enhancements in the [Windows IT Pro Blog](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/pilot-new-features-with-the-windows-insider-program-for-business/ba-p/1220464).
|
||||
|
||||
### SetupDiag
|
||||
|
||||
In Windows 10, version 2004, SetupDiag is now automatically installed.
|
||||
|
||||
[SetupDiag](https://docs.microsoft.com/windows/deployment/upgrade/setupdiag) is a command-line tool that can help diagnose why a Windows 10 update failed. SetupDiag works by searching Windows Setup log files. When searching log files, SetupDiag uses a set of rules to match known issues.
|
||||
|
||||
During the upgrade process, Windows Setup will extract all its sources files to the **%SystemDrive%\$Windows.~bt\Sources** directory. With Windows 10, version 2004 and later, Windows Setup now also installs SetupDiag.exe to this directory. If there is an issue with the upgrade, SetupDiag is automatically run to determine the cause of the failure. If the upgrade process proceeds normally, this directory is moved under %SystemDrive%\Windows.Old for cleanup.
|
||||
|
||||
### Windows Autopilot
|
||||
|
||||
With this release, you can configure [Windows Autopilot user-driven](https://docs.microsoft.com/windows/deployment/windows-autopilot/user-driven) Hybrid Azure Active Directory join with VPN support. This support is also backported to Windows 10, version 1909 and 1903.
|
||||
|
||||
If you configure the language settings in the Autopilot profile and the device is connected to Ethernet, all scenarios will now skip the language, locale, and keyboard pages. In previous versions, this was only supported with self-deploying profiles.
|
||||
|
||||
### Microsoft Endpoint Manager
|
||||
|
||||
An in-place upgrade wizard is available in Configuration Manager. For more information, see [Simplifying Windows 10 deployment with Configuraton Manager](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/simplifying-windows-10-deployment-with-configuration-manager/ba-p/1214364).
|
||||
|
||||
Also see [What's new in Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/whats-new).
|
||||
|
||||
### Windows Assessment and Deployment Toolkit (ADK)
|
||||
|
||||
Download the Windows ADK and Windows PE add-on for Windows 10, version 2004 [here](https://docs.microsoft.com/windows-hardware/get-started/adk-install).
|
||||
|
||||
For information about what's new in the ADK, see [What's new in the Windows ADK for Windows 10, version 2004](https://docs.microsoft.com/windows-hardware/get-started/what-s-new-in-kits-and-tools#whats-new-in-the-windows-adk-for-windows-10-version-2004).
|
||||
|
||||
### Microsoft Deployment Toolkit (MDT)
|
||||
|
||||
MDT version 8456 supports Windows 10, version 2004, but there is currently an issue that causes MDT to incorrectly detect that UEFI is present. This issue is currently under investigation.
|
||||
|
||||
For the latest information about MDT, see the [MDT release notes](https://docs.microsoft.com/mem/configmgr/mdt/release-notes).
|
||||
|
||||
## Servicing
|
||||
|
||||
### Delivery Optimization
|
||||
|
||||
Windows PowerShell cmdlets have been improved:
|
||||
|
||||
- **Get-DeliveryOptimizationStatus** has added the **-PeerInfo** option for a real-time peak behind the scenes on peer-to-peer activity (for example the peer IP Address, bytes received / sent).
|
||||
- **Get-DeliveryOptimizationLogAnalysis** is a new cmdlet that provides a summary of the activity in your DO log (# of downloads, downloads from peers, overall peer efficiency). Use the **-ListConnections** option to for in-depth look at peer-to-peer connections.
|
||||
- **Enable-DeliveryOptimizationVerboseLogs** is a new cmdlet that enables a greater level of logging detail to assist in troubleshooting.
|
||||
|
||||
Additional improvements:
|
||||
- Enterprise network [throttling is enhanced](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#new-download-throttling-options-for-delivery-optimization-build-18917) to optimize foreground vs. background throttling.
|
||||
- Automatic cloud-based congestion detection is available for PCs with cloud service support.
|
||||
|
||||
The following [Delivery Optimization](https://docs.microsoft.com/windows/deployment/update/waas-delivery-optimization) policies are removed in this release:
|
||||
|
||||
- Percentage of Maximum Download Bandwidth (DOPercentageMaxDownloadBandwidth)
|
||||
- Reason: Replaced with separate policies for foreground and background
|
||||
- Max Upload Bandwidth (DOMaxUploadBandwidth)
|
||||
- Reason: impacts uploads to internet peers only, which isn't used in Enterprises.
|
||||
- Absolute max throttle (DOMaxDownloadBandwidth)
|
||||
- Reason: separated to foreground and background
|
||||
|
||||
### Windows Update for Business
|
||||
|
||||
[Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb) enhancements in this release include:
|
||||
- Intune console updates: target version is now available allowing you to specify which version of Windows 10 you want devices to move to. Additionally, this capability enables you to keep devices on their current version until they reach end of service. Check it out in Intune, also available as a Group Policy and Configuration Service Provider (CSP) policy.
|
||||
- Validation improvements: To ensure devices and end users stay productive and protected, Microsoft uses safeguard holds to block devices from updating when there are known issues that would impact that device. Also, to better enable IT administrators to validate on the latest release, we have created a new policy that enables admins to opt devices out of the built-in safeguard holds.
|
||||
|
||||
## Virtualization
|
||||
|
||||
### Containers on Windows
|
||||
|
||||
This update includes 5 fixes to allow the host to run down-level containers on up-level for process (Argon) isolation. Previously [Containers on Windows](https://docs.microsoft.com/virtualization/windowscontainers/) required matched host and container version. This limited Windows containers from supporting mixed-version container pod scenarios.
|
||||
|
||||
### Windows Sandbox
|
||||
|
||||
[Windows Sandbox](https://techcommunity.microsoft.com/t5/Windows-Kernel-Internals/Windows-Sandbox/ba-p/301849) is an isolated desktop environment where you can install software without the fear of lasting impact to your device. This feature was released with Windows 10, version 1903. Windows 10, version 2004 includes bugfixes and enables even more control over configuration.
|
||||
|
||||
[Windows Sandbox configuration](https://docs.microsoft.com/windows/security/threat-protection/windows-sandbox/windows-sandbox-configure-using-wsb-file) includes:
|
||||
- MappedFolders now supports a destination folder. Previously no destination could be specified, it was always mapped to the Sandbox desktop.
|
||||
- AudioInput/VideoInput settings now enable you to share their host microphone or webcam with the Sandbox.
|
||||
- ProtectedClient is a new security setting that runs the connection to the Sandbox with extra security settings enabled. This is disabled by default due to issues with copy & paste.
|
||||
- PrinterRedirection: You can now enable and disable host printer sharing with the Sandbox.
|
||||
- ClipboardRedirection: You can now enable and disable host clipboard sharing with the Sandbox.
|
||||
- MemoryInMB adds the ability to specify the maximum memory usage of the Sandbox.
|
||||
|
||||
Windows Media Player is also added back to the Sandbox image in this release.
|
||||
|
||||
Windows Sandbox also has improved accessibility in this release, including:
|
||||
- Microphone support is available.
|
||||
- Added functionality to configure the audio input device via the Windows Sandbox config file.
|
||||
- A Shift + Alt + PrintScreen key sequence that activates the ease of access dialog for enabling high contrast mode.
|
||||
- A ctrl + alt + break key sequence that allows entering/exiting fullscreen mode.
|
||||
|
||||
### Windows Subsystem for Linux (WSL)
|
||||
|
||||
With this release, memory that is no longer in use in a Linux VM will be freed back to Windows. Previously, a WSL VM's memory could grow, but would not shrink when no longer needed.
|
||||
|
||||
[WSL2](https://docs.microsoft.com/windows/wsl/wsl2-index) support is has been added for ARM64 devices if your device supports virtualization.
|
||||
|
||||
For a full list of updates to WSL, see the [WSL release notes](https://docs.microsoft.com/windows/wsl/release-notes).
|
||||
|
||||
### Windows Virtual Desktop (WVD)
|
||||
|
||||
Windows 10 is an integral part of WVD, and several enhancements are available in the Spring 2020 update. Check out [Windows Virtual Desktop documentation](https://aka.ms/wvdgetstarted) for the latest and greatest information, as well as the [WVD Virtual Event from March](https://aka.ms/wvdvirtualevent).
|
||||
|
||||
## Microsoft Edge
|
||||
|
||||
Read about plans for the new Microsoft Edge and other innovations announced at [Build 2020](https://blogs.windows.com/msedgedev/2020/05/19/microsoft-edge-news-developers-build-2020/) and [What's new at Microsoft Edge Insider](https://www.microsoftedgeinsider.com/whats-new).
|
||||
|
||||
Also see information about the exciting new Edge browser [here](https://blogs.windows.com/windowsexperience/2020/01/15/new-year-new-browser-the-new-microsoft-edge-is-out-of-preview-and-now-available-for-download/).
|
||||
|
||||
## Application settings
|
||||
|
||||
This release enables explicit [control over when Windows automatically restarts apps](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#control-over-restarting-apps-at-sign-in-build-18965) that were open when you restart your PC.
|
||||
|
||||
## Windows Shell
|
||||
|
||||
Several enhancements to the Windows 10 user interface are implemented in this release:
|
||||
|
||||
### Cortana
|
||||
|
||||
[Cortana](https://www.microsoft.com/cortana) has been updated and enhanced in Windows 10, version 2004:
|
||||
- Productivity: chat-based UI gives you the ability to [interact with Cortana using typed or spoken natural language queries](https://support.microsoft.com/help/4557165) to easily get information across Microsoft 365 and stay on track. Productivity focused capabilities such as finding people profiles, checking schedules, joining meetings, and adding to lists in Microsoft To Do are currently available to English speakers in the US.
|
||||
- In the coming months, with regular app updates through the Microsoft Store, we’ll enhance this experience to support wake word invocation and enable listening when you say “Cortana,” offer more productivity capabilities such as surfacing relevant emails and documents to help you prepare for meetings, and expand supported capabilities for international users.
|
||||
- Security: tightened access to Cortana so that you must be securely logged in with your work or school account or your Microsoft account before using Cortana. Because of this tightened access, some consumer skills including music, connected home, and third-party skills will no longer be available. Additionally, users [get cloud-based assistance services that meet Office 365’s enterprise-level privacy, security, and compliance promises](https://docs.microsoft.com/microsoft-365/admin/misc/cortana-integration?view=o365-worldwide) as set out in the Online Services Terms.
|
||||
- Move the Cortana window: drag the Cortana window to a more convenient location on your desktop.
|
||||
|
||||
For updated information, see the [Microsoft 365 blog](https://aka.ms/CortanaUpdatesMay2020).
|
||||
|
||||
### Windows Search
|
||||
|
||||
Windows Search is [improved](https://insider.windows.com/community-news/desktop-search/) in several ways.
|
||||
|
||||
### Virtual Desktops
|
||||
|
||||
You can now [rename your virtual desktops](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#renaming-your-virtual-desktops-build-18975), instead of getting stuck with the system-issued names like Desktop 1.
|
||||
|
||||
### Bluetooth pairing
|
||||
|
||||
Pairing Bluetooth devices with your computer will occur through notifications, so you won't need to go to the Settings app to finish pairing. Other improvements include faster pairing and device name display. For more information, see [Improving your Bluetooth pairing experience](https://docs.microsoft.com/windows-insider/at-home/Whats-new-wip-at-home-20h1#improving-your-bluetooth-pairing-experience-build-18985).
|
||||
|
||||
### Reset this PC
|
||||
|
||||
The 'reset this PC' recovery function now includes a [cloud download](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#new-reset-this-pc-option-cloud-download-build-18970) option.
|
||||
|
||||
### Task Manager
|
||||
|
||||
The following items are added to Task Manager in this release:
|
||||
- GPU Temperature is available on the Performance tab for devices with a dedicated GPU card.
|
||||
- Disk type is now [listed for each disk on the Performance tab](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#disk-type-visible-in-task-manager-performance-tab-build-18898).
|
||||
|
||||
## Graphics & display
|
||||
|
||||
### DirectX
|
||||
|
||||
[New DirectX 12 features](https://devblogs.microsoft.com/directx/dev-preview-of-new-directx-12-features/) are available in this release.
|
||||
|
||||
### 2-in-1 PCs
|
||||
|
||||
A [new tablet experience](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#new-tablet-experience-for-2-in-1-convertible-pcs-build-18970) for two-in-one convertible PCs is available. The screen will be optimized for touch When you detach your two-in-one's keyboard, but you'll still keep the familiar look of your desktop without interruption.
|
||||
|
||||
### Specialized displays
|
||||
|
||||
With this update, devices running Windows 10 Enterprise or Windows 10 Pro for Workstations with multiple displays can be configured to prevent Windows from using a display, making it available for a specialized purpose.
|
||||
|
||||
Examples include:
|
||||
- Fixed-function arcade & gaming such as cockpit, driving, flight, and military simulators
|
||||
- Medical imaging devices with custom panels, such as grayscale X-ray displays
|
||||
- Video walls like those displayed in Microsoft Store
|
||||
- Dedicated video monitoring
|
||||
- Monitor panel testing and validation
|
||||
- Independent Hardware Vendor (IHV) driver testing and validation
|
||||
|
||||
To prevent Windows from using a display, choose Settings > Display and click Advanced display settings. Select a display to view or change, and then set the Remove display from desktop setting to On. The display will now be available for a specialized use.
|
||||
|
||||
## Desktop Analytics
|
||||
|
||||
[Desktop Analytics](https://docs.microsoft.com/configmgr/desktop-analytics/overview) is a cloud-connected service, integrated with Configuration Manager that provides data-driven insights to the management of Windows endpoints in your organization. Desktop Analytics requires a Windows E3 or E5 license, or a Microsoft 365 E3 or E5 license.
|
||||
|
||||
For information about Desktop Analytics and this release of Windows 10, see [What's new in Desktop Analytics](https://docs.microsoft.com/mem/configmgr/desktop-analytics/whats-new).
|
||||
|
||||
## See Also
|
||||
|
||||
[What's New in Windows Server](https://docs.microsoft.com/windows-server/get-started/whats-new-in-windows-server): New and updated features in Windows Server.<br>
|
||||
[Windows 10 Features](https://www.microsoft.com/windows/features): General information about Windows 10 features.<br>
|
||||
[What's New in Windows 10](https://docs.microsoft.com/windows/whats-new/): See what’s new in other versions of Windows 10.<br>
|
||||
[Start developing on Windows 10, version 2004 today](https://blogs.windows.com/windowsdeveloper/2020/05/12/start-developing-on-windows-10-version-2004-today/): New and updated features in Windows 10 that are of interest to developers.<br>
|
||||
[What's new for business in Windows 10 Insider Preview Builds](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new): A preview of new features for businesses.<br>
|
||||
[What's new in Windows 10, version 2004 - Windows Insiders](https://docs.microsoft.com/windows-insider/at-home/whats-new-wip-at-home-20h1): This list also includes consumer focused new features.<br>
|
||||
[Features and functionality removed in Windows 10](https://docs.microsoft.com/windows/deployment/planning/windows-10-removed-features): Removed features.<br>
|
||||
[Windows 10 features we’re no longer developing](https://docs.microsoft.com/windows/deployment/planning/windows-10-deprecated-features): Features that are not being developed.<br>
|
||||
[What’s new for IT pros in Windows 10, version 2004](https://aka.ms/whats-new-in-2004): Windows IT Pro blog.<br>
|
||||
Loading…
x
Reference in New Issue
Block a user