mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Merge branch 'master' into atp-mac
This commit is contained in:
Denise Vangel-MSFT
commit
1d59cd61d2
@ -157,13 +157,13 @@ This table includes the attributes used by the Enterprise Mode schema.
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><version></td>
|
||||
<td>version</td>
|
||||
<td>Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <rules> element.</td>
|
||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><exclude></td>
|
||||
<td>Specifies the domain or path excluded from applying the behavior and is supported on the <domain> and <path> elements.
|
||||
<td>exclude</td>
|
||||
<td>Specifies the domain or path is excluded from applying Enterprise Mode. This attribute is only supported on the <domain> and <path> elements in the <emie> section.
|
||||
<p><b>Example</b>
|
||||
<pre class="syntax">
|
||||
<emie>
|
||||
@ -175,7 +175,7 @@ Where <a href="https://fabrikam.com" data-raw-source="https://fabrikam.com">http
|
||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><docMode></td>
|
||||
<td>docMode</td>
|
||||
<td>Specifies the document mode to apply. This attribute is only supported on <domain> or <path> elements in the <docMode> section.
|
||||
<p><b>Example</b>
|
||||
<pre class="syntax">
|
||||
|
||||
@ -46,19 +46,19 @@ The following is an example of the v.2 version of the Enterprise Mode schema.
|
||||
|
||||
```xml
|
||||
<site-list version="205">
|
||||
<!--- File creation header --->
|
||||
<!-- File creation header -->
|
||||
<created-by>
|
||||
<tool>EnterpriseSitelistManager</tool>
|
||||
<version>10240</version>
|
||||
<date-created>20150728.135021</date-created>
|
||||
</created-by>
|
||||
<!--- Begin Site List --->
|
||||
<!-- Begin Site List -->
|
||||
<site url="www.cpandl.com">
|
||||
<compat-mode>IE8Enterprise</compat-mode>
|
||||
<open-in>MSEdge</open-in>
|
||||
</site>
|
||||
<site url="www.woodgrovebank.com">
|
||||
<compat-mode>default</compat-mode>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="adatum.com">
|
||||
@ -66,14 +66,15 @@ The following is an example of the v.2 version of the Enterprise Mode schema.
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="contoso.com">
|
||||
<compat-mode>default</compat-mode>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="relecloud.com"/>
|
||||
<compat-mode>default</compat-mode>
|
||||
<open-in>none</open-in>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>None</open-in>
|
||||
<site url="relecloud.com/about">
|
||||
<compat-mode>IE8Enterprise"</compat-mode>
|
||||
<open-in>None</open-in>
|
||||
</site>
|
||||
<site url="contoso.com/travel">
|
||||
<compat-mode>IE7</compat-mode>
|
||||
@ -232,26 +233,26 @@ These v.1 version schema attributes have been deprecated in the v.2 version of t
|
||||
<table>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th>Deprecated attribute</th>
|
||||
<th>New attribute</th>
|
||||
<th>Deprecated element/attribute</th>
|
||||
<th>New element</th>
|
||||
<th>Replacement example</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><forceCompatView></td>
|
||||
<td>forceCompatView</td>
|
||||
<td><compat-mode></td>
|
||||
<td>Replace <forceCompatView="true"> with <compat-mode>IE7Enterprise</compat-mode></td>
|
||||
<td>Replace forceCompatView="true" with <compat-mode>IE7Enterprise</compat-mode></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><docMode></td>
|
||||
<td>docMode</td>
|
||||
<td><compat-mode></td>
|
||||
<td>Replace <docMode="IE5"> with <compat-mode>IE5</compat-mode></td>
|
||||
<td>Replace docMode="IE5" with <compat-mode>IE5</compat-mode></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><doNotTransition></td>
|
||||
<td>doNotTransition</td>
|
||||
<td><open-in></td>
|
||||
<td>Replace <doNotTransition="true"> with <open-in>none</open-in></td>
|
||||
<td>Replace doNotTransition="true" with <open-in>none</open-in></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><domain> and <path></td>
|
||||
@ -259,25 +260,28 @@ These v.1 version schema attributes have been deprecated in the v.2 version of t
|
||||
<td>Replace:
|
||||
<pre class="syntax">
|
||||
<emie>
|
||||
<domain exclude="false">contoso.com</domain>
|
||||
<domain>contoso.com</domain>
|
||||
</emie></pre>
|
||||
With:
|
||||
<pre class="syntax">
|
||||
<site url="contoso.com"/>
|
||||
<compat-mode>IE8Enterprise</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site></pre>
|
||||
<b>-AND-</b><p>
|
||||
Replace:
|
||||
<pre class="syntax">
|
||||
<emie>
|
||||
<domain exclude="true">contoso.com
|
||||
<path exclude="false" forceCompatView="true">/about</path>
|
||||
<domain exclude="true" doNotTransition="true">
|
||||
contoso.com
|
||||
<path forceCompatView="true">/about</path>
|
||||
</domain>
|
||||
</emie></pre>
|
||||
With:
|
||||
<pre class="syntax">
|
||||
<site url="contoso.com/about">
|
||||
<compat-mode>IE7Enterprise</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site></pre></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -71,19 +71,19 @@ This is a view of the [raw EMIE v2 schema.xml file](https://gist.github.com/kypf
|
||||
|
||||
```xml
|
||||
<site-list version="205">
|
||||
<!--- File creation header --->
|
||||
<!-- File creation header -->
|
||||
<created-by>
|
||||
<tool>EnterpriseSiteListManager</tool>
|
||||
<version>10586</version>
|
||||
<date-created>20150728.135021</date-created>
|
||||
</created-by>
|
||||
<!--- Begin Site List --->
|
||||
<!-- Begin Site List -->
|
||||
<site url="www.cpandl.com">
|
||||
<compat-mode>IE8Enterprise</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="www.woodgrovebank.com">
|
||||
<compat-mode>default</compat-mode>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site>
|
||||
<site url="adatum.com">
|
||||
@ -92,8 +92,8 @@ This is a view of the [raw EMIE v2 schema.xml file](https://gist.github.com/kypf
|
||||
</site>
|
||||
<site url="relecloud.com"/>
|
||||
<!-- default for self-closing XML tag is
|
||||
<compat-mode>default</compat-mode>
|
||||
<open-in>none</open-in>
|
||||
<compat-mode>Default</compat-mode>
|
||||
<open-in>None</open-in>
|
||||
-->
|
||||
<site url="relecloud.com/products">
|
||||
<compat-mode>IE8Enterprise"</compat-mode>
|
||||
|
||||
@ -56,6 +56,8 @@
|
||||
## Overview
|
||||
### [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md)
|
||||
### [Operating system essentials (Surface Hub)](differences-between-surface-hub-and-windows-10-enterprise.md)
|
||||
### [Technical information for 55” Microsoft Surface Hub](surface-hub-technical-55.md)
|
||||
### [Technical information for 84” Microsoft Surface Hub](surface-hub-technical-84.md)
|
||||
|
||||
## Plan
|
||||
### [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
|
||||
@ -111,7 +113,6 @@
|
||||
## Troubleshoot
|
||||
### [Using the Surface Hub Recovery Tool](surface-hub-recovery-tool.md)
|
||||
### [Surface Hub SSD replacement](surface-hub-ssd-replacement.md)
|
||||
|
||||
### [Top support solutions for Surface Hub](support-solutions-surface-hub.md)
|
||||
### [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
|
||||
### [Surface Hub Update History](surface-hub-update-history.md)
|
||||
@ -124,6 +125,4 @@
|
||||
### [Surface Hub may install updates and restart outside maintenance hours](surface-hub-installs-updates-and-restarts-outside-maintenance-hours.md)
|
||||
### [General Data Privacy Regulation and Surface Hub](general-data-privacy-regulation-and-surface-hub.md)
|
||||
### [Useful downloads for Surface Hub administrators](surface-hub-downloads.md)
|
||||
### [Technical information for 55” Microsoft Surface Hub](surface-hub-technical-55.md)
|
||||
### [Technical information for 84” Microsoft Surface Hub](surface-hub-technical-84.md)
|
||||
### [Change history for Surface Hub](change-history-surface-hub.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ApplicationControl CSP
|
||||
description: ApplicationControl CSP
|
||||
title: ApplicationControl CSP DDF
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the **ApplicationControl** configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: EnrollmentStatusTracking CSP
|
||||
description: EnrollmentStatusTracking CSP
|
||||
title: EnrollmentStatusTracking DDF
|
||||
description: This topic shows the OMA DM device description framework (DDF) for the EnrollmentStatusTracking configuration service provider. DDF files are used only with OMA DM provisioning XML.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: EnrollmentStatusTracking CSP
|
||||
description: EnrollmentStatusTracking CSP
|
||||
description: During Autopilot deployment, you can configure the Enrollment Status Page (ESP) to block the device use until the required apps are installed.
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
@ -11,7 +11,6 @@ ms.date: 05/21/2019
|
||||
|
||||
# EnrollmentStatusTracking CSP
|
||||
|
||||
|
||||
During Autopilot deployment, you can configure the Enrollment Status Page (ESP) to block the device use until the required apps are installed. You can select the apps that must be installed before using the device. The EnrollmentStatusTracking configuration service provider (CSP) is used by Intune's agents, such as SideCar to configure ESP for blocking the device use until the required Win32 apps are installed. It tracks the installation status of the required policy providers and the apps they install and sends it to ESP, which displays the installation progress message to the user. For more information on ESP, see [Windows Autopilot Enrollment Status page](https://docs.microsoft.com/windows/deployment/windows-autopilot/enrollment-status).
|
||||
|
||||
ESP uses the EnrollmentStatusTracking CSP along with the DMClient CSP to track the installation of different apps. The EnrollmentStatusTracking CSP tracks Win32 apps installations and DMClient CSP tracks MSI and Universal Windows Platform apps installations. In DMClient CSP, the **FirstSyncStatus/ExpectedMSIAppPackages** and **FirstSyncStatus/ExpectedModernAppPackages** nodes list the apps to track their installation. See [DMClient CSP](dmclient-csp.md) for more information.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Policy CSP - TimeLanguageSettings
|
||||
title: Policy CSP - DeviceHealthMonitoring
|
||||
description: Policy CSP - TimeLanguageSettings
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows as a service
|
||||
title: Windows as a service news & resources
|
||||
ms.prod: w10
|
||||
ms.topic: article
|
||||
ms.manager: elizapo
|
||||
|
||||
@ -14,6 +14,7 @@ manager: laurawi
|
||||
ms.localizationpriority: high
|
||||
ms.collection: M365-modern-desktop
|
||||
---
|
||||
|
||||
# Windows as a service
|
||||
|
||||
Find the tools and resources you need to help deploy and support Windows as a service in your organization.
|
||||
|
||||
@ -6,7 +6,7 @@ ms.mktglfcycl:
|
||||
audience: itpro
|
||||
itproauthor: jaimeo
|
||||
author: jaimeo
|
||||
ms.localizationprioauthor: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.audience: itpro
|
||||
author: jaimeo
|
||||
ms.date: 09/18/2018
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Autopilot support
|
||||
ms.reviewer:
|
||||
title: Windows Autopilot FAQ
|
||||
ms.reviewer: This topic provides OEMs, partners, administrators, and end-users with answers to some frequently asked questions about deploying Windows 10 with Windows Autopilot.
|
||||
manager: laurawi
|
||||
description: Support information for Windows Autopilot
|
||||
keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
|
||||
@ -99,7 +99,7 @@ A [glossary](#glossary) of abbreviations used in this topic is provided at the e
|
||||
|How do I know that I received Autopilot?|You can tell that you received Windows Autopilot (as in the device received a configuration but has not yet applied it) when you skip the selection page (as seen below), and are immediately taken to a generic or customized sign-in page.|
|
||||
|Windows Autopilot didn’t work, what do I do now?| Questions and actions to assist in troubleshooting: Did a screen not get skipped? Did a user end up as an admin when configured not to? Remember that AAD Admins will be local admins regardless of whether Windows Autopilot is configured to disable local admin Collection information – run licensingdiag.exe and send the .cab (Cabinet file) file that is generated to AutopilotHelp@microsoft.com. If possible, collect an ETL from WPR. Often in these cases, users are not signing into the right AAD tenant, or are creating local user accounts. For a complete list of support options, refer to [Windows Autopilot support](autopilot-support.md). |
|
||||
| If an Administrator makes changes to an existing profile, will the changes take effect on devices that have that profile assigned to them that have already been deployed? |No. Windows Autopilot profiles are not resident on the device. They are downloaded during OOBE, the settings defined at the time are applied. Then, the profile is discarded on the device. If the device is re-imaged or reset, the new profile settings will take effect the next time the device goes through OOBE.|
|
||||
|What is the experience if a device isn’t registered or if an IT Admin doesn’t configure Windows Autopilot prior to an end user attempting to self-deploy? |If the device isn’t registered, it will not receive the Windows Autopilot experience and the end user will go through normal OOBE. The Windows Autopilot configurations will NOT be applied until the user runs through OOBE again, after registration. If a device is started before an MDM profile is created, the device will go through standard OOBE experience. The IT Admin would then have to manually enrol that device into the MDM, after which—the next time that device is “reset”—it will go through the Windows Autopilot OOBE experience.|
|
||||
|What is the experience if a device isn’t registered or if an IT Admin doesn’t configure Windows Autopilot prior to an end user attempting to self-deploy? |If the device isn’t registered, it will not receive the Windows Autopilot experience and the end user will go through normal OOBE. The Windows Autopilot configurations will NOT be applied until the user runs through OOBE again, after registration. If a device is started before an MDM profile is created, the device will go through standard OOBE experience. The IT Admin would then have to manually enroll that device into the MDM, after which—the next time that device is “reset”—it will go through the Windows Autopilot OOBE experience.|
|
||||
|What may be a reason why I did not receive a customized sign-in screen during Autopilot? |Tenant branding must be configured in portal.azure.com to receive a customized sign-in experience.|
|
||||
|What happens if a device is registered with Azure AD but does not have an Windows Autopilot profile assigned? |The regular AAD OOBE will occur since no Windows Autopilot profile was assigned to the device.|
|
||||
|How can I collect logs on Autopilot?|The best way to collect logs on Windows Autopilot performance is to collect a Windows Performance Recorder (WPR) trace during OOBE. The XML file (WPRP extension) for this trace may be provided upon request.|
|
||||
@ -132,7 +132,7 @@ A [glossary](#glossary) of abbreviations used in this topic is provided at the e
|
||||
|------------------|-----------------|
|
||||
|If I wipe the machine and restart, will I still receive Windows Autopilot?|Yes, if the device is still registered for Windows Autopilot and is running Windows 10, version 1703 7B and above releases, it will receive the Windows Autopilot experience.|
|
||||
|Can I harvest the device fingerprint on existing machines?|Yes, if the device is running Windows 10, version 1703 and above, you can harvest device fingerprints for registration. There are no plans to backport the functionality to previous releases and no way to harvest them on pre-Windows 10 Windows 10, version 1703 devices that have not been updated to Windows 10, version 1703.|
|
||||
|What is Windows 10, version 1703 7B and why does it matter?| Windows 10, version 1703 7B is a Windows 10, version 1703 image bundled with cumulative updates. To receive Autopilot, clients **must** run Windows 10, version 1703 7B or later. These cumulative updates contain a critical fix for Autopilot. Consider the following:<br><br><I>Windows Autopilot will not apply its profiles to the machine unless AAD credentials match the expected AAD tenant. For the Windows 10, version 1703 release, it was assumed that would be determined by the domain name, so the domain name used to register (for example contoso.com) should match the domain name used to sign in (for example user@contoso.com). But what happens if your tenant has multiple domains (for example us.contoso.com, or fr.contoso.com)? Since these domain names do not match, the device will not be configured for Autopilot. However, both domains are part of the same AAD tenant, and as such it was determined the matching scheme was not useful. This was improved upon by making use of the tenant ID. By using the tenant ID, we can determine that if the user signs into a domain with a tenant matching the one they registered with, we can safely consider this to be a match. The fix for this problem already exists in Windows 10, version 1709 and was backported into the Windows 10, version 1703 7B release.</I> <br><br>**Key Take-Aways**: When using pre-Windows 10, version 1703 7B clients the user’s domain **must** match the domain they registered with. This functionality is found in Windows 10 version 1709 clients using build >= 16215, and Windows 10, version 1703 clients >= 7B. |
|
||||
|What is Windows 10, version 1703 7B and why does it matter?| Windows 10, version 1703 7B is a Windows 10, version 1703 image bundled with cumulative updates. To receive Autopilot, clients **must** run Windows 10, version 1703 7B or later. These cumulative updates contain a critical fix for Autopilot. Consider the following:<br><br><I>Windows Autopilot will not apply its profiles to the machine unless AAD credentials match the expected AAD tenant. For the Windows 10, version 1703 release, it was assumed that would be determined by the domain name, so the domain name used to register (for example contoso.com) should match the domain name used to sign in (for example user@contoso.com). But what happens if your tenant has multiple domains (for example us.contoso.com, or fr.contoso.com)? Since these domain names do not match, the device will not be configured for Autopilot. However, both domains are part of the same AAD tenant, and as such it was determined the matching scheme was not useful. This was improved upon by making use of the tenant ID. By using the tenant ID, we can determine that if the user signs into a domain with a tenant matching the one they registered with, we can safely consider this to be a match. The fix for this problem already exists in Windows 10, version 1709 and was backported into the Windows 10, version 1703 7B release.</I> <br><br>**Key takeaways**: When using pre-Windows 10, version 1703 7B clients the user’s domain **must** match the domain they registered with. This functionality is found in Windows 10 version 1709 clients using build >= 16215, and Windows 10, version 1703 clients >= 7B. |
|
||||
|What is the impact of not updating to 7B?|See the detailed scenario described directly above.|
|
||||
|Is Windows Autopilot supported on other SKUs, e.g. Surface Hub, HoloLens, Windows Mobile.|No, Windows Autopilot isn’t supported on other SKUs.|
|
||||
|Does Windows Autopilot work after MBR or image re-installation?|Yes.|
|
||||
|
||||
@ -8,7 +8,7 @@
|
||||
### [Diagnostic Data Viewer Overview](diagnostic-data-viewer-overview.md)
|
||||
### [Diagnostic Data Viewer for PowerShell Overview](Microsoft-DiagnosticDataViewer.md)
|
||||
## Basic level Windows diagnostic data events and fields
|
||||
### [Windows 10, version 1903 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
||||
### [Windows 10, version 1903 and Windows 10, version 1909 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1903.md)
|
||||
### [Windows 10, version 1809 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||
### [Windows 10, version 1803 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1803.md)
|
||||
### [Windows 10, version 1709 basic level Windows diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1709.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
description: Use this article to learn more about what Windows diagnostic data is gathered at the basic level.
|
||||
title: Windows 10, version 1903 basic diagnostic events and fields (Windows 10)
|
||||
title: Windows 10, version 1903 and Windows 10, version 1909 basic diagnostic events and fields (Windows 10)
|
||||
keywords: privacy, telemetry
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -13,15 +13,16 @@ manager: dansimp
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
audience: ITPro
|
||||
ms.date: 04/23/2019
|
||||
ms.date: 12/04/2019
|
||||
---
|
||||
|
||||
|
||||
# Windows 10, version 1903 basic level Windows diagnostic events and fields
|
||||
# Windows 10, version 1903 and Windows 10, version 1909 basic level Windows diagnostic events and fields
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10, version 1903
|
||||
- Windows 10, version 1909
|
||||
|
||||
|
||||
The Basic level gathers a limited set of information that is critical for understanding the device and its configuration including: basic device information, quality-related information, app compatibility, and Microsoft Store. When the level is set to Basic, it also includes the Security level information.
|
||||
@ -666,7 +667,7 @@ The following fields are available:
|
||||
- **HasUxBlockOverride** Does the file have a block that is overridden by a tag in the SDB?
|
||||
- **MigApplication** Does the file have a MigXML from the SDB associated with it that applies to the current upgrade mode?
|
||||
- **MigRemoval** Does the file have a MigXML from the SDB that will cause the app to be removed on upgrade?
|
||||
- **NeedsDismissAction** Will the file cause an action that can be dimissed?
|
||||
- **NeedsDismissAction** Will the file cause an action that can be dismissed?
|
||||
- **NeedsInstallPostUpgradeData** After upgrade, the file will have a post-upgrade notification to install a replacement for the app.
|
||||
- **NeedsNotifyPostUpgradeData** Does the file have a notification that should be shown after upgrade?
|
||||
- **NeedsReinstallPostUpgradeData** After upgrade, this file will have a post-upgrade notification to reinstall the app.
|
||||
@ -1469,7 +1470,7 @@ The following fields are available:
|
||||
- **RunAppraiser** Indicates if Appraiser was set to run at all. If this if false, it is understood that data events will not be received from this device.
|
||||
- **RunDate** The date that the telemetry run was stated, expressed as a filetime.
|
||||
- **RunGeneralTel** Indicates if the generaltel.dll component was run. Generaltel collects additional telemetry on an infrequent schedule and only from machines at telemetry levels higher than Basic.
|
||||
- **RunOnline** Indicates if appraiser was able to connect to Windows Update and theefore is making decisions using up-to-date driver coverage information.
|
||||
- **RunOnline** Indicates if appraiser was able to connect to Windows Update and therefore is making decisions using up-to-date driver coverage information.
|
||||
- **RunResult** The hresult of the Appraiser telemetry run.
|
||||
- **ScheduledUploadDay** The day scheduled for the upload.
|
||||
- **SendingUtc** Indicates if the Appraiser client is sending events during the current telemetry run.
|
||||
@ -1678,7 +1679,7 @@ This event sends Windows Insider data from customers participating in improvemen
|
||||
The following fields are available:
|
||||
|
||||
- **DeviceSampleRate** The telemetry sample rate assigned to the device.
|
||||
- **DriverTargetRing** Indicates if the device is participating in receiving pre-release drivers and firmware contrent.
|
||||
- **DriverTargetRing** Indicates if the device is participating in receiving pre-release drivers and firmware content.
|
||||
- **EnablePreviewBuilds** Used to enable Windows Insider builds on a device.
|
||||
- **FlightIds** A list of the different Windows Insider builds on this device.
|
||||
- **FlightingBranchName** The name of the Windows Insider branch currently used by the device.
|
||||
@ -1935,7 +1936,7 @@ This event sends data about the current user's default preferences for browser a
|
||||
The following fields are available:
|
||||
|
||||
- **CalendarType** The calendar identifiers that are used to specify different calendars.
|
||||
- **DefaultApp** The current uer's default program selected for the following extension or protocol: .html, .htm, .jpg, .jpeg, .png, .mp3, .mp4, .mov, .pdf.
|
||||
- **DefaultApp** The current user's default program selected for the following extension or protocol: .html, .htm, .jpg, .jpeg, .png, .mp3, .mp4, .mov, .pdf.
|
||||
- **DefaultBrowserProgId** The ProgramId of the current user's default browser.
|
||||
- **LongDateFormat** The long date format the user has selected.
|
||||
- **ShortDateFormat** The short date format the user has selected.
|
||||
@ -5135,8 +5136,8 @@ The following fields are available:
|
||||
- **DeploymentProviderMode** The mode of operation of the update deployment provider.
|
||||
- **DeviceModel** Device model as defined in the system bios
|
||||
- **EventInstanceID** A globally unique identifier for event instance
|
||||
- **EventScenario** Indicates the purpose of the event - whether because scan started, succeded, failed, etc.
|
||||
- **EventType** Possible values are "Child", "Bundle", "Relase" or "Driver".
|
||||
- **EventScenario** Indicates the purpose of the event - whether because scan started, succeeded, failed, etc.
|
||||
- **EventType** Possible values are "Child", "Bundle", "Release" or "Driver".
|
||||
- **FlightId** The specific id of the flight the device is getting
|
||||
- **HandlerType** Indicates the kind of content (app, driver, windows patch, etc.)
|
||||
- **RevisionNumber** Identifies the revision number of this specific piece of content
|
||||
@ -5241,7 +5242,7 @@ The following fields are available:
|
||||
|
||||
- **CallerApplicationName** The name provided by the caller who initiated API calls into the software distribution client
|
||||
- **ClientVersion** The version number of the software distribution client
|
||||
- **EventScenario** Indicates the purpose of sending this event - whether because the software distribution just started checking for content, or whether it was cancelled, succeeded, or failed
|
||||
- **EventScenario** Indicates the purpose of sending this event - whether because the software distribution just started checking for content, or whether it was canceled, succeeded, or failed
|
||||
- **EventType** Possible values are "Child", "Bundle", "Relase" or "Driver"
|
||||
- **ExtendedStatusCode** Secondary error code for certain scenarios where StatusCode wasn't specific enough
|
||||
- **FileId** A hash that uniquely identifies a file
|
||||
@ -5274,7 +5275,7 @@ The following fields are available:
|
||||
- **IsNetworkMetered** Indicates whether Windows considered the current network to be ?metered"
|
||||
- **MOAppDownloadLimit** Mobile operator cap on size of application downloads, if any
|
||||
- **MOUpdateDownloadLimit** Mobile operator cap on size of operating system update downloads, if any
|
||||
- **PowerState** Indicates the power state of the device at the time of heartbeart (DC, AC, Battery Saver, or Connected Standby)
|
||||
- **PowerState** Indicates the power state of the device at the time of heartbeat (DC, AC, Battery Saver, or Connected Standby)
|
||||
- **RelatedCV** The previous correlation vector that was used by the client, before swapping with a new one
|
||||
- **ResumeCount** Number of times this active download has resumed from a suspended state
|
||||
- **RevisionNumber** Identifies the revision number of this specific piece of content
|
||||
@ -5311,7 +5312,7 @@ The following fields are available:
|
||||
- **DriverPingBack** Contains information about the previous driver and system state.
|
||||
- **DriverRecoveryIds** The list of identifiers that could be used for uninstalling the drivers if a recovery is required.
|
||||
- **EventInstanceID** A globally unique identifier for event instance.
|
||||
- **EventScenario** Indicates the purpose of sending this event - whether because the software distribution just started installing content, or whether it was cancelled, succeeded, or failed.
|
||||
- **EventScenario** Indicates the purpose of sending this event - whether because the software distribution just started installing content, or whether it was canceled, succeeded, or failed.
|
||||
- **EventType** Possible values are Child, Bundle, or Driver.
|
||||
- **ExtendedErrorCode** The extended error code.
|
||||
- **ExtendedStatusCode** Secondary error code for certain scenarios where StatusCode is not specific enough.
|
||||
@ -5436,7 +5437,7 @@ The following fields are available:
|
||||
- **DriverPingBack** Contains information about the previous driver and system state.
|
||||
- **DriverRecoveryIds** The list of identifiers that could be used for uninstalling the drivers when a recovery is required.
|
||||
- **EventInstanceID** A globally unique identifier for event instance.
|
||||
- **EventScenario** Indicates the purpose of the event (a scan started, succeded, failed, etc.).
|
||||
- **EventScenario** Indicates the purpose of the event (a scan started, succeeded, failed, etc.).
|
||||
- **EventType** Indicates the event type. Possible values are "Child", "Bundle", "Release" or "Driver".
|
||||
- **ExtendedStatusCode** Secondary status code for certain scenarios where StatusCode is not specific enough.
|
||||
- **FeatureUpdatePause** Indicates whether feature OS updates are paused on the device.
|
||||
@ -5488,7 +5489,7 @@ The following fields are available:
|
||||
|
||||
- **CallerApplicationName** Name of application making the Windows Update request. Used to identify context of request.
|
||||
- **EndpointUrl** URL of the endpoint where client obtains update metadata. Used to identify test vs staging vs production environments.
|
||||
- **EventScenario** Indicates the purpose of the event - whether because scan started, succeded, failed, etc.
|
||||
- **EventScenario** Indicates the purpose of the event - whether because scan started, succeeded, failed, etc.
|
||||
- **ExtendedStatusCode** Secondary status code for certain scenarios where StatusCode was not specific enough.
|
||||
- **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.
|
||||
@ -5515,7 +5516,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.SysReset.FlightUninstallCancel
|
||||
|
||||
This event indicates the customer has cancelled uninstallation of Windows.
|
||||
This event indicates the customer has canceled uninstallation of Windows.
|
||||
|
||||
|
||||
|
||||
@ -6019,7 +6020,7 @@ The following fields are available:
|
||||
- **Setup360Result** The result of Setup360 (HRESULT used to diagnose errors).
|
||||
- **Setup360Scenario** The Setup360 flow type (for example, Boot, Media, Update, MCT).
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of the target OS).
|
||||
- **State** Exit state of given Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
- **State** Exit state of given Setup360 run. Example: succeeded, failed, blocked, canceled.
|
||||
- **TestId** An ID that uniquely identifies a group of events.
|
||||
- **WuId** This is the Windows Update Client ID. In the Windows Update scenario, this is the same as the clientId.
|
||||
|
||||
@ -6041,7 +6042,7 @@ The following fields are available:
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that is used to diagnose errors.
|
||||
- **Setup360Scenario** The Setup360 flow type. Example: Boot, Media, Update, MCT.
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of target OS).
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, canceled.
|
||||
- **TestId** ID that uniquely identifies a group of events.
|
||||
- **WuId** This is the Windows Update Client ID. With Windows Update, this is the same as the clientId.
|
||||
|
||||
@ -6063,7 +6064,7 @@ The following fields are available:
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that is used to diagnose errors.
|
||||
- **Setup360Scenario** The Setup360 flow type. Example: Boot, Media, Update, MCT
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of target OS).
|
||||
- **State** Exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
- **State** Exit state of a Setup360 run. Example: succeeded, failed, blocked, canceled.
|
||||
- **TestId** ID that uniquely identifies a group of events.
|
||||
- **WuId** Windows Update client ID.
|
||||
|
||||
@ -6085,7 +6086,7 @@ The following fields are available:
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that's used to diagnose errors.
|
||||
- **Setup360Scenario** The Setup360 flow type. Example: Boot, Media, Update, MCT
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of target OS).
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, canceled
|
||||
- **TestId** A string to uniquely identify a group of events.
|
||||
- **WuId** This is the Windows Update Client ID. With Windows Update, this is the same as ClientId.
|
||||
|
||||
@ -6129,7 +6130,7 @@ The following fields are available:
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that can be used to diagnose errors.
|
||||
- **Setup360Scenario** The Setup360 flow type. Example: Boot, Media, Update, MCT.
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of the target OS).
|
||||
- **State** The exit state of the Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
- **State** The exit state of the Setup360 run. Example: succeeded, failed, blocked, canceled.
|
||||
- **TestId** ID that uniquely identifies a group of events.
|
||||
- **WuId** Windows Update client ID.
|
||||
|
||||
@ -6151,7 +6152,7 @@ The following fields are available:
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that can be used to diagnose errors.
|
||||
- **Setup360Scenario** Setup360 flow type (Boot, Media, Update, MCT).
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of target OS).
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, canceled.
|
||||
- **TestId** A string to uniquely identify a group of events.
|
||||
- **WuId** This is the Windows Update Client ID. With Windows Update, this is the same as the clientId.
|
||||
|
||||
@ -6173,7 +6174,7 @@ The following fields are available:
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that is used to diagnose errors.
|
||||
- **Setup360Scenario** The Setup360 flow type, Example: Boot, Media, Update, MCT.
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of target OS).
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, canceled.
|
||||
- **TestId** A string to uniquely identify a group of events.
|
||||
- **WuId** Windows Update client ID.
|
||||
|
||||
@ -6288,7 +6289,7 @@ The following fields are available:
|
||||
- **Setup360Result** The result of Setup360. This is an HRESULT error code that can be used to diagnose errors.
|
||||
- **Setup360Scenario** The Setup360 flow type. Example: Boot, Media, Update, MCT.
|
||||
- **SetupVersionBuildNumber** The build number of Setup360 (build number of target OS).
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, cancelled.
|
||||
- **State** The exit state of a Setup360 run. Example: succeeded, failed, blocked, canceled.
|
||||
- **TestId** A string to uniquely identify a group of events.
|
||||
- **WuId** This is the Windows Update Client ID. With Windows Update, this is the same as the clientId.
|
||||
|
||||
@ -6330,7 +6331,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.WERVertical.OSCrash
|
||||
|
||||
This event sends binary data from the collected dump file wheneveer a bug check occurs, to help keep Windows up to date. The is the OneCore version of this event.
|
||||
This event sends binary data from the collected dump file whenever a bug check occurs, to help keep Windows up to date. The is the OneCore version of this event.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -6793,12 +6794,12 @@ The following fields are available:
|
||||
|
||||
- **CatalogId** The Store Catalog ID for the product being installed.
|
||||
- **ProductId** The Store Product ID for the product being installed.
|
||||
- **SkuId** Specfic edition of the app being updated.
|
||||
- **SkuId** Specific edition of the app being updated.
|
||||
|
||||
|
||||
### Microsoft.Windows.StoreAgent.Telemetry.StateTransition
|
||||
|
||||
Products in the process of being fulfilled (installed or updated) are maintained in a list. This event is sent any time there is a change in a product's fulfillment status (pending, working, paused, cancelled, or complete), to help keep Windows up to date and secure.
|
||||
Products in the process of being fulfilled (installed or updated) are maintained in a list. This event is sent any time there is a change in a product's fulfillment status (pending, working, paused, canceled, or complete), to help keep Windows up to date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -7177,7 +7178,7 @@ The following fields are available:
|
||||
- **detectionBlockreason** The reason detection did not complete.
|
||||
- **detectionRetryMode** Indicates whether we will try to scan again.
|
||||
- **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.
|
||||
- **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 canceled, succeeded, or failed.
|
||||
- **flightID** The specific ID of the Windows Insider build the device is getting.
|
||||
- **interactive** Indicates whether the session was user initiated.
|
||||
- **networkStatus** Error info
|
||||
@ -7215,7 +7216,7 @@ This event indicates the reboot was postponed due to needing a display.
|
||||
The following fields are available:
|
||||
|
||||
- **displayNeededReason** Reason the display is needed.
|
||||
- **eventScenario** Indicates the purpose of sending this event - whether because the software distribution just started checking for content, or whether it was cancelled, succeeded, or failed.
|
||||
- **eventScenario** Indicates the purpose of sending this event - whether because the software distribution just started checking for content, or whether it was canceled, succeeded, or failed.
|
||||
- **rebootOutsideOfActiveHours** Indicates whether the reboot was to occur outside of active hours.
|
||||
- **revisionNumber** Revision number of the update.
|
||||
- **updateId** Update ID.
|
||||
@ -7310,7 +7311,7 @@ The following fields are available:
|
||||
|
||||
- **batteryLevel** Current battery capacity in mWh or percentage left.
|
||||
- **deferReason** Reason for install not completing.
|
||||
- **errorCode** The error code reppresented by a hexadecimal value.
|
||||
- **errorCode** The error code represented by a hexadecimal value.
|
||||
- **eventScenario** End-to-end update session ID.
|
||||
- **flightID** The ID of the Windows Insider build the device is getting.
|
||||
- **flightUpdate** Indicates whether the update is a Windows Insider build.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Validate Public Key Infrastructure (Windows Hello for Business)
|
||||
title: Validate Public Key Infrastructure - certificate trust model (Windows Hello for Business)
|
||||
description: How to Validate Public Key Infrastructure for Windows Hello for Business
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: w10
|
||||
|
||||
@ -17,6 +17,7 @@ ms.topic: article
|
||||
localizationpriority: medium
|
||||
ms.date: 05/05/2018
|
||||
---
|
||||
|
||||
# Windows Hello for Business
|
||||
|
||||
In Windows 10, Windows Hello for Business replaces passwords with strong two-factor authentication on PCs and mobile devices. This authentication consists of a new type of user credential that is tied to a device and uses a biometric or PIN.</br>
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Validate Public Key Infrastructure (Windows Hello for Business)
|
||||
title: Validate Public Key Infrastructure - key trust model (Windows Hello for Business)
|
||||
description: How to Validate Public Key Infrastructure for Windows Hello for Business
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: w10
|
||||
@ -16,6 +16,7 @@ localizationpriority: medium
|
||||
ms.date: 08/19/2018
|
||||
ms.reviewer:
|
||||
---
|
||||
|
||||
# Validate and Configure Public Key Infrastructure
|
||||
|
||||
**Applies to**
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows Hello for Business (Windows 10)
|
||||
ms.reviewer:
|
||||
title: Windows Hello for Business Overview (Windows 10)
|
||||
ms.reviewer: An overview of Windows Hello for Business
|
||||
description: An overview of Windows Hello for Business
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: w10
|
||||
@ -15,6 +15,7 @@ ms.collection: M365-identity-device-management
|
||||
ms.topic: conceptual
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Windows Hello for Business Overview
|
||||
|
||||
**Applies to**
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Advanced security audit policy settings (Windows 10)
|
||||
description: This reference for IT professionals provides information about the advanced audit policy settings that are available in Windows and the audit events that they generate.
|
||||
ms.assetid: 93b28b92-796f-4036-a53b-8b9e80f9f171
|
||||
ms.reviewer:
|
||||
ms.reviewer: This reference for IT professionals provides information about the advanced audit policy settings that are available in Windows and the audit events that they generate.
|
||||
ms.author: dansimp
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: How Microsoft identifies malware and potentially unwanted applications
|
||||
ms.reviewer:
|
||||
title: Submit files for analysis by Microsoft
|
||||
description: Learn how to submit files to Microsoft for malware analysis, how to track your submissions, and dispute detections.
|
||||
ms.reviewer:
|
||||
keywords: security, sample submission help, malware file, virus file, trojan file, submit, send to Microsoft, submit a sample, virus, trojan, worm, undetected, doesn’t detect, email microsoft, email malware, I think this is malware, I think it's a virus, where can I send a virus, is this a virus, MSE, doesn’t detect, no signature, no detection, suspect file, MMPC, Microsoft Malware Protection Center, researchers, analyst, WDSI, security intelligence
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: secure
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: File resource type
|
||||
description: Retrieves top recent alerts.
|
||||
description: Retrieves information associated with files alerts.
|
||||
keywords: apis, graph api, supported apis, get, alerts, recent
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: File resource type
|
||||
title: User resource type
|
||||
description: Retrieves top recent alerts.
|
||||
keywords: apis, graph api, supported apis, get, alerts, recent
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Advanced security audit policy settings (Windows 10)
|
||||
title: Advanced security audit policy settings in brief (Windows 10)
|
||||
description: Provides information about the advanced security audit policy settings that are available in Windows and the audit events that they generate.
|
||||
ms.assetid: 6BF9A642-DBC3-4101-94A3-B2316C553CE3
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Select the types of rules to create (Windows 10)
|
||||
description: Select the types of rules to create.
|
||||
title: Understand WDAC policy rules and file rules (Windows 10)
|
||||
description: Windows Defender Application Control (WDAC) provides control over a computer running Windows 10 by using policies that specify whether a driver or application is trusted and can be run. A policy includes *policy rules* that control options.
|
||||
keywords: whitelisting, security, malware
|
||||
ms.assetid: 8d6e0474-c475-411b-b095-1c61adb2bdbb
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How a Windows Defender System Guard helps protect Windows 10
|
||||
title: How Windows Defender System Guard protect Windows 10 from firmware exploits
|
||||
description: Windows Defender System Guard in Windows 10 uses a hardware-based root of trust to securely protect systems against firmware exploits.
|
||||
ms.assetid: 8d6e0474-c475-411b-b095-1c61adb2bdbb
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Get support
|
||||
title: Get support for Windows security baselines
|
||||
description: This article, and the articles it links to, answers frequently asked question on how to get support for Windows baselines, the Security Compliance Toolkit (SCT), and related topics in your organization
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Microsoft Security Compliance Toolkit 1.0
|
||||
title: Microsoft Security Compliance Toolkit 1.0 Guide
|
||||
description: This article describes how to use the Security Compliance Toolkit in your organization
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows security baselines
|
||||
title: Windows security baselines guide
|
||||
description: This article, and the articles it links to, describe how to use Windows security baselines in your organization
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user