mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 16:27:22 +00:00
Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client
This commit is contained in:
Greg Lindsay
commit
baafb223c7
@ -13891,6 +13891,11 @@
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/deployment/windows-autopilot/windows-10-autopilot.md",
|
||||
"redirect_url": "/windows/deployment/windows-autopilot/windows-autopilot",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/manage-windows-endpoints.md",
|
||||
"redirect_url": "/windows/privacy/manage-windows-1809-endpoints",
|
||||
"redirect_document_id": true
|
||||
|
||||
@ -28,7 +28,7 @@ Specifically, SDT for Business enables you to:
|
||||
To run SDT for Business, download the components listed in the following table.
|
||||
|
||||
>[!NOTE]
|
||||
>In contrast to the way you typically install MSI packages, the SDT distributable MSI package can only be created by running Windows Installer (MSI.exe) at a command prompt and setting the custom flag `ADMINMODE = 1`. For details, see [Run Surface Diagnostic Toolkit using commands](surface-diagnostic-toolkit-command-line.md).
|
||||
>In contrast to the way you typically install MSI packages, the SDT distributable MSI package can only be created by running Windows Installer (msiexec.exe) at a command prompt and setting the custom flag `ADMINMODE = 1`. For details, see [Run Surface Diagnostic Toolkit using commands](surface-diagnostic-toolkit-command-line.md).
|
||||
|
||||
Mode | Primary scenarios | Download | Learn more
|
||||
--- | --- | --- | ---
|
||||
|
||||
@ -8,10 +8,12 @@ ms.pagetype: mobile
|
||||
ms.author: elizapo
|
||||
author: lizap
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 08/23/2018
|
||||
ms.date: 12/12/2018
|
||||
---
|
||||
# Understand the different apps included in Windows 10
|
||||
|
||||
>Applies to: Windows 10
|
||||
|
||||
The following types of apps run on Windows 10:
|
||||
- Windows apps - introduced in Windows 8, primarily installed from the Store app.
|
||||
- Universal Windows Platform (UWP) apps - designed to work across platforms, can be installed on multiple platforms including Windows client, Windows Phone, and Xbox. All UWP apps are also Windows apps, but not all Windows apps are UWP apps.
|
||||
@ -38,6 +40,8 @@ Here are the provisioned Windows apps in Windows 10 versions 1703, 1709, 1803 an
|
||||
> Get-AppxProvisionedPackage -Online | Format-Table DisplayName, PackageName
|
||||
> ```
|
||||
|
||||
<br>
|
||||
|
||||
| Package name | App name | 1703 | 1709 | 1803 | 1809 | Uninstall through UI? |
|
||||
|----------------------------------------|--------------------------------------------------------------------------------------------------------------------|:----:|:----:|:----:|:----:|:---------------------:|
|
||||
| Microsoft.3DBuilder | [3D Builder](ms-windows-store://pdp/?PFN=Microsoft.3DBuilder_8wekyb3d8bbwe) | x | | | | Yes |
|
||||
@ -83,10 +87,9 @@ Here are the provisioned Windows apps in Windows 10 versions 1703, 1709, 1803 an
|
||||
| Microsoft.ZuneMusic | [Groove Music](ms-windows-store://pdp/?PFN=Microsoft.ZuneMusic_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
| Microsoft.ZuneVideo | [Movies & TV](ms-windows-store://pdp/?PFN=Microsoft.ZuneVideo_8wekyb3d8bbwe) | x | x | x | x | No |
|
||||
|
||||
---
|
||||
|
||||
>[!NOTE]
|
||||
>The Store app can't be removed. If you want to remove and reinstall the Store app, you can only bring Store back by either restoring your system from a backup or resetting your system. Instead of removing the Store app, you should use group policies to hide or disable it.
|
||||
---
|
||||
|
||||
## System apps
|
||||
|
||||
@ -98,6 +101,8 @@ System apps are integral to the operating system. Here are the typical system ap
|
||||
> Get-AppxPackage -PackageTypeFilter Main | ? { $_.SignatureKind -eq "System" } | Sort Name | Format-Table Name, InstallLocation
|
||||
> ```
|
||||
|
||||
<br>
|
||||
|
||||
| Name | Package Name | 1703 | 1709 | 1803 | Uninstall through UI? |
|
||||
|----------------------------------|---------------------------------------------|:-----:|:----:|:----:|-----------------------|
|
||||
| File Picker | 1527c705-839a-4832-9118-54d4Bd6a0c89 | | | x | No |
|
||||
|
||||
@ -354,6 +354,12 @@ Footnote:
|
||||
|
||||
When the Bluetooth/ServicesAllowedList policy is provisioned, it will only allow pairing and connections of Windows PCs and phones to explicitly defined Bluetooth profiles and services. It is an allowed list, enabling admins to still allow custom Bluetooth profiles that are not defined by the Bluetooth Special Interests Group (SIG).
|
||||
|
||||
- Disabling a service shall block incoming and outgoing connections for such services
|
||||
- Disabling a service shall not publish an SDP record containing the service being blocked
|
||||
- Disabling a service shall not allow SDP to expose a record for a blocked service
|
||||
- Disabling a service shall log when a service is blocked for auditing purposes
|
||||
- Disabling a service shall take effect upon reload of the stack or system reboot
|
||||
|
||||
To define which profiles and services are allowed, enter the semicolon delimited profile or service Universally Unique Identifiers (UUID). To get a profile UUID, refer to the [Service Discovery](https://www.bluetooth.com/specifications/assigned-numbers/service-discovery) page on the Bluetooth SIG website.
|
||||
|
||||
These UUIDs all use the same base UUID with the profile identifiers added to the beginning of the base UUID.
|
||||
@ -449,4 +455,10 @@ Footnote: * The Surface pen uses the HID over GATT profile
|
||||
|Object Exchange (OBEX) |Protocol for file transfer |0x0008 |
|
||||
|PnP Information|Used to identify devices occasionally|0x1200|
|
||||
|
||||
{00001105-0000-1000-8000-00805F9B34FB};{00000008-0000-1000-8000-00805F9B34FB};{00001200-0000-1000-8000-00805F9B34FB}
|
||||
{00001105-0000-1000-8000-00805F9B34FB};{00000008-0000-1000-8000-00805F9B34FB};{00001200-0000-1000-8000-00805F9B34FB}
|
||||
|
||||
Disabling file transfer shall have the following effects
|
||||
- Fsquirt shall not allow sending of files
|
||||
- Fsquirt shall not allow receiving of files
|
||||
- Fsquirt shall display error message informing user of policy preventing file transfer
|
||||
- 3rd-party apps shall not be permitted to send or receive files using MSFT Bluetooth API
|
||||
|
||||
@ -101,7 +101,7 @@ The memory dump file is saved at the following locations.
|
||||
|
||||
You can use the Microsoft DumpChk (Crash Dump File Checker) tool to verify that the memory dump files are not corrupted or invalid. For more information, see the following video:
|
||||
|
||||
>[!video https://www.youtube.com/embed?v=xN7tOfgNKag]
|
||||
>[!video https://www.youtube.com/watch?v=xN7tOfgNKag&feature=youtu.be]
|
||||
|
||||
|
||||
More information on how to use Dumpchk.exe to check your dump files:
|
||||
|
||||
@ -60,7 +60,7 @@ sections:
|
||||
Windows 10 upgrade options are discussed and information is provided about planning, testing, and managing your production deployment.
|
||||
<br> <br>
|
||||
<table border='0'><tr><td>Topic</td><td>Description</td></tr>
|
||||
<tr><td>[Overview of Windows Autopilot](windows-autopilot/windows-10-autopilot.md) </td><td>Windows Autopilot deployment is a new cloud service from Microsoft that provides a zero touch experience for deploying Windows 10 devices. </td>
|
||||
<tr><td>[Overview of Windows Autopilot](windows-autopilot/windows-autopilot.md) </td><td>Windows Autopilot deployment is a new cloud service from Microsoft that provides a zero touch experience for deploying Windows 10 devices. </td>
|
||||
<tr><td>[Windows 10 upgrade paths](upgrade/windows-10-upgrade-paths.md) </td><td>This topic provides information about support for upgrading directly to Windows 10 from a previous operating system. </td>
|
||||
<tr><td>[Windows 10 edition upgrade](upgrade/windows-10-edition-upgrades.md) </td><td>This topic provides information about support for upgrading from one edition of Windows 10 to another. </td>
|
||||
<tr><td>[Windows 10 volume license media](windows-10-media.md) </td><td>This topic provides information about media available in the Microsoft Volume Licensing Service Center. </td>
|
||||
|
||||
@ -1,23 +0,0 @@
|
||||
---
|
||||
title: Delivery Optimization reference
|
||||
description: Delivery Optimization is a new peer-to-peer distribution method in Windows 10
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: JaimeO
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.date: 10/23/2018
|
||||
---
|
||||
|
||||
# Delivery Optimization reference
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
There are a great many details you can set in Delivery Optimization to customize it to do just what you need it to. This topic summarizes them for your reference.
|
||||
|
||||
@ -1,42 +0,0 @@
|
||||
---
|
||||
title: Set up Delivery Optimization
|
||||
description: Delivery Optimization is a new peer-to-peer distribution method in Windows 10
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
author: JaimeO
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.date: 10/23/2018
|
||||
---
|
||||
|
||||
# Set up Delivery Optimization for Windows 10 updates
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
## Plan to use Delivery Optimization
|
||||
|
||||
general guidelines + “recommended policies” chart
|
||||
|
||||
|
||||
## Implement Delivery Optimization
|
||||
[procedural-type material; go here, click this]
|
||||
|
||||
### Peer[?] topology (steps for setting up Group download mode)
|
||||
|
||||
|
||||
### Hub and spoke topology (steps for setting up peer selection)
|
||||
|
||||
|
||||
## Monitor Delivery Optimization
|
||||
how to tell if it’s working? What values are reasonable; which are not? If not, which way to adjust and how?
|
||||
|
||||
### Monitor w/ PS
|
||||
|
||||
### Monitor w/ Update Compliance
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Delivery Optimization for Windows 10 updates (Windows 10)
|
||||
title: Configure Delivery Optimization for Windows 10 updates (Windows 10)
|
||||
description: Delivery Optimization is a new peer-to-peer distribution method in Windows 10
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
@ -8,10 +8,10 @@ ms.sitesec: library
|
||||
author: JaimeO
|
||||
ms.localizationpriority: medium
|
||||
ms.author: jaimeo
|
||||
ms.date: 10/23/2018
|
||||
ms.date: 04/30/2018
|
||||
---
|
||||
|
||||
# Delivery Optimization for Windows 10 updates
|
||||
# Configure Delivery Optimization for Windows 10 updates
|
||||
|
||||
|
||||
**Applies to**
|
||||
@ -20,14 +20,15 @@ ms.date: 10/23/2018
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
Delivery Optimization reduces the bandwidth needed to download Windows updates and applications by sharing the work of downloading these packages among multiple devices in your deployment. It does this by using a self-organizing distributed cache that allows clients to download those packages from alternate sources (such as other peers on the network) in addition to the traditional Internet-based Windows Update servers.
|
||||
Windows updates, upgrades, and applications can contain packages with very large files. Downloading and distributing updates can consume quite a bit of network resources on the devices receiving them. You can use Delivery Optimization to reduce bandwidth consumption by sharing the work of downloading these packages among multiple devices in your deployment. Delivery Optimization can accomplish this because it is a self-organizing distributed cache that allows clients to download those packages from alternate sources (such as other peers on the network) in addition to the traditional Internet-based Windows Update servers. You can use Delivery Optimization in conjunction with stand-alone Windows Update, Windows Server Update Services (WSUS), Windows Update for Business, or System Center Configuration Manager when installation of Express Updates is enabled.
|
||||
|
||||
You can use Delivery Optimization in conjunction with standalone Windows Update, Windows Server Update Services (WSUS), Windows Update for Business, or System Center Configuration Manager (when installation of Express Updates is enabled).
|
||||
Delivery Optimization is a cloud-managed solution. Access to the Delivery Optimization cloud services is a requirement. This means that in order to use the peer-to-peer functionality of Delivery Optimization, devices must have access to the internet.
|
||||
|
||||
To take advantage of Delivery Optimization, you'll need the following:
|
||||
|
||||
- The devices being updated must have access to the internet.
|
||||
- The devices must be running at least these minimum versions:
|
||||
>[!NOTE]
|
||||
>WSUS can also use [BranchCache](waas-branchcache.md) for content sharing and caching. If Delivery Optimization is enabled on devices that use BranchCache, Delivery Optimization will be used instead.
|
||||
|
||||
The following table lists the minimum Windows 10 version that supports Delivery Optimization:
|
||||
|
||||
| Device type | Minimum Windows version |
|
||||
|------------------|---------------|
|
||||
@ -36,11 +37,10 @@ To take advantage of Delivery Optimization, you'll need the following:
|
||||
| IoT devices | 1803 |
|
||||
| HoloLens devices | 1803 |
|
||||
|
||||
In Windows 10 Enterprise and Education editions, Delivery Optimization allows peer-to-peer sharing on the organization's own network only, but you can configure it differently in Group Policy and mobile device management (MDM) solutions such as Microsoft Intune. These options are detailed in [Download mode](#download-mode).
|
||||
|
||||
>[!NOTE]
|
||||
>WSUS can also use [BranchCache](waas-branchcache.md) for content sharing and caching. If Delivery Optimization is enabled on devices that use BranchCache, Delivery Optimization will be used instead.
|
||||
By default in Windows 10 Enterprise and Education editions, Delivery Optimization allows peer-to-peer sharing on the organization's own network only, but you can configure it differently in Group Policy and mobile device management (MDM) solutions such as Microsoft Intune.
|
||||
|
||||
For more details, see [Download mode](#download-mode).
|
||||
|
||||
## Delivery Optimization options
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.topic: landing-page
|
||||
ms.manager: elizapo
|
||||
author: lizap
|
||||
ms.author: elizapo
|
||||
ms.date: 12/05/2018
|
||||
ms.date: 12/12/2018
|
||||
ms.localizationpriority: high
|
||||
---
|
||||
# Windows as a service
|
||||
@ -25,6 +25,7 @@ Windows 10 is the most secure version of Windows yet. Learn what updates we rele
|
||||
The latest news:
|
||||
<ul compact style="list-style: none">
|
||||
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Measuring-Delivery-Optimization-and-its-impact-to-your-network/ba-p/301809#M409">Measuring Delivery Optimization and its impact to your network</a> - December 13, 2018</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181">LTSC: What is it, and when should it be used?</a> - November 29, 2018</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Local-Experience-Packs-What-are-they-and-when-should-you-use/ba-p/286841">Local Experience Packs: What are they and when should you use them?</a> - November 14, 2018</li>
|
||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/11/13/resuming-the-rollout-of-the-windows-10-october-2018-update/#amAFU5YS1igMQRoB.97">Resuming the Rollout of the Windows 10 October 2018 Update</a> - November 13, 2018</li>
|
||||
|
||||
@ -6,7 +6,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: jaimeo
|
||||
ms.date: 12/10/2018
|
||||
ms.date: 12/12/2018
|
||||
---
|
||||
|
||||
# Upgrade Readiness deployment script
|
||||
@ -87,9 +87,7 @@ The deployment script displays the following exit codes to let you know if it wa
|
||||
|-----------|--------------|
|
||||
| 0 - Success | N/A |
|
||||
| 1 - Unexpected error occurred while executing the script. | The files in the deployment script are likely corrupted. Download the [latest script](https://go.microsoft.com/fwlink/?LinkID=822966) from the download center and try again. |
|
||||
| 2 - Error when logging to console. $logMode = 0.
|
||||
(console only) | Try changing the $logMode value to **1** and try again.
|
||||
$logMode value 1 logs to both console and file. |
|
||||
| 2 - Error when logging to console. $logMode = 0. (console only) | Try changing the $logMode value to **1** and try again. $logMode value 1 logs to both console and file. |
|
||||
| 3 - Error when logging to console and file. $logMode = 1. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. |
|
||||
| 4 - Error when logging to file. $logMode = 2. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. |
|
||||
| 5 - Error when logging to console and file. $logMode = unknown. | Verify that you have set the logPath parameter in RunConfig.bat, and that the configuration script has access to connect and write to this location. |
|
||||
|
||||
@ -1,16 +1,15 @@
|
||||
# [Windows Autopilot](windows-autopilot.md)
|
||||
## [Requirements](windows-autopilot-requirements.md)
|
||||
### [Configuration requirements](windows-autopilot-requirements-configuration.md)
|
||||
#### [Intune Connector (preview)](intune-connector.md)
|
||||
### [Network requirements](windows-autopilot-requirements-network.md)
|
||||
### [Licensing requirements](windows-autopilot-requirements-licensing.md)
|
||||
### [Intune Connector (preview)](intune-connector.md)
|
||||
## [Scenarios and Capabilities](windows-autopilot-scenarios.md)
|
||||
### [Support for existing devices](existing-devices.md)
|
||||
### [User-driven mode](user-driven.md)
|
||||
#### [Azure Active Directory joined](user-driven-aad.md)
|
||||
#### [Hybrid Azure Active Directory joined](user-driven-hybrid.md)
|
||||
### [Self-deploying mode](self-deploying.md)
|
||||
### [Enrollment status page](enrollment-status.md)
|
||||
### [Windows Autopilot Reset](windows-autopilot-reset.md)
|
||||
#### [Remote reset](windows-autopilot-reset-remote.md)
|
||||
#### [Local reset](windows-autopilot-reset-local.md)
|
||||
@ -18,6 +17,7 @@
|
||||
### [Configuring](configure-autopilot.md)
|
||||
#### [Adding devices](add-devices.md)
|
||||
#### [Creating profiles](profiles.md)
|
||||
#### [Enrollment status page](enrollment-status.md)
|
||||
### [Administering Autopilot via Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles)
|
||||
### [Administering Autopilot via Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot)
|
||||
### [Administering Autopilot via Microsoft 365 Business & Office 365 Admin portal](https://support.office.com/article/Create-and-edit-Autopilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa)
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.author: greg-lindsay
|
||||
ms.date: 10/02/2018
|
||||
ms.date: 12/12/2018
|
||||
---
|
||||
|
||||
# Adding devices to Windows Autopilot
|
||||
@ -20,6 +20,20 @@ ms.date: 10/02/2018
|
||||
|
||||
Before deploying a device using Windows Autopilot, the device must be registered with the Windows Autopilot deployment service. Ideally, this would be performed by the OEM, reseller, or distributor from which the devices were purchased, but this can also be done by the organization by collecting the hardware identity and uploading it manually.
|
||||
|
||||
## Manual registration
|
||||
|
||||
To perform manual registration of a device, you must caputure its hardware ID (also known as a hardware hash) and upload this to the Windows Autopilot deployment service. See the topics below for detailed information on how to collect and upload hardware IDs.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Do not connect devices to the Internet prior to capturing the hardware ID and creating an Autopilot device profile. This includes collecting the hardware ID, uploading the .CSV into MSfB or Intune, assigning the profile, and confirming the profile assignment. Connecting the device to the Internet before this process is complete will result in the device downloading a blank profile that is stored on the device until it is explicity removed. In Windows 10 version 1809, you can clear the cached profile by restarting OOBE. In previous versions, the only way to clear the stored profile is to re-install the OS, reimage the PC, or run **sysprep /generalize /oobe**. <br>
|
||||
>After Intune reports the profile ready to go, only then should the device be connected to the Internet.
|
||||
|
||||
Also note that if OOBE is restarted too many times it can enter a recovery mode and fail to run the Autopilot configuration. You can identify this scenario if OOBE displays multiple configuration options on the same page, including language, region, and keyboard layout. The normal OOBE displays each of these on a separate page. The following value key tracks the count of OOBE retries:
|
||||
|
||||
**HKCU\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\UserOOBE**
|
||||
|
||||
To ensure OOBE has not been restarted too many times, you can change this value to 1.
|
||||
|
||||
## Device identification
|
||||
|
||||
To define a device to the Windows Autopilot deployment service, a unique hardware ID for the device needs to be captured and uploaded to the service. While this step is ideally done by the hardware vendor (OEM, reseller, or distributor), automatically associating the device with an organization, it is also possible to do this through a harvesting process that collects the device from within a running Windows 10 version 1703 or later installation.
|
||||
@ -32,28 +46,26 @@ Note that the hardware hash also contains details about when it was generated, s
|
||||
|
||||
The hardware ID, or hardware hash, for an existing device is available through Windows Management Instrumentation (WMI), as long as that device is running Windows 10 version 1703 or later. To help gather this information, as well as the serial number of the device (useful to see at a glance the machine to which it belongs), a PowerShell script called [Get-WindowsAutoPilotInfo.ps1 has been published to the PowerShell Gallery website](https://www.powershellgallery.com/packages/Get-WindowsAutoPilotInfo).
|
||||
|
||||
To use this script, you can download it from the PowerShell Gallery and run it on each computer, or you can install it directly from the PowerShell Gallery. To install it directly and capture the hardware hash from the local computer, these commands can be used:
|
||||
To use this script, you can download it from the PowerShell Gallery and run it on each computer, or you can install it directly from the PowerShell Gallery. To install it directly and capture the hardware hash from the local computer, use the following commands from an elevated Windows PowerShell prompt:
|
||||
|
||||
*md c:\\HWID*
|
||||
```powershell
|
||||
md c:\\HWID
|
||||
Set-Location c:\\HWID
|
||||
Set-ExecutionPolicy Unrestricted
|
||||
Install-Script -Name Get-WindowsAutoPilotInfo
|
||||
Get-WindowsAutoPilotInfo.ps1 -OutputFile AutoPilotHWID.csv
|
||||
```
|
||||
|
||||
*Set-Location c:\\HWID*
|
||||
|
||||
*Set-ExecutionPolicy Unrestricted*
|
||||
|
||||
*Install-Script -Name Get-WindowsAutoPilotInfo*
|
||||
|
||||
*Get-WindowsAutoPilotInfo.ps1 -OutputFile AutoPilotHWID.csv*
|
||||
|
||||
You must run this PowerShell script with administrator privileges (elevated). It can also be run remotely, as long as WMI permissions are in place and WMI is accessible through the Windows Firewall on that remote computer. See the Get-WindowsAutoPilotInfo script’s help (using “Get-Help Get-WindowsAutoPilotInfo.ps1”) for more information.
|
||||
The commands can also be run remotely, as long as WMI permissions are in place and WMI is accessible through the Windows Firewall on that remote computer. See the Get-WindowsAutoPilotInfo script’s help (using “Get-Help Get-WindowsAutoPilotInfo.ps1”) for more information about running the script.
|
||||
|
||||
>[!NOTE]
|
||||
>With Windows 10 version 1803 and above, devices will download an Autopilot profile as soon as they connect to the internet. For devices that are not yet registered with the Autopilot deployment service, a profile will be downloaded that indicates the device should not be deployed using Autopilot. If the device connects to the internet as part of the collection process, you will need to reset the PC, reimage the PC, or re-generalize the OS (using sysprep /generalize /oobe).
|
||||
>If you will connect to the device remotely to collect the hardware ID, see the information at the top of this page about device connectivity to the Internet.
|
||||
|
||||
## Collecting the hardware ID from existing devices using System Center Configuration Manager
|
||||
|
||||
Starting with System Center Configuration Manager current branch version 1802, the hardware hashes for existing Windows 10 version 1703 and higher devices are automatically collected by Configuration Manager. See the [What’s new in version 1802](https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1802#report-on-windows-autopilot-device-information) documentation for more details.
|
||||
|
||||
## Uploading hardware IDs
|
||||
## Registering devices
|
||||
|
||||
Once the hardware IDs have been captured from existing devices, they can be uploaded through a variety of means. See the detailed documentation for each available mechanism:
|
||||
|
||||
|
||||
@ -26,7 +26,10 @@ When deploying new devices using Windows Autopilot, a common set of steps are re
|
||||
|
||||
2. [Assign a profile of settings to each device](profiles.md), specifying how the device should be deployed and what user experience should be presented.
|
||||
|
||||
3. Boot the device. When the device is connected to a network with internet access, it will contact the Windows Autopilot deployment service to see if the device is registered, and if it is, it will download the profile settings which are used to customize the end user experience.
|
||||
3. Boot the device. When the device is connected to a network with internet access, it will contact the Windows Autopilot deployment service to see if the device is registered, and if it is, it will download profile settings such as the [Enrollment Status page](enrollment-status.md), which are used to customize the end user experience.
|
||||
|
||||
<img src="./images/image2.png" width="511" height="249" />
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows Autopilot scenarios](windows-autopilot-scenarios.md)
|
||||
@ -10,7 +10,7 @@ ms.pagetype: deploy
|
||||
ms.localizationpriority: medium
|
||||
author: greg-lindsay
|
||||
ms.author: greg-lindsay
|
||||
ms.date: 11/01/2018
|
||||
ms.date: 12/13/2018
|
||||
---
|
||||
|
||||
# Windows Autopilot Enrollment Status page
|
||||
@ -33,6 +33,7 @@ The Windows Autopilot Enrollment Status page displaying the status of the comple
|
||||
<tr><td>Show error when installation takes longer than specified number of minutes<td colspan="2">Specify the number of minutes to wait for installation to complete. A default value of 60 minutes is entered.
|
||||
<tr><td>Show custom message when an error occurs<td>A text box is provided where you can specify a custom message to display in case of an installation error.<td>The default message is displayed: <br><b>Oh no! Something didn't do what it was supposed to. Please contact your IT department.<b>
|
||||
<tr><td>Allow users to collect logs about installation errors<td>If there is an installation error, a <b>Collect logs</b> button is displayed. <br>If the user clicks this button they are asked to choose a location to save the log file <b>MDMDiagReport.cab</b><td>The <b>Collect logs</b> button is not displayed if there is an installation error.
|
||||
<tr><td>Block device use until these required apps are installed if they are assigned to the user/device<td colspan="2">Choose <b>All</b> or <b>Selected</b>. <br><br>If <b>Selected</b> is chosen, a <b>Select apps</b> button is displayed that enables you to choose which apps must be installed prior to enabling device use.
|
||||
</table>
|
||||
|
||||
See the following example:
|
||||
@ -48,13 +49,20 @@ The Enrollment Status page tracks a subset of the available MDM CSP policies tha
|
||||
- Enterprise desktop apps (single-file MSIs) installed by the [Enterprise Desktop App Management CSP](https://docs.microsoft.com/windows/client-management/mdm/enterprisedesktopappmanagement-csp).
|
||||
- Certain device configuration policies.
|
||||
|
||||
Presently the following types of policies are not tracked:
|
||||
The following types of policies and installations are not tracked:
|
||||
|
||||
- Intune Management Extensions PowerShell scripts.
|
||||
- Office 365 ProPlus installations.
|
||||
- System Center Configuration Manager apps, packages, and task sequences.
|
||||
- Intune Management Extensions PowerShell scripts
|
||||
- Office 365 ProPlus installations<sup>**</sup>
|
||||
- System Center Configuration Manager apps, packages, and task sequences
|
||||
|
||||
## For more information
|
||||
<sup>**</sup>The ability to track Office 365 ProPlus installations was added with Windows 10, version 1809.<br>
|
||||
|
||||
## More information
|
||||
|
||||
For more information on configuring the Enrollment Status page, see the [Microsoft Intune documentation](https://docs.microsoft.com/intune/windows-enrollment-status).<br>
|
||||
For details about the underlying implementation, see the [FirstSyncStatus details in the DMClient CSP docuementation](https://docs.microsoft.com/windows/client-management/mdm/dmclient-csp).<br>
|
||||
For more information about blocking for app installation:
|
||||
- [Blocking for app installation using Enrollment Status Page](https://blogs.technet.microsoft.com/mniehaus/2018/12/06/blocking-for-app-installation-using-enrollment-status-page/).
|
||||
- [Support Tip: Office C2R installation is now tracked during ESP](https://techcommunity.microsoft.com/t5/Intune-Customer-Success/Support-Tip-Office-C2R-installation-is-now-tracked-during-ESP/ba-p/295514).
|
||||
|
||||
For more information on configuring the Enrollment Status page, [see the Microsoft Intune documentation](https://docs.microsoft.com/intune/windows-enrollment-status). For details about the underlying implementation, see the [FirstSyncStatus details in the DMClient CSP docuementation](https://docs.microsoft.com/windows/client-management/mdm/dmclient-csp).
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 62 KiB After Width: | Height: | Size: 31 KiB |
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.author: greg-lindsay
|
||||
ms.date: 10/02/2018
|
||||
ms.date: 12/13/2018
|
||||
---
|
||||
|
||||
# Configure Autopilot profiles
|
||||
@ -18,7 +18,29 @@ ms.date: 10/02/2018
|
||||
|
||||
- Windows 10
|
||||
|
||||
For each device that has been defined to the Windows Autopilot deployment service, a profile of settings needs to be applied to specify the exact behavior of that device when it is deployed. The following profile settings are available:
|
||||
For each device that has been defined to the Windows Autopilot deployment service, a profile of settings needs to be applied that specifies the exact behavior of that device when it is deployed. For detailed procedures on how to configure profile settings and register devices, see [Registering devices](add-devices.md#registering-devices).
|
||||
|
||||
## Profile download
|
||||
|
||||
When an Internet-connected Windows 10 device boots up, it will attempt to connect to the Autopilot service and download an Autopilot profile. Note: It is important that a profile exists at this stage so that a blank profile is not cached locally on the PC. To remove the currently cached local profile in Windows 10 version 1803 and earlier, it is necessary to re-generalize the OS using **sysprep /generalize /oobe**, reinstall the OS, or re-image the PC. In Windows 10 version 1809 and later, you can retrieve a new profile by rebooting the PC.
|
||||
|
||||
When a profile is downloaded depends on the version of Windows 10 that is running on the PC. See the following table.
|
||||
|
||||
| Windows 10 version | Profile download behavior |
|
||||
| --- | --- |
|
||||
| 1703 and 1709 | The profile is downloaded after the OOBE network connection page. This page is not displayed when using a wired connection. In this case, the profile is downloaded just prior to the EULA screen. |
|
||||
| 1803 | The profile is downloaded as soon as possible. If wired, it is downloaded at the start of OOBE. If wireless, it is downloaded after the network connection page. |
|
||||
| 1809 | The profile is downloaded as soon as possible (same as 1803), and again after each reboot. |
|
||||
|
||||
If you need to reboot a computer during OOBE:
|
||||
- Press Shift-F10 to open a command prompt.
|
||||
- Enter **shutdown /r /t 0** to restart immediately, or **shutdown /s /t 0** to shutdown immediately.
|
||||
|
||||
For more information, see [Windows Setup Command-Line Options](https://docs.microsoft.com/windows-hardware/manufacture/desktop/windows-setup-command-line-options).
|
||||
|
||||
## Profile settings
|
||||
|
||||
The following profile settings are available:
|
||||
|
||||
- **Skip Cortana, OneDrive and OEM registration setup pages**. All devices registered with Autopilot will automatically skip these pages during the out-of-box experience (OOBE) process.
|
||||
|
||||
@ -33,3 +55,7 @@ For each device that has been defined to the Windows Autopilot deployment servic
|
||||
- **Skip End User License Agreement (EULA)**. Starting in Windows 10 version 1709, organizations can decide to skip the EULA page presented during the OOBE process. This means that organizations accept the EULA terms on behalf of their users.
|
||||
|
||||
- **Disable Windows consumer features**. Starting in Windows 10 version 1803, organizations can disable Windows consumer features so that the device does not automatically install any additional Microsoft Store apps when the user first signs into the device. See the [MDM documentation](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-experience#experience-allowwindowsconsumerfeatures) for more details.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Configure Autopilot deployment](configure-autopilot.md)
|
||||
@ -1,144 +0,0 @@
|
||||
---
|
||||
title: Overview of Windows Autopilot
|
||||
description: This topic goes over Windows Autopilot and how it helps setup OOBE Windows 10 devices.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.author: greg-lindsay
|
||||
ms.date: 10/02/2018
|
||||
---
|
||||
|
||||
# Overview of Windows Autopilot
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
Windows Autopilot is a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use. In addition, you can use Windows Autopilot to reset, repurpose and recover devices.</br>
|
||||
This solution enables an IT department to achieve the above with little to no infrastructure to manage, with a process that's easy and simple.
|
||||
|
||||
The following video shows the process of setting up Autopilot:
|
||||
|
||||
</br>
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/KYVptkpsOqs" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
|
||||
## Benefits of Windows Autopilot
|
||||
|
||||
Traditionally, IT pros spend a lot of time on building and customizing images that will later be deployed to devices with a perfectly good OS already installed on them. Windows Autopilot introduces a new approach.
|
||||
|
||||
From the users' perspective, it only takes a few simple operations to make their device ready to use.
|
||||
|
||||
From the IT pros' perspective, the only interaction required from the end user, is to connect to a network and to verify their credentials. Everything past that is automated.
|
||||
|
||||
## Windows Autopilot Scenarios
|
||||
|
||||
### Cloud-Driven
|
||||
|
||||
The Cloud-Driven scenario enables you to pre-register devices through the Windows Autopilot Deployment Program. Your devices will be fully configured with no additional intervention required on the users' side.
|
||||
|
||||
#### The Windows Autopilot Deployment Program experience
|
||||
|
||||
The Windows Autopilot Deployment Program enables you to:
|
||||
* Automatically join devices to Azure Active Directory (Azure AD)
|
||||
* Auto-enroll devices into MDM services, such as Microsoft Intune ([*Requires an Azure AD Premium subscription*](#prerequisites))
|
||||
* Restrict the Administrator account creation
|
||||
* Create and auto-assign devices to configuration groups based on a device's profile
|
||||
* Customize OOBE content specific to the organization
|
||||
|
||||
##### Prerequisites
|
||||
|
||||
>[!NOTE]
|
||||
>Today, Windows Autopilot user-driven mode supports joining devices to Azure Active Directory. Support for Hybrid Azure Active Directory Join (with devices joined to an on-premises Active Directory domain) will be available in a future Windows 10 release. See [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction) for more information about the differences between these two join options.
|
||||
|
||||
* [Devices must be registered to the organization](#device-registration-and-oobe-customization)
|
||||
* [Company branding needs to be configured](#configure-company-branding-for-oobe)
|
||||
* [Network connectivity to cloud services used by Windows Autopilot](#network-connectivity-requirements)
|
||||
* Devices have to be pre-installed with Windows 10 Professional, Enterprise or Education, of version 1703 or later
|
||||
* Devices must have access to the internet
|
||||
* [Azure AD Premium P1 or P2](https://www.microsoft.com/cloud-platform/azure-active-directory-features)
|
||||
* [Users must be allowed to join devices into Azure AD](https://docs.microsoft.com/azure/active-directory/device-management-azure-portal)
|
||||
* Microsoft Intune or other MDM services to manage your devices
|
||||
|
||||
The end-user unboxes and turns on a new device. What follows are a few simple configuration steps:
|
||||
* Select a language and keyboard layout
|
||||
* Connect to the network
|
||||
* Provide email address (the email address of the user's Azure AD account) and password
|
||||
|
||||
Multiple additional settings are skipped here, since the device automatically recognizes that [it belongs to an organization](#registering-devices-to-your-organization). Following this process the device is joined to Azure AD, enrolled in Microsoft Intune (or any other MDM service).
|
||||
|
||||
MDM enrollment ensures policies are applied, apps are installed and setting are configured on the device. Windows Update for Business applies the latest updates to ensure the device is up to date.
|
||||
|
||||
</br>
|
||||
<iframe width="560" height="315" align="center" src="https://www.youtube-nocookie.com/embed/4K4hC5NchbE" frameborder="0" allowfullscreen></iframe>
|
||||
|
||||
#### Device registration and OOBE customization
|
||||
|
||||
To register devices, you will need to acquire their hardware ID and register it. We are actively working with various hardware vendors to enable them to provide the required information to you, or upload it on your behalf.
|
||||
|
||||
If you would like to capture that information by yourself, you can use the [Get-WindowsAutopilotInfo PowerShell script](https://www.powershellgallery.com/packages/Get-WindowsAutopilotInfo), which will generate a .csv file with the device's hardware ID.
|
||||
|
||||
Once devices are registered, these are the OOBE customization options available for Windows 10, starting with version 1703:
|
||||
* Skipping Work or Home usage selection (*Automatic*)
|
||||
* Skipping OEM registration, OneDrive and Cortana (*Automatic*)
|
||||
* Skipping privacy settings
|
||||
* Skipping EULA (*starting with Windows 10, version 1709*)
|
||||
* Preventing the account used to set-up the device from getting local administrator permissions
|
||||
|
||||
For guidance on how to register devices, configure and apply deployment profiles, follow one of the available administration options:
|
||||
* [Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles)
|
||||
* [Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot)
|
||||
* [Microsoft 365 Business & Office 365 Admin](https://support.office.com/article/Create-and-edit-Autopilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa)
|
||||
|
||||
##### Configure company branding for OOBE
|
||||
|
||||
In order for your company branding to appear during the OOBE, you'll need to configure it in Azure Active Directory first.
|
||||
|
||||
See [Add company branding to your directory](https://docs.microsoft.com/azure/active-directory/customize-branding#add-company-branding-to-your-directory), to configure these settings.
|
||||
|
||||
##### Configure MDM auto-enrollment in Microsoft Intune
|
||||
|
||||
In order for your devices to be auto-enrolled into MDM management, MDM auto-enrollment needs to be configured in Azure AD. To do that with Microsoft Intune, please see [Enroll Windows devices for Microsoft Intune](https://docs.microsoft.com/intune/windows-enroll). For other MDM vendors, please consult your vendor for further details.
|
||||
|
||||
>[!NOTE]
|
||||
>MDM auto-enrollment requires an Azure AD Premium P1 or P2 subscription.
|
||||
|
||||
#### Network connectivity requirements
|
||||
|
||||
The Windows Autopilot Deployment Program uses a number of cloud services to get your devices to a productive state. This means those services need to be accessible from devices registered as Windows Autopilot devices.
|
||||
|
||||
To manage devices behind firewalls and proxy servers, the following URLs need to be accessible:
|
||||
|
||||
* https://go.microsoft.com
|
||||
* https://login.microsoftonline.com
|
||||
* https://login.live.com
|
||||
* https://account.live.com
|
||||
* https://signup.live.com
|
||||
* https://licensing.mp.microsoft.com
|
||||
* https://licensing.md.mp.microsoft.com
|
||||
* ctldl.windowsupdate.com
|
||||
* download.windowsupdate.com
|
||||
|
||||
>[!NOTE]
|
||||
>Where not explicitly specified, both HTTPS (443) and HTTP (80) need to be accessible.
|
||||
|
||||
>[!TIP]
|
||||
>If you're auto-enrolling your devices into Microsoft Intune, or deploying Microsoft Office, make sure you follow the networking guidelines for [Microsoft Intune](https://docs.microsoft.com/intune/network-bandwidth-use#network-communication-requirements) and [Office 365](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2).
|
||||
|
||||
### IT-Driven
|
||||
|
||||
If you are planning to configure devices with traditional on-premises or cloud-based solutions, the [Windows Configuration Designer](https://www.microsoft.com/store/p/windows-configuration-designer/9nblggh4tx22) can be used to help automate the process. This is more suited to scenarios in which you require a higher level of control over the provisioning process. For more information on creating provisioning packages with Windows Configuration Designer, see [Create a provisioning package for Windows 10](/windows/configuration/provisioning-packages/provisioning-create-package).
|
||||
|
||||
|
||||
### Self-Deploying
|
||||
|
||||
Windows Autopilot self-deploying mode offers truly zero touch provisioning. With this mode, all you need to do is power on a device, plug it into Ethernet, and watch Windows Autopilot fully configure the device. No additional user interaction is required. see [Windows Autopilot Self-Deploying mode (Preview)] (/windows/deployment/windows-autopilot/self-deploying).
|
||||
|
||||
|
||||
### Teacher-Driven
|
||||
|
||||
If you're an IT pro or a technical staff member at a school, your scenario might be simpler. The [Set Up School PCs](https://www.microsoft.com/store/p/set-up-school-pcs/9nblggh4ls40) app can be used to quickly set up PCs for students and will get you to a productive state faster and simpler. Please see [Use the Set up School PCs app](https://docs.microsoft.com/education/windows/use-set-up-school-pcs-app) for all the details.
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.author: greg-lindsay
|
||||
ms.date: 10/02/2018
|
||||
ms.date: 12/13/2018
|
||||
---
|
||||
|
||||
# Windows Autopilot requirements
|
||||
@ -18,6 +18,14 @@ ms.date: 10/02/2018
|
||||
|
||||
Windows Autopilot depends on specific capabilities available in Windows 10, Azure Active Directory, and MDM services such as Microsoft Intune. In order to use Windows Autopilot and leverage these capabilities, some requirements must be met:
|
||||
|
||||
- [Licensing requirements](windows-autopilot-requirements-licensing.md) must be met.
|
||||
- [Networking requirements](windows-autopilot-requirements-network.md) need to be met.
|
||||
- [Configuration requirements](windows-autopilot-requirements-configuration.md) need to be completed.
|
||||
See the following topics for details on licensing, network, and configuration requirements:
|
||||
- [Licensing requirements](windows-autopilot-requirements-licensing.md)
|
||||
- [Networking requirements](windows-autopilot-requirements-network.md)
|
||||
- [Configuration requirements](windows-autopilot-requirements-configuration.md)
|
||||
- For details about specific configuration requirements to enable user-driven Hybrid Azure Active Directory join for Windows Autopilot, see [Intune Connector (preview) language requirements](intune-connector.md). This requirement is a temporary workaround, and will be removed in the next release of Intune Connector.
|
||||
|
||||
There are no additional hardware requirements to use Windows 10 Autopilot, beyond the [requirements to run Windows 10](https://www.microsoft.com/windows/windows-10-specifications).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Configure Autopilot deployment](configure-autopilot.md)
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.author: greg-lindsay
|
||||
ms.date: 10/02/2018
|
||||
ms.date: 12/13/2018
|
||||
---
|
||||
|
||||
# Windows Autopilot scenarios
|
||||
@ -20,7 +20,11 @@ Windows Autopilot includes support for a growing list of scenarios, designed to
|
||||
|
||||
For details about these scenarios, see these additional topics:
|
||||
|
||||
- [Windows Autopilot user-driven mode](user-driven.md), for devices that will be set up by a member of the organization and configured for that person.
|
||||
- [Windows Autopilot self-deploying mode](self-deploying.md), for devices that will be automatically configured for shared use, as a kiosk, or as a digital signage device.
|
||||
- [Windows Autopilot Reset](windows-autopilot-reset.md),
|
||||
- [Windows Autopilot for existing devices](existing-devices.md), to deploy Windows 10 on an existing Windows 7 or 8.1 device.
|
||||
- [Windows Autopilot user-driven mode](user-driven.md), for devices that will be set up by a member of the organization and configured for that person.
|
||||
- [Windows Autopilot self-deploying mode](self-deploying.md), for devices that will be automatically configured for shared use, as a kiosk, or as a digital signage device.
|
||||
- [Windows Autopilot Reset](windows-autopilot-reset.md), to re-deploy a device in a business-ready state.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Windows Autopilot Enrollment Status page](enrollment-status.md)
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: Overview of Windows Autopilot
|
||||
description: This topic goes over Windows Autopilot and how it helps setup OOBE Windows 10 devices.
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, msfb, intune
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: high
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
@ -14,7 +14,12 @@ ms.date: 10/02/2018
|
||||
|
||||
# Overview of Windows Autopilot
|
||||
|
||||
**Applies to: Windows 10**
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
Windows Autopilot is a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use. In addition, you can use Windows Autopilot to reset, repurpose and recover devices.</br>
|
||||
This solution enables an IT department to achieve the above with little to no infrastructure to manage, with a process that's easy and simple.
|
||||
|
||||
Windows Autopilot is designed to simplify all parts of the lifecycle of Windows devices, for both IT and end users, from initial deployment through the eventual end of life. Leveraging cloud-based services, it can reduce the overall costs for deploying, managing, and retiring devices by reducing the amount of time that IT needs to spend on these processes and the amount of infrastructure that they need to maintain, while ensuring ease of use for all types of end users.
|
||||
|
||||
@ -24,3 +29,126 @@ When initially deploying new Windows devices, Windows Autopilot leverages the OE
|
||||
|
||||
Once deployed, Windows 10 devices can be managed by tools such as Microsoft Intune, Windows Update for Business, System Center Configuration Manager, and other similar tools. Windows Autopilot can help with device re-purposing scenarios, leveraging Windows Autopilot Reset to quickly prepare a device for a new user, as well as in break/fix scenarios to enable a device to quickly be brought back to a business-ready state.
|
||||
|
||||
## Windows Autopilot walkthrough
|
||||
|
||||
The following video shows the process of setting up Windows Autopilot:
|
||||
|
||||
</br>
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/KYVptkpsOqs" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
|
||||
|
||||
## Benefits of Windows Autopilot
|
||||
|
||||
Traditionally, IT pros spend a lot of time on building and customizing images that will later be deployed to devices with a perfectly good OS already installed on them. Windows Autopilot introduces a new approach.
|
||||
|
||||
From the users' perspective, it only takes a few simple operations to make their device ready to use.
|
||||
|
||||
From the IT pros' perspective, the only interaction required from the end user, is to connect to a network and to verify their credentials. Everything past that is automated.
|
||||
|
||||
## Windows Autopilot Scenarios
|
||||
|
||||
### Cloud-Driven
|
||||
|
||||
The Cloud-Driven scenario enables you to pre-register devices through the Windows Autopilot Deployment Program. Your devices will be fully configured with no additional intervention required on the users' side.
|
||||
|
||||
#### The Windows Autopilot Deployment Program experience
|
||||
|
||||
The Windows Autopilot Deployment Program enables you to:
|
||||
* Automatically join devices to Azure Active Directory (Azure AD)
|
||||
* Auto-enroll devices into MDM services, such as Microsoft Intune ([*Requires an Azure AD Premium subscription*](#prerequisites))
|
||||
* Restrict the Administrator account creation
|
||||
* Create and auto-assign devices to configuration groups based on a device's profile
|
||||
* Customize OOBE content specific to the organization
|
||||
|
||||
##### Prerequisites
|
||||
|
||||
>[!NOTE]
|
||||
>Today, Windows Autopilot user-driven mode supports joining devices to Azure Active Directory. Support for Hybrid Azure Active Directory Join (with devices joined to an on-premises Active Directory domain) will be available in a future Windows 10 release. See [Introduction to device management in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/device-management-introduction) for more information about the differences between these two join options.
|
||||
|
||||
* [Devices must be registered to the organization](#device-registration-and-oobe-customization)
|
||||
* [Company branding needs to be configured](#configure-company-branding-for-oobe)
|
||||
* [Network connectivity to cloud services used by Windows Autopilot](#network-connectivity-requirements)
|
||||
* Devices have to be pre-installed with Windows 10 Professional, Enterprise or Education, of version 1703 or later
|
||||
* Devices must have access to the internet
|
||||
* [Azure AD Premium P1 or P2](https://www.microsoft.com/cloud-platform/azure-active-directory-features)
|
||||
* [Users must be allowed to join devices into Azure AD](https://docs.microsoft.com/azure/active-directory/device-management-azure-portal)
|
||||
* Microsoft Intune or other MDM services to manage your devices
|
||||
|
||||
The end-user unboxes and turns on a new device. What follows are a few simple configuration steps:
|
||||
* Select a language and keyboard layout
|
||||
* Connect to the network
|
||||
* Provide email address (the email address of the user's Azure AD account) and password
|
||||
|
||||
Multiple additional settings are skipped here, since the device automatically recognizes that [it belongs to an organization](#registering-devices-to-your-organization). Following this process the device is joined to Azure AD, enrolled in Microsoft Intune (or any other MDM service).
|
||||
|
||||
MDM enrollment ensures policies are applied, apps are installed and setting are configured on the device. Windows Update for Business applies the latest updates to ensure the device is up to date.
|
||||
|
||||
</br>
|
||||
<iframe width="560" height="315" align="center" src="https://www.youtube-nocookie.com/embed/4K4hC5NchbE" frameborder="0" allowfullscreen></iframe>
|
||||
|
||||
#### Device registration and OOBE customization
|
||||
|
||||
To register devices, you will need to acquire their hardware ID and register it. We are actively working with various hardware vendors to enable them to provide the required information to you, or upload it on your behalf.
|
||||
|
||||
If you would like to capture that information by yourself, you can use the [Get-WindowsAutopilotInfo PowerShell script](https://www.powershellgallery.com/packages/Get-WindowsAutopilotInfo), which will generate a .csv file with the device's hardware ID.
|
||||
|
||||
Once devices are registered, these are the OOBE customization options available for Windows 10, starting with version 1703:
|
||||
* Skipping Work or Home usage selection (*Automatic*)
|
||||
* Skipping OEM registration, OneDrive and Cortana (*Automatic*)
|
||||
* Skipping privacy settings
|
||||
* Skipping EULA (*starting with Windows 10, version 1709*)
|
||||
* Preventing the account used to set-up the device from getting local administrator permissions
|
||||
|
||||
For guidance on how to register devices, configure and apply deployment profiles, follow one of the available administration options:
|
||||
* [Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles)
|
||||
* [Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot)
|
||||
* [Microsoft 365 Business & Office 365 Admin](https://support.office.com/article/Create-and-edit-Autopilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa)
|
||||
|
||||
##### Configure company branding for OOBE
|
||||
|
||||
In order for your company branding to appear during the OOBE, you'll need to configure it in Azure Active Directory first.
|
||||
|
||||
See [Add company branding to your directory](https://docs.microsoft.com/azure/active-directory/customize-branding#add-company-branding-to-your-directory), to configure these settings.
|
||||
|
||||
##### Configure MDM auto-enrollment in Microsoft Intune
|
||||
|
||||
In order for your devices to be auto-enrolled into MDM management, MDM auto-enrollment needs to be configured in Azure AD. To do that with Microsoft Intune, please see [Enroll Windows devices for Microsoft Intune](https://docs.microsoft.com/intune/windows-enroll). For other MDM vendors, please consult your vendor for further details.
|
||||
|
||||
>[!NOTE]
|
||||
>MDM auto-enrollment requires an Azure AD Premium P1 or P2 subscription.
|
||||
|
||||
#### Network connectivity requirements
|
||||
|
||||
The Windows Autopilot Deployment Program uses a number of cloud services to get your devices to a productive state. This means those services need to be accessible from devices registered as Windows Autopilot devices.
|
||||
|
||||
To manage devices behind firewalls and proxy servers, the following URLs need to be accessible:
|
||||
|
||||
* https://go.microsoft.com
|
||||
* https://login.microsoftonline.com
|
||||
* https://login.live.com
|
||||
* https://account.live.com
|
||||
* https://signup.live.com
|
||||
* https://licensing.mp.microsoft.com
|
||||
* https://licensing.md.mp.microsoft.com
|
||||
* ctldl.windowsupdate.com
|
||||
* download.windowsupdate.com
|
||||
|
||||
>[!NOTE]
|
||||
>Where not explicitly specified, both HTTPS (443) and HTTP (80) need to be accessible.
|
||||
|
||||
>[!TIP]
|
||||
>If you're auto-enrolling your devices into Microsoft Intune, or deploying Microsoft Office, make sure you follow the networking guidelines for [Microsoft Intune](https://docs.microsoft.com/intune/network-bandwidth-use#network-communication-requirements) and [Office 365](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2).
|
||||
|
||||
### IT-Driven
|
||||
|
||||
If you are planning to configure devices with traditional on-premises or cloud-based solutions, the [Windows Configuration Designer](https://www.microsoft.com/store/p/windows-configuration-designer/9nblggh4tx22) can be used to help automate the process. This is more suited to scenarios in which you require a higher level of control over the provisioning process. For more information on creating provisioning packages with Windows Configuration Designer, see [Create a provisioning package for Windows 10](/windows/configuration/provisioning-packages/provisioning-create-package).
|
||||
|
||||
|
||||
### Self-Deploying
|
||||
|
||||
Windows Autopilot self-deploying mode offers truly zero touch provisioning. With this mode, all you need to do is power on a device, plug it into Ethernet, and watch Windows Autopilot fully configure the device. No additional user interaction is required. see [Windows Autopilot Self-Deploying mode (Preview)] (/windows/deployment/windows-autopilot/self-deploying).
|
||||
|
||||
|
||||
### Teacher-Driven
|
||||
|
||||
If you're an IT pro or a technical staff member at a school, your scenario might be simpler. The [Set Up School PCs](https://www.microsoft.com/store/p/set-up-school-pcs/9nblggh4ls40) app can be used to quickly set up PCs for students and will get you to a productive state faster and simpler. Please see [Use the Set up School PCs app](https://docs.microsoft.com/education/windows/use-set-up-school-pcs-app) for all the details.
|
||||
|
||||
|
||||
197
windows/privacy/Microsoft-DiagnosticDataViewer.md
Normal file
197
windows/privacy/Microsoft-DiagnosticDataViewer.md
Normal file
@ -0,0 +1,197 @@
|
||||
---
|
||||
title: Diagnostic Data Viewer for PowerShell Overview (Windows 10)
|
||||
description: Use this article to use the Diagnostic Data Viewer for PowerShell to review the diagnostic data sent to Microsoft by your device.
|
||||
keywords: privacy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
author: brianlic-msft
|
||||
ms.author: brianlic
|
||||
ms.date: 01/17/2018
|
||||
---
|
||||
|
||||
# Diagnostic Data Viewer for PowerShell Overview
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10, version 1809
|
||||
- Windows 10, version 1803
|
||||
- Windows Server, version 1803
|
||||
- Windows Server 2019
|
||||
|
||||
## Introduction
|
||||
The Diagnostic Data Viewer for PowerShell is a PowerShell module that lets you review the diagnostic data your device is sending to Microsoft, grouping the info into simple categories based on how it's used by Microsoft.
|
||||
|
||||
## Requirements
|
||||
|
||||
You must have administrative privilege on the device in order to use this PowerShell module. This module requires OS version 1803 and higher.
|
||||
|
||||
## Install and Use the Diagnostic Data Viewer for PowerShell
|
||||
|
||||
You must install the module before you can use the Diagnostic Data Viewer for PowerShell.
|
||||
|
||||
### Install the Diagnostic Data Viewer for PowerShell
|
||||
|
||||
>[!IMPORTANT]
|
||||
>It is recommended to visit the documentation on [Getting Started](https://docs.microsoft.com/en-us/powershell/gallery/getting-started) with PowerShell Gallery. This page provides more specific details on installing a PowerShell module.
|
||||
|
||||
To install the newest version of the Diagnostic Data Viewer PowerShell module:
|
||||
1. From an elevated Command Prompt, start a PowerShell session by running `C:\> powershell.exe`.
|
||||
2. Install the module by name
|
||||
```powershell
|
||||
PS C:\> Install-Module -Name Microsoft.DiagnosticDataViewer
|
||||
```
|
||||
|
||||
To see more information about the module, visit [PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.DiagnosticDataViewer).
|
||||
|
||||
### Turn on data viewing
|
||||
Before you can use this tool, you must turn on data viewing. Turning on data viewing enables Windows to store a local history of your device's diagnostic data for you to view until you turn it off.
|
||||
|
||||
Note that this setting does not control whether your device sends diagnostic data. Instead, it controls whether your Windows device saves a local copy of the diagnostic data sent for your viewing.
|
||||
|
||||
**To turn on data viewing through the Settings page**
|
||||
1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
|
||||
|
||||
2. Under **Diagnostic data**, turn on the **If data viewing is enabled, you can see your diagnostics data** option.
|
||||
|
||||
|
||||
|
||||
**To turn on data viewing through PowerShell**
|
||||
|
||||
1. Install the Diagnostic Data Viewer for PowerShell module.
|
||||
2. Run the Command prompt **as administrator**.
|
||||
3. Start a PowerShell session by running `C:\> powershell.exe`.
|
||||
4. Run the following commands in the PowerShell session:
|
||||
|
||||
```powershell
|
||||
PS C:\> Enable-DiagnosticDataViewing
|
||||
```
|
||||
|
||||
Once data viewing is enabled, your Windows machine will begin saving a history of diagnostic data that is sent to Microsoft from this point on.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Turning on data viewing can use up to 1GB (default setting) of disk space on your system drive. We recommend that you turn off data viewing when you're done using the Diagnostic Data Viewer. For info about turning off data viewing, see the [Turn off data viewing](#turn-off-data-viewing) section in this article.
|
||||
|
||||
### Start the Diagnostic Data Viewer
|
||||
You must start this app from the **Settings** panel.
|
||||
|
||||
**To start the Diagnostic Data Viewer**
|
||||
1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
|
||||
|
||||
2. Under **Diagnostic data**, select the **Diagnostic Data Viewer** button.
|
||||
|
||||
<br><br>-OR-<br><br>
|
||||
|
||||
Go to **Start** and search for _Diagnostic Data Viewer_.
|
||||
|
||||
3. Close the Diagnostic Data Viewer app, use your device as you normally would for a few days, and then open Diagnostic Data Viewer again to review the updated list of diagnostic data.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Turning on data viewing can use up to 1GB of disk space on your system drive. We strongly recommend that your turn off data viewing when you're done using the Diagnostic Data Viewer. For info about turning off data viewing, see the [Turn off data viewing](#turn-off-data-viewing) section in this article.
|
||||
|
||||
### Getting Started with Diagnostic Data Viewer for PowerShell
|
||||
To see how to use the cmdlet, the parameters it accepts, and examples, run the following command from an elevated PowerShell session:
|
||||
|
||||
```powershell
|
||||
PS C:\> Get-Help Get-DiagnosticData
|
||||
```
|
||||
|
||||
**To Start Viewing Diagnostic Data**
|
||||
|
||||
From an elevated PowerShell session, run the following command:
|
||||
|
||||
```powershell
|
||||
PS C:\> Get-DiagnosticData
|
||||
```
|
||||
|
||||
If the number of events is large, and you'd like to stop the command, enter `Ctrl+C`.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>The above command may produce little to no results if you enabled data viewing recently. It can take several minutes before your Windows device can show diagnostic data it has sent. Use your device as you normally would in the mean time and try again.
|
||||
|
||||
### Doing more with the Diagnostic Data Viewer for PowerShell
|
||||
The Diagnostic Data Viewer for PowerShell provides you with the following features to view and filter your device's diagnostic data. You can also use the extensive suite of other PowerShell tools with this module.
|
||||
|
||||
- **View your diagnostic events.** Running `PS C:\> Get-DiagnosticData`, you can review your diagnostic events. These events reflect activities that occurred and were sent to Microsoft.
|
||||
|
||||
Each event is displayed as a PowerShell Object. By default each event shows the event name, the time when it was seen by your Windows device, whether the event is [Basic](https://docs.microsoft.com/en-us/windows/privacy/configure-windows-diagnostic-data-in-your-organization), its [diagnostic event category](#view-diagnostic-event-categories), and a detailed JSON view of the information it contains, which shows the event exactly as it was when sent to Microsoft. Microsoft uses this info to continually improve the Windows operating system.
|
||||
|
||||
- **View Diagnostic event categories.** Each event shows the diagnostic event categories that it belongs to. These categories define how events are used by Microsoft. The categories are shown as numeric identifiers. For more information about these categories, see [Windows Diagnostic Data](https://docs.microsoft.com/en-us/windows/privacy/windows-diagnostic-data).
|
||||
|
||||
To view the diagnostic category represented by each numeric identifier and what the category means, you can run the command:
|
||||
|
||||
```powershell
|
||||
PS C:\> Get-DiagnosticDataTypes
|
||||
```
|
||||
|
||||
- **Filter events by when they were sent.** You can view events within specified time ranges by specifying a start time and end time of each command. For example, to see all diagnostic data sent between 12 and 6 hours ago, run the following command. Note that data is shown in order of oldest first.
|
||||
```powershell
|
||||
PS C:\> Get-DiagnosticData -StartTime (Get-Date).AddHours(-12) -EndTime (Get-Date).AddHours(-6)
|
||||
```
|
||||
|
||||
- **Export the results of each command.** You can export the results of each command to a separate file such as a csv by using pipe `|`. For example,
|
||||
|
||||
```powershell
|
||||
PS C:\> Get-DiagnosticData | Export-Csv 'mydata.csv'
|
||||
```
|
||||
|
||||
## Turn off data viewing
|
||||
When you're done reviewing your diagnostic data, we recommend turning off data viewing to prevent using up more memory. Turning off data viewing stops Windows from saving a history of your diagnostic data and clears the existing history of diagnostic data from your device.
|
||||
|
||||
**To turn off data viewing through the Settings page**
|
||||
1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
|
||||
|
||||
2. Under **Diagnostic data**, turn off the **If data viewing is enabled, you can see your diagnostics data** option.
|
||||
|
||||
|
||||
|
||||
**To turn off data viewing through PowerShell**
|
||||
|
||||
1. Run the Command prompt **as administrator**.
|
||||
2. Start a PowerShell session by running `C:\> powershell.exe`.
|
||||
3. Run the following commands in the PowerShell session:
|
||||
|
||||
```powershell
|
||||
PS C:\> Disable-DiagnosticDataViewing
|
||||
```
|
||||
|
||||
## Modifying the size of your data history
|
||||
By default, the tool will show you up to 1GB or 30 days of data (whichever comes first). Once either the time or space limit is reached, the data is incrementally dropped with the oldest data points dropped first.
|
||||
|
||||
**Modify the size of your data history**
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Modifying the maximum amount of diagnostic data viewable by the tool may come with performance impacts to your machine.
|
||||
|
||||
You can change the maximum data history size (in megabytes) that you can view. For example, to set the maximum data history size to 2048MB (2GB), you can run the following command.
|
||||
|
||||
```powershell
|
||||
PS C:\> Set-DiagnosticStoreCapacity -Size 2048
|
||||
```
|
||||
|
||||
You can change the maximum data history time (in hours) that you can view. For example, to set the maximum data history time to 24 hours, you can run the following command.
|
||||
|
||||
```powershell
|
||||
PS C:\> Set-DiagnosticStoreCapacity -Time 24
|
||||
```
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You may need to restart your machine for the new settings to take effect.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you have the [Diagnostic Data Viewer](diagnostic-data-viewer-overview.md) store app installed on the same device, modifications to the size of your data history through the PowerShell module will also be reflected in the app.
|
||||
|
||||
**Reset the size of your data history**
|
||||
|
||||
To reset the maximum data history size back to its original 1GB default value, run the following command in an elevated PowerShell session:
|
||||
|
||||
```powershell
|
||||
PS C:\> Set-DiagnosticStoreCapacity -Size 1024 -Time 720
|
||||
```
|
||||
|
||||
|
||||
## Related Links
|
||||
- [Module in PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.DiagnosticDataViewer)
|
||||
- [Documentation for Diagnostic Data Viewer for PowerShell](https://docs.microsoft.com/en-us/powershell/module/microsoft.diagnosticdataviewer/?view=win10-ps)
|
||||
@ -3,7 +3,9 @@
|
||||
## [Windows and the GDPR: Information for IT Administrators and Decision Makers](gdpr-it-guidance.md)
|
||||
## [Windows 10 personal data services configuration](windows-personal-data-services-configuration.md)
|
||||
## [Configure Windows diagnostic data in your organization](configure-windows-diagnostic-data-in-your-organization.md)
|
||||
## [Diagnostic Data Viewer Overview](diagnostic-data-viewer-overview.md)
|
||||
## Diagnostic Data Viewer
|
||||
### [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 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)
|
||||
|
||||
@ -9,7 +9,7 @@ ms.pagetype: security
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
ms.author: brianlic
|
||||
ms.date: 11/07/2018
|
||||
ms.date: 12/13/2018
|
||||
---
|
||||
|
||||
|
||||
@ -61,15 +61,15 @@ The following fields are available:
|
||||
- **DecisionMatchingInfoPostUpgrade_RS3** The total DecisionMatchingInfoPostUpgrade objects targeting the next release of Windows on this device.
|
||||
- **DecisionMediaCenter_RS3** The total DecisionMediaCenter objects targeting the next release of Windows on this device.
|
||||
- **DecisionSystemBios_RS3** The total DecisionSystemBios objects targeting the next release of Windows on this device.
|
||||
- **InventoryLanguagePack** The total InventoryLanguagePack objects that are present on this device.
|
||||
- **InventorySystemBios** The total InventorySystemBios objects that are present on this device.
|
||||
- **PCFP** An ID for the system that is calculated by hashing hardware identifiers.
|
||||
- **SystemProcessorCompareExchange** The total SystemProcessorCompareExchange objects that are present on this device.
|
||||
- **SystemProcessorNx** The total SystemProcessorNx objects that are present on this device.
|
||||
- **SystemProcessorSse2** The total SystemProcessorSse2 objects that are present on this device.
|
||||
- **SystemWim** The total SystemWim objects that are present on this device
|
||||
- **SystemWindowsActivationStatus** The total SystemWindowsActivationStatus objects that are present on this device.
|
||||
- **SystemWlan** The total SystemWlan objects that are present on this device.
|
||||
- **InventoryLanguagePack** The count of DecisionApplicationFile objects present on this machine targeting the next release of Windows
|
||||
- **InventorySystemBios** The count of DecisionDevicePnp objects present on this machine targeting the next release of Windows
|
||||
- **PCFP** The count of DecisionDriverPackage objects present on this machine targeting the next release of Windows
|
||||
- **SystemProcessorCompareExchange** The count of DecisionMatchingInfoBlock objects present on this machine targeting the next release of Windows
|
||||
- **SystemProcessorNx** The count of DataSourceMatchingInfoPostUpgrade objects present on this machine targeting the next release of Windows
|
||||
- **SystemProcessorSse2** The count of DecisionMatchingInfoPostUpgrade objects present on this machine targeting the next release of Windows
|
||||
- **SystemWim** The count of DecisionMediaCenter objects present on this machine targeting the next release of Windows
|
||||
- **SystemWindowsActivationStatus** The count of DecisionSystemBios objects present on this machine targeting the next release of Windows
|
||||
- **SystemWlan** The count of InventoryApplicationFile objects present on this machine.
|
||||
- **Wmdrm_RS3** The total Wmdrm objects targeting the next release of Windows on this device.
|
||||
|
||||
|
||||
@ -335,7 +335,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Appraiser.General.DecisionApplicationFileRemove
|
||||
|
||||
This event indicates that the DecisionApplicationFile object is no longer present.
|
||||
This event indicates Indicates that the DecisionApplicationFile object is no longer present.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
@ -671,7 +671,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Appraiser.General.InventoryApplicationFileStartSync
|
||||
|
||||
This event indicates that a new set of InventoryApplicationFileAdd events will be sent.
|
||||
This event indicates indicates that a new set of InventoryApplicationFileAdd events will be sent.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
@ -1757,8 +1757,107 @@ The following fields are available:
|
||||
- **syncId** A string used to group StartSync, EndSync, Add, and Remove operations that belong together. This field is unique by Sync period and is used to disambiguate in situations where multiple agents perform overlapping inventories for the same object.
|
||||
|
||||
|
||||
## Content Delivery Manager events
|
||||
|
||||
### Microsoft.Windows.ContentDeliveryManager.ProcessCreativeEvent
|
||||
|
||||
This event sends tracking data about the reliability of interactions with Windows spotlight content, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **creativeId** A serialized string containing the ID of the offer being rendered, the ID of the current rotation period, the ID of the surface/ring/market combination, the offer index in the current branch, the ID of the batch, the rotation period length, and the expiration timestamp.
|
||||
- **eventToken** In there are multiple item offers, such as Start tiles, this indicates which tile the event corresponds to.
|
||||
- **eventType** A code that indicates the type of creative event, such a impression, click, positive feedback, negative feedback, etc..
|
||||
- **placementId** Name of surface, such as LockScreen or Start.
|
||||
|
||||
|
||||
### Microsoft.Windows.ContentDeliveryManager.ReportPlacementHealth
|
||||
|
||||
This event sends aggregated client health data, summarizing information about the state of offers on a device, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **dataVersion** Schema version of the event that is used to determine what serialized content is available for placementReportedInfo and trackingInfo fields.
|
||||
- **healthResult** A code that identifies user account health status as Unknown, Healthy, Unhealthy.
|
||||
- **healthStateFlags** A code that represents a set of flags used to group devices in a health/unhealthy way. For example, Unhealthy, Healthy, RefreshNotScheduled, EmptyResponse, RenderedDefault, RenderFailure, RenderDelayed, and CacheEmpty.
|
||||
- **placementHealthId** A code that represents which surface's health is being reported. For example, Default, LockScreen, LockScreenOverlay, StartMenu, SoftLanding, DefaultStartLayout1, DefaultStartLayout2, OemPreInstalledApps, FeatureManagement, SilentInstalledApps, NotificationChannel, SuggestedPenAppsSubscribedContent, TestAppSubscribedContent, OneDriveSyncNamespaceSubscribedContent, OneDriveLocalNamespaceSubscribedContent, OneDriveSyncNamespaceInternalSubscribedContent, and OneDriveLocalNamespaceInternalSubscribedContent.
|
||||
- **placementReportedInfo** Serialized information that contains domain-specific health information written by each surface, such as lastUpportunityTime, lastOpportunityReportedTime, expectedExpirationTime, and rotationPeriod.
|
||||
- **trackingInfo** Serialized information that contains domain-specific health information written by the content delivery manager, such as lastRefreshTime, nextRefreshTime, nextUpdateTime,renderPriorToLastOpportunityTime, lastRenderTime, lastImpressionTime, lastRulesRegistrationTime, registrationTime, lastRefreshBatchCount, lastEligibleCreativeCount, availableAppSlotCount, placeholderAppSlotCount, lastRenderSuccess, lastRenderDefault, isEnabled.
|
||||
|
||||
|
||||
### Microsoft.Windows.ContentDeliveryManager.ReportPlacementState
|
||||
|
||||
This event sends data about the opt-out state of a device or user that uses Windows spotlight, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **isEnabled** Indicates if the surface is enable to receive offers.
|
||||
- **lastImpressionTime** The time when the last offer was seen.
|
||||
- **lastRenderedCreativeId** ID of the last offer rendered by the surface.
|
||||
- **lastRenderedTime** The time that the last offer was rendered.
|
||||
- **nextRotationTime** The time in which the next offer will be rendered.
|
||||
- **placementName** Name of surface, such as LockScreen or Start.
|
||||
- **placementStateReportFlags** Flags that represent if the surface is capable of receiving offers, such as off by edition, off by Group Policy, off by user choice.
|
||||
- **selectedPlacementId** ID of the surface/ring/markey combination, such as Lock-Internal-en-US.
|
||||
|
||||
|
||||
## 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** Retrieves the Boot ID for which the abnormal shutdown was observed.
|
||||
- **CrashDumpEnabled** OS configuration of the type of crash dump enabled; 0 = not enabled
|
||||
- **CumulativeCrashCount** Cumulative count of OS crashes since the BootId reset
|
||||
- **CurrentBootId** Retrieves the current boot ID.
|
||||
- **FirmwareResetReasonEmbeddedController** Firmware-supplied reason for the reset.
|
||||
- **FirmwareResetReasonEmbeddedControllerAdditional** Additional data related to the reset reason provided by the firmware.
|
||||
- **FirmwareResetReasonPch** Hardware-supplied reason for the reset.
|
||||
- **FirmwareResetReasonPchAdditional** Additional data related to the reset reason provided by the hardware.
|
||||
- **FirmwareResetReasonSupplied** Indicates whether the firmware supplied any reset reason.
|
||||
- **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 captured Last Bug Check""; important to match AbnormalShutdownBootId for analysis or the Last Bug Check info in the event does not correlate with the rest of the information""""ootId of the captured ""Last Bug Check""; important to match AbnormalShutdownBootId for analysis or the Last Bug Check info in the event does not correlate with the """"otId of the captured ""Last Bug Check""; important to match AbnormalShutdownBootId for analysis or the Last Bug Check info in the event does n""""tId of the captured ""Last Bug Check""; important to match AbnormalShutdownBootId for analysis or the Last Bug Check inf""""Id of the captured ""Last Bug Check""; important to match AbnormalShutdownBootId for analysis or th""""d of the captured ""Last Bug Check""; important to match AbnormalShutdownBootId"""" of the captured ""Last Bug Check""; important to match Abno""""of the captured ""Last Bug Check""; import""""f the captured ""Last Bu"""" the ca"""
|
||||
- **LastBugCheckCode** Bug Check code indicating the type of error; LastBugCheck data is only available on UEFI-enabled systems (as indicated by FirmwareTypeId == 2) because it is saved in an EFI variable; LastBugCheck data is only available if crashdumping is enabled (as indicated by CrashDumpEnabled > 0)
|
||||
- **LastBugCheckContextFlags** Additional crashdump settings; LastBugCheck data is only available on UEFI-enabled systems (as indicated by FirmwareTypeId == 2) because it is saved in an EFI variable; LastBugCheck data is only available if crashdumping is enabled (as indicated by CrashDumpEnabled > 0)
|
||||
- **LastBugCheckOriginalDumpType** Type of crashdump the system intended to save; LastBugCheck data is only available on UEFI-enabled systems (as indicated by FirmwareTypeId == 2) because it is saved in an EFI variable; LastBugCheck data is only available if crashdumping is enabled (as indicated by CrashDumpEnabled > 0)
|
||||
- **LastBugCheckOtherSettings** Other crashdump settings; LastBugCheck data is only available on UEFI-enabled systems (as indicated by FirmwareTypeId == 2) because it is saved in an EFI variable; LastBugCheck data is only available if crashdumping is enabled (as indicated by CrashDumpEnabled > 0)
|
||||
- **LastBugCheckParameter1** First Bug Check parameter with additional info on the type of the error; LastBugCheck data is only available on UEFI-enabled systems (as indicated by FirmwareTypeId == 2) because it is saved in an EFI variable; LastBugCheck data is only available if crashdumping is enabled (as indicated by CrashDumpEnabled > 0)
|
||||
- **LastBugCheckProgress** Progress towards writing out the last crashdump; non-zero value indicates an attempt; LastBugCheck data is only available on UEFI-enabled systems (as indicated by FirmwareTypeId == 2) because it is saved in an EFI variable; LastBugCheck data is only available if crashdumping is enabled (as indicated by CrashDumpEnabled .> 0)
|
||||
- **LastSuccessfullyShutdownBootId** Retrieves the last successfully/cleanly shutdown boot ID.
|
||||
- **PowerButtonCumulativePressCount** "Number of times the Power Button was detected to have been pressed (pressed" not to be confused with "released") for the BootId specified in PowerButtonLastPressBootId""umber of times the Power Button was detected to have been pressed ("pressed" not to be confused wit""mber of times the Power Button """umber of times the Power Button was detected to have been pressed (pressed" not to be confused with "released") for the BootId specified in PowerButtonLastPressBootId""umber of times the Power Button was detected to have been ""mber of times the Power Button was detected to have been pressed (pressed" not to be confused with "released") for the BootId specified in PowerButtonL""ber of times the Power Button was detected to have been pressed (pressed" not""er o"
|
||||
- **PowerButtonCumulativeReleaseCount** "Number of times the Power Button was detected to have been released (released" not to be confused with "pressed") for the BootId specified in PowerButtonLastReleaseBootId""umber of times the Power Button was detected to have been released ("released" not to be confused wit""mber of times the Power Button w"""umber of times the Power Button was detected to have been released (released" not to be confused with "pressed") for the BootId specified in PowerButtonLastReleaseBootId""umber of times the Power Button was detected to have been r""mber of times the Power Button was detected to have been released (released" not to be confused with "pressed") for the BootId specified in PowerButtonLa""ber of times the Power Button was detected to have been released (released" n""er"
|
||||
- **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")""ootId of the last time the Power Button was """ootId of the last time the Power Button was detected to have been pressed (pressed""""
|
||||
- **PowerButtonLastPressTime** "Date/time of the last time the Power Button was detected to have been pressed (pressed" not to be confused with "released")""ate/time of the last time the Power Button w"""ate/time of the last time the Power Button was detected to have been pressed (press"
|
||||
- **PowerButtonLastReleaseBootId** "BootId of the last time the Power Button was detected to have been released (released" not to be confused with "pressed")""ootId of the last time the Power Button was """ootId of the last time the Power Button was detected to have been released (releas"
|
||||
- **PowerButtonLastReleaseTime** "Date/time of the last time the Power Button was detected to have been released (released" not to be confused with "pressed")""ate/time of the last time the Power Button w"""ate/time of the last time the Power Button was detected to have been released (rel"
|
||||
- **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** Progress while monitor/display is being turned on; ranges from 0 (no progress) to 0x50 (completion); if PowerButtonPressPowerWatchdogArmed == TRUE (armed), the value represents the current stage whereas if PowerButtonPressPowerWatchdogArmed == FALSE (not armed),the value represents the last completed stage at the time of the last Power Button press,
|
||||
- **PowerButtonPressPowerWatchdogArmed** Inidicates whether or not the watchdog for the monitor/display was active at the time of the last Power Button press
|
||||
- **TransitionInfoBootId** "BootId of the captured Transition Info""; important to match AbnormalShutdownBootId for analysis or the Transition Info in the event does not correlate with the rest of the information""""ootId of the captured ""Transition Info""; important to match AbnormalShutdownBootId for analysis or the Transition Info in the event does not correlate with the """"otId of the captured ""Transition Info""; important to match AbnormalShutdownBootId for analysis or the Transition Info in the event does n""""tId of the captured ""Transition Info""; important to match AbnormalShutdownBootId for analysis or the Transition Inf""""Id of the captured ""Transition Info""; important to match AbnormalShutdownBootId for analysis o""""d of the captured ""Transition Info""; important to match AbnormalShutdownBo"""" of the captured ""Transition Info""; important to match """"of the captured ""Transition Info""; im""""f the captured ""Tran"""" the"""
|
||||
- **TransitionInfoCSCount** "Total number of times the system transitioned from Connected Standby mode to on" at the time the last marker was saved""otal number of times the system transitio"""otal number of times the system transitioned from Connected Standby mode to on" at""tal"
|
||||
- **TransitionInfoCSEntryReason** Indicates the reason the device last entered Connected Standby mode
|
||||
- **TransitionInfoCSExitReason** Indicates the reason the device last exited Connected Standby mode
|
||||
- **TransitionInfoCSInProgress** At the time the last marker was saved,the system was in or entering Connected Standby mode
|
||||
- **TransitionInfoLastReferenceTimeChecksum** Checksum of TransitionInfoLastReferenceTimestamp
|
||||
- **TransitionInfoLastReferenceTimestamp** Date/time the marker was last saved
|
||||
- **TransitionInfoPowerButtonTimestamp** Date/time of the last time the Power Button was detected to have been pressed (collected via a different mechanism than PowerButtonLastPressTime)
|
||||
- **TransitionInfoSleepInProgress** At the time the last marker was saved,the system was in or entering Sleep mode
|
||||
- **TransitionInfoSleepTranstionsToOn** "Total number of times the system transitioned from Sleep mode to on" at the time the last marker was saved""otal number of times the system transitio"""otal number of times the system transitioned from Sleep mode to on" at the time th""tal number of t"
|
||||
- **TransitionInfoSystemRunning** At the time the last marker was saved,the system was running
|
||||
- **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.
|
||||
|
||||
|
||||
### 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.
|
||||
@ -1856,6 +1955,24 @@ The following fields are available:
|
||||
- **VortexHttpFailures5xx** The number of 500-599 error codes received from Vortex.
|
||||
|
||||
|
||||
### TelClientSynthetic.HeartBeat_Aria_5
|
||||
|
||||
This event is the telemetry client ARIA heartbeat.
|
||||
|
||||
|
||||
|
||||
### TelClientSynthetic.HeartBeat_Seville_5
|
||||
|
||||
This event is sent by the universal telemetry client (UTC) as a heartbeat signal for Sense.
|
||||
|
||||
|
||||
|
||||
### TelClientSynthetic.TailoredExperiencesWithDiagnosticDataUpdate
|
||||
|
||||
This event is triggered when UTC determines it needs to send information about personalization settings of the user.
|
||||
|
||||
|
||||
|
||||
## DxgKernelTelemetry events
|
||||
|
||||
### DxgKrnlTelemetry.GPUAdapterInventoryV2
|
||||
@ -2571,6 +2688,31 @@ The following fields are available:
|
||||
- **UserInputTime** The amount of time the loader application spent waiting for user input.
|
||||
|
||||
|
||||
### Microsoft.Windows.Kernel.Power.OSStateChange
|
||||
|
||||
This event denotes the transition between operating system states (e.g., On, Off, Sleep, etc.). By using this event with Windows Analytics, organizations can use this to help monitor reliability and performance of managed devices.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **AcPowerOnline** If "TRUE," the device is using AC power. If "FALSE," the device is using battery power.
|
||||
- **ActualTransitions** This will give the actual transitions number
|
||||
- **BatteryCapacity** Maximum battery capacity in mWh
|
||||
- **BatteryCharge** Current battery charge as a percentage of total capacity
|
||||
- **BatteryDischarging** Flag indicating whether the battery is discharging or charging
|
||||
- **BootId** Monotonically increasing boot id, reset on upgrades.
|
||||
- **BootTimeUTC** Boot time in UTC file time.
|
||||
- **EventSequence** Monotonically increasing event number for OsStateChange events logged during this boot.
|
||||
- **LastStateTransition** The previous state transition on the device.
|
||||
- **LastStateTransitionSub** The previous state subtransition on the device.
|
||||
- **StateDurationMS** Milliseconds spent in the state being departed
|
||||
- **StateTransition** Transition type PowerOn=1, Shutdown, Suspend, Resume, Heartbeat.
|
||||
- **StateTransitionSub** Subtransition type Normal=1, Reboot, Hiberboot, Standby, Hibernate, ConnectedStandby, Reserved, HybridSleep.
|
||||
- **TotalDurationMS** Total time device has been up in milliseconds in wall clock time.
|
||||
- **TotalUptimeMS** Total time device has been on (not in a suspended state) in milliseconds.
|
||||
- **TransitionsToOn** TransitionsToOn increments each time the system successfully completes a system sleep event, and is sent as part of the PowerTransitionEnd ETW event.
|
||||
- **UptimeDeltaMS** Duration in last state in milliseconds.
|
||||
|
||||
|
||||
## OneDrive events
|
||||
|
||||
### Microsoft.OneDrive.Sync.Setup.APIOperation
|
||||
@ -2627,43 +2769,6 @@ The following fields are available:
|
||||
- **UnregisterOldTaskResult** The HResult of the UnregisterOldTask operation.
|
||||
|
||||
|
||||
### Microsoft.OneDrive.Sync.Setup.SetupCommonData
|
||||
|
||||
This event contains basic OneDrive configuration data that helps to diagnose failures.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **AppVersion** The version of the app.
|
||||
- **BuildArchitecture** Is the architecture x86 or x64?
|
||||
- **Environment** Is the device on the production or int service?
|
||||
- **MachineGuid** The CEIP machine ID.
|
||||
- **Market** Which market is this in?
|
||||
- **MSFTInternal** Is this an internal Microsoft device?
|
||||
- **OfficeVersionString** The version of Office that is installed.
|
||||
- **OSDeviceName** Only if the device is internal to Microsoft, the device name.
|
||||
- **OSUserName** Only if the device is internal to Microsoft, the user name.
|
||||
- **UserGuid** The CEIP user ID.
|
||||
|
||||
|
||||
### Microsoft.OneDrive.Sync.Updater.CommonData
|
||||
|
||||
This event contains basic OneDrive configuration data that helps to diagnose failures.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **AppVersion** The version of the app.
|
||||
- **BuildArch** Is the architecture x86 or x64?
|
||||
- **Environment** Is the device on the production or int service?
|
||||
- **IsMSFTInternal** TRUE if the device is an internal Microsoft device.
|
||||
- **MachineGuid** The GUID (Globally Unique ID) that identifies the machine for the CEIP (Customer Experience Improvement Program).
|
||||
- **Market** Which market is this in?
|
||||
- **OfficeVersion** The version of Office that is installed.
|
||||
- **OneDriveDeviceId** The OneDrive device ID.
|
||||
- **OSDeviceName** Only if the device is internal to Microsoft, the device name.
|
||||
- **OSUserName** Only if the device is internal to Microsoft, the user name.
|
||||
- **UserGuid** The GUID (Globally Unique ID) of the user currently logged in.
|
||||
|
||||
|
||||
### Microsoft.OneDrive.Sync.Updater.ComponentInstallState
|
||||
|
||||
This event includes basic data about the installation state of dependent OneDrive components.
|
||||
@ -2750,48 +2855,11 @@ The following fields are available:
|
||||
- **winInetError** The HResult of the operation.
|
||||
|
||||
|
||||
## Other events
|
||||
|
||||
### Microsoft.Xbox.XamTelemetry.AppActivationError
|
||||
|
||||
This event indicates whether the system detected an activation error in the app.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ActivationUri** Activation URI (Uniform Resource Identifier) used in the attempt to activate the app.
|
||||
- **AppId** The Xbox LIVE Title ID.
|
||||
- **AppUserModelId** The AUMID (Application User Model ID) of the app to activate.
|
||||
- **Result** The HResult error.
|
||||
- **UserId** The Xbox LIVE User ID (XUID).
|
||||
|
||||
|
||||
### Microsoft.Xbox.XamTelemetry.AppActivity
|
||||
|
||||
This event is triggered whenever the current app state is changed by: launch, switch, terminate, snap, etc.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **AppActionId** The ID of the application action.
|
||||
- **AppCurrentVisibilityState** The ID of the current application visibility state.
|
||||
- **AppId** The Xbox LIVE Title ID of the app.
|
||||
- **AppPackageFullName** The full name of the application package.
|
||||
- **AppPreviousVisibilityState** The ID of the previous application visibility state.
|
||||
- **AppSessionId** The application session ID.
|
||||
- **AppType** The type ID of the application (AppType_NotKnown, AppType_Era, AppType_Sra, AppType_Uwa).
|
||||
- **BCACode** The BCA (Burst Cutting Area) mark code of the optical disc used to launch the application.
|
||||
- **DurationMs** The amount of time (in milliseconds) since the last application state transition.
|
||||
- **IsTrialLicense** This boolean value is TRUE if the application is on a trial license.
|
||||
- **LicenseType** The type of licensed used to authorize the app (0 - Unknown, 1 - User, 2 - Subscription, 3 - Offline, 4 - Disc).
|
||||
- **LicenseXuid** If the license type is 1 (User), this field contains the XUID (Xbox User ID) of the registered owner of the license.
|
||||
- **ProductGuid** The Xbox product GUID (Globally-Unique ID) of the application.
|
||||
- **UserId** The XUID (Xbox User ID) of the current user.
|
||||
|
||||
|
||||
## Remediation events
|
||||
|
||||
### Microsoft.Windows.Remediation.Applicable
|
||||
|
||||
This event sends simple device connectivity and configuration data about an application installed on the system that helps keep the Windows Update stack healthy.
|
||||
This event indicates a remedial plug-in is applicable if/when such a plug-in is detected. This is used to ensure Windows is up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -2814,7 +2882,7 @@ The following fields are available:
|
||||
- **HResult** The HRESULT for detection or perform action phases of the plugin.
|
||||
- **IsAppraiserLatestResult** The HRESULT from the appraiser task.
|
||||
- **IsConfigurationCorrected** Indicates whether the configuration of SIH task was successfully corrected.
|
||||
- **LastHresult** The HResult of the operation.
|
||||
- **LastHresult** The HRESULT for detection or perform action phases of the plugin.
|
||||
- **LastRun** The date of the most recent SIH run.
|
||||
- **NextRun** Date of the next scheduled SIH run.
|
||||
- **PackageVersion** The version of the current remediation package.
|
||||
@ -2875,7 +2943,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Remediation.Completed
|
||||
|
||||
This event sends simple device connectivity and configuration data about an application installed on the system that helps keep the Windows Update stack healthy.
|
||||
This event enables completion tracking of a process that remediates issues preventing security and quality updates.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -2964,9 +3032,123 @@ The following fields are available:
|
||||
- **WindowsSxsTempFolderSizeInMegabytes** The size of the WinSxS (Windows Side-by-Side) Temp folder, measured in Megabytes.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.DiskCleanUnExpectedErrorEvent
|
||||
|
||||
This event indicates that an unexpected error occurred during an update and provides information to help address the issue.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** The Correlation vector.
|
||||
- **ErrorMessage** A description of any errors encountered while the plug-in was running.
|
||||
- **GlobalEventCounter** The client-side counter that indicates ordering of events.
|
||||
- **Hresult** The result of the event execution.
|
||||
- **PackageVersion** The version number of the current remediation package.
|
||||
- **SessionGuid** GUID associated with a given execution of sediment pack.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.Error
|
||||
|
||||
This event indicates a Sediment Pack error (update stack failure) has been detected and provides information to help address the issue.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **HResult** The result of the event execution.
|
||||
- **Message** A message containing information about the error that occurred.
|
||||
- **PackageVersion** The version number of the current remediation package.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.FallbackError
|
||||
|
||||
This event indicates an error when Self Update results in a Fallback and provides information to help address the issue.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **s0** Indicates the Fallback error level. See [Microsoft.Windows.Remediation.wilResult](#microsoftwindowsremediationwilresult).
|
||||
- **wilResult** The result of the Windows Installer Logging. See [wilResult](#wilresult).
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.RemediationNotifyUserFixIssuesInvokeUIEvent
|
||||
|
||||
This event occurs when the Notify User task executes and provides information about the cause of the notification.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** The Correlation vector.
|
||||
- **GlobalEventCounter** The client-side counter that indicates ordering of events.
|
||||
- **PackageVersion** The version number of the current remediation package.
|
||||
- **RemediationNotifyUserFixIssuesCallResult** The result of calling the USO (Update Session Orchestrator) sequence steps.
|
||||
- **RemediationNotifyUserFixIssuesUsoDownloadCalledHr** The error code from the USO (Update Session Orchestrator) download call.
|
||||
- **RemediationNotifyUserFixIssuesUsoInitializedHr** The error code from the USO (Update Session Orchestrator) initialize call.
|
||||
- **RemediationNotifyUserFixIssuesUsoProxyBlanketHr** The error code from the USO (Update Session Orchestrator) proxy blanket call.
|
||||
- **RemediationNotifyUserFixIssuesUsoSetSessionHr** The error code from the USO (Update Session Orchestrator) session call.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.RemediationShellFailedAutomaticAppUpdateModifyEventId
|
||||
|
||||
This event provides the modification of the date on which an Automatic App Update scheduled task failed and provides information about the failure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** The Correlation Vector.
|
||||
- **GlobalEventCounter** The client-side counter that indicates ordering of events.
|
||||
- **hResult** The result of the event execution.
|
||||
- **PackageVersion** The version number of the current remediation package.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.RemediationShellUnexpectedExceptionId
|
||||
|
||||
This event identifies the remediation plug-in that returned an unexpected exception and provides information about the exception.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** The Correlation Vector.
|
||||
- **GlobalEventCounter** The client-side counter that indicates ordering of events.
|
||||
- **PackageVersion** The version number of the current remediation package.
|
||||
- **RemediationShellUnexpectedExceptionId** The ID of the remediation plug-in that caused the exception.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.RemediationUHEnableServiceFailed
|
||||
|
||||
This event tracks the health of key update (Remediation) services and whether they are enabled.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** The Correlation Vector.
|
||||
- **GlobalEventCounter** The client-side counter that indicates ordering of events.
|
||||
- **hResult** The result of the event execution.
|
||||
- **PackageVersion** The version number of the current remediation package.
|
||||
- **serviceName** The name associated with the operation.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.RemediationUpgradeSucceededDataEventId
|
||||
|
||||
This event returns information about the upgrade upon success to help ensure Windows is up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **AppraiserPlugin** TRUE / FALSE depending on whether the Appraiser plug-in task fix was successful.
|
||||
- **ClearAUOptionsPlugin** TRUE / FALSE depending on whether the AU (Auto Updater) Options registry keys were successfully deleted.
|
||||
- **CV** The Correlation Vector.
|
||||
- **DatetimeSyncPlugin** TRUE / FALSE depending on whether the DateTimeSync plug-in ran successfully.
|
||||
- **DiskCleanupPlugin** TRUE / FALSE depending on whether the DiskCleanup plug-in ran successfully.
|
||||
- **GlobalEventCounter** The client-side counter that indicates ordering of events.
|
||||
- **NoisyHammerPlugin** TRUE / FALSE depending on whether the NoisyHammer plug-in ran successfully.
|
||||
- **PackageVersion** The version number of the current remediation package.
|
||||
- **RebootRequiredPlugin** TRUE / FALSE depending on whether the Reboot plug-in ran successfully.
|
||||
- **RemediationNotifyUserFixIssuesPlugin** TRUE / FALSE depending on whether the User Fix Issues plug-in ran successfully
|
||||
- **RemediationPostUpgradeDiskSpace** The amount of disk space available after the upgrade.
|
||||
- **RemediationPostUpgradeHibernationSize** The size of the Hibernation file after the upgrade.
|
||||
- **ServiceHealthPlugin** A list of services updated by the plug-in.
|
||||
- **SIHHealthPlugin** TRUE / FALSE depending on whether the SIH Health plug-in ran successfully.
|
||||
- **StackDataResetPlugin** TRUE / FALSE depending on whether the update stack completed successfully.
|
||||
- **TaskHealthPlugin** A list of tasks updated by the plug-in.
|
||||
- **UpdateApplicabilityFixerPlugin** TRUE / FALSE depending on whether the update applicability fixer plug-in completed successfully.
|
||||
- **WindowsUpdateEndpointPlugin** TRUE / FALSE depending on whether the Windows Update Endpoint was successful.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.Started
|
||||
|
||||
This event sends simple device connectivity and configuration data about an application installed on the system that helps keep the Windows Update stack healthy.
|
||||
This event reports whether a plug-in started, to help ensure Windows is up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -2977,6 +3159,31 @@ The following fields are available:
|
||||
- **Result** This is the HRESULT for detection or perform action phases of the plugin.
|
||||
|
||||
|
||||
### Microsoft.Windows.Remediation.wilResult
|
||||
|
||||
This event provides Self Update information to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **callContext** A list of diagnostic activities containing this error.
|
||||
- **currentContextId** An identifier for the newest diagnostic activity containing this error.
|
||||
- **currentContextMessage** A message associated with the most recent diagnostic activity containing this error (if any).
|
||||
- **currentContextName** Name of the most recent diagnostic activity containing this error.
|
||||
- **failureCount** Number of failures seen within the binary where the error occurred.
|
||||
- **failureId** The identifier assigned to this failure.
|
||||
- **failureType** Indicates the type of failure observed (exception, returned, error, logged error, or fail fast).
|
||||
- **fileName** The source code file name where the error occurred.
|
||||
- **function** The name of the function where the error occurred.
|
||||
- **hresult** The failure error code.
|
||||
- **lineNumber** The Line Number within the source code file where the error occurred.
|
||||
- **message** A message associated with the failure (if any).
|
||||
- **module** The name of the binary module in which the error occurred.
|
||||
- **originatingContextId** The identifier for the oldest diagnostic activity containing this error.
|
||||
- **originatingContextMessage** A message associated with the oldest diagnostic activity containing this error (if any).
|
||||
- **originatingContextName** The name of the oldest diagnostic activity containing this error.
|
||||
- **threadId** The identifier of the thread the error occurred on.
|
||||
|
||||
|
||||
## Sediment events
|
||||
|
||||
### Microsoft.Windows.Sediment.Info.AppraiserData
|
||||
@ -3326,17 +3533,15 @@ The following fields are available:
|
||||
- **Time** The system time at which the event occurred.
|
||||
|
||||
|
||||
## Sediment Launcher events
|
||||
|
||||
### Microsoft.Windows.SedimentLauncher.Applicable
|
||||
|
||||
This event sends simple device connectivity and configuration data about an application installed on the system that helps keep the Windows Update stack healthy.
|
||||
Indicates whether a given plugin is applicable.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **DetectedCondition** Boolean true if detect condition is true and perform action will be run.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
||||
- **IsSelfUpdateEnabledInOneSettings** True if self update enabled in Settings.
|
||||
- **IsSelfUpdateNeeded** True if self update needed by device.
|
||||
- **PackageVersion** Current package version of Remediation.
|
||||
@ -3346,43 +3551,97 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.SedimentLauncher.Completed
|
||||
|
||||
This event sends simple device connectivity and configuration data about an application installed on the system that helps keep the Windows Update stack healthy.
|
||||
Indicates whether a given plugin has completed its work.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **FailedReasons** Concatenated list of failure reasons.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
||||
- **PackageVersion** Current package version of Remediation.
|
||||
- **PluginName** Name of the plugin specified for each generic plugin event.
|
||||
- **Result** This is the HRESULT for detection or perform action phases of the plugin.
|
||||
- **SedLauncherExecutionResult** HRESULT for one execution of the Sediment Launcher.
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentLauncher.Error
|
||||
|
||||
This event indicates an error occurred during the execution of the plug-in. The information provided helps ensure future upgrade/update attempts are more successful.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **HResult** The result for the Detection or Perform Action phases of the plug-in.
|
||||
- **Message** A message containing information about the error that occurred (if any).
|
||||
- **PackageVersion** The version number of the current remediation package.
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentLauncher.FallbackError
|
||||
|
||||
This event indicates that an error occurred during execution of the plug-in fallback.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **s0** Error occurred during execution of the plugin fallback. See [Microsoft.Windows.SedimentLauncher.wilResult](#microsoftwindowssedimentlauncherwilresult).
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentLauncher.Information
|
||||
|
||||
This event provides general information returned from the plug-in.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **HResult** This is the HRESULT for detection or perform action phases of the plugin.
|
||||
- **Message** Information message returned from a plugin containing only information internal to the plugins execution.
|
||||
- **PackageVersion** Current package version of Remediation.
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentLauncher.Started
|
||||
|
||||
This event sends simple device connectivity and configuration data about an application installed on the system that helps keep the Windows Update stack healthy.
|
||||
This event indicates that a given plug-in has started.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
||||
- **PackageVersion** Current package version of Remediation.
|
||||
- **PluginName** Name of the plugin specified for each generic plugin event.
|
||||
- **Result** This is the HRESULT for detection or perform action phases of the plugin.
|
||||
|
||||
|
||||
## Sediment Service events
|
||||
### Microsoft.Windows.SedimentLauncher.wilResult
|
||||
|
||||
This event provides the result from the Windows internal library.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **callContext** List of telemetry activities containing this error.
|
||||
- **currentContextId** Identifier for the newest telemetry activity containing this error.
|
||||
- **currentContextMessage** Custom message associated with the newest telemetry activity containing this error (if any).
|
||||
- **currentContextName** Name of the newest telemetry activity containing this error.
|
||||
- **failureCount** Number of failures seen within the binary where the error occurred.
|
||||
- **failureId** Identifier assigned to this failure.
|
||||
- **failureType** Indicates what type of failure was observed (exception, returned error, logged error or fail fast).
|
||||
- **fileName** Source code file name where the error occurred.
|
||||
- **function** Name of the function where the error occurred.
|
||||
- **hresult** Failure error code.
|
||||
- **lineNumber** Line number within the source code file where the error occurred.
|
||||
- **message** Custom message associated with the failure (if any).
|
||||
- **module** Name of the binary where the error occurred.
|
||||
- **originatingContextId** Identifier for the oldest telemetry activity containing this error.
|
||||
- **originatingContextMessage** Custom message associated with the oldest telemetry activity containing this error (if any).
|
||||
- **originatingContextName** Name of the oldest telemetry activity containing this error.
|
||||
- **threadId** Identifier of the thread the error occurred on.
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentService.Applicable
|
||||
|
||||
This event sends simple device connectivity and configuration data about a service on the system that helps keep Windows up to date.
|
||||
This event indicates whether a given plug-in is applicable.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **DetectedCondition** Determine whether action needs to run based on device properties.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
||||
- **IsSelfUpdateEnabledInOneSettings** Indicates if self update is enabled in One Settings.
|
||||
- **IsSelfUpdateNeeded** Indicates if self update is needed.
|
||||
- **PackageVersion** Current package version of Remediation.
|
||||
@ -3392,13 +3651,13 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.SedimentService.Completed
|
||||
|
||||
This event sends simple device connectivity and configuration data about a service on the system that helps keep Windows up to date.
|
||||
This event indicates whether a given plug-in has completed its work.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CV** Correlation vector.
|
||||
- **FailedReasons** List of reasons when the plugin action failed.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events.
|
||||
- **GlobalEventCounter** Client side counter which indicates ordering of events sent by this user.
|
||||
- **PackageVersion** Current package version of Remediation.
|
||||
- **PluginName** Name of the plugin specified for each generic plugin event.
|
||||
- **Result** This is the HRESULT for detection or perform action phases of the plugin.
|
||||
@ -3412,9 +3671,40 @@ The following fields are available:
|
||||
- **SedimentServiceTotalIterations** Number of 5 second iterations service will wait before running again.
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentService.Error
|
||||
|
||||
This event indicates whether an error condition occurred in the plug-in.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **HResult** This is the HRESULT for detection or perform action phases of the plugin.
|
||||
- **Message** Custom message associated with the failure (if any).
|
||||
- **PackageVersion** Current package version of Remediation.
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentService.FallbackError
|
||||
|
||||
This event indicates whether an error occurred for a fallback in the plug-in.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **s0** Event returned when an error occurs for a fallback in the plugin. See [Microsoft.Windows.SedimentService.wilResult](#microsoftwindowssedimentservicewilresult).
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentService.Information
|
||||
|
||||
This event provides general information returned from the plug-in.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **HResult** This is the HRESULT for detection or perform action phases of the plugin.
|
||||
- **Message** Custom message associated with the failure (if any).
|
||||
- **PackageVersion** Current package version of Remediation.
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentService.Started
|
||||
|
||||
This event sends simple device connectivity and configuration data about a service on the system that helps keep Windows up to date.
|
||||
This event indicates a specified plug-in has started. This information helps ensure Windows is up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -3425,6 +3715,31 @@ The following fields are available:
|
||||
- **Result** This is the HRESULT for Detection or Perform Action phases of the plugin.
|
||||
|
||||
|
||||
### Microsoft.Windows.SedimentService.wilResult
|
||||
|
||||
This event provides the result from the Windows internal library.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **callContext** List of telemetry activities containing this error.
|
||||
- **currentContextId** Identifier for the newest telemetry activity containing this error.
|
||||
- **currentContextMessage** Custom message associated with the newest telemetry activity containing this error (if any).
|
||||
- **currentContextName** Name of the newest telemetry activity containing this error.
|
||||
- **failureCount** Number of failures seen within the binary where the error occurred.
|
||||
- **failureId** Identifier assigned to this failure.
|
||||
- **failureType** Indicates what type of failure was observed (exception, returned error, logged error or fail fast).
|
||||
- **fileName** Source code file name where the error occurred.
|
||||
- **function** Name of the function where the error occurred.
|
||||
- **hresult** Failure error code.
|
||||
- **lineNumber** Line number within the source code file where the error occurred.
|
||||
- **message** Custom message associated with the failure (if any).
|
||||
- **module** Name of the binary where the error occurred.
|
||||
- **originatingContextId** Identifier for the oldest telemetry activity containing this error.
|
||||
- **originatingContextMessage** Custom message associated with the oldest telemetry activity containing this error (if any).
|
||||
- **originatingContextName** Name of the oldest telemetry activity containing this error.
|
||||
- **threadId** Identifier of the thread the error occurred on.
|
||||
|
||||
|
||||
## Setup events
|
||||
|
||||
### SetupPlatformTel.SetupPlatformTelActivityEvent
|
||||
@ -3719,7 +4034,7 @@ The following fields are available:
|
||||
- **RelatedCV** The previous Correlation Vector that was used before swapping with a new one
|
||||
- **RepeatFailFlag** Indicates whether this specific piece of content had previously failed to download.
|
||||
- **RevisionNumber** Identifies the revision number of this specific piece of content.
|
||||
- **ServiceGuid** An ID which represents which service the software distribution client is installing content for (Windows Update, Windows Store, etc.).
|
||||
- **ServiceGuid** An ID which represents which service the software distribution client is installing content for (Windows Update, Microsoft Store, etc.).
|
||||
- **Setup360Phase** If the download is for an operating system upgrade, this datapoint indicates which phase of the upgrade is underway.
|
||||
- **ShippingMobileOperator** The mobile operator that a device shipped on.
|
||||
- **StatusCode** Indicates the result of a Download event (success, cancellation, failure code HResult).
|
||||
@ -3762,6 +4077,30 @@ The following fields are available:
|
||||
- **WUDeviceID** The unique identifier of a specific device, used to identify how many devices are encountering success or a particular issue
|
||||
|
||||
|
||||
### SoftwareUpdateClientTelemetry.DownloadHeartbeat
|
||||
|
||||
This event allows tracking of ongoing downloads and contains data to explain the current state of the download
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **BundleID** Identifier associated with the specific content bundle. If this value is found, it shouldn't report as all zeros
|
||||
- **BytesTotal** Total bytes to transfer for this content
|
||||
- **BytesTransferred** Total bytes transferred for this content at the time of heartbeat
|
||||
- **ConnectionStatus** Indicates the connectivity state of the device at the time of heartbeat
|
||||
- **CurrentError** Last (transient) error encountered by the active download
|
||||
- **DownloadFlags** Flags indicating if power state is ignored
|
||||
- **DownloadState** Current state of the active download for this content (queued, suspended, or progressing)
|
||||
- **IsNetworkMetered** Indicates whether Windows considered the current network to be ?metered"
|
||||
- **MOAppDownloadLimit** Mobile operator cap on size of application downloads, if any
|
||||
- **MOUpdateDownloadLimit** Mobile operator cap on size of operating system update downloads, if any
|
||||
- **PowerState** Indicates the power state of the device at the time of heartbeart (DC, AC, Battery Saver, or Connected Standby)
|
||||
- **RelatedCV** The previous correlation vector that was used by the client, before swapping with a new one
|
||||
- **ResumeCount** Number of times this active download has resumed from a suspended state
|
||||
- **ServiceID** Identifier for the service to which the software distribution client is connecting (Windows Update, Microsoft Store, etc)
|
||||
- **SuspendCount** Number of times this active download has entered a suspended state
|
||||
- **SuspendReason** Last reason for why this active download entered a suspended state
|
||||
|
||||
|
||||
### SoftwareUpdateClientTelemetry.Install
|
||||
|
||||
This event sends tracking data about the software distribution client installation of the content for that update, to help keep Windows up to date.
|
||||
@ -3891,7 +4230,7 @@ The following fields are available:
|
||||
- **RawValidityWindowInDays** The raw unparsed validity window string in days of the timestamp token. This field is null if not applicable.
|
||||
- **RevisionId** The revision ID for a specific piece of content.
|
||||
- **RevisionNumber** The revision number for a specific piece of content.
|
||||
- **ServiceGuid** Identifies the service to which the software distribution client is connected, Example: Windows Update or Windows Store
|
||||
- **ServiceGuid** Identifies the service to which the software distribution client is connected, Example: Windows Update or Microsoft Store
|
||||
- **SHA256OfLeafCerData** A base64 encoding of the hash for the Base64CerData in the FragmentSigning data of the leaf certificate.
|
||||
- **SHA256OfLeafCertPublicKey** A base64 encoding of the hash of the Base64CertData in the FragmentSigning data of the leaf certificate.
|
||||
- **SHA256OfTimestampToken** A base64-encoded string of hash of the timestamp token blob.
|
||||
@ -4296,9 +4635,9 @@ The following fields are available:
|
||||
- **Setup360Extended** Detailed information about the phase or 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 is used to diagnose errors.
|
||||
- **Setup360Scenario** The Setup360 flow type. Example: Boot, Media, Update, MCT.
|
||||
- **Setup360Scenario** The Setup360 flow type. Example: Boot, Media, Update, MCT
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of target OS).
|
||||
- **State** Exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled
|
||||
- **State** Exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
- **TestId** ID that uniquely identifies a group of events.
|
||||
- **WuId** Windows Update client ID.
|
||||
|
||||
@ -4460,7 +4799,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.
|
||||
@ -4488,6 +4827,45 @@ The following fields are available:
|
||||
- **ReportId** WER Report Id associated with this bug check (used for finding the corresponding report archive in Watson).
|
||||
|
||||
|
||||
### WerTraceloggingProvider.AppCrashEvent
|
||||
|
||||
This event sends data about crashes for both native and managed applications, to help keep Windows up to date. The data includes information about the crashing process and a summary of its exception record.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **AppName** The name of the app that crashed.
|
||||
- **AppSessionGuid** The unique ID used as a correlation vector for process instances in the telemetry backend.
|
||||
- **AppTimeStamp** The date time stamp of the app.
|
||||
- **AppVersion** The version of the app that crashed.
|
||||
- **ExceptionCode** The exception code returned by the process that crashed.
|
||||
- **ExceptionOffset** The address where the exception occurred.
|
||||
- **Flags** Flags indicating how reporting is done. For example, queue the report, do not offer JIT debugging, do not terminate the process after reporting.
|
||||
- **ModName** The module name of the process that crashed.
|
||||
- **ModTimeStamp** The date time stamp of the module.
|
||||
- **ModVersion** The module version of the process that crashed.
|
||||
- **PackageFullName** The package name if the crashing application is packaged.
|
||||
- **PackageRelativeAppId** The relative application ID if the crashing application is packaged.
|
||||
- **ProcessArchitecture** The architecture of the system.
|
||||
- **ProcessCreateTime** The time of creation of the process that crashed.
|
||||
- **ProcessId** The ID of the process that crashed.
|
||||
- **ReportId** A unique ID used to identify the report. This can be used to track the report.
|
||||
- **TargetAppId** The target app ID.
|
||||
- **TargetAppVer** The target app version.
|
||||
|
||||
|
||||
## Windows Phone events
|
||||
|
||||
### Microsoft.Windows.Phone.Telemetry.OnBoot.RebootReason
|
||||
|
||||
This event lists the reboot reason when an app is going to reboot.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **BootId** The boot ID.
|
||||
- **BoottimeSinceLastShutdown** The boot time since the last shutdown.
|
||||
- **RebootReason** Reason for the reboot.
|
||||
|
||||
|
||||
## Windows Store events
|
||||
|
||||
### Microsoft.Windows.Store.Partner.ReportApplication
|
||||
@ -4496,6 +4874,17 @@ Report application event for Windows Store client.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Store.StoreActivating
|
||||
|
||||
This event sends tracking data about when the Store app activation via protocol URI is in progress, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **correlationVectorRoot** Identifies multiple events within a session/sequence. Initial value before incrementation or extension.
|
||||
- **protocolUri** Protocol URI used to activate the store.
|
||||
- **reason** The reason for activating the store.
|
||||
|
||||
|
||||
### Microsoft.Windows.StoreAgent.Telemetry.AbortedInstallation
|
||||
|
||||
This event is sent when an installation or update is canceled by a user or the system and is used to help keep Windows Apps up to date and secure.
|
||||
@ -4519,7 +4908,7 @@ The following fields are available:
|
||||
- **ProductId** The identity of the package or packages being installed.
|
||||
- **SystemAttemptNumber** The total number of automatic attempts at installation before it was canceled.
|
||||
- **UserAttemptNumber** The total number of user attempts at installation before it was canceled.
|
||||
- **WUContentId** Licensing identity of this package.
|
||||
- **WUContentId** The Windows Update content ID.
|
||||
|
||||
|
||||
### Microsoft.Windows.StoreAgent.Telemetry.BeginGetInstalledContentIds
|
||||
@ -5275,7 +5664,7 @@ The following fields are available:
|
||||
- **EventPublishedTime** Time when this event was generated.
|
||||
- **flightID** The specific ID of the Windows Insider build.
|
||||
- **revisionNumber** Update revision number.
|
||||
- **updateId** Unique Update ID.
|
||||
- **updateId** Unique Windows Update ID.
|
||||
- **updateScenarioType** Update session type.
|
||||
- **UpdateStatus** Last status of update.
|
||||
- **wuDeviceid** Unique Device ID.
|
||||
@ -5470,6 +5859,19 @@ The following fields are available:
|
||||
- **wuDeviceid** The ID of the device in which the error occurred.
|
||||
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.USODiagnostics
|
||||
|
||||
This event sends data on whether the state of the update attempt, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **errorCode** result showing success or failure of current update
|
||||
- **revisionNumber** Unique revision number of the Update
|
||||
- **updateId** Unique ID for Update
|
||||
- **updateState** Progress within an update state
|
||||
- **wuDeviceid** Unique ID for Device
|
||||
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.UsoSession
|
||||
|
||||
This event represents the state of the USO service at start and completion.
|
||||
@ -5598,4 +6000,41 @@ This event signals the completion of the setup process. It happens only once dur
|
||||
|
||||
|
||||
|
||||
## XBOX events
|
||||
|
||||
### Microsoft.Xbox.XamTelemetry.AppActivationError
|
||||
|
||||
This event indicates whether the system detected an activation error in the app.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ActivationUri** Activation URI (Uniform Resource Identifier) used in the attempt to activate the app.
|
||||
- **AppId** The Xbox LIVE Title ID.
|
||||
- **AppUserModelId** The AUMID (Application User Model ID) of the app to activate.
|
||||
- **Result** The HResult error.
|
||||
- **UserId** The Xbox LIVE User ID (XUID).
|
||||
|
||||
|
||||
### Microsoft.Xbox.XamTelemetry.AppActivity
|
||||
|
||||
This event is triggered whenever the current app state is changed by: launch, switch, terminate, snap, etc.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **AppActionId** The ID of the application action.
|
||||
- **AppCurrentVisibilityState** The ID of the current application visibility state.
|
||||
- **AppId** The Xbox LIVE Title ID of the app.
|
||||
- **AppPackageFullName** The full name of the application package.
|
||||
- **AppPreviousVisibilityState** The ID of the previous application visibility state.
|
||||
- **AppSessionId** The application session ID.
|
||||
- **AppType** The type ID of the application (AppType_NotKnown, AppType_Era, AppType_Sra, AppType_Uwa).
|
||||
- **BCACode** The BCA (Burst Cutting Area) mark code of the optical disc used to launch the application.
|
||||
- **DurationMs** The amount of time (in milliseconds) since the last application state transition.
|
||||
- **IsTrialLicense** This boolean value is TRUE if the application is on a trial license.
|
||||
- **LicenseType** The type of licensed used to authorize the app (0 - Unknown, 1 - User, 2 - Subscription, 3 - Offline, 4 - Disc).
|
||||
- **LicenseXuid** If the license type is 1 (User), this field contains the XUID (Xbox User ID) of the registered owner of the license.
|
||||
- **ProductGuid** The Xbox product GUID (Globally-Unique ID) of the application.
|
||||
- **UserId** The XUID (Xbox User ID) of the current user.
|
||||
|
||||
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -309,33 +309,6 @@ The following fields are available:
|
||||
- **isTrustletRunning:** Indicates whether an enhanced security component is currently running
|
||||
- **isVsmCfg:** Flag indicating whether virtual secure mode is configured or not
|
||||
|
||||
## Microsoft.Windows.Security.Certificates.PinRulesCaCertUsedAnalytics
|
||||
The Microsoft.Windows.Security.Certificates.Pin\*Analytics events summarize which server certificates the client encounters. By using this event with Windows Analytics, organizations can use this to determine potential scope and impact of pending certificate revocations or expirations.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **certBinary:** Binary blob of public certificate as presented to the client (does not include any private keys)
|
||||
- **certThumbprint:** Certificate thumbprint
|
||||
|
||||
## Microsoft.Windows.Security.Certificates.PinRulesCheckedAnalytics
|
||||
The Microsoft.Windows.Security.Certificates.Pin\*Analytics events summarize which server certificates the client encounters. By using this event with Windows Analytics, organizations can use this to determine potential scope and impact of pending certificate revocations or expirations.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **caThumbprints:** Intermediate certificate thumbprints
|
||||
- **rootThumbprint:** Root certificate thumbprint
|
||||
- **serverName:** Server name associated with the certificate
|
||||
- **serverThumbprint:** Server certificate thumbprint
|
||||
- **statusBits:** Certificate status
|
||||
|
||||
## Microsoft.Windows.Security.Certificates.PinRulesServerCertUsedAnalytics
|
||||
The Microsoft.Windows.Security.Certificates.Pin\*Analytics events summarize which server certificates the client encounters. By using this event with Windows Analytics, organizations can use this to determine potential scope and impact of pending certificate revocations or expirations.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **certBinary:** Binary blob of public certificate as presented to the client (does not include any private keys)
|
||||
- **certThumbprint:** Certificate thumbprint
|
||||
|
||||
## Microsoft.Windows.Security.Winlogon.SystemBootStop
|
||||
System boot has completed.
|
||||
|
||||
@ -437,5 +410,8 @@ A previous revision of this list stated that a field named PartA_UserSid was a m
|
||||
### Office events added
|
||||
In Windows 10, version 1809 (also applies to versions 1709 and 1803 starting with [KB 4462932](https://support.microsoft.com/help/4462932/windows-10-update-kb4462932) and [KB 4462933](https://support.microsoft.com/help/4462933/windows-10-update-kb4462933) respectively), 16 events were added, describing Office app launch and availability. These events were added to improve the precision of Office data in Windows Analytics.
|
||||
|
||||
### CertAnalytics events removed
|
||||
In Windows 10, version 1809 (also applies to versions 1709 and 1803 starting with [KB 4462932](https://support.microsoft.com/help/4462932/windows-10-update-kb4462932) and [KB 4462933](https://support.microsoft.com/help/4462933/windows-10-update-kb4462933) respectively), 3 "CertAnalytics" events were removed, as they are no longer required for Windows Analytics.
|
||||
|
||||
>[!NOTE]
|
||||
>You can use the Windows Diagnostic Data Viewer to observe and review events and their fields as described in this topic.
|
||||
|
||||
@ -10,7 +10,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 11/02/2018
|
||||
ms.date: 12/14/2018
|
||||
---
|
||||
|
||||
# Onboard servers to the Windows Defender ATP service
|
||||
@ -109,7 +109,15 @@ Agent Resource | Ports
|
||||
| winatp-gw-aue.microsoft.com |443 |
|
||||
|
||||
## Windows Server, version 1803 and Windows Server 2019
|
||||
To onboard Windows Server, version 1803 or Windows Server 2019, use the same method used when onboarding Windows 10 machines. For more information, see [Onboard Windows 10 machines](configure-endpoints-windows-defender-advanced-threat-protection.md). Support for Windows Server, version 1803 and Windows 2019 provides deeper insight into activities happening on the server, coverage for kernel and memory attack detection, and enables response actions on Windows Server endpoint as well.
|
||||
To onboard Windows Server, version 1803 or Windows Server 2019, use the same method used when onboarding Windows 10 machines.
|
||||
|
||||
Supported tools include:
|
||||
- Local script
|
||||
- Group Policy
|
||||
- System Center Configuration Manager 2012 / 2012 R2 1511 / 1602
|
||||
- VDI onboarding scripts for non-persistent machines
|
||||
|
||||
For more information, see [Onboard Windows 10 machines](configure-endpoints-windows-defender-advanced-threat-protection.md). Support for Windows Server, version 1803 and Windows 2019 provides deeper insight into activities happening on the server, coverage for kernel and memory attack detection, and enables response actions on Windows Server endpoint as well.
|
||||
|
||||
1. Configure Windows Defender ATP onboarding settings on the server. For more information, see [Onboard Windows 10 machines](configure-endpoints-windows-defender-advanced-threat-protection.md).
|
||||
|
||||
|
||||
@ -58,9 +58,6 @@ Review the following details to verify minimum system requirements:
|
||||
>Only applicable for Windows 7 SP1 Enterprise and Windows 7 SP1 Pro.
|
||||
|
||||
- Install the [Update for customer experience and diagnostic telemetry](https://support.microsoft.com/help/3080149/update-for-customer-experience-and-diagnostic-telemetry)
|
||||
|
||||
>[!NOTE]
|
||||
>Only applicable for Windows 7 SP1 Enterprise and Windows 7 SP1 Pro.
|
||||
|
||||
- Install either [.NET framework 4.5](https://www.microsoft.com/en-us/download/details.aspx?id=30653) (or later) or [KB3154518](https://support.microsoft.com/help/3154518/support-for-tls-system-default-versions-included-in-the-net-framework)
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user