mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
another 30 titles
This commit is contained in:
martyav
parent
2b951b3d00
commit
7737ac88fa
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to apply the deployment configuration file by using Windows PowerShell (Windows 10)
|
||||
title: Apply a deployment config file via Windows PowerShell (Windows 10)
|
||||
description: How to apply the deployment configuration file by using Windows PowerShell for Windows 10.
|
||||
author: dansimp
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Implement server-side support for mobile application management on Windows
|
||||
title: Provide server-side support for mobile app management on Windows
|
||||
description: The Windows version of mobile application management (MAM) is a lightweight solution for managing company data access and security on personal devices. MAM support is built into Windows on top of Windows Information Protection (WIP).
|
||||
ms.author: dansimp
|
||||
ms.topic: article
|
||||
|
||||
@ -1,107 +1,108 @@
|
||||
---
|
||||
title: Create an application to deploy with Windows 10 using Configuration Manager (Windows 10)
|
||||
description: Microsoft System Center 2012 R2 Configuration Manager supports deploying applications as part of the Windows 10 deployment process.
|
||||
ms.assetid: 2dfb2f39-1597-4999-b4ec-b063e8a8c90c
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: deployment, task sequence, custom, customize
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Create an application to deploy with Windows 10 using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 versions 1507, 1511
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see [Scenarios to deploy enterprise operating systems with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems).
|
||||
>Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see [Support for Windows 10 for System Center Configuration Manager](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10).
|
||||
|
||||
Microsoft System Center 2012 R2 Configuration Manager supports deploying applications as part of the Windows 10 deployment process. In this section, you create an application in System Center 2012 R2 Configuration Manager that you later configure the task sequence to use.
|
||||
|
||||
For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard that is a member of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
>[!NOTE]
|
||||
>Even though the new application model is fully supported to deploy via the task sequence, the most reliable way to deploy software via the task sequence is still the legacy packages, especially if you deploy many applications.
|
||||
|
||||
## Example: Create the Adobe Reader XI application
|
||||
|
||||
|
||||
The following steps show you how to create the Adobe Reader XI application. This section assumes that you have downloaded the MSI version of Adobe Reader XI to the C:\\Setup\\Adobe Reader XI folder on CM01.
|
||||
|
||||
1. On CM01, using File Explorer, copy the **C:\\Setup\\Adobe Reader XI** folder to the **E:\\Sources\\Software\\Adobe** folder.
|
||||
|
||||
2. Using the Configuration Manager Console, in the Software Library workspace, expand **Application Management**.
|
||||
|
||||
3. Right-click **Applications** and select **Folder / Create Folder**. Assign the name **OSD**.
|
||||
|
||||
4. Right-click the **OSD** folder, and select **Create Application**.
|
||||
|
||||
5. In the Create Application Wizard, on the **General** page, use the following settings:
|
||||
|
||||
* Automatically detect information about this application from installation files
|
||||
|
||||
* Type: Windows Installer (\*.msi file)
|
||||
|
||||
* Location: \\\\CM01\\Sources$\\Software\\Adobe\\Adobe Reader XI
|
||||
|
||||
* \\AdbeRdr11000\_en\_US.msi
|
||||
|
||||
|
||||
|
||||
*Figure 19. The Create Application Wizard*
|
||||
|
||||
6. Click **Next**, and wait while Configuration Manager parses the MSI file.
|
||||
|
||||
7. On the **Import Information** page, review the information and then click **Next**.
|
||||
|
||||
8. On the **General Information** page, name the application Adobe Reader XI - OSD Install, click **Next** twice, and then click **Close**.
|
||||
|
||||
>[!NOTE]
|
||||
>Because it is not possible to reference an application deployment type in the task sequence, you should have a single deployment type for applications deployed by the task sequence. If you are deploying applications via both the task sequence and normal application deployment, and you have multiple deployment types, you should have two applications of the same software. In this section, you add the "OSD Install" suffix to applications that are deployed via the task sequence. If using packages, you can still reference both package and program in the task sequence.
|
||||
|
||||
|
||||
|
||||
*Figure 20. Add the "OSD Install" suffix to the application name*
|
||||
|
||||
9. In the **Applications** node, select the Adobe Reader XI - OSD Install application, and click **Properties** on the ribbon bar.
|
||||
|
||||
10. In the **General Information** tab, select the **Allow this application to be installed from the Install Application task sequence action without being deployed** check box, and click **OK**.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Create an app to deploy with Windows 10 using Configuration Manager
|
||||
description: Microsoft System Center 2012 R2 Configuration Manager supports deploying applications as part of the Windows 10 deployment process.
|
||||
ms.assetid: 2dfb2f39-1597-4999-b4ec-b063e8a8c90c
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: deployment, task sequence, custom, customize
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Create an application to deploy with Windows 10 using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10 versions 1507, 1511
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see [Scenarios to deploy enterprise operating systems with System Center Configuration Manager](https://docs.microsoft.com/sccm/osd/deploy-use/scenarios-to-deploy-enterprise-operating-systems).
|
||||
>Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see [Support for Windows 10 for System Center Configuration Manager](https://docs.microsoft.com/sccm/core/plan-design/configs/support-for-windows-10).
|
||||
|
||||
Microsoft System Center 2012 R2 Configuration Manager supports deploying applications as part of the Windows 10 deployment process. In this section, you create an application in System Center 2012 R2 Configuration Manager that you later configure the task sequence to use.
|
||||
|
||||
For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard that is a member of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
>[!NOTE]
|
||||
>Even though the new application model is fully supported to deploy via the task sequence, the most reliable way to deploy software via the task sequence is still the legacy packages, especially if you deploy many applications.
|
||||
|
||||
## Example: Create the Adobe Reader XI application
|
||||
|
||||
|
||||
The following steps show you how to create the Adobe Reader XI application. This section assumes that you have downloaded the MSI version of Adobe Reader XI to the C:\\Setup\\Adobe Reader XI folder on CM01.
|
||||
|
||||
1. On CM01, using File Explorer, copy the **C:\\Setup\\Adobe Reader XI** folder to the **E:\\Sources\\Software\\Adobe** folder.
|
||||
|
||||
2. Using the Configuration Manager Console, in the Software Library workspace, expand **Application Management**.
|
||||
|
||||
3. Right-click **Applications** and select **Folder / Create Folder**. Assign the name **OSD**.
|
||||
|
||||
4. Right-click the **OSD** folder, and select **Create Application**.
|
||||
|
||||
5. In the Create Application Wizard, on the **General** page, use the following settings:
|
||||
|
||||
* Automatically detect information about this application from installation files
|
||||
|
||||
* Type: Windows Installer (\*.msi file)
|
||||
|
||||
* Location: \\\\CM01\\Sources$\\Software\\Adobe\\Adobe Reader XI
|
||||
|
||||
* \\AdbeRdr11000\_en\_US.msi
|
||||
|
||||
|
||||
|
||||
*Figure 19. The Create Application Wizard*
|
||||
|
||||
6. Click **Next**, and wait while Configuration Manager parses the MSI file.
|
||||
|
||||
7. On the **Import Information** page, review the information and then click **Next**.
|
||||
|
||||
8. On the **General Information** page, name the application Adobe Reader XI - OSD Install, click **Next** twice, and then click **Close**.
|
||||
|
||||
>[!NOTE]
|
||||
>Because it is not possible to reference an application deployment type in the task sequence, you should have a single deployment type for applications deployed by the task sequence. If you are deploying applications via both the task sequence and normal application deployment, and you have multiple deployment types, you should have two applications of the same software. In this section, you add the "OSD Install" suffix to applications that are deployed via the task sequence. If using packages, you can still reference both package and program in the task sequence.
|
||||
|
||||
|
||||
|
||||
*Figure 20. Add the "OSD Install" suffix to the application name*
|
||||
|
||||
9. In the **Applications** node, select the Adobe Reader XI - OSD Install application, and click **Properties** on the ribbon bar.
|
||||
|
||||
10. In the **General Information** tab, select the **Allow this application to be installed from the Install Application task sequence action without being deployed** check box, and click **OK**.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](../deploy-windows-mdt/integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Create a task sequence with Configuration Manager and MDT](../deploy-windows-mdt/create-a-task-sequence-with-configuration-manager-and-mdt.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Installing and Uninstalling Custom Compatibility Databases in Compatibility Administrator (Windows 10)
|
||||
title: Using Compatibility Administrator to Install/Uninstall Custom Databases (Windows 10)
|
||||
description: The Compatibility Administrator tool enables the creation and the use of custom-compatibility and standard-compatibility databases.
|
||||
ms.assetid: 659c9d62-5f32-433d-94aa-12141c01368f
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Deploy Windows 10 updates using System Center Configuration Manager (Windows 10)
|
||||
title: Deploy Windows 10 updates via System Center Configuration Manager
|
||||
description: System Center Configuration Manager provides maximum control over quality and feature updates for Windows 10.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Walkthrough use Group Policy to configure Windows Update for Business - Windows 10
|
||||
description: Configure Windows Update for Business settings using Group Policy.
|
||||
title: Configure Windows Update for Business via Group Policy (Windows 10)
|
||||
description: Walkthrough demonstrating how to configure Windows Update for Business settings, using Group Policy.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
author: jaimeo
|
||||
@ -11,7 +11,7 @@ manager: laurawi
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Walkthrough: use Group Policy to configure Windows Update for Business
|
||||
# Walkthrough: Use Group Policy to configure Windows Update for Business
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
@ -1,216 +1,217 @@
|
||||
---
|
||||
title: Perform an in-place upgrade to Windows 10 using Configuration Manager (Windows 10)
|
||||
description: The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. Use a System Center Configuration Manager task sequence to completely automate the process.
|
||||
ms.assetid: F8DF6191-0DB0-4EF5-A9B1-6A11D5DE4878
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: upgrade, update, task sequence, deploy
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
ms.mktglfcycl: deploy
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Perform an in-place upgrade to Windows 10 using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process.
|
||||
|
||||
## Proof-of-concept environment
|
||||
|
||||
|
||||
For the purposes of this topic, we will use three machines: DC01, CM01, and PC0001. DC01 is a domain controller and CM01 is a Windows Server 2012 R2 standard machine, fully patched with the latest security updates, and configured as a member server in the fictional contoso.com domain. PC0001 is a machine with Windows 7 SP1, targeted for the Windows 10 upgrade. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
|
||||
|
||||
Figure 1. The machines used in this topic.
|
||||
|
||||
## Upgrade to Windows 10 with System Center 2012 R2 Configuration Manager
|
||||
|
||||
|
||||
System Center 2012 R2 Configuration Manager SP1 adds support to manage and deploy Windows 10. Although it does not include built-in support to perform an in-place upgrade from Windows 7, Windows 8, or Windows 8.1 to Windows 10, you can build a custom task sequence to perform the necessary tasks.
|
||||
|
||||
## Create the task sequence
|
||||
|
||||
|
||||
To help with this process, the Configuration Manager team has published [a blog](https://go.microsoft.com/fwlink/p/?LinkId=620179) that provides a sample task sequence, as well as the [original blog that includes the instructions for setting up the task sequence](https://go.microsoft.com/fwlink/p/?LinkId=620180). To summarize, here are the tasks you need to perform:
|
||||
|
||||
1. Download the [Windows10Upgrade1506.zip](https://go.microsoft.com/fwlink/p/?LinkId=620182) file that contains the sample task sequence and related scripts. Extract the contents onto a network share.
|
||||
2. Copy the Windows 10 Enterprise RTM x64 media into the extracted but empty **Windows vNext Upgrade Media** folder.
|
||||
3. Using the Configuration Manager Console, right-click the **Task Sequences** node, and then choose **Import Task Sequence**. Select the **Windows-vNextUpgradeExport.zip** file that you extracted in Step 1.
|
||||
4. Distribute the two created packages (one contains the Windows 10 Enterprise x64 media, the other contains the related scripts) to the Configuration Manager distribution point.
|
||||
|
||||
For full details and an explanation of the task sequence steps, review the full details of the two blogs that are referenced above.
|
||||
|
||||
## Create a device collection
|
||||
|
||||
|
||||
After you create the upgrade task sequence, you can create a collection to test a deployment. In this section, we assume you have the PC0001 machine running Windows 7 SP1, with the Configuration Manager client installed.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
- General
|
||||
|
||||
- Name: Windows 10 Enterprise x64 Upgrade
|
||||
|
||||
- Limited Collection: All Systems
|
||||
|
||||
- Membership rules:
|
||||
|
||||
- Direct rule
|
||||
|
||||
- Resource Class: System Resource
|
||||
|
||||
- Attribute Name: Name
|
||||
|
||||
- Value: PC0001
|
||||
|
||||
- Select Resources
|
||||
|
||||
- Select PC0001
|
||||
|
||||
2. Review the Windows 10 Enterprise x64 Upgrade collection. Do not continue until you see the PC0001 machine in the collection.
|
||||
|
||||
## Deploy the Windows 10 upgrade
|
||||
|
||||
|
||||
In this section, you create a deployment for the Windows 10 Enterprise x64 Update application.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Software Library workspace, right-click the **Windows vNext Upgrade** task sequence, and then select **Deploy**.
|
||||
2. On the **General** page, select the **Windows 10 Enterprise x64 Upgrade** collection, and then click **Next**.
|
||||
3. On the **Content** page, click **Next**.
|
||||
4. On the **Deployment Settings** page, select the following settings, and then click **Next**:
|
||||
- Action: Install
|
||||
|
||||
- Purpose: Available
|
||||
|
||||
5. On the **Scheduling** page, accept the default settings, and then click **Next**.
|
||||
6. On the **User Experience** page, accept the default settings, and then click **Next**.
|
||||
7. On the **Alerts** page, accept the default settings, and then click **Next**.
|
||||
8. On the **Summary** page, click **Next**, and then click **Close**.
|
||||
|
||||
## Start the Windows 10 upgrade
|
||||
|
||||
|
||||
In this section, you start the Windows 10 Upgrade task sequence on PC0001 (currently running Windows 7 SP1).
|
||||
|
||||
1. On PC0001, start the **Software Center**.
|
||||
2. Select the **Windows vNext Upgrade** task sequence, and then click **Install**.
|
||||
|
||||
When the task sequence begins, it will automatically initiate the in-place upgrade process by invoking the Windows setup program (Setup.exe) with the necessary command-line parameters to perform an automated upgrade, which preserves all data, settings, apps, and drivers.
|
||||
|
||||
|
||||
|
||||
Figure 2. Upgrade from Windows 7 to Windows 10 Enterprise x64 with a task sequence.
|
||||
|
||||
After the task sequence finishes, the computer will be fully upgraded to Windows 10.
|
||||
|
||||
## Upgrade to Windows 10 with System Center Configuration Manager Current Branch
|
||||
|
||||
|
||||
With System Center Configuration Manager Current Branch, new built-in functionality makes it easier to upgrade to Windows 10.
|
||||
|
||||
**Note**
|
||||
For more details about Configuration Manager Current Branch, see the [Configuration Manager Team blog](https://go.microsoft.com/fwlink/p/?LinkId=620205). An [evaluation version is currently available](https://go.microsoft.com/fwlink/p/?LinkId=620206) for you to try. The instructions below are specific to the Technical Preview 2 release and may change after the next version of Configuration Manager is released.
|
||||
|
||||
|
||||
|
||||
### Create the OS upgrade package
|
||||
|
||||
First, you need to create an operating system upgrade package that contains the full Windows 10 Enterprise x64 installation media.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Software Library workspace, right-click the **Operating System Upgrade Packages** node, then select **Add Operating System Upgrade Package**.
|
||||
2. On the **Data Source** page, specify the UNC path to the Windows 10 Enterprise x64 media, and then click **Next**.
|
||||
3. On the **General** page, specify Windows 10 Enterprise x64 Upgrade, and then click **Next**.
|
||||
4. On the **Summary** page, click **Next**, and then click **Close**.
|
||||
5. Right-click the created **Windows 10 Enterprise x64 Update** package, and then select **Distribute Content**. Choose the CM01 distribution point.
|
||||
|
||||
### Create the task sequence
|
||||
|
||||
To create an upgrade task sequence, perform the following steps:
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Software Library workspace, right-click the **Task Sequences** node, and then select **Create Task Sequence**.
|
||||
2. On the **Create a new task sequence** page, select **Upgrade an operating system from upgrade package**, and then click **Next**.
|
||||
3. On the **Task Sequence Information** page, specify **Windows 10 Enterprise x64 Upgrade**, and then click **Next**.
|
||||
4. On the **Upgrade the Windows operating system** page, select the **Windows 10 Enterprise x64 Upgrade operating system upgrade** package, and then click **Next**.
|
||||
5. Click **Next** through the remaining wizard pages, and then click **Close**.
|
||||
|
||||
|
||||
|
||||
Figure 3. The Configuration Manager upgrade task sequence.
|
||||
|
||||
### Create a device collection
|
||||
|
||||
After you create the upgrade task sequence, you can create a collection to test a deployment. In this section, we assume you have the PC0001 machine running Windows 7 SP1, with the next version of System Center Configuration Manager client installed.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
- General
|
||||
|
||||
- Name: Windows 10 Enterprise x64 Upgrade
|
||||
|
||||
- Limited Collection: All Systems
|
||||
|
||||
- Membership rules:
|
||||
|
||||
- Direct rule
|
||||
|
||||
- Resource Class: System Resource
|
||||
|
||||
- Attribute Name: Name
|
||||
|
||||
- Value: PC0001
|
||||
|
||||
- Select Resources
|
||||
|
||||
- Select PC0001
|
||||
|
||||
2. Review the Windows 10 Enterprise x64 Upgrade collection. Do not continue until you see the PC0001 machine in the collection.
|
||||
|
||||
### Deploy the Windows 10 upgrade
|
||||
|
||||
In this section, you create a deployment for the Windows 10 Enterprise x64 Update application.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Software Library workspace, right-click the **Windows vNext Upgrade** task sequence, and then select **Deploy**.
|
||||
2. On the **General** page, select the **Windows 10 Enterprise x64 Upgrade** collection, and then click **Next**.
|
||||
3. On the **Content** page, click **Next**.
|
||||
4. On the **Deployment Settings** page, select the following settings and click **Next**:
|
||||
- Action: Install
|
||||
|
||||
- Purpose: Available
|
||||
|
||||
5. On the **Scheduling** page, accept the default settings, and then click **Next**.
|
||||
6. On the **User Experience** page, accept the default settings, and then click **Next**.
|
||||
7. On the **Alerts** page, accept the default settings, and then click **Next**.
|
||||
8. On the **Summary** page, click **Next**, and then click **Close**.
|
||||
|
||||
### Start the Windows 10 upgrade
|
||||
|
||||
In this section, you start the Windows 10 Upgrade task sequence on PC0001 (currently running Windows 7 SP1).
|
||||
|
||||
1. On PC0001, start the **Software Center**.
|
||||
2. Select the **Windows 10 Enterprise x64 Upgrade** task sequence, and then click **Install.**
|
||||
|
||||
When the task sequence begins, it automatically initiates the in-place upgrade process by invoking the Windows setup program (Setup.exe) with the necessary command-line parameters to perform an automated upgrade, which preserves all data, settings, apps, and drivers.
|
||||
|
||||
After the task sequence completes, the computer will be fully upgraded to Windows 10.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Windows 10 deployment scenarios](../windows-10-deployment-scenarios.md)
|
||||
|
||||
[Configuration Manager Team blog](https://go.microsoft.com/fwlink/p/?LinkId=620109)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
title: Perform in-place upgrade to Windows 10 via Configuration Manager
|
||||
description: The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. Use a System Center Configuration Manager task sequence to completely automate the process.
|
||||
ms.assetid: F8DF6191-0DB0-4EF5-A9B1-6A11D5DE4878
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: upgrade, update, task sequence, deploy
|
||||
ms.prod: w10
|
||||
ms.localizationpriority: medium
|
||||
ms.mktglfcycl: deploy
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Perform an in-place upgrade to Windows 10 using Configuration Manager
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process.
|
||||
|
||||
## Proof-of-concept environment
|
||||
|
||||
|
||||
For the purposes of this topic, we will use three machines: DC01, CM01, and PC0001. DC01 is a domain controller and CM01 is a Windows Server 2012 R2 standard machine, fully patched with the latest security updates, and configured as a member server in the fictional contoso.com domain. PC0001 is a machine with Windows 7 SP1, targeted for the Windows 10 upgrade. For more details on the setup for this topic, please see [Deploy Windows 10 with the Microsoft Deployment Toolkit](../deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
|
||||
|
||||
Figure 1. The machines used in this topic.
|
||||
|
||||
## Upgrade to Windows 10 with System Center 2012 R2 Configuration Manager
|
||||
|
||||
|
||||
System Center 2012 R2 Configuration Manager SP1 adds support to manage and deploy Windows 10. Although it does not include built-in support to perform an in-place upgrade from Windows 7, Windows 8, or Windows 8.1 to Windows 10, you can build a custom task sequence to perform the necessary tasks.
|
||||
|
||||
## Create the task sequence
|
||||
|
||||
|
||||
To help with this process, the Configuration Manager team has published [a blog](https://go.microsoft.com/fwlink/p/?LinkId=620179) that provides a sample task sequence, as well as the [original blog that includes the instructions for setting up the task sequence](https://go.microsoft.com/fwlink/p/?LinkId=620180). To summarize, here are the tasks you need to perform:
|
||||
|
||||
1. Download the [Windows10Upgrade1506.zip](https://go.microsoft.com/fwlink/p/?LinkId=620182) file that contains the sample task sequence and related scripts. Extract the contents onto a network share.
|
||||
2. Copy the Windows 10 Enterprise RTM x64 media into the extracted but empty **Windows vNext Upgrade Media** folder.
|
||||
3. Using the Configuration Manager Console, right-click the **Task Sequences** node, and then choose **Import Task Sequence**. Select the **Windows-vNextUpgradeExport.zip** file that you extracted in Step 1.
|
||||
4. Distribute the two created packages (one contains the Windows 10 Enterprise x64 media, the other contains the related scripts) to the Configuration Manager distribution point.
|
||||
|
||||
For full details and an explanation of the task sequence steps, review the full details of the two blogs that are referenced above.
|
||||
|
||||
## Create a device collection
|
||||
|
||||
|
||||
After you create the upgrade task sequence, you can create a collection to test a deployment. In this section, we assume you have the PC0001 machine running Windows 7 SP1, with the Configuration Manager client installed.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
- General
|
||||
|
||||
- Name: Windows 10 Enterprise x64 Upgrade
|
||||
|
||||
- Limited Collection: All Systems
|
||||
|
||||
- Membership rules:
|
||||
|
||||
- Direct rule
|
||||
|
||||
- Resource Class: System Resource
|
||||
|
||||
- Attribute Name: Name
|
||||
|
||||
- Value: PC0001
|
||||
|
||||
- Select Resources
|
||||
|
||||
- Select PC0001
|
||||
|
||||
2. Review the Windows 10 Enterprise x64 Upgrade collection. Do not continue until you see the PC0001 machine in the collection.
|
||||
|
||||
## Deploy the Windows 10 upgrade
|
||||
|
||||
|
||||
In this section, you create a deployment for the Windows 10 Enterprise x64 Update application.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Software Library workspace, right-click the **Windows vNext Upgrade** task sequence, and then select **Deploy**.
|
||||
2. On the **General** page, select the **Windows 10 Enterprise x64 Upgrade** collection, and then click **Next**.
|
||||
3. On the **Content** page, click **Next**.
|
||||
4. On the **Deployment Settings** page, select the following settings, and then click **Next**:
|
||||
- Action: Install
|
||||
|
||||
- Purpose: Available
|
||||
|
||||
5. On the **Scheduling** page, accept the default settings, and then click **Next**.
|
||||
6. On the **User Experience** page, accept the default settings, and then click **Next**.
|
||||
7. On the **Alerts** page, accept the default settings, and then click **Next**.
|
||||
8. On the **Summary** page, click **Next**, and then click **Close**.
|
||||
|
||||
## Start the Windows 10 upgrade
|
||||
|
||||
|
||||
In this section, you start the Windows 10 Upgrade task sequence on PC0001 (currently running Windows 7 SP1).
|
||||
|
||||
1. On PC0001, start the **Software Center**.
|
||||
2. Select the **Windows vNext Upgrade** task sequence, and then click **Install**.
|
||||
|
||||
When the task sequence begins, it will automatically initiate the in-place upgrade process by invoking the Windows setup program (Setup.exe) with the necessary command-line parameters to perform an automated upgrade, which preserves all data, settings, apps, and drivers.
|
||||
|
||||
|
||||
|
||||
Figure 2. Upgrade from Windows 7 to Windows 10 Enterprise x64 with a task sequence.
|
||||
|
||||
After the task sequence finishes, the computer will be fully upgraded to Windows 10.
|
||||
|
||||
## Upgrade to Windows 10 with System Center Configuration Manager Current Branch
|
||||
|
||||
|
||||
With System Center Configuration Manager Current Branch, new built-in functionality makes it easier to upgrade to Windows 10.
|
||||
|
||||
**Note**
|
||||
For more details about Configuration Manager Current Branch, see the [Configuration Manager Team blog](https://go.microsoft.com/fwlink/p/?LinkId=620205). An [evaluation version is currently available](https://go.microsoft.com/fwlink/p/?LinkId=620206) for you to try. The instructions below are specific to the Technical Preview 2 release and may change after the next version of Configuration Manager is released.
|
||||
|
||||
|
||||
|
||||
### Create the OS upgrade package
|
||||
|
||||
First, you need to create an operating system upgrade package that contains the full Windows 10 Enterprise x64 installation media.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Software Library workspace, right-click the **Operating System Upgrade Packages** node, then select **Add Operating System Upgrade Package**.
|
||||
2. On the **Data Source** page, specify the UNC path to the Windows 10 Enterprise x64 media, and then click **Next**.
|
||||
3. On the **General** page, specify Windows 10 Enterprise x64 Upgrade, and then click **Next**.
|
||||
4. On the **Summary** page, click **Next**, and then click **Close**.
|
||||
5. Right-click the created **Windows 10 Enterprise x64 Update** package, and then select **Distribute Content**. Choose the CM01 distribution point.
|
||||
|
||||
### Create the task sequence
|
||||
|
||||
To create an upgrade task sequence, perform the following steps:
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Software Library workspace, right-click the **Task Sequences** node, and then select **Create Task Sequence**.
|
||||
2. On the **Create a new task sequence** page, select **Upgrade an operating system from upgrade package**, and then click **Next**.
|
||||
3. On the **Task Sequence Information** page, specify **Windows 10 Enterprise x64 Upgrade**, and then click **Next**.
|
||||
4. On the **Upgrade the Windows operating system** page, select the **Windows 10 Enterprise x64 Upgrade operating system upgrade** package, and then click **Next**.
|
||||
5. Click **Next** through the remaining wizard pages, and then click **Close**.
|
||||
|
||||
|
||||
|
||||
Figure 3. The Configuration Manager upgrade task sequence.
|
||||
|
||||
### Create a device collection
|
||||
|
||||
After you create the upgrade task sequence, you can create a collection to test a deployment. In this section, we assume you have the PC0001 machine running Windows 7 SP1, with the next version of System Center Configuration Manager client installed.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections**, and then select **Create Device Collection**. Use the following settings:
|
||||
- General
|
||||
|
||||
- Name: Windows 10 Enterprise x64 Upgrade
|
||||
|
||||
- Limited Collection: All Systems
|
||||
|
||||
- Membership rules:
|
||||
|
||||
- Direct rule
|
||||
|
||||
- Resource Class: System Resource
|
||||
|
||||
- Attribute Name: Name
|
||||
|
||||
- Value: PC0001
|
||||
|
||||
- Select Resources
|
||||
|
||||
- Select PC0001
|
||||
|
||||
2. Review the Windows 10 Enterprise x64 Upgrade collection. Do not continue until you see the PC0001 machine in the collection.
|
||||
|
||||
### Deploy the Windows 10 upgrade
|
||||
|
||||
In this section, you create a deployment for the Windows 10 Enterprise x64 Update application.
|
||||
|
||||
1. On CM01, using the Configuration Manager console, in the Software Library workspace, right-click the **Windows vNext Upgrade** task sequence, and then select **Deploy**.
|
||||
2. On the **General** page, select the **Windows 10 Enterprise x64 Upgrade** collection, and then click **Next**.
|
||||
3. On the **Content** page, click **Next**.
|
||||
4. On the **Deployment Settings** page, select the following settings and click **Next**:
|
||||
- Action: Install
|
||||
|
||||
- Purpose: Available
|
||||
|
||||
5. On the **Scheduling** page, accept the default settings, and then click **Next**.
|
||||
6. On the **User Experience** page, accept the default settings, and then click **Next**.
|
||||
7. On the **Alerts** page, accept the default settings, and then click **Next**.
|
||||
8. On the **Summary** page, click **Next**, and then click **Close**.
|
||||
|
||||
### Start the Windows 10 upgrade
|
||||
|
||||
In this section, you start the Windows 10 Upgrade task sequence on PC0001 (currently running Windows 7 SP1).
|
||||
|
||||
1. On PC0001, start the **Software Center**.
|
||||
2. Select the **Windows 10 Enterprise x64 Upgrade** task sequence, and then click **Install.**
|
||||
|
||||
When the task sequence begins, it automatically initiates the in-place upgrade process by invoking the Windows setup program (Setup.exe) with the necessary command-line parameters to perform an automated upgrade, which preserves all data, settings, apps, and drivers.
|
||||
|
||||
After the task sequence completes, the computer will be fully upgraded to Windows 10.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Windows 10 deployment scenarios](../windows-10-deployment-scenarios.md)
|
||||
|
||||
[Configuration Manager Team blog](https://go.microsoft.com/fwlink/p/?LinkId=620109)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Prepare and Deploy Windows Server 2016 Active Directory Federation Services (Windows Hello for Business)
|
||||
description: How toPrepare and Deploy Windows Server 2016 Active Directory Federation Services for Windows Hello for Business
|
||||
title: Prepare & Deploy Windows Active Directory Federation Services (Windows Hello for Business)
|
||||
description: How to Prepare and Deploy Windows Server 2016 Active Directory Federation Services for Windows Hello for Business
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Configuring Hybrid Windows Hello for Business - Directory Synchronization
|
||||
title: Configure Hybrid Windows Hello for Business Directory Synch
|
||||
description: Discussing Directory Synchronization in a Hybrid deployment of Windows Hello for Business
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, dirsync, connect
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows Hello for Business Key Trust New Installation (Windows Hello for Business)
|
||||
title: Windows Hello for Business Key Trust New Installation
|
||||
description: Windows Hello for Business Hybrid baseline deployment
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Configuring Hybrid key trust Windows Hello for Business - Public Key Infrastructure (PKI)
|
||||
title: Configure Hybrid key trust Windows Hello for Business
|
||||
description: Configuring Hybrid key trust Windows Hello for Business - Public Key Infrastructure (PKI)
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, PKI, Windows Hello, key trust, key-trust
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Prepare and Deploy Windows Server 2016 Active Directory Federation Services (Windows Hello for Business)
|
||||
description: How toPrepare and Deploy Windows Server 2016 Active Directory Federation Services for Windows Hello for Business
|
||||
title: Prepare & Deploy Windows Active Directory Federation Services (Windows Hello for Business)
|
||||
description: How to Prepare and Deploy Windows Server 2016 Active Directory Federation Services for Windows Hello for Business
|
||||
keywords: identity, PIN, biometric, Hello, passport
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate (Windows 10)
|
||||
title: Make & verify an EFS Data Recovery Agent certificate (Windows 10)
|
||||
description: Follow these steps to create, verify, and perform a quick recovery by using a Encrypting File System (EFS) Data Recovery Agent (DRA) certificate.
|
||||
keywords: Windows Information Protection, WIP, EDP, Enterprise Data Protection
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: 1108(S) The event logging service encountered an error while processing an incoming event published from %1. (Windows 10)
|
||||
title: 1108(S) The event logging service encountered an error (Windows 10)
|
||||
description: Describes security event 1108(S) The event logging service encountered an error while processing an incoming event published from %1.
|
||||
ms.pagetype: security
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Monitor the central access policies that apply on a file server (Windows 10)
|
||||
title: Monitor central access policies on a file server (Windows 10)
|
||||
description: This topic for the IT professional describes how to monitor changes to the central access policies that apply to a file server when using advanced security auditing options to monitor dynamic access control objects.
|
||||
ms.assetid: 126b051e-c20d-41f1-b42f-6cff24dcf20c
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Update data retention settings for Microsoft Defender Advanced Threat Protection
|
||||
description: Update data retention settings by selecting between 30 days to 180 days.
|
||||
title: Update how long data is stored by MDATP
|
||||
description: Update data retention settings for Microsoft Defender Advanced Threat Protection (MDATP) by selecting between 30 days to 180 days.
|
||||
keywords: data, storage, settings, retention, update
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Interactive logon Message text for users attempting to log on (Windows 10)
|
||||
title: Interactive Logon Message text (Windows 10)
|
||||
description: Describes the best practices, location, values, management, and security considerations for the Interactive logon Message text for users attempting to log on security policy setting.
|
||||
ms.assetid: fcfe8a6d-ca65-4403-b9e6-2fa017a31c2e
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Microsoft network server Attempt S4U2Self to obtain claim information (Windows 10)
|
||||
title: Microsoft network server Attempt S4U2Self (Windows 10)
|
||||
description: Describes the best practices, location, values, management, and security considerations for the Microsoft network server Attempt S4U2Self to obtain claim information security policy setting.
|
||||
ms.assetid: e4508387-35ed-4a3f-a47c-27f8396adbba
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: User Account Control Run all administrators in Admin Approval Mode (Windows 10)
|
||||
title: UAC Run all administrators in Admin Approval Mode (Windows 10)
|
||||
description: Describes the best practices, location, values, policy management and security considerations for the User Account Control Run all administrators in Admin Approval Mode security policy setting.
|
||||
ms.assetid: b838c561-7bfc-41ef-a7a5-55857259c7bf
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Allow COM object registration in a Windows Defender Application Control policy (Windows 10)
|
||||
title: Allow COM object registration in a WDAC policy (Windows 10)
|
||||
description: You can allow COM object registration in a Windows Defender Application Control policy.
|
||||
keywords: whitelisting, security, malware
|
||||
ms.assetid: 8d6e0474-c475-411b-b095-1c61adb2bdbb
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Document the Group Policy structure and AppLocker rule enforcement (Windows 10)
|
||||
title: Document Group Policy structure & AppLocker rule enforcement (Windows 10)
|
||||
description: This planning topic describes what you need to investigate, determine, and record in your application control policies plan when you use AppLocker.
|
||||
ms.assetid: 389ffa8e-11fc-49ff-b0b1-89553e6fb6e5
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Audit Windows Defender Application Control (WDAC) policies (Windows 10)
|
||||
description: Windows Defender Application Control restricts which applications users are allowed to run and the code that runs in the system core.
|
||||
title: Audit Windows Defender Application Control policies (Windows 10)
|
||||
description: Windows Defender Application Control (WDAC) restricts which applications users are allowed to run and the code that runs in the system core.
|
||||
keywords: whitelisting, security, malware
|
||||
ms.assetid: 8d6e0474-c475-411b-b095-1c61adb2bdbb
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Frequently asked questions - Windows Defender Application Guard (Windows 10)
|
||||
title: FAQ - Windows Defender Application Guard (Windows 10)
|
||||
description: Learn about the commonly asked questions and answers for Windows Defender Application Guard.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Testing scenarios using Windows Defender Application Guard in your business or organization (Windows 10)
|
||||
title: Testing scenarios with Windows Defender Application Guard (Windows 10)
|
||||
description: Suggested testing scenarios for Windows Defender Application Guard, showing how it works in both Standalone and Enterprise-managed mode.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Checklist Creating Rules for Clients of a Standalone Isolated Server Zone (Windows 10)
|
||||
description: Checklist Creating Rules for Clients of a Standalone Isolated Server Zone
|
||||
title: Create Rules for Standalone Isolated Server Zone Clients (Windows 10)
|
||||
description: Checklist for when creating rules for clients of a Standalone Isolated Server Zone
|
||||
ms.assetid: 6a5e6478-add3-47e3-8221-972549e013f6
|
||||
ms.reviewer:
|
||||
ms.author: dansimp
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Designing a Windows Defender Firewall with Advanced Security Strategy (Windows 10)
|
||||
description: Designing a Windows Defender Firewall Strategy
|
||||
title: Designing a Windows Defender Firewall Strategy (Windows 10)
|
||||
description: Designing a Windows Defender Firewall with Advanced Security Strategy
|
||||
ms.assetid: 6d98b184-33d6-43a5-9418-4f24905cfd71
|
||||
ms.reviewer:
|
||||
ms.author: dansimp
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Open the Group Policy Management Console to Windows Defender Firewall (Windows 10)
|
||||
title: Open a GPO to Windows Defender Firewall (Windows 10)
|
||||
description: Open the Group Policy Management Console to Windows Defender Firewall with Advanced Security
|
||||
ms.assetid: 5090b2c8-e038-4905-b238-19ecf8227760
|
||||
ms.reviewer:
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user