mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Update metadata titles marvel seo 4_1 3
This commit is contained in:
1justingilmore
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Add a Windows 10 operating system image using Configuration Manager (Windows 10)
|
||||
title: Add a Windows 10 operating system image using Configuration Manager
|
||||
description: Operating system images are typically the production image used for deployment throughout the organization.
|
||||
ms.assetid: 77f769cc-1a47-4f36-8082-201cd77b8d3b
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Add a Windows 10 operating system image using Configuration Manager
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager (Windows 10)
|
||||
title: Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
|
||||
description: Learn how to configure the Windows Preinstallation Environment (Windows PE) to include required network and storage drivers.
|
||||
ms.assetid: 97b3ea46-28d9-407e-8c42-ded2e45e8d5c
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Prepare for Zero Touch Installation of Windows 10 with Configuration Manager (Windows 10)
|
||||
title: Prepare for Zero Touch Installation of Windows 10 with Configuration Manager
|
||||
description: Learn how to prepare a Zero Touch Installation of Windows 10 with Configuration Manager, by integrating Configuration Manager with Microsoft Deployment Toolkit.
|
||||
ms.assetid: 06e3a221-31ef-47a5-b4da-3b927cb50d08
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Prepare for Zero Touch Installation of Windows 10 with Configuration Manager
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager (Windows 10)
|
||||
title: Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
description: Learn how to use Configuration Manager and Microsoft Deployment Toolkit (MDT) to refresh a Windows 7 SP1 client with Windows 10.
|
||||
ms.assetid: 57c81667-1019-4711-b3de-15ae9c5387c7
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager (Windows 10)
|
||||
title: Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
description: In this topic, you will learn how to replacing a Windows 7 SP1 computer using Microsoft Endpoint Configuration Manager.
|
||||
ms.assetid: 3c8a2d53-8f08-475f-923a-bca79ca8ac36
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista (Windows 10)
|
||||
title: Compatibility Fixes for Windows 10, Windows 8, Windows 7, & Windows Vista
|
||||
description: Find compatibility fixes for all Windows operating systems that have been released from Windows Vista through Windows 10.
|
||||
ms.assetid: cd51c824-557f-462a-83bb-54b0771b7dff
|
||||
ms.reviewer:
|
||||
@ -13,6 +13,7 @@ audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.date: 04/19/2017
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista
|
||||
@ -75,7 +76,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>BIOSRead</p></td>
|
||||
<td align="left"><p>This problem is indicated when an application cannot access the <strong>Device\PhysicalMemory</strong> object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems.</p>
|
||||
<td align="left"><p>This problem is indicated when an application cannot access the <strong>Device\PhysicalMemory</strong> object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems.</p>
|
||||
<p>The fix enables OEM executable (.exe) files to use the GetSystemFirmwareTable function instead of the NtOpenSection function when the BIOS is queried for the <strong>\Device\Physical</strong> memory information..</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -92,7 +93,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<tr class="even">
|
||||
<td align="left"><p>ChangeFolderPathToXPStyle</p></td>
|
||||
<td align="left"><p>This fix is required when an application cannot return shell folder paths when it uses the <strong>SHGetFolder</strong> API.</p>
|
||||
<p>The fix intercepts the <strong>SHGetFolder</strong> path request to the common <strong>appdata</strong> file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path.</p></td>
|
||||
<p>The fix intercepts the <strong>SHGetFolder</strong> path request to the common <strong>appdata</strong> file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ClearLastErrorStatusonIntializeCriticalSection</p></td>
|
||||
@ -188,7 +189,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>DirectXVersionLie</p></td>
|
||||
<td align="left"><p>This problem occurs when an application fails because it does not find the correct version number for DirectX®.</p>
|
||||
<td align="left"><p>This problem occurs when an application fails because it does not find the correct version number for DirectX®.</p>
|
||||
<p>The fix modifies the DXDIAGN GetProp function call to return the correct DirectX version.</p>
|
||||
<p>You can control this fix further by typing the following command at the command prompt:</p>
|
||||
<p>MAJORVERSION.MINORVERSION.LETTER</p>
|
||||
@ -456,7 +457,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<tr class="odd">
|
||||
<td align="left"><p>IgnoreMSOXMLMF</p></td>
|
||||
<td align="left"><p>The problem is indicated by an error message that states that the operating system cannot locate the MSVCR80D.DLL file.</p>
|
||||
<p>The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system any time that you load an XML file, and then it fails the CoGetClassObject for its CLSID. This compatibility fix will just ignore the registered MSOXMLMF and fail the CoGetClassObject for its CLSID.</p></td>
|
||||
<p>The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system any time that you load an XML file, and then it fails the CoGetClassObject for its CLSID. This compatibility fix will just ignore the registered MSOXMLMF and fail the CoGetClassObject for its CLSID.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>IgnoreSetROP2</p></td>
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Best practices and recommendations for deploying Windows 10 Feature updates to mission-critical devices
|
||||
title: Best practices for deploying Windows 10 Feature updates to mission critical devices
|
||||
description: Learn how to deploy feature updates to your mission-critical devices
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -12,13 +12,14 @@ ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Best practices and recommendations for deploying Windows 10 Feature updates to mission critical devices
|
||||
|
||||
**Applies to**: Windows 10
|
||||
|
||||
Managing an environment with devices that provide mission critical services 24 hours a day, 7 days a week, can present challenges in keeping these devices current with Windows 10 feature updates. The processes that you use to keep regular devices current with Windows 10 feature updates, often aren’t the most effective to service mission critical devices. This whitepaper will focus on the recommended approach of using the Microsoft Endpoint Configuration Manager (current branch) software updates feature to deploy Windows 10 semi-annual feature updates.
|
||||
Managing an environment with devices that provide mission critical services 24 hours a day, 7 days a week, can present challenges in keeping these devices current with Windows 10 feature updates. The processes that you use to keep regular devices current with Windows 10 feature updates, often aren't the most effective to service mission critical devices. This whitepaper will focus on the recommended approach of using the Microsoft Endpoint Configuration Manager (current branch) software updates feature to deploy Windows 10 semi-annual feature updates.
|
||||
|
||||
For simplicity, we will outline the steps to deploy a feature update manually. If you prefer an automated approach, see [Manage Windows as a service using Configuration Manager](https://docs.microsoft.com/configmgr/osd/deploy-use/manage-windows-as-a-service).
|
||||
|
||||
|
||||
@ -1,9 +1,8 @@
|
||||
---
|
||||
title: Windows 10 - How to make FoD and language packs available when you're using WSUS/SCCM
|
||||
title: Make FoD and language packs available for WSUS/SCCM (Windows 10)
|
||||
description: Learn how to make FoD and language packs available when you're using WSUS/SCCM
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
ms.pagetype: article
|
||||
ms.author: jaimeo
|
||||
audience: itpro
|
||||
@ -13,6 +12,7 @@ ms.date: 03/13/2019
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
# How to make Features on Demand and language packs available when you're using WSUS/SCCM
|
||||
|
||||
@ -20,11 +20,11 @@ ms.topic: article
|
||||
|
||||
As of Windows 10 version 1709, you can't use Windows Server Update Services (WSUS) to host [Features on Demand](https://docs.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) (FODs) locally. Starting with Windows 10 version 1803, language packs can no longer be hosted on WSUS.
|
||||
|
||||
The **Specify settings for optional component installation and component repair** policy, located under `Computer Configuration\Administrative Templates\System` in the Group Policy Editor, can be used to specify alternate ways to acquire FOD packages, language packages, and content for corruption repair. However, it’s important to note this policy only allows specifying one alternate location and behaves differently across OS versions.
|
||||
The **Specify settings for optional component installation and component repair** policy, located under `Computer Configuration\Administrative Templates\System` in the Group Policy Editor, can be used to specify alternate ways to acquire FOD packages, language packages, and content for corruption repair. However, it's important to note this policy only allows specifying one alternate location and behaves differently across OS versions.
|
||||
|
||||
In Windows 10 version 1709 and 1803, changing the **Specify settings for optional component installation and component repair** policy to download content from Windows Update enables acquisition of FOD packages while also enabling corruption repair. Specifying a network location works for either, depending on the content is found at that location. Changing this policy on these OS versions does not influence how language packs are acquired.
|
||||
|
||||
In Windows 10 version 1809 and beyond, changing the **Specify settings for optional component installation and component repair** policy also influences how language packs are acquired, however language packs can only be acquired directly from Windows Update. It’s currently not possible to acquire them from a network share. Specifying a network location works for FOD packages or corruption repair, depending on the content at that location.
|
||||
In Windows 10 version 1809 and beyond, changing the **Specify settings for optional component installation and component repair** policy also influences how language packs are acquired, however language packs can only be acquired directly from Windows Update. It's currently not possible to acquire them from a network share. Specifying a network location works for FOD packages or corruption repair, depending on the content at that location.
|
||||
|
||||
For all OS versions, changing the **Specify settings for optional component installation and component repair** policy does not affect how OS updates are distributed. They continue to come from WSUS or SCCM or other sources as you have scheduled them, even while optional content is sourced from Windows Update or a network location.
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Monitor Windows Updates and Windows Defender AV with Update Compliance (Windows 10)
|
||||
title: Monitor Windows 10 Updates & Windows Defender AV with Update Compliance
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
description: You can use Update Compliance in Azure Portal to monitor the progress of updates and key antimalware protection features on devices in your network.
|
||||
@ -13,6 +13,7 @@ ms.author: jaimeo
|
||||
ms.localizationpriority: medium
|
||||
ms.collection: M365-analytics
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# Monitor Windows Updates with Update Compliance
|
||||
|
||||
Reference in New Issue
Block a user