mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge pull request #1637 from MicrosoftDocs/seo-update-duplicate-titles
SEO update -- remove/alter duplicate titles 61 of 61
This commit is contained in:
Tina Burden
GitHub
@ -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.
|
||||
|
||||
@ -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.|
|
||||
|
||||
@ -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
|
||||
|
||||
Reference in New Issue
Block a user