mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-15 14:57:23 +00:00
Merged PR 14473: From master
This commit is contained in:
Dolcita Montemayor
commit
e47ccadcaf
@ -1,11 +1,6 @@
|
||||
{
|
||||
"redirections": [
|
||||
{
|
||||
"source_path": "windows/deployment/update/waas-servicing-differences.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/deployment/update/windows-as-a-service",
|
||||
"redirect_document_id": true
|
||||
},
|
||||
{
|
||||
"source_path": "windows/application-management/msix-app-packaging-tool-walkthrough.md",
|
||||
"redirect_url": "https://docs.microsoft.com/windows/msix/mpt-overview",
|
||||
"redirect_document_id": true
|
||||
|
||||
@ -20,8 +20,8 @@ ms.date: 07/27/2017
|
||||
|
||||
Use Internet Explorer to collect data on computers running Windows Internet Explorer 8 through Internet Explorer 11 on Windows 10, Windows 8.1, or Windows 7. This inventory information helps you build a list of websites used by your company so you can make more informed decisions about your IE deployments, including figuring out which sites might be at risk or require overhauls during future upgrades.
|
||||
|
||||
>**Upgrade Analytics and Windows upgrades**<br>
|
||||
>You can use Upgrade Analytics to help manage your Windows 10 upgrades on devices running Windows 8.1 and Windows 7 (SP1). You can also use Upgrade Analytics to review several site discovery reports. Check out Upgrade Analytics from [here](https://technet.microsoft.com/itpro/windows/deploy/upgrade-analytics-get-started).
|
||||
>**Upgrade Readiness and Windows upgrades**<br>
|
||||
>You can use Upgrade Readiness to help manage your Windows 10 upgrades on devices running Windows 8.1 and Windows 7 (SP1). You can also use Upgrade Readiness to review several site discovery reports. For more information, see [Manage Windows upgrades with Upgrade Readiness](https://docs.microsoft.com/en-us/windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness).
|
||||
|
||||
|
||||
## Before you begin
|
||||
|
||||
@ -335,9 +335,11 @@ This is what happens when you choose an option.
|
||||
|
||||
- **Use Microsoft Azure Active Directory**
|
||||
|
||||
Clicking this option allows you to join the device to Azure AD. Once you click **Next**, the device will restart to apply some settings, and then you’ll be taken to the [Use Microsoft Azure Active Directory](#use-microsoft-azure) page and asked to enter credentials that can allow you to join Azure AD. After joining, admins from the joined organization will be able to use the Settings app. The specific people that will be allowed depends on your Azure AD subscription and how you’ve configured the settings for your Azure AD organization.
|
||||
Clicking this option allows you to join the device to Azure AD. Once you click **Next**, the device will restart to apply some settings, and then you’ll be taken to the [Use Microsoft Azure Active Directory](#use-microsoft-azure) page and asked to enter credentials that can allow you to join Azure AD. Members of the Azure Global Admins security group from the joined organization will be able to use the Settings app. The specific people that will be allowed depends on your Azure AD subscription and how you’ve configured the settings for your Azure AD organization.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Administrators added to the Azure Global Admins group after you join the device to Azure AD will be unable to use the Settings app.
|
||||
>
|
||||
>If you join Surface Hub to Azure AD during first-run setup, single sign-on (SSO) for Office apps will not work properly. Users will have to sign in to each Office app individually.
|
||||
|
||||
- **Use Active Directory Domain Services**
|
||||
|
||||
@ -18,7 +18,7 @@ ms.topic: article
|
||||
|
||||
This article provides a list of the available downloads for Surface devices and links to download the drivers and firmware for your device.
|
||||
|
||||
As easy as it is to keep Surface device drivers and firmware up to date automatically with Windows Update, it is sometimes necessary to download and install updates manually, such as during a Windows deployment. For any situation where you need to install drivers and firmware separately from Windows Update, you can find the files available for download at the Microsoft Download Center.
|
||||
Although Surface devices are typically automatically updated with the latest device drivers and firmware via Windows Update, sometimes it's necessary to download and install updates manually, such as during a Windows deployment. If you need to install drivers and firmware separately from Windows Update, you can find the requisite files on the Microsoft Download Center.
|
||||
|
||||
On the Microsoft Download Center page for your device, you will find several files available. These files allow you to deploy drivers and firmware in various ways. You can read more about the different deployment methods for Surface drivers and firmware in [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md).
|
||||
|
||||
@ -27,31 +27,29 @@ Driver and firmware updates for Surface devices are **cumulative updates** which
|
||||
Installation files for administrative tools, drivers for accessories, and updates for Windows are also available for some devices and are detailed here in this article.
|
||||
|
||||
>[!NOTE]
|
||||
>To simplify the process of locating drivers for your device, downloads for Surface devices have been reorganized to separate pages for each model. Bookmark the Microsoft Download Center page for your device from the links provided on this page. Many of the filenames contain a placeholder denoted with *xxxxxx*, which identifies the current version number or date of the file.
|
||||
|
||||
|
||||
Recent additions to the downloads for Surface devices provide you with options to install Windows 10 on your Surface devices and update LTE devices with the latest Windows 10 drivers and firmware.
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>A battery charge of 40% or greater is required before you install firmware to a Surface device. See [Microsoft Support article KB2909710](https://go.microsoft.com/fwlink/p/?LinkId=618106) for more information.
|
||||
>Many of the filenames contain a placeholder denoted with *xxxxxx*, representing the latest version number listed in the Microsoft Download Center. A battery charge of 40 percent or greater is required before you install firmware to a Surface device. See [Microsoft Support article KB2909710](https://go.microsoft.com/fwlink/p/?LinkId=618106) for more information.
|
||||
|
||||
## Surface Laptop 2
|
||||
|
||||
Download the following updates for [Surface Laptop 2 from the Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=57515).
|
||||
* SurfaceLaptop2_Win10_XXXXX_XXXXXXX_X.msi – Cumulative firmware and driver update package for Windows 10
|
||||
* SurfaceLaptop2_Win10_xxxxx_xxxxxxx_x.msi – Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
## Surface Pro 6
|
||||
|
||||
Download the following updates for [Surface Pro 6 from the Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=57514).
|
||||
|
||||
* SurfacePro6_Win10_XXXXX_XXXXXXX_X.msi – Cumulative firmware and driver update package for Windows 10
|
||||
* SurfacePro6_Win10_xxxxx_xxxxxxx_x.msi – Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
## Surface GO
|
||||
## Surface Go
|
||||
|
||||
Download the following updates for [Surface GO from the Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=57439).
|
||||
* SurfaceGO_Win10_17134_1802010_6.msi - Cumulative firmware and driver update package for Windows 10
|
||||
Download the following updates for [Surface Go from the Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=57439).
|
||||
* SurfaceGO_Win10_xxxxx_xxxxxxx_x.msi - Cumulative firmware and driver update package for Windows 10
|
||||
|
||||
## Surface Go with LTE Advanced
|
||||
|
||||
Download the following updates for [Surface Go with LTE Advanced from the Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=57601).
|
||||
|
||||
* SurfaceGo_Win10_xxxxx_xxxxxxx_LTE_1.msi - Cumulative firmware and driver update package for Windows 10 including optional WinTab drivers.
|
||||
|
||||
## Surface Book 2
|
||||
|
||||
@ -79,7 +77,7 @@ Download the following updates for [Surface Pro with LTE Advanced from the Micro
|
||||
|
||||
Download the following updates for [Surface Pro 6 from the Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=57514).
|
||||
|
||||
* SurfacePro6_Win10_17134_xxxxx_xxxxxx.msi
|
||||
* SurfacePro6_Win10_xxxxx_xxxxxxx_x.msi
|
||||
|
||||
## Surface Studio
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 12 KiB |
@ -2785,7 +2785,7 @@ ADMX Info:
|
||||
Supported values:
|
||||
|
||||
- Blank (default) - Load the pages specified in App settings as the default Start pages.
|
||||
- String - Enter the URLs of the pages you want to load as the Start pages, separating each page using angle brackets:<p><p> \<support.contoso.com\> \<support.microsoft.com\>
|
||||
- String - Enter the URLs of the pages you want to load as the Start pages, separating each page using angle brackets and comma:<p><p> \<support.contoso.com\>,\<support.microsoft.com\>
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--/Policy-->
|
||||
|
||||
@ -442,13 +442,6 @@ To verify the policy is applied, check C:\windows\INF\setupapi.dev.log and see i
|
||||
<<< Section end 2018/11/15 12:26:41.751
|
||||
<<< [Exit status: SUCCESS]
|
||||
```
|
||||
|
||||
Windows Defender ATP also blocks installation and usage of prohibited peripherals by using a custom profile in Intune.
|
||||
|
||||
For example, this custom profile blocks installation and usage of USB devices with hardware IDs "USBSTOR\DiskVendorCo" and "USBSTOR\DiskSanDisk_Cruzer_Glide_3.0", and applies to USB devices with matching hardware IDs that are already installed.
|
||||
|
||||
|
||||
|
||||
<hr/>
|
||||
|
||||
<!--Policy-->
|
||||
@ -546,6 +539,13 @@ To verify the policy is applied, check C:\windows\INF\setupapi.dev.log and see i
|
||||
<<< [Exit status: SUCCESS]
|
||||
```
|
||||
|
||||
Windows Defender ATP also blocks installation and usage of prohibited peripherals by using a custom profile in Intune.
|
||||
|
||||
For example, this custom profile blocks installation and usage of USB devices with hardware IDs "USB\Composite" and "USB\Class_FF", and applies to USB devices with matching hardware IDs that are already installed.
|
||||
|
||||
|
||||
|
||||
|
||||
<!--Policy-->
|
||||
<a href="" id="deviceinstallation-preventinstallationofmatchingdevicesetupclasses"></a>**DeviceInstallation/PreventInstallationOfMatchingDeviceSetupClasses**
|
||||
|
||||
|
||||
@ -288,7 +288,7 @@ The following list shows the supported values:
|
||||
|
||||
<!--/Scope-->
|
||||
<!--Description-->
|
||||
Determines the type of PIN or password required. This policy only applies if the **DeviceLock/DevicePasswordEnabled** policy is set to 0 (required).
|
||||
Determines the type of PIN required. This policy only applies if the **DeviceLock/DevicePasswordEnabled** policy is set to 0 (required).
|
||||
|
||||
> [!NOTE]
|
||||
> This policy must be wrapped in an Atomic command.
|
||||
@ -306,9 +306,9 @@ Determines the type of PIN or password required. This policy only applies if the
|
||||
<!--SupportedValues-->
|
||||
The following list shows the supported values:
|
||||
|
||||
- 0 – Alphanumeric PIN or password required.
|
||||
- 1 – Numeric PIN or password required.
|
||||
- 2 (default) – Users can choose: Numeric PIN or password, or Alphanumeric PIN or password.
|
||||
- 0 – Password or Alphanumeric PIN required.
|
||||
- 1 – Password or Numeric PIN required.
|
||||
- 2 (default) – Password, Numeric PIN, or Alphanumeric PIN required.
|
||||
|
||||
<!--/SupportedValues-->
|
||||
<!--/Policy-->
|
||||
|
||||
BIN
windows/deployment/update/images/security-only-update.png
Normal file
BIN
windows/deployment/update/images/security-only-update.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 217 KiB |
115
windows/deployment/update/waas-servicing-differences.md
Normal file
115
windows/deployment/update/waas-servicing-differences.md
Normal file
@ -0,0 +1,115 @@
|
||||
---
|
||||
title: Servicing differences between Windows 10 and older operating systems
|
||||
description: Learn the differences between servicing Windows 10 and servicing older operating systems.
|
||||
keywords: updates, servicing, current, deployment, semi-annual channel, feature, quality, rings, insider, tools
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: KarenSimWindows
|
||||
ms.localizationpriority: medium
|
||||
ms.author: karensim
|
||||
---
|
||||
# Understanding the differences between servicing Windows 10-era and legacy Windows operating systems
|
||||
|
||||
>Applies to: Windows 10
|
||||
|
||||
>**February 15, 2019: This document has been corrected and edited to reflect that security-only updates for legacy OS versions are not cumulative. They were previously identified as cumulative similar to monthly rollups, which is inaccurate.**
|
||||
|
||||
Today, many enterprise customers have a mix of modern and legacy client and server operating systems. Managing the servicing and updating differences between those legacy operating systems and Windows 10 versions adds a level of complexity that is not well understood. This can be confusing. With the end of support for legacy [Windows 7 SP1](https://support.microsoft.com/help/4057281/windows-7-support-will-end-on-january-14-2020) and Windows Server 2008 R2 variants on January 14, 2020, System Administrators have a critical need critical to understand how best to leverage a modern workplace to support system updates.
|
||||
|
||||
The following provides an initial overview of how updating client and server differs between the Windows 10-era Operating Systems (such as, Windows 10 version 1709, Windows Server 2016) and legacy operating systems (such as Windows 7, Windows 8.1, Windows Server 2008 R2, Windows Server 2012 R2).
|
||||
|
||||
>[!NOTE]
|
||||
>A note on naming convention in this article: For brevity, "Windows 10" refers to all operating systems across client, server and IoT released since July 2015, while "legacy" refers to all operating systems prior to that period for client and server, including Windows 7, Window 8.1, Windows Server 2008 R2, Windows Server 2012 R2, etc.
|
||||
|
||||
## Infinite fragmentation
|
||||
Prior to Windows 10, all updates to operating system (OS) components were published individually. On "Update Tuesday," customers would pick and choose individual updates they wanted to apply. Most chose to update security fixes, while far fewer selected non-security fixes, updated drivers, or installed .NET Framework updates.
|
||||
|
||||
As a result, each environment within the global Windows ecosystem that had only a subset of security and non-security fixes installed had a different set of binaries and behaviors than those that consistently installed every available update as tested by Microsoft.
|
||||
|
||||
This resulted in a fragmented ecosystem that created diverse challenges in predictively testing interoperability, resulting in high update failure rates - which were subsequently mitigated by customers removing individual updates that were causing issues. Each customer that selectively removed individual updates amplified this fragmentation by creating more diverse environment permutations across the ecosystem. As an IT Administrator once quipped, "If you’ve seen one Windows 7 PC, you have seen one Windows 7 PC," suggesting no consistency or predictability across more than 250M commercial devices at the time.
|
||||
|
||||
## Windows 10 – Next generation
|
||||
Windows 10 provided an opportunity to end the era of infinite fragmentation. With Windows 10 and the Windows as a service model, updates came rolled together in the "latest cumulative update" (LCU) packages for both client and server. Every new update published includes all changes from previous updates, as well as new fixes. Since Windows client and server share the same code base, these LCUs allow the same update to be installed on the same client and server OS family, further reducing fragmentation.
|
||||
|
||||
This helps simplify servicing. Devices with the original Release to Market (RTM) version of a feature release installed could get up to date by installing the most recent LCU.
|
||||
|
||||
Windows publishes the new LCU packages for each Windows 10 version (1607, 1709, etc.) on the second Tuesday of each month. This package is classified as a required security update and contains contents from the previous LCU as well as new security, non-security and Internet Explorer 11 (IE11) fixes. The security classification, by definition, requires a reboot of the device to complete installation of the update.
|
||||
|
||||
|
||||
|
||||
*Figure 1.0 - High level cumulative update model*
|
||||
|
||||
Another benefit of the LCU model is fewer steps. Devices that have the original Release to Market (RTM) version of a release can install the most recent LCU to get up to date in one step, rather than having to install multiple updates with reboots after each.
|
||||
|
||||
This cumulative update model for Windows 10 has helped provide the Windows ecosystem with consistent update experiences that can be predicted by baseline testing before release. Even with highly complex updates with hundreds of fixes, the number of incidents with monthly security updates for Windows 10 have fallen month over month since the initial release of Windows 10.
|
||||
|
||||
### Points to consider
|
||||
|
||||
- Windows 10 does not have the concept of a Security-Only or Monthly Rollup for updates. All updates are an LCU package, which includes the last release plus anything new.
|
||||
- Windows 10 no longer has the concept of a "hotfix" since all individual updates must be rolled into the cumulative packages. (Note: Any private fix is offered for customer validation only, and then rolled into an LCU.)
|
||||
- [Updates for the .NET Framework](https://blogs.msdn.microsoft.com/dotnet/2016/10/11/net-framework-monthly-rollups-explained/) are NOT included in the Windows 10 LCU. They are separate packages with different behaviors depending on the version of .NET Framework being updated, and on which OS. As of October 2018, .NET Framework updates for Windows 10 will be separate and have their own cumulative update model.
|
||||
- For Windows 10, available update types vary by publishing channel:
|
||||
- For customers using Windows Server Update Services (WSUS) and for the Update Catalog, several different updates types for Windows 10 are rolled together for the core OS in a single LCU package, with exception of Servicing Stack Updates.
|
||||
- Servicing Stack Updates (SSU) are available for download from the Update Catalog and can be imported through WSUS, but will not be automatically synced. (See this example for Windows 10, version 1709) For more information on Servicing Stack Updates, please see this blog.
|
||||
- For customers connecting to Windows Update, the new cloud update architecture uses a database of updates which break out all the different update types, including Servicing Stack Updates (SSU) and Dynamic Updates (DU). The update scanning in the Windows 10 servicing stack on the client automatically takes only the updates that are needed by the device to be completely up to date.
|
||||
- Windows 7 and other legacy operating systems have cumulative updates that operate differently than in Windows 10 (see next section).
|
||||
|
||||
## Windows 7 and legacy OS versions
|
||||
While Windows 10 updates could have been controlled as cumulative from "Day 1," the legacy OS ecosystem for both client and server was highly fragmented. Recognizing the challenges of update quality in a fragmented environment, we moved Windows 7 to a cumulative update model in October 2016.
|
||||
|
||||
Customers saw the LCU model used for Windows 10 as having packages that were too large and represented too much of a change for legacy operating systems, so a different model was implemented. Windows instead offered one cumulative package (Monthly Rollup) and one individual package (Security Only) for all legacy operating systems.
|
||||
|
||||
The Monthly Rollup includes new non-security (if appropriate), security updates, Internet Explorer (IE) updates, and all updates from the previous month similar to the Windows 10 model. The Security-only package includes only new security updates for the month. This means that any security updates from any previous month are not included in current month’s Security-Only Package. If a Security-Only update is missed, it is missed. Those updates will not appear in a future Security-Only update. Additionally, a cumulative package is offered for IE, which can be tested and installed separately, reducing the total update package size. The IE cumulative update includes both security and non-security fixes following the same model as Windows 10.
|
||||
|
||||
|
||||
*Figure 2.0 - Legacy OS security-only update model*
|
||||
|
||||
Moving to the cumulative model for legacy OS versions continues to improve predictability of update quality. The Windows legacy environments which have fully updated machines with Monthly Rollups are running the same baseline against which all legacy OS version updates are tested. These include all of the updates (security and non-security) prior to and after October 2016. Many customer environments do not have all updates prior to this change installed, which leaves some continued fragmentation in the ecosystem. Further, customers who are installing Security-Only Updates and potentially doing so inconsistently are also more fragmented than Microsoft’s test environments for legacy OS version. This remaining fragmentation results in issues like those seen when the September 2016 Servicing Stack Update (SSU) was needed for smooth installation of the August 2018 security update. These environments did not have the SSU applied previously.
|
||||
|
||||
### Points to consider
|
||||
- Windows 7 and Windows 8 legacy operating system updates [moved from individual to cumulative in October 2016](https://techcommunity.microsoft.com/t5/Windows-Blog-Archive/More-on-Windows-7-and-Windows-8-1-servicing-changes/ba-p/166783). Devices with updates missing prior to that point are still missing those updates, as they were not included in the subsequent cumulative packages.
|
||||
- "Hotfixes" are no longer published for legacy OS versions. All updates are rolled into the appropriate package depending on their classification as either non-security, security, or Internet Explorer updates. (Note: any private fix is offered for customer validation only. Once validated they are then rolled into a Monthly Rollup or IE cumulative update, as appropriate.)
|
||||
- Both Monthly Rollups and Security-only updates released on Update Tuesday for legacy OS versions are identified as "security required" updates, because both have the full set of security updates in them. The Monthly Rollup may have additional non-security updates that are not included in the Security Only update. The "security" classification requires the device be rebooted so the update can be fully installed.
|
||||
- Given the differences between the cumulative Monthly Rollups and the single-month Security-only update packages, switching between these update types is not advised. Differences in the baselines of these packages may result in installation errors and conflicts. Choosing one and staying on that update type with high consistency – Monthly Rollup or Security-only – is recommended.
|
||||
- With all Legacy OS versions now in the Extended Support stage of their 10-year lifecycle, they typically receive only security updates for both Monthly Rollup and Security Only updates. Using Express for the Monthly Rollup results in almost the same package size as Security Only, with the added confidence of ensuring all relevant updates are installed.
|
||||
- In [February 2017](https://techcommunity.microsoft.com/t5/Windows-Blog-Archive/Simplified-servicing-for-Windows-7-and-Windows-8-1-the-latest/ba-p/166798), Windows pulled IE updates out of the legacy OS versions Security-only updates, while leaving them in the Monthly Rollup updates. This was done specifically to reduce package size based on customer feedback.
|
||||
- The IE cumulative update includes both security and non-security updates and is also needed for to help secure the entire environment. This update can be installed separately or as part of the Monthly Rollup.
|
||||
- [Updates for .NET Framework](https://blogs.msdn.microsoft.com/dotnet/2016/10/11/net-framework-monthly-rollups-explained/) are NOT included in legacy Monthly Rollup or Security Only packages. They are separate packages with different behaviors depending on the version of the .NET Framework, and which legacy OS, being updated.
|
||||
- For [Windows Server 2008 SP2](https://cloudblogs.microsoft.com/windowsserver/2018/06/12/windows-server-2008-sp2-servicing-changes/), cumulative updates began in October 2018, and follow the same model as Windows 7. Updates for IE9 are included in those packages, as the last supported version of Internet Explorer for that Legacy OS version.
|
||||
|
||||
## Public preview releases
|
||||
Lastly, the cumulative update model directly impacts the public Preview releases offered in the 3rd and/or 4th weeks of the month. Update Tuesday, also referred to as the "B" week release occurs on the second Tuesday of the month. It is always a required security update across all operating systems. In addition to this monthly release, Windows also releases non-security update "previews" targeting the 3rd (C) and the 4th (D) weeks of the month. These preview releases include that month’s B-release plus a set of non-security updates for testing and validation as a cumulative package. We recommend IT Administrators uses the C/D previews to test the update in their environments. Any issues identified with the updates in the C/D releases are identified and then fixed or removed, prior to being rolled up in to the next month’s B release package together with new security updates. Security-only Packages are not part of the C/D preview program.
|
||||
|
||||
### Examples
|
||||
Windows 10 version 1709:
|
||||
- (9B) September 11, 2018 Update Tuesday / B release - includes security, non-security and IE update. This update is categorized as "Required, Security" it requires a system reboot.
|
||||
- (9C) September 26, 2018 Preview C release - includes everything from 9B PLUS some non-security updates for testing/validation. This update is qualified as not required, non-security. No system reboot is required.
|
||||
- (10B) October 9, 2018 Update Tuesday / B release includes all fixes included in 9B, all fixes in 9C and introduces new security fixes and IE updates. This update is qualified as "Required, Security" and requires a system reboot.
|
||||
All of these updates are cumulative and build on each other for Windows 10. This is in contrast to legacy OS versions, where the 9C release becomes part of the "Monthly Rollup," but not the "Security Only" update. In other words, a Window 7 SP1 9C update is part of the cumulative "Monthly Rollup" but not included in the "Security Only" update because the fixes are qualified as "non-security". This is an important variation to note on the two models.
|
||||
|
||||
|
||||
*Figure 3.0 - Preview releases within the Windows 10 LCU model*
|
||||
|
||||
## Previews vs. on-demand releases
|
||||
In 2018, we experienced incidents which required urgent remediation that didn’t map to the monthly update release cadence. These incidents were situations that required an immediate fix to an Update Tuesday release. While Windows engineering worked aggressively to respond within a week of the B-release, these "on-demand" releases created confusion with the C Preview releases.
|
||||
|
||||
As a general policy, if a Security-Only package has a regression, which is defined as an unintentional error in the code of an update, then the fix for that regression will be added to the next month’s Security-Only Update. The fix for that regression may also be offered as part an On-Demand release and will be rolled into the next Monthly Update. (Note: Exceptions do exist to this policy, based on timing.)
|
||||
|
||||
### Point to consider
|
||||
- When Windows identifies an issue with a Update Tuesday release, engineering teams work to remediate or fix the issue as quickly as possible. The outcome is often a new update which may be released at any time, including during the 3rd or 4th week of the month. Such updates are independent of the regularly scheduled "C" and "D" update previews. These updates are created on-demand to remediate a customer impacting issue. In most cases they are qualified as a "non-security" update, and do not require a system reboot.
|
||||
- Rarely do incidents with Update Tuesday releases impact more than .1% of the total population. With the new Windows Update (WU) architecture, updates can be targeted to affected devices. This targeting is not available through the Update Catalog or WSUS channels, however.
|
||||
- On-demand releases address a specific issue with an Update Tuesday release and are often qualified as "non-security" for one of two reasons. First, the fix may not be an additional security fix, but a non-security change to the update. Second, the "non-security" designation allows individuals or companies to choose when and how to reboot the devices, rather than forcing a system reboot on all Windows devices receiving the update globally. This trade-off is rarely a difficult choice as it has the potential to impact customer experience across client and server, across consumer and commercial customers for more than one billion devices.
|
||||
- Because the cumulative model is used across Window 10 and legacy Windows OS versions, despite variations between these OS versions, an out of band release will include all of the changes from the Update Tuesday release plus the fix that addresses the issue. And since Windows no longer releases hotfixes, everything is cumulative in some way.
|
||||
|
||||
In closing, I hope this overview of the update model across current and legacy Windows OS versions highlights the benefits of the Windows 10 cumulative update model to help defragment the Windows ecosystem environments, simplify servicing and help make systems more secure.
|
||||
|
||||
## Resources
|
||||
- [Simplifying updates for Windows 7 and 8.1](https://techcommunity.microsoft.com/t5/Windows-Blog-Archive/Simplifying-updates-for-Windows-7-and-8-1/ba-p/166530)
|
||||
- [Further simplifying servicing models for Windows 7 and Windows 8.1](https://techcommunity.microsoft.com/t5/Windows-Blog-Archive/Further-simplifying-servicing-models-for-Windows-7-and-Windows-8/ba-p/166772)
|
||||
- [More on Windows 7 and Windows 8.1 servicing changes](https://techcommunity.microsoft.com/t5/Windows-Blog-Archive/More-on-Windows-7-and-Windows-8-1-servicing-changes/ba-p/166783)
|
||||
- [.NET Framework Monthly Rollups Explained](https://blogs.msdn.microsoft.com/dotnet/2016/10/11/net-framework-monthly-rollups-explained/)
|
||||
- [Simplified servicing for Windows 7 and Windows 8.1: the latest improvements](https://techcommunity.microsoft.com/t5/Windows-Blog-Archive/Simplified-servicing-for-Windows-7-and-Windows-8-1-the-latest/ba-p/166798)
|
||||
- [Windows Server 2008 SP2 servicing changes](https://cloudblogs.microsoft.com/windowsserver/2018/06/12/windows-server-2008-sp2-servicing-changes/)
|
||||
- [Windows 10 update servicing cadence](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-update-servicing-cadence/ba-p/222376)
|
||||
- [Windows 7 servicing stack updates: managing change and appreciating cumulative updates](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-7-servicing-stack-updates-managing-change-and/ba-p/260434)
|
||||
@ -195,7 +195,7 @@ Finally, Upgrade Readiness only collects IE site discovery data on devices that
|
||||
> IE site discovery is disabled on devices running Windows 7 and Windows 8.1 that are in Switzerland and EU countries.
|
||||
|
||||
### Device names not appearing for Windows 10 devices
|
||||
Starting with Windows 10, version 1803, the device name is no longer collected by default and requires a separate opt-in. For more information, see [Enrolling devices in Windows Analytics](windows-analytics-get-started.md).
|
||||
Starting with Windows 10, version 1803, the device name is no longer collected by default and requires a separate opt-in. For more information, see [Enrolling devices in Windows Analytics](windows-analytics-get-started.md). Allowing device names to be collected can make it easier for you to identify individual devices that report problems. Without the device name, Windows Analytics can only label devices by a GUID that it generates.
|
||||
|
||||
### Disable Upgrade Readiness
|
||||
|
||||
|
||||
@ -163,7 +163,7 @@ These policies are under Microsoft\Windows\DataCollection:
|
||||
| CommercialId | In order for your devices to show up in Windows Analytics, they must be configured with your organization’s Commercial ID. |
|
||||
| AllowTelemetry (in Windows 10) | 1 (Basic), 2 (Enhanced) or 3 (Full) diagnostic data. Windows Analytics will work with basic diagnostic data, but more features are available when you use the Enhanced level (for example, Device Health requires Enhanced diagnostic data and Upgrade Readiness only collects app usage and site discovery data on Windows 10 devices with Enhanced diagnostic data). For more information, see [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization). |
|
||||
| LimitEnhancedDiagnosticDataWindowsAnalytics (in Windows 10) | Only applies when AllowTelemetry=2. Limits the Enhanced diagnostic data events sent to Microsoft to just those needed by Windows Analytics. For more information, see [Windows 10, version 1709 enhanced diagnostic data events and fields used by Windows Analytics](https://docs.microsoft.com/windows/configuration/enhanced-diagnostic-data-windows-analytics-events-and-fields).|
|
||||
| AllowDeviceNameInTelemetry (in Windows 10) | In Windows 10, version 1803, a separate opt-in is required to enable devices to continue to send the device name. |
|
||||
| AllowDeviceNameInTelemetry (in Windows 10) | In Windows 10, version 1803, a separate opt-in is required to enable devices to continue to send the device name. Allowing device names to be collected can make it easier for you to identify individual devices that report problems. Without the device name, Windows Analytics can only label devices by a GUID that it generates. |
|
||||
| CommercialDataOptIn (in Windows 7 and Windows 8) | 1 is required for Upgrade Readiness, which is the only solution that runs on Windows 7 or Windows 8. |
|
||||
|
||||
|
||||
|
||||
@ -42,13 +42,15 @@ The latest news:
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-7-servicing-stack-updates-managing-change-and/ba-p/260434">Windows 7 Servicing Stack Updates: Managing Change and Appreciating Cumulative Updates</a> - September 21, 2018</li>
|
||||
<li><a href="https://www.microsoft.com/en-us/microsoft-365/blog/2018/09/06/helping-customers-shift-to-a-modern-desktop/">Helping customers shift to a modern desktop</a> - September 6, 2018</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-amp-Windows-Analytics-a-real-world/ba-p/242417#M228">Windows Update for Business & Windows Analytics: a real-world experience</a> - September 5, 2018</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-next-for-Windows-10-and-Windows-Server-quality-updates/ba-p/229461">What's next for Windows 10 and Windows Server quality updates</a> - August 16, 2018
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-next-for-Windows-10-and-Windows-Server-quality-updates/ba-p/229461">What's next for Windows 10 and Windows Server quality updates</a> - August 16, 2018</li>
|
||||
<li><a href="https://www.youtube-nocookie.com/watch/BwB10v55WSk">Windows 10 monthly updates</a> - August 1, 2018 (**video**)</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-update-servicing-cadence/ba-p/222376">Windows 10 update servicing cadence</a> - August 1, 2018
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-quality-updates-explained-amp-the-end-of-delta/ba-p/214426">Windows 10 quality updates explained and the end of delta updates</a> - July 11, 2018
|
||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/06/14/ai-powers-windows-10-april-2018-update-rollout/#67LrSyWdwgTyciSG.97">AI Powers Windows 10 April 2018 Update Rollout</a> - June 14, 2018
|
||||
<li><a href="https://cloudblogs.microsoft.com/windowsserver/2018/06/12/windows-server-2008-sp2-servicing-changes/">Windows Server 2008 SP2 Servicing Changes</a> - June 12, 2018
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-Enhancements-diagnostics/ba-p/201978">Windows Update for Business - Enhancements, diagnostics, configuration</a> - June 7, 2018</ul>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-update-servicing-cadence/ba-p/222376">Windows 10 update servicing cadence</a> - August 1, 2018</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-quality-updates-explained-amp-the-end-of-delta/ba-p/214426">Windows 10 quality updates explained and the end of delta updates</a> - July 11, 2018</li>
|
||||
<li><a href="https://blogs.windows.com/windowsexperience/2018/06/14/ai-powers-windows-10-april-2018-update-rollout/#67LrSyWdwgTyciSG.97">AI Powers Windows 10 April 2018 Update Rollout</a> - June 14, 2018</li>
|
||||
<li><a href="https://cloudblogs.microsoft.com/windowsserver/2018/06/12/windows-server-2008-sp2-servicing-changes/">Windows Server 2008 SP2 Servicing Changes</a> - June 12, 2018</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-Enhancements-diagnostics/ba-p/201978">Windows Update for Business - Enhancements, diagnostics, configuration</a> - June 7, 2018</li>
|
||||
<li><a href="https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-and-the-disappearing-SAC-T/ba-p/199747">Windows 10 and the “disappearing” SAC-T</a> - May 31, 2018</li>
|
||||
</ul>
|
||||
|
||||
[See more news](waas-morenews.md). You can also check out the [Windows 10 blog](https://techcommunity.microsoft.com/t5/Windows-10-Blog/bg-p/Windows10Blog).
|
||||
|
||||
|
||||
@ -103,10 +103,10 @@ If downloads through a proxy server fail with a 0x80d05001 DO_E_HTTP_BLOCKSIZE_M
|
||||
|
||||
You may choose to apply a rule to permit HTTP RANGE requests for the following URLs:
|
||||
*.download.windowsupdate.com
|
||||
*.au.windowsupdate.com
|
||||
*.tlu.dl.delivery.mp.microsoft.com
|
||||
*.dl.delivery.mp.microsoft.com
|
||||
*.emdl.ws.microsoft.com
|
||||
|
||||
If you cannot permit RANGE requests, you can configure a Group Policy or MDM Policy setting that will bypass Delivery Optimization and use BITS instead.
|
||||
If you cannot permit RANGE requests, keep in mind that this means you are downloading more content than needed in updates (as delta patching will not work).
|
||||
|
||||
|
||||
## The update is not applicable to your computer
|
||||
|
||||
@ -22,7 +22,7 @@ You can use Upgrade Readiness to plan and manage your upgrade project end-to-end
|
||||
|
||||
Before you begin, consider reviewing the following helpful information:<BR>
|
||||
- [Upgrade Readiness requirements](upgrade-readiness-requirements.md): Provides detailed requirements to use Upgrade Readiness.<BR>
|
||||
- [Upgrade Readiness blog](https://blogs.technet.microsoft.com/UpgradeAnalytics): Contains announcements of new features and provides helpful tips for using Upgrade Readiness.
|
||||
- [Upgrade Readiness blog](https://aka.ms/blog/WindowsAnalytics): Contains announcements of new features and provides helpful tips for using Upgrade Readiness.
|
||||
|
||||
>If you are using System Center Configuration Manager, also check out information about how to integrate Upgrade Readiness with Configuration Manager: [Integrate Upgrade Readiness with System Center Configuration Manager](https://docs.microsoft.com/sccm/core/clients/manage/upgrade/upgrade-analytics).
|
||||
|
||||
|
||||
@ -23,7 +23,7 @@ For a list of operating systems that qualify for the Windows 10 Pro Upgrade or W
|
||||
|
||||
The following table shows the methods and paths available to change the edition of Windows 10 that is running on your computer. **Note**: The reboot requirement for upgrading from Pro to Enterprise was removed in version 1607.
|
||||
|
||||
Note: Although it isn't displayed yet in the table, edition upgrade is also possible using [edition upgrade policy](https://docs.microsoft.com/sccm/compliance/deploy-use/upgrade-windows-version) in System Center Configuratio Manager.
|
||||
Note: Although it isn't displayed yet in the table, edition upgrade is also possible using [edition upgrade policy](https://docs.microsoft.com/sccm/compliance/deploy-use/upgrade-windows-version) in System Center Configuration Manager.
|
||||
|
||||
 (X) = not supported</br>
|
||||
 (green checkmark) = supported, reboot required</br>
|
||||
|
||||
@ -41,11 +41,11 @@ In environments that have more restrictive internet access, or for those that re
|
||||
|
||||
- NOTE: If Windows Update is inaccessible, the AutoPilot process will still continue.
|
||||
|
||||
- **Delivery Optimization.** When downloading Windows Updates and Microsoft Store apps and app updates (with additional content types expected in the future), the Delivery Optimization service is contacted to enable peer-to-peer sharing of content, so that all devices don’t need to download it from the internet.
|
||||
- **Delivery Optimization.** When downloading Windows Updates, Microsoft Store apps and app updates, Office Updates and Intune Win32 Apps, the Delivery Optimization service is contacted to enable peer-to-peer sharing of content so that only a few devices need to download it from the internet.
|
||||
|
||||
- <https://docs.microsoft.com/windows/deployment/update/waas-delivery-optimization>
|
||||
|
||||
- NOTE: If Delivery Optimization is inaccessible, the AutoPilot process will still continue.
|
||||
- NOTE: If Delivery Optimization Service is inaccessible, the AutoPilot process will still continue with Delivery Optimization downloads from the cloud (without peer-to-peer).
|
||||
|
||||
- **Network Time Protocol (NTP) Sync.** When a Windows device starts up, it will talk to a network time server to ensure that the time on the device is accurate.
|
||||
|
||||
|
||||
@ -25,6 +25,9 @@
|
||||
- name: Mobile Device Management
|
||||
tocHref: /windows/client-management/mdm/
|
||||
topicHref: /windows/client-management/mdm/index
|
||||
- name: Known issues
|
||||
tocHref: /windows/known-issues/
|
||||
topicHref: /windows/known-issues/index
|
||||
- name: Privacy
|
||||
tocHref: /windows/privacy/
|
||||
topicHref: /windows/privacy/index
|
||||
|
||||
@ -7,8 +7,12 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
author: brianlic-msft
|
||||
ms.author: brianlic
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 01/17/2018
|
||||
---
|
||||
|
||||
|
||||
@ -7,9 +7,13 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
localizationpriority: high
|
||||
audience: ITPro
|
||||
author: brianlic-msft
|
||||
ms.author: brianlic
|
||||
ms.date: 12/27/2018
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 02/15/2019
|
||||
---
|
||||
|
||||
|
||||
@ -65,11 +69,12 @@ The following fields are available:
|
||||
- **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
|
||||
- **SystemProcessorNx** The total number of objects of this type present on this device.
|
||||
- **SystemProcessorPrefetchW** The total number of objects of this type present on this device.
|
||||
- **SystemProcessorSse2** The total number of objects of this type present on this device.
|
||||
- **SystemWim** The total number of objects of this type present on this device.
|
||||
- **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.
|
||||
- **SystemWlan** The total number of objects of this type present on this device.
|
||||
- **Wmdrm_RS3** The total Wmdrm objects targeting the next release of Windows on this device.
|
||||
|
||||
|
||||
@ -475,7 +480,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Appraiser.General.DecisionMatchingInfoPassiveAdd
|
||||
|
||||
This event sends compatibility decision data about non-blocking entries on the system that are not keyed by either applications or devices, to help keep Windows up-to-date.
|
||||
This event sends compatibility decision data about non-blocking entries on the system that are not keyed by either applications or devices, to help keep Windows up to date.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -1270,7 +1275,7 @@ This event sends version data about the Apps running on this device, to help kee
|
||||
The following fields are available:
|
||||
|
||||
- **CensusVersion** The version of Census that generated the current data for this device.
|
||||
- **IEVersion** Retrieves which version of Internet Explorer is running on this device.
|
||||
- **IEVersion** The version of Internet Explorer that is running on the device.
|
||||
|
||||
|
||||
### Census.Battery
|
||||
@ -1757,6 +1762,20 @@ 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.
|
||||
|
||||
|
||||
## Component-based Servicing events
|
||||
|
||||
### CbsServicingProvider.CbsCapabilitySessionFinalize
|
||||
|
||||
This event provides information about the results of installing or uninstalling optional Windows content from Windows Update.
|
||||
|
||||
|
||||
|
||||
### CbsServicingProvider.CbsCapabilitySessionPended
|
||||
|
||||
This event provides information about the results of installing optional Windows content that requires a reboot to keep Windows up to date.
|
||||
|
||||
|
||||
|
||||
## Content Delivery Manager events
|
||||
|
||||
### Microsoft.Windows.ContentDeliveryManager.ProcessCreativeEvent
|
||||
@ -1827,6 +1846,7 @@ The following fields are available:
|
||||
- **LastBugCheckOriginalDumpType** The type of crash dump the system intended to save.
|
||||
- **LastBugCheckOtherSettings** Other crash dump settings.
|
||||
- **LastBugCheckParameter1** The first parameter with additional info on the type of the error.
|
||||
- **LastBugCheckProgress** Progress towards writing out the last crash dump.
|
||||
- **LastSuccessfullyShutdownBootId** The Boot ID of the last fully successful shutdown.
|
||||
- **PowerButtonCumulativePressCount** Indicates the number of times the power button has been pressed ("pressed" not to be confused with "released").
|
||||
- **PowerButtonCumulativeReleaseCount** Indicates the number of times the power button has been released ("released" not to be confused with "pressed").
|
||||
@ -1841,7 +1861,7 @@ The following fields are available:
|
||||
- **PowerButtonPressPowerWatchdogArmed** Indicates whether or not the watchdog for the monitor was active at the time of the last power button press.
|
||||
- **TransitionInfoBootId** The Boot ID of the captured transition information.
|
||||
- **TransitionInfoCSCount** The total number of times the system transitioned from "Connected Standby" mode to "On" when the last marker was saved.
|
||||
- **TransitionInfoCSEntryReason** Indicates the reason the device last entered "Connected Standby" mode ("entered" not to be confused with "exited").
|
||||
- **TransitionInfoCSEntryReason** Indicates the reason the device last entered "Connected Standby" mode ("entered" not to be confused with "exited").
|
||||
- **TransitionInfoCSExitReason** Indicates the reason the device last exited "Connected Standby" mode ("exited" not to be confused with "entered").
|
||||
- **TransitionInfoCSInProgress** Indicates whether the system was in or entering Connected Standby mode when the last marker was saved.
|
||||
- **TransitionInfoLastReferenceTimeChecksum** The checksum of TransitionInfoLastReferenceTimestamp.
|
||||
@ -1890,7 +1910,7 @@ The following fields are available:
|
||||
- **CanPerformDiagnosticEscalations** True if UTC is allowed to perform all scenario escalations.
|
||||
- **CanPerformScripting** True if UTC is allowed to perform scripting.
|
||||
- **CanPerformTraceEscalations** True if UTC is allowed to perform scenario escalations with tracing actions.
|
||||
- **CanReportScenarios** True if UTC is allowed to load and report scenario completion, failure, and cancellation events.
|
||||
- **CanReportScenarios** True if we can report scenario completions, false otherwise.
|
||||
- **PreviousPermissions** Bitmask representing the previously configured permissions since the telemetry client was last started.
|
||||
- **TransitionFromEverythingOff** True if this transition is moving from not allowing core telemetry to allowing core telemetry.
|
||||
|
||||
@ -2017,6 +2037,80 @@ The following fields are available:
|
||||
- **WDDMVersion** The Windows Display Driver Model version.
|
||||
|
||||
|
||||
## Failover Clustering events
|
||||
|
||||
### Microsoft.Windows.Server.FailoverClusteringCritical.ClusterSummary2
|
||||
|
||||
This event returns information about how many resources and of what type are in the server cluster. This data is collected to keep Windows Server safe, secure, and up to date. The data includes information about whether hardware is configured correctly, if the software is patched correctly, and assists in preventing crashes by attributing issues (like fatal errors) to workloads and system configurations.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **autoAssignSite** The cluster parameter: auto site.
|
||||
- **autoBalancerLevel** The cluster parameter: auto balancer level.
|
||||
- **autoBalancerMode** The cluster parameter: auto balancer mode.
|
||||
- **blockCacheSize** The configured size of the block cache.
|
||||
- **ClusterAdConfiguration** The ad configuration of the cluster.
|
||||
- **clusterAdType** The cluster parameter: mgmt_point_type.
|
||||
- **clusterDumpPolicy** The cluster configured dump policy.
|
||||
- **clusterFunctionalLevel** The current cluster functional level.
|
||||
- **clusterGuid** The unique identifier for the cluster.
|
||||
- **clusterWitnessType** The witness type the cluster is configured for.
|
||||
- **countNodesInSite** The number of nodes in the cluster.
|
||||
- **crossSiteDelay** The cluster parameter: CrossSiteDelay.
|
||||
- **crossSiteThreshold** The cluster parameter: CrossSiteThreshold.
|
||||
- **crossSubnetDelay** The cluster parameter: CrossSubnetDelay.
|
||||
- **crossSubnetThreshold** The cluster parameter: CrossSubnetThreshold.
|
||||
- **csvCompatibleFilters** The cluster parameter: ClusterCsvCompatibleFilters.
|
||||
- **csvIncompatibleFilters** The cluster parameter: ClusterCsvIncompatibleFilters.
|
||||
- **csvResourceCount** The number of resources in the cluster.
|
||||
- **currentNodeSite** The name configured for the current site for the cluster.
|
||||
- **dasModeBusType** The direct storage bus type of the storage spaces.
|
||||
- **downLevelNodeCount** The number of nodes in the cluster that are running down-level.
|
||||
- **drainOnShutdown** Specifies whether a node should be drained when it is shut down.
|
||||
- **dynamicQuorumEnabled** Specifies whether dynamic Quorum has been enabled.
|
||||
- **enforcedAntiAffinity** The cluster parameter: enforced anti affinity.
|
||||
- **genAppNames** The win32 service name of a clustered service.
|
||||
- **genSvcNames** The command line of a clustered genapp.
|
||||
- **hangRecoveryAction** The cluster parameter: hang recovery action.
|
||||
- **hangTimeOut** Specifies the “hang time out” parameter for the cluster.
|
||||
- **isCalabria** Specifies whether storage spaces direct is enabled.
|
||||
- **isMixedMode** Identifies if the cluster is running with different version of OS for nodes.
|
||||
- **isRunningDownLevel** Identifies if the current node is running down-level.
|
||||
- **logLevel** Specifies the granularity that is logged in the cluster log.
|
||||
- **logSize** Specifies the size of the cluster log.
|
||||
- **lowerQuorumPriorityNodeId** The cluster parameter: lower quorum priority node ID.
|
||||
- **minNeverPreempt** The cluster parameter: minimum never preempt.
|
||||
- **minPreemptor** The cluster parameter: minimum preemptor priority.
|
||||
- **netftIpsecEnabled** The parameter: netftIpsecEnabled.
|
||||
- **NodeCount** The number of nodes in the cluster.
|
||||
- **nodeId** The current node number in the cluster.
|
||||
- **nodeResourceCounts** Specifies the number of node resources.
|
||||
- **nodeResourceOnlineCounts** Specifies the number of node resources that are online.
|
||||
- **numberOfSites** The number of different sites.
|
||||
- **numNodesInNoSite** The number of nodes not belonging to a site.
|
||||
- **plumbAllCrossSubnetRoutes** The cluster parameter: plumb all cross subnet routes.
|
||||
- **preferredSite** The preferred site location.
|
||||
- **privateCloudWitness** Specifies whether a private cloud witness exists for this cluster.
|
||||
- **quarantineDuration** The quarantine duration.
|
||||
- **quarantineThreshold** The quarantine threshold.
|
||||
- **quorumArbitrationTimeout** In the event of an arbitration event, this specifies the quorum timeout period.
|
||||
- **resiliencyLevel** Specifies the level of resiliency.
|
||||
- **resourceCounts** Specifies the number of resources.
|
||||
- **resourceTypeCounts** Specifies the number of resource types in the cluster.
|
||||
- **resourceTypes** Data representative of each resource type.
|
||||
- **resourceTypesPath** Data representative of the DLL path for each resource type.
|
||||
- **sameSubnetDelay** The cluster parameter: same subnet delay.
|
||||
- **sameSubnetThreshold** The cluster parameter: same subnet threshold.
|
||||
- **secondsInMixedMode** The amount of time (in seconds) that the cluster has been in mixed mode (nodes with different operating system versions in the same cluster).
|
||||
- **securityLevel** The cluster parameter: security level.
|
||||
- **sharedVolumeBlockCacheSize** Specifies the block cache size for shared for shared volumes.
|
||||
- **shutdownTimeoutMinutes** Specifies the amount of time it takes to time out when shutting down.
|
||||
- **upNodeCount** Specifies the number of nodes that are up (online).
|
||||
- **useClientAccessNetworksForCsv** The cluster parameter: use client access networks for CSV.
|
||||
- **vmIsolationTime** The cluster parameter: VM isolation time.
|
||||
- **witnessDatabaseWriteTimeout** Specifies the timeout period for writing to the quorum witness database.
|
||||
|
||||
|
||||
## Fault Reporting events
|
||||
|
||||
### Microsoft.Windows.FaultReporting.AppCrashEvent
|
||||
@ -2227,6 +2321,30 @@ The following fields are available:
|
||||
- **Version** The version number of the program.
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryApplicationDriverAdd
|
||||
|
||||
This event represents what drivers an application installs.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryApplicationDriverStartSync
|
||||
|
||||
The InventoryApplicationDriverStartSync event indicates that a new set of InventoryApplicationDriverStartAdd events will be sent.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryApplicationFrameworkAdd
|
||||
|
||||
This event provides the basic metadata about the frameworks an application may depend on.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryApplicationFrameworkStartSync
|
||||
|
||||
This event indicates that a new set of InventoryApplicationFrameworkAdd events will be sent.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryApplicationRemove
|
||||
|
||||
This event indicates that a new set of InventoryDevicePnpAdd events will be sent.
|
||||
@ -2378,33 +2496,34 @@ This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedevic
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **Class** The device setup class of the driver loaded for the device
|
||||
- **ClassGuid** The device class GUID from the driver package
|
||||
- **COMPID** A JSON array the provides the value and order of the compatible ID tree for the device. See [COMPID](#compid).
|
||||
- **ContainerId** A system-supplied GUID that uniquely groups the functional devices associated with a single-function or multifunction device installed in the device.
|
||||
- **Description** The device description
|
||||
- **DeviceState** DeviceState is a bitmask of the following: DEVICE_IS_CONNECTED 0x0001 (currently only for container). DEVICE_IS_NETWORK_DEVICE 0x0002 (currently only for container). DEVICE_IS_PAIRED 0x0004 (currently only for container). DEVICE_IS_ACTIVE 0x0008 (currently never set). DEVICE_IS_MACHINE 0x0010 (currently only for container). DEVICE_IS_PRESENT 0x0020 (currently always set). DEVICE_IS_HIDDEN 0x0040. DEVICE_IS_PRINTER 0x0080 (currently only for container). DEVICE_IS_WIRELESS 0x0100. DEVICE_IS_WIRELESS_FAT 0x0200. The most common values are therefore: 32 (0x20)= device is present. 96 (0x60)= device is present but hidden. 288 (0x120)= device is a wireless device that is present
|
||||
- **DriverId** A unique identifier for the installed device.
|
||||
- **Class** The device setup class of the driver loaded for the device.
|
||||
- **ClassGuid** The device class unique identifier of the driver package loaded on the device.
|
||||
- **COMPID** The list of “Compatible IDs” for this device. See [COMPID](#compid).
|
||||
- **ContainerId** The system-supplied unique identifier that specifies which group(s) the device(s) installed on the parent (main) device belong to.
|
||||
- **Description** The description of the device.
|
||||
- **DeviceState** Identifies the current state of the parent (main) device.
|
||||
- **DriverId** The unique identifier for the installed driver.
|
||||
- **DriverName** The name of the driver image file.
|
||||
- **DriverPackageStrongName** The immediate parent directory name in the Directory field of InventoryDriverPackage.
|
||||
- **DriverVerDate** The date of the driver loaded for the device
|
||||
- **DriverVerVersion** The version of the driver loaded for the device
|
||||
- **Enumerator** The bus that enumerated the device
|
||||
- **HWID** A JSON array that provides the value and order of the HWID tree for the device. See [HWID](#hwid).
|
||||
- **Inf** The INF file name.
|
||||
- **InstallState** The device installation state. One of these values: https://msdn.microsoft.com/en-us/library/windows/hardware/ff543130.aspx
|
||||
- **InventoryVersion** The version of the inventory file generating the events.
|
||||
- **LowerClassFilters** Lower filter class drivers IDs installed for the device.
|
||||
- **LowerFilters** Lower filter drivers IDs installed for the device
|
||||
- **Manufacturer** The device manufacturer
|
||||
- **MatchingID** Represents the hardware ID or compatible ID that Windows uses to install a device instance
|
||||
- **Model** The device model
|
||||
- **ParentId** Device instance id of the parent of the device
|
||||
- **ProblemCode** The current error code for the device.
|
||||
- **Provider** The device provider
|
||||
- **Service** The device service name
|
||||
- **STACKID** A JSON array that provides the value and order of the STACKID tree for the device. See [STACKID](#stackid).
|
||||
- **UpperClassFilters** Upper filter class drivers IDs installed for the device
|
||||
- **UpperFilters** Upper filter drivers IDs installed for the device
|
||||
- **Enumerator** Identifies the bus that enumerated the device.
|
||||
- **HWID** A list of hardware IDs for the device. See [HWID](#hwid).
|
||||
- **Inf** The name of the INF file (possibly renamed by the OS, such as oemXX.inf).
|
||||
- **InstallState** The device installation state. For a list of values, see: https://msdn.microsoft.com/en-us/library/windows/hardware/ff543130.aspx
|
||||
- **InventoryVersion** The version number of the inventory process generating the events.
|
||||
- **LowerClassFilters** The identifiers of the Lower Class filters installed for the device.
|
||||
- **LowerFilters** The identifiers of the Lower filters installed for the device.
|
||||
- **Manufacturer** The manufacturer of the device.
|
||||
- **MatchingID** The Hardware ID or Compatible ID that Windows uses to install a device instance.
|
||||
- **Model** Identifies the model of the device.
|
||||
- **ParentId** The Device Instance ID of the parent of the device.
|
||||
- **ProblemCode** The error code currently returned by the device, if applicable.
|
||||
- **Provider** Identifies the device provider.
|
||||
- **Service** The name of the device service.
|
||||
- **STACKID** The list of hardware IDs for the stack. See [STACKID](#stackid).
|
||||
- **UpperClassFilters** The identifiers of the Upper Class filters installed for the device.
|
||||
- **UpperFilters** The identifiers of the Upper filters installed for the device.
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDevicePnpRemove
|
||||
@ -2429,6 +2548,18 @@ The following fields are available:
|
||||
- **InventoryVersion** The version of the inventory file generating the events.
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDeviceUsbHubClassAdd
|
||||
|
||||
This event sends basic metadata about the USB hubs on the device.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDeviceUsbHubClassStartSync
|
||||
|
||||
This event indicates that a new set of InventoryDeviceUsbHubClassAdd events will be sent.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.Core.InventoryDriverBinaryAdd
|
||||
|
||||
This event provides the basic metadata about driver binaries running on the system.
|
||||
@ -2567,6 +2698,18 @@ This event provides insight data on the installed Office products
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.General.InventoryMiscellaneousOfficeInsightsRemove
|
||||
|
||||
Indicates that this particular data object represented by the objectInstanceId is no longer present.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.General.InventoryMiscellaneousOfficeInsightsStartSync
|
||||
|
||||
This diagnostic event indicates that a new sync is being generated for this object type.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.General.InventoryMiscellaneousOfficeProductsAdd
|
||||
|
||||
Describes Office Products installed.
|
||||
@ -2591,6 +2734,18 @@ Indicates a new sync is being generated for this object type.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.General.InventoryMiscellaneousOfficeVBARuleViolationsStartSync
|
||||
|
||||
This event indicates that a new sync is being generated for this object type.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.General.InventoryMiscellaneousOfficeVBAStartSync
|
||||
|
||||
Diagnostic event to indicate a new sync is being generated for this object type.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Inventory.General.InventoryMiscellaneousUUPInfoAdd
|
||||
|
||||
Provides data on Unified Update Platform (UUP) products and what version they are at.
|
||||
@ -3215,6 +3370,12 @@ The following fields are available:
|
||||
- **Time** The system time at which the event began.
|
||||
|
||||
|
||||
### Microsoft.Windows.Sediment.Info.DetailedState
|
||||
|
||||
This event is sent when detailed state information is needed from an update trial run.
|
||||
|
||||
|
||||
|
||||
### Microsoft.Windows.Sediment.Info.DownloadServiceError
|
||||
|
||||
This event provides information when the Download Service returns an error. The information provided helps keep Windows up to date.
|
||||
@ -3394,6 +3555,17 @@ The following fields are available:
|
||||
- **Url** The new URL from which content will be executed.
|
||||
|
||||
|
||||
### Microsoft.Windows.Sediment.OSRSS.SelfUpdate
|
||||
|
||||
This event returns metadata after Operating System Remediation System Service (OSRSS) successfully replaces itself with a new version.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ServiceVersionMajor** The major version number for the component.
|
||||
- **ServiceVersionMinor** The minor version number for the component.
|
||||
- **Time** The system timestamp for when the event occurred.
|
||||
|
||||
|
||||
### Microsoft.Windows.Sediment.OSRSS.UrlState
|
||||
|
||||
This event indicates the state the Operating System Remediation System Service (OSRSS) is in while attempting a download from the URL.
|
||||
@ -3408,6 +3580,17 @@ The following fields are available:
|
||||
- **Time** System timestamp the event was fired
|
||||
|
||||
|
||||
### Microsoft.Windows.Sediment.ServiceInstaller.ApplicabilityCheckFailed
|
||||
|
||||
This event returns data relating to the error state after one of the applicability checks for the installer component of the Operating System Remediation System Service (OSRSS) has failed.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **CheckName** The name of the applicability check that failed.
|
||||
- **InstallerVersion** The version information for the installer component.
|
||||
- **Time** The system timestamp for when the event occurred.
|
||||
|
||||
|
||||
### Microsoft.Windows.Sediment.ServiceInstaller.AttemptingUpdate
|
||||
|
||||
This event indicates the Operating System Remediation System Service (OSRSS) installer is attempting an update to itself. This information helps ensure Windows is up to date.
|
||||
@ -3855,6 +4038,26 @@ The following fields are available:
|
||||
- **threadId** The ID of the thread on which the activity is executing.
|
||||
|
||||
|
||||
## SIH events
|
||||
|
||||
### SIHEngineTelemetry.EvalApplicability
|
||||
|
||||
This event is sent when targeting logic is evaluated to determine if a device is eligible a given action.
|
||||
|
||||
|
||||
|
||||
### SIHEngineTelemetry.ExecuteAction
|
||||
|
||||
This event is triggered with SIH attempts to execute (e.g. install) the update or action in question. Includes important information like if the update required a reboot.
|
||||
|
||||
|
||||
|
||||
### SIHEngineTelemetry.PostRebootReport
|
||||
|
||||
This event reports the status of an action following a reboot, should one have been required.
|
||||
|
||||
|
||||
|
||||
## Software update events
|
||||
|
||||
### SoftwareUpdateClientTelemetry.CheckForUpdates
|
||||
@ -3977,36 +4180,36 @@ The following fields are available:
|
||||
|
||||
- **ActiveDownloadTime** How long the download took, in seconds, excluding time where the update wasn't actively being downloaded.
|
||||
- **AppXBlockHashValidationFailureCount** A count of the number of blocks that have failed validation after being downloaded.
|
||||
- **AppXDownloadScope** Indicates the scope of the download for application content. For streaming install scenarios, AllContent - non-streaming download, RequiredOnly - streaming download requested content required for launch, AutomaticOnly - streaming download requested automatic streams for the app, and Unknown - for events sent before download scope is determined by the Windows Update client.
|
||||
- **AppXDownloadScope** Indicates the scope of the download for application content.
|
||||
- **BiosFamily** The family of the BIOS (Basic Input Output System).
|
||||
- **BiosName** The name of the device BIOS.
|
||||
- **BiosReleaseDate** The release date of the device BIOS.
|
||||
- **BiosSKUNumber** The sku number of the device BIOS.
|
||||
- **BiosSKUNumber** The SKU number of the device BIOS.
|
||||
- **BIOSVendor** The vendor of the BIOS.
|
||||
- **BiosVersion** The version of the BIOS.
|
||||
- **BundleBytesDownloaded** How many bytes were downloaded for the specific content bundle.
|
||||
- **BundleId** Identifier associated with the specific content bundle; should not be all zeros if the bundleID was found.
|
||||
- **BundleBytesDownloaded** Number of bytes downloaded for the specific content bundle.
|
||||
- **BundleId** Identifier associated with the specific content bundle.
|
||||
- **BundleRepeatFailFlag** Indicates whether this particular update bundle had previously failed to download.
|
||||
- **BundleRevisionNumber** Identifies the revision number of the content bundle.
|
||||
- **BytesDownloaded** How many bytes were downloaded for an individual piece of content (not the entire bundle).
|
||||
- **CachedEngineVersion** For self-initiated healing, the version of the SIH engine that is cached on the device. If the SIH engine does not exist, the value is null.
|
||||
- **CallerApplicationName** The name provided by the caller who initiated API calls into the software distribution client.
|
||||
- **CbsDownloadMethod** Indicates whether the download was a full-file download or a partial/delta download.
|
||||
- **CachedEngineVersion** The version of the “Self-Initiated Healing” (SIH) engine that is cached on the device, if applicable.
|
||||
- **CallerApplicationName** The name provided by the application that initiated API calls into the software distribution client.
|
||||
- **CbsDownloadMethod** Indicates whether the download was a full- or a partial-file download.
|
||||
- **CDNCountryCode** Two letter country abbreviation for the Content Distribution Network (CDN) location.
|
||||
- **CDNId** ID which defines which CDN the software distribution client downloaded the content from.
|
||||
- **ClientManagedByWSUSServer** Indicates whether the client is managed by Windows Server Update Services (WSUS).
|
||||
- **ClientVersion** The version number of the software distribution client.
|
||||
- **CurrentMobileOperator** The mobile operator the device is currently connected to.
|
||||
- **DeviceModel** What is the device model.
|
||||
- **DeviceOEM** What OEM does this device belong to.
|
||||
- **DeviceModel** The model of the device.
|
||||
- **DeviceOEM** Identifies the Original Equipment Manufacturer (OEM) of the device.
|
||||
- **DownloadPriority** Indicates whether a download happened at background, normal, or foreground priority.
|
||||
- **DownloadScenarioId** A unique ID for a given download used to tie together WU and DO events.
|
||||
- **DownloadType** Differentiates the download type of SIH downloads between Metadata and Payload downloads.
|
||||
- **Edition** Indicates the edition of Windows being used.
|
||||
- **DownloadScenarioId** A unique ID for a given download, used to tie together Windows Update and Delivery Optimizer events.
|
||||
- **DownloadType** Differentiates the download type of “Self-Initiated Healing” (SIH) downloads between Metadata and Payload downloads.
|
||||
- **Edition** Identifies the edition of Windows currently running on the device.
|
||||
- **EventInstanceID** A globally unique identifier for event instance.
|
||||
- **EventNamespaceID** Indicates whether the event succeeded or failed. Has the format EventType+Event where Event is Succeeded, Cancelled, Failed, etc.
|
||||
- **EventScenario** Indicates the purpose of sending this event - whether because the software distribution just started downloading content, or whether it was cancelled, succeeded, or failed.
|
||||
- **EventType** Possible values are Child, Bundle, or Driver.
|
||||
- **EventNamespaceID** The ID of the test events environment.
|
||||
- **EventScenario** Indicates the purpose for sending this event: whether because the software distribution just started downloading content; or whether it was cancelled, succeeded, or failed.
|
||||
- **EventType** Identifies the type of the event (Child, Bundle, or Driver).
|
||||
- **ExtendedStatusCode** Secondary error code for certain scenarios where StatusCode wasn't specific enough.
|
||||
- **FeatureUpdatePause** Indicates whether feature OS updates are paused on the device.
|
||||
- **FlightBranch** The branch that a device is on if participating in flighting (pre-release builds).
|
||||
@ -4016,39 +4219,39 @@ The following fields are available:
|
||||
- **HandlerType** Indicates what kind of content is being downloaded (app, driver, windows patch, etc.).
|
||||
- **HardwareId** If this download was for a driver targeted to a particular device model, this ID indicates the model of the device.
|
||||
- **HomeMobileOperator** The mobile operator that the device was originally intended to work with.
|
||||
- **HostName** The hostname URL the content is downloading from.
|
||||
- **HostName** The parent URL the content is downloading from.
|
||||
- **IPVersion** Indicates whether the download took place over IPv4 or IPv6.
|
||||
- **IsAOACDevice** Is it Always On, Always Connected?
|
||||
- **IsAOACDevice** Indicates whether the device is an Always On, Always Connected (AOAC) device.
|
||||
- **IsDependentSet** Indicates whether a driver is a part of a larger System Hardware/Firmware Update
|
||||
- **IsWUfBDualScanEnabled** Indicates if Windows Update for Business dual scan is enabled on the device.
|
||||
- **IsWUfBEnabled** Indicates if Windows Update for Business is enabled on the device.
|
||||
- **NetworkCostBitMask** Indicates what kind of network the device is connected to (roaming, metered, over data cap, etc.)
|
||||
- **NetworkCostBitMask** A flag indicating the cost of the network (congested, fixed, variable, over data limit, roaming, etc.) used for downloading the update content.
|
||||
- **NetworkRestrictionStatus** More general version of NetworkCostBitMask, specifying whether Windows considered the current network to be "metered."
|
||||
- **PackageFullName** The package name of the content.
|
||||
- **PhonePreviewEnabled** Indicates whether a phone was opted-in to getting preview builds, prior to flighting (pre-release builds) being introduced.
|
||||
- **PlatformRole** The PowerPlatformRole as defined on MSDN
|
||||
- **PlatformRole** The role of the OS platform (Desktop, Mobile, Workstation, etc.).
|
||||
- **ProcessName** The process name of the caller who initiated API calls, in the event where CallerApplicationName was not provided.
|
||||
- **ProcessorArchitecture** Processor architecture of the system (x86, AMD64, ARM).
|
||||
- **QualityUpdatePause** Indicates whether quality OS updates are paused on the device.
|
||||
- **RelatedCV** The previous Correlation Vector that was used before swapping with a new one
|
||||
- **RelatedCV** The Correlation Vector that was used before the most recent change to a new Correlation Vector.
|
||||
- **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, 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.
|
||||
- **RevisionNumber** The revision number of the specified piece of content.
|
||||
- **ServiceGuid** A unique identifier for the service that the software distribution client is installing content for (Windows Update, Windows Store, etc.).
|
||||
- **Setup360Phase** Identifies the active phase of the upgrade download if the current download is for an Operating System upgrade.
|
||||
- **ShippingMobileOperator** The mobile operator linked to the device when the device shipped.
|
||||
- **StatusCode** Indicates the result of a Download event (success, cancellation, failure code HResult).
|
||||
- **SystemBIOSMajorRelease** Major version of the BIOS.
|
||||
- **SystemBIOSMinorRelease** Minor version of the BIOS.
|
||||
- **TargetGroupId** For drivers targeted to a specific device model, this ID indicates the distribution group of devices receiving that driver.
|
||||
- **TargetingVersion** For drivers targeted to a specific device model, this is the version number of the drivers being distributed to the device.
|
||||
- **TargetMetadataVersion** For self-initiated healing, this is the target version of the SIH engine to download (if needed). If not, the value is null.
|
||||
- **TargetMetadataVersion** The version of the currently downloading (or most recently downloaded) package.
|
||||
- **ThrottlingServiceHResult** Result code (success/failure) while contacting a web service to determine whether this device should download content yet.
|
||||
- **TimeToEstablishConnection** Time (in ms) it took to establish the connection prior to beginning downloaded.
|
||||
- **TotalExpectedBytes** The total count of bytes that the download is expected to be.
|
||||
- **TimeToEstablishConnection** Time (in milliseconds) it took to establish the connection prior to beginning downloaded.
|
||||
- **TotalExpectedBytes** The total size (in Bytes) expected to be downloaded.
|
||||
- **UpdateId** An identifier associated with the specific piece of content.
|
||||
- **UpdateID** An identifier associated with the specific piece of content.
|
||||
- **UpdateImportance** Indicates whether a piece of content was marked as Important, Recommended, or Optional.
|
||||
- **UsedDO** Whether the download used the delivery optimization service.
|
||||
- **UpdateImportance** Indicates whether the content was marked as Important, Recommended, or Optional.
|
||||
- **UsedDO** Indicates whether the download used the Delivery Optimization (DO) service.
|
||||
- **UsedSystemVolume** Indicates whether the content was downloaded to the device's main system storage drive, or an alternate storage drive.
|
||||
- **WUDeviceID** The unique identifier of a specific device, used to identify how many devices are encountering success or a particular issue.
|
||||
- **WUSetting** Indicates the users' current updating settings.
|
||||
@ -4221,7 +4424,7 @@ The following fields are available:
|
||||
- **EndpointUrl** The endpoint URL where the device obtains update metadata. This is used to distinguish between test, staging, and production environments.
|
||||
- **EventScenario** The purpose of this event, such as scan started, scan succeeded, or scan failed.
|
||||
- **ExtendedStatusCode** The secondary status code of the event.
|
||||
- **LeafCertId** Integral ID from the FragmentSigning data for certificate that failed.
|
||||
- **LeafCertId** The integral ID from the FragmentSigning data for the certificate that failed.
|
||||
- **ListOfSHA256OfIntermediateCerData** A semicolon delimited list of base64 encoding of hashes for the Base64CerData in the FragmentSigning data of an intermediate certificate.
|
||||
- **MetadataIntegrityMode** The mode of the transport metadata integrity check. 0 = unknown; 1 = ignore; 2 = audit; 3 = enforce
|
||||
- **MetadataSignature** A base64-encoded string of the signature associated with the update metadata (specified by revision ID).
|
||||
@ -4232,7 +4435,7 @@ The following fields are available:
|
||||
- **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.
|
||||
- **SHA256OfTimestampToken** An encoded string of the timestamp token.
|
||||
- **SignatureAlgorithm** The hash algorithm for the metadata signature.
|
||||
- **SLSPrograms** A test program to which a device may have opted in. Example: Insider Fast
|
||||
- **StatusCode** The status code of the event.
|
||||
@ -4452,6 +4655,22 @@ The following fields are available:
|
||||
- **UpdateId** Unique ID for each update.
|
||||
|
||||
|
||||
### Update360Telemetry.UpdateAgentCommit
|
||||
|
||||
This event collects information regarding the commit phase of the new Unified Update Platform (UUP) update scenario, which is leveraged by both Mobile and Desktop.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ErrorCode** The error code returned for the current install phase.
|
||||
- **FlightId** Unique ID for each flight.
|
||||
- **ObjectId** Unique value for each Update Agent mode.
|
||||
- **RelatedCV** Correlation vector value generated from the latest USO scan.
|
||||
- **Result** Outcome of the install phase of the update.
|
||||
- **ScenarioId** Indicates the update scenario.
|
||||
- **SessionId** Unique value for each update attempt.
|
||||
- **UpdateId** Unique ID for each update.
|
||||
|
||||
|
||||
### Update360Telemetry.UpdateAgentDownloadRequest
|
||||
|
||||
This event sends data for the download request phase of updating Windows via the new Unified Update Platform (UUP) scenario. Applicable to PC and Mobile.
|
||||
@ -4483,6 +4702,26 @@ The following fields are available:
|
||||
- **UpdateId** Unique ID for each Update.
|
||||
|
||||
|
||||
### Update360Telemetry.UpdateAgentExpand
|
||||
|
||||
This event collects information regarding the expansion phase of the new Unified Update Platform (UUP) update scenario, which is leveraged by both Mobile and Desktop.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ElapsedTickCount** Time taken for expand phase.
|
||||
- **EndFreeSpace** Free space after expand phase.
|
||||
- **EndSandboxSize** Sandbox size after expand phase.
|
||||
- **ErrorCode** The error code returned for the current install phase.
|
||||
- **FlightId** Unique ID for each flight.
|
||||
- **ObjectId** Unique value for each Update Agent mode.
|
||||
- **RelatedCV** Correlation vector value generated from the latest USO scan.
|
||||
- **ScenarioId** Indicates the update scenario.
|
||||
- **SessionId** Unique value for each update attempt.
|
||||
- **StartFreeSpace** Free space before expand phase.
|
||||
- **StartSandboxSize** Sandbox size after expand phase.
|
||||
- **UpdateId** Unique ID for each update.
|
||||
|
||||
|
||||
### Update360Telemetry.UpdateAgentInitialize
|
||||
|
||||
This event sends data for the initialize phase of updating Windows via the new Unified Update Platform (UUP) scenario, which is applicable to both PCs and Mobile.
|
||||
@ -4501,6 +4740,22 @@ The following fields are available:
|
||||
- **UpdateId** Unique ID for each update.
|
||||
|
||||
|
||||
### Update360Telemetry.UpdateAgentInstall
|
||||
|
||||
This event sends data for the install phase of updating Windows.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ErrorCode** The error code returned for the current install phase.
|
||||
- **FlightId** Unique value for each Update Agent mode (same concept as InstanceId for Setup360).
|
||||
- **ObjectId** Correlation vector value generated from the latest USO scan.
|
||||
- **RelatedCV** Correlation vector value generated from the latest USO scan.
|
||||
- **Result** The result for the current install phase.
|
||||
- **ScenarioId** Indicates the update scenario.
|
||||
- **SessionId** Unique value for each update attempt.
|
||||
- **UpdateId** Unique ID for each update.
|
||||
|
||||
|
||||
### Update360Telemetry.UpdateAgentMitigationResult
|
||||
|
||||
This event sends data indicating the result of each update agent mitigation.
|
||||
@ -4578,6 +4833,18 @@ The following fields are available:
|
||||
|
||||
## Upgrade events
|
||||
|
||||
### FacilitatorTelemetry.DCATDownload
|
||||
|
||||
This event indicates whether devices received additional or critical supplemental content during an OS Upgrade, to help keep Windows up-to-date and secure.
|
||||
|
||||
|
||||
|
||||
### FacilitatorTelemetry.InitializeDU
|
||||
|
||||
This event determines whether devices received additional or critical supplemental content during an OS upgrade.
|
||||
|
||||
|
||||
|
||||
### Setup360Telemetry.Downlevel
|
||||
|
||||
This event sends data indicating that the device has started the downlevel phase of the upgrade, to help keep Windows up-to-date and secure.
|
||||
@ -4865,7 +5132,7 @@ The following fields are available:
|
||||
- **RebootReason** Reason for the reboot.
|
||||
|
||||
|
||||
## Microsoft Store events
|
||||
## Windows Store events
|
||||
|
||||
### Microsoft.Windows.Store.Partner.ReportApplication
|
||||
|
||||
@ -5623,17 +5890,17 @@ This event indicates that a scan for a Windows Update occurred.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **deferReason** Reason why the device could not check for updates.
|
||||
- **detectionBlockreason** Reason for detection not completing.
|
||||
- **deferReason** The reason why the device could not check for updates.
|
||||
- **detectionBlockreason** The reason detection did not complete.
|
||||
- **detectionDeferreason** A log of deferral reasons for every update state.
|
||||
- **errorCode** The returned error code.
|
||||
- **errorCode** The error code returned for the current process.
|
||||
- **eventScenario** End-to-end update session ID, or indicates the purpose of sending this event - whether because the software distribution just started installing content, or whether it was cancelled, succeeded, or failed.
|
||||
- **flightID** The specific ID of the Windows Insider build the device is getting.
|
||||
- **interactive** Indicates whether the session was user initiated.
|
||||
- **revisionNumber** Update revision number.
|
||||
- **updateId** Update ID.
|
||||
- **updateScenarioType** The update session type.
|
||||
- **wuDeviceid** Unique device ID used by Windows Update.
|
||||
- **flightID** The unique identifier for the flight (Windows Insider pre-release build) should be delivered to the device, if applicable.
|
||||
- **interactive** Indicates whether the user initiated the session.
|
||||
- **revisionNumber** The Update revision number.
|
||||
- **updateId** The unique identifier of the Update.
|
||||
- **updateScenarioType** Identifies the type of update session being performed.
|
||||
- **wuDeviceid** The unique device ID used by Windows Update.
|
||||
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.Download
|
||||
@ -5696,7 +5963,7 @@ The following fields are available:
|
||||
- **deferReason** Reason for install not completing.
|
||||
- **errorCode** The error code reppresented by a hexadecimal value.
|
||||
- **eventScenario** End-to-end update session ID.
|
||||
- **flightID** The specific ID of the Windows Insider build the device is getting.
|
||||
- **flightID** The ID of the Windows Insider build the device is getting.
|
||||
- **flightUpdate** Indicates whether the update is a Windows Insider build.
|
||||
- **ForcedRebootReminderSet** A boolean value that indicates if a forced reboot will happen for updates.
|
||||
- **installCommitfailedtime** The time it took for a reboot to happen but the upgrade failed to progress.
|
||||
@ -5741,14 +6008,26 @@ This event is sent after a Windows update install completes.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **batteryLevel** Current battery capacity in mWh or percentage left.
|
||||
- **bundleId** Identifier associated with the specific content bundle.
|
||||
- **batteryLevel** Current battery capacity in megawatt-hours (mWh) or percentage left.
|
||||
- **bundleId** The unique identifier associated with the specific content bundle.
|
||||
- **bundleRevisionnumber** Identifies the revision number of the content bundle.
|
||||
- **errorCode** The error code returned for the current phase.
|
||||
- **eventScenario** State of update action.
|
||||
- **flightID** Unique update ID.
|
||||
- **flightID** The unique identifier for the flight (Windows Insider pre-release build) should be delivered to the device, if applicable.
|
||||
- **sessionType** The Windows Update session type (Interactive or Background).
|
||||
- **wuDeviceid** Unique device ID used by Windows Update.
|
||||
- **wuDeviceid** The unique device identifier used by Windows Update.
|
||||
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.PowerMenuOptionsChanged
|
||||
|
||||
This event is sent when the options in power menu changed, usually due to an update pending reboot, or after a update is installed.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **powermenuNewOptions** The new options after the power menu changed.
|
||||
- **powermenuOldOptions** The old options before the power menu changed.
|
||||
- **rebootPendingMinutes** If the power menu changed because a reboot is pending due to a update, this indicates how long that reboot has been pending.
|
||||
- **wuDeviceid** The device ID recorded by Windows Update if the power menu changed because a reboot is pending due to an update.
|
||||
|
||||
|
||||
### Microsoft.Windows.Update.Orchestrator.PreShutdownStart
|
||||
@ -5953,7 +6232,7 @@ The following fields are available:
|
||||
- **revisionNumber** Revision number of the OS.
|
||||
- **scheduledRebootTime** Time scheduled for the reboot.
|
||||
- **updateId** Identifies which update is being scheduled.
|
||||
- **wuDeviceid** Unique device ID used by Windows Update.
|
||||
- **wuDeviceid** The unique device ID used by Windows Update.
|
||||
|
||||
|
||||
### Microsoft.Windows.Update.Ux.MusNotification.ToastDisplayedToScheduleReboot
|
||||
@ -5985,12 +6264,44 @@ The following fields are available:
|
||||
|
||||
## Windows Update mitigation events
|
||||
|
||||
### Mitigation360Telemetry.MitigationCustom.CleanupSafeOsImages
|
||||
|
||||
This event sends data specific to the CleanupSafeOsImages mitigation used for OS Updates.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
- **ClientId** The client ID used by Windows Update.
|
||||
- **FlightId** The ID of each Windows Insider build the device received.
|
||||
- **InstanceId** A unique device ID that identifies each update instance.
|
||||
- **MitigationScenario** The update scenario in which the mitigation was executed.
|
||||
- **MountedImageCount** The number of mounted images.
|
||||
- **MountedImageMatches** The number of mounted image matches.
|
||||
- **MountedImagesFailed** The number of mounted images that could not be removed.
|
||||
- **MountedImagesRemoved** The number of mounted images that were successfully removed.
|
||||
- **MountedImagesSkipped** The number of mounted images that were not found.
|
||||
- **RelatedCV** The correlation vector value generated from the latest USO scan.
|
||||
- **Result** HResult of this operation.
|
||||
- **ScenarioId** ID indicating the mitigation scenario.
|
||||
- **ScenarioSupported** Indicates whether the scenario was supported.
|
||||
- **SessionId** Unique value for each update attempt.
|
||||
- **UpdateId** Unique ID for each Windows Update.
|
||||
- **WuId** Unique ID for the Windows Update client.
|
||||
|
||||
|
||||
### Mitigation360Telemetry.MitigationCustom.FixupEditionId
|
||||
|
||||
This event sends data specific to the FixupEditionId mitigation used for OS Updates.
|
||||
|
||||
|
||||
|
||||
## Windows Update Reserve Manager events
|
||||
|
||||
### Microsoft.Windows.UpdateReserveManager.RemovePendingHardReserveAdjustment
|
||||
|
||||
This event is sent when the Update Reserve Manager removes a pending hard reserve adjustment.
|
||||
|
||||
|
||||
|
||||
## Winlogon events
|
||||
|
||||
### Microsoft.Windows.Security.Winlogon.SetupCompleteLogon
|
||||
|
||||
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
@ -7,7 +7,12 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 04/04/2018
|
||||
---
|
||||
|
||||
|
||||
@ -7,8 +7,12 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
author: brianlic-msft
|
||||
ms.author: brianlic
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 01/17/2018
|
||||
---
|
||||
|
||||
|
||||
@ -7,9 +7,13 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
ms.date: 11/9/2018
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 11/9/2018
|
||||
---
|
||||
|
||||
|
||||
|
||||
@ -7,8 +7,12 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 05/11/2018
|
||||
---
|
||||
# Windows and the GDPR: Information for IT Administrators and Decision Makers
|
||||
|
||||
@ -7,8 +7,12 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: pwiglemsft
|
||||
ms.author: pwigle
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 09/25/2017
|
||||
---
|
||||
|
||||
|
||||
@ -22,7 +22,13 @@ metadata:
|
||||
|
||||
ms.date: 04/25/2018
|
||||
|
||||
ms.topic: article
|
||||
ms.topic: conceptual
|
||||
|
||||
audience: ITPro
|
||||
|
||||
manager: dansimp
|
||||
|
||||
ms.collection: M365-security-compliance
|
||||
|
||||
ms.devlang: na
|
||||
|
||||
|
||||
@ -7,8 +7,12 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 11/16/2018
|
||||
robots: noindex,nofollow
|
||||
---
|
||||
|
||||
@ -7,8 +7,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 06/05/2018
|
||||
---
|
||||
|
||||
|
||||
@ -6,8 +6,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 6/26/2018
|
||||
---
|
||||
# Manage connection endpoints for Windows 10, version 1709
|
||||
|
||||
@ -6,8 +6,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 6/26/2018
|
||||
---
|
||||
# Manage connection endpoints for Windows 10, version 1803
|
||||
|
||||
@ -6,8 +6,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 6/26/2018
|
||||
---
|
||||
# Manage connection endpoints for Windows 10, version 1809
|
||||
|
||||
@ -6,8 +6,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
author: eross-msft
|
||||
ms.author: lizross
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 11/28/2017
|
||||
---
|
||||
|
||||
|
||||
@ -6,8 +6,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
author: brianlic-msft
|
||||
ms.author: brianlic
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 03/13/2018
|
||||
---
|
||||
|
||||
|
||||
@ -6,8 +6,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 6/26/2018
|
||||
---
|
||||
# Windows 10, version 1709, connection endpoints for non-Enterprise editions
|
||||
|
||||
@ -6,8 +6,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 6/26/2018
|
||||
---
|
||||
# Windows 10, version 1803, connection endpoints for non-Enterprise editions
|
||||
|
||||
@ -6,8 +6,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 6/26/2018
|
||||
---
|
||||
# Windows 10, version 1809, connection endpoints for non-Enterprise editions
|
||||
|
||||
@ -7,8 +7,12 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: high
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
ms.date: 05/11/2018
|
||||
---
|
||||
# Windows 10 personal data services configuration
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 07/18/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 12/10/2018
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 10/13/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,6 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,7 +5,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/11/2017
|
||||
---
|
||||
|
||||
|
||||
@ -7,7 +7,12 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: jdeckerms
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
---
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/17/2017
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/31/2017
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/17/2017
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/17/2017
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 09/04/2018
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/17/2017
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/17/2017
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 01/12/2018
|
||||
---
|
||||
|
||||
|
||||
@ -6,7 +6,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/17/2017
|
||||
---
|
||||
|
||||
|
||||
@ -7,7 +7,12 @@ ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
author: brianlic-msft
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: daniha
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.date: 08/17/2017
|
||||
---
|
||||
|
||||
|
||||
@ -1,10 +1,14 @@
|
||||
---
|
||||
title: Enterprise Certificate Pinning
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.author: mstephens
|
||||
author: MikeStephens-MS
|
||||
description: Enterprise certificate pinning is a Windows feature for remembering, or “pinning” a root, issuing certificate authority, or end entity certificate to a given domain name.
|
||||
manager: alanth
|
||||
audience: ITPro
|
||||
author: MikeStephens-MS
|
||||
ms.author: mstephens
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
ms.sitesec: library
|
||||
|
||||
@ -0,0 +1,46 @@
|
||||
---
|
||||
title: WebAuthn APIs
|
||||
description: Enabling password-less authentication for your sites and apps
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: aabhathipsay
|
||||
ms.author: aathipsa
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 02/15/2019
|
||||
---
|
||||
# WebAuthn APIs for password-less authentication on Windows 10
|
||||
|
||||
|
||||
### Passwords leave your customers vulnerable. With the new WebAuthn APIs, your sites and apps can leverage password-less authentication.
|
||||
|
||||
Microsoft has long been a proponent to do away with passwords.
|
||||
While working towards that goal, we'd like to introduce you to the latest Windows 10 (version 1903) W3C/FIDO2 Win32 WebAuthn platform APIs!
|
||||
These APIs allow Microsoft developer partners and the developer community to leverage Windows Hello and FIDO2 security keys
|
||||
as a password-less authentication mechanism for their applications on Windows 10 devices.
|
||||
|
||||
#### What does this mean?
|
||||
This opens opportunities for developers or relying parties (RPs) to enable password-less authentication.
|
||||
They can now leverage [Windows Hello](https://aka.ms/whfb) or [FIDO2 Security Keys](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/microsoft-compatible-security-key)
|
||||
as a password-less multi-factor credential for authentication.
|
||||
<br>
|
||||
Users of these sites can use any browser that supports WebAuthn Windows 10 APIs for password-less authentication
|
||||
and will have a familiar and consistent experience on Windows 10, no matter which browser they use to get to the RPs site!
|
||||
<br> <br>
|
||||
The native Windows 10 WebAuthn APIs are currently supported by Microsoft Edge on Windows 10 1809 or later
|
||||
and latest versions of other browsers.
|
||||
<br> <br>
|
||||
Developers of FIDO2 authentication keys should use the new Windows 10 APIs, to enable these scenarios in a consistent way for users.
|
||||
Moreover, this enables the use of all the transports available per FIDO2 specifications - USB, NFC and BLE
|
||||
without having to deal with the interaction and management overhead.
|
||||
This also implies browsers or apps on Windows 10 will no longer have direct access to above transports for FIDO related messaging.
|
||||
|
||||
#### Where can developers learn more?
|
||||
The new Windows 10 APIs are documented on [GitHub](https://github.com/Microsoft/webauthn)
|
||||
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 03/20/2018
|
||||
---
|
||||
# Multifactor Unlock
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/20/2018
|
||||
---
|
||||
# Planning an adequate number of Windows Server 2016 Domain Controllers for Windows Hello for Business deployments
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: DaniHalfin
|
||||
ms.localizationpriority: medium
|
||||
ms.author: daniha
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: danihalf
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
---
|
||||
# Windows Hello and password changes
|
||||
|
||||
@ -7,9 +7,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Prepare and Deploy Windows Server 2016 Active Directory Federation Services
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Configure or Deploy Multifactor Authentication Services
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/20/2018
|
||||
---
|
||||
# Configure Windows Hello for Business Policy settings
|
||||
@ -126,7 +130,7 @@ Windows 10 provides eight PIN Complexity Group Policy settings that give you gra
|
||||
* Require special characters
|
||||
* Require uppercase letters
|
||||
|
||||
In the Windows 10, version 1703, the PIN complexity Group Policy settings have moved to remove misunderstanding that PIN complexity policy settings were exclusive to Windows Hello for Business. The new location of these Group Policy settings is under Administrative Templates\System\PIN Complexity under both the Computer and User Configuration nodes of the Group Policy editor.
|
||||
In the Windows 10, version 1703, the PIN complexity Group Policy settings have moved to remove misunderstanding that PIN complexity policy settings were exclusive to Windows Hello for Business. The new location of these Group Policy settings is under Computer Configuration\Administrative Templates\System\PIN Complexity in the Group Policy editor.
|
||||
|
||||
## Review
|
||||
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Validate Active Directory prerequisites
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Validate and Deploy Multifactor Authentication Services (MFA)
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Validate and Configure Public Key Infrastructure
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# On Premises Certificate Trust Deployment
|
||||
@ -27,15 +31,3 @@ Below, you can find all the information you will need to deploy Windows Hello fo
|
||||
3. [Prepare and Deploy Windows Server 2016 Active Directory Federation Services](hello-cert-trust-adfs.md)
|
||||
4. [Validate and Deploy Multifactor Authentication Services (MFA)](hello-cert-trust-validate-deploy-mfa.md)
|
||||
5. [Configure Windows Hello for Business Policy settings](hello-cert-trust-policy-settings.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/29/2018
|
||||
---
|
||||
# Windows Hello for Business Deployment Guide
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/20/2018
|
||||
---
|
||||
# On Premises Key Trust Deployment
|
||||
|
||||
@ -7,9 +7,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: DaniHalfin
|
||||
ms.localizationpriority: medium
|
||||
ms.author: daniha
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: danihalf
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: troubleshooting
|
||||
localizationpriority: medium
|
||||
ms.date: 05/05/2018
|
||||
---
|
||||
|
||||
|
||||
@ -7,9 +7,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
author: DaniHalfin
|
||||
ms.localizationpriority: medium
|
||||
ms.author: daniha
|
||||
audience: ITPro
|
||||
author: danihalfin
|
||||
ms.author: danihalf
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 07/27/2017
|
||||
---
|
||||
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Windows Hello for Business Frequently Ask Questions
|
||||
|
||||
@ -7,9 +7,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 05/05/2018
|
||||
---
|
||||
# Windows Hello for Business Features
|
||||
|
||||
@ -5,9 +5,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Windows Hello for Business and Authentication
|
||||
|
||||
@ -5,9 +5,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Windows Hello for Business and Device Registration
|
||||
|
||||
@ -5,9 +5,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Windows Hello for Business Provisioning
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Technical Deep Dive
|
||||
|
||||
@ -5,9 +5,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 10/08/2018
|
||||
---
|
||||
# Technology and Terms
|
||||
|
||||
@ -5,9 +5,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 05/05/2018
|
||||
---
|
||||
# How Windows Hello for Business works
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Configure Azure AD joined devices for On-premises Single-Sign On using Windows Hello for Business
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Using Certificates for AADJ On-premises Single-sign On
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
localizationpriority: high
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Azure AD Join Single Sign-on Deployment Guides
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Windows Hello for Business Certificate Trust New Installation
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/18/2018
|
||||
---
|
||||
# Configure Device Registration for Hybrid Windows Hello for Business
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Hybrid Windows Hello for Business Prerequisites
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 09/08/2017
|
||||
---
|
||||
# Hybrid Azure AD joined Certificate Trust Deployment
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Hybrid Windows Hello for Business Provisioning
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Configuring Windows Hello for Business: Active Directory
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/20/2018
|
||||
---
|
||||
# Configure Windows Hello for Business: Active Directory Federation Services
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 10/23/2017
|
||||
---
|
||||
# Configure Hybrid Windows Hello for Business: Directory Synchronization
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
|
||||
|
||||
@ -6,9 +6,13 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security, mobile
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
author: mikestephens-MS
|
||||
ms.author: mstephen
|
||||
manager: dansimp
|
||||
ms.collection: M365-identity-device-management
|
||||
ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
---
|
||||
# Configure Hybrid Windows Hello for Business: Group Policy
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user