mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
another 30 titles before thanksgiving break
This commit is contained in:
martyav
parent
7737ac88fa
commit
77e1835da4
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Install the Publishing Server on a Remote Computer (Windows 10)
|
||||
title: Install the Publishing Server on a Remote Computer (Windows 10)
|
||||
description: How to Install the App-V Publishing Server on a Remote Computer
|
||||
author: lomayor
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Use Group Policy and mobile device management (MDM) settings to configure Cortana in your organization (Windows 10)
|
||||
title: Configure Cortana in your organization using Group Policy and MDM settings (Windows 10)
|
||||
description: The list of Group Policy and mobile device management (MDM) policy settings that apply to Cortana at work.
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Customize Windows 10 Start and taskbar with mobile device management (MDM) (Windows 10)
|
||||
title: Customize Windows 10 Start and taskbar with mobile device management
|
||||
description: In Windows 10, you can use a mobile device management (MDM) policy to deploy a customized Start and tasbkar layout to users.
|
||||
ms.assetid: F487850D-8950-41FB-9B06-64240127C1E4
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Introduction to configuration service providers (CSPs) for IT pros (Windows 10)
|
||||
title: Intro to configuration service providers for IT pros (Windows 10)
|
||||
description: Configuration service providers (CSPs) expose device configuration settings in Windows 10.
|
||||
ms.assetid: 25C1FDCA-0E10-42A1-A368-984FFDB2B7B6
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Managing the UE-V Service and Packages with Windows PowerShell and WMI
|
||||
title: Manage UE-V Service and Packages with Windows PowerShell and WMI
|
||||
description: Managing the UE-V service and packages with Windows PowerShell and WMI
|
||||
author: dansimp
|
||||
ms.pagetype: mdop, virtualization
|
||||
|
||||
@ -1,190 +1,191 @@
|
||||
---
|
||||
title: Create a task sequence with Configuration Manager and MDT (Windows 10)
|
||||
description: In this topic, you will learn how to create a Microsoft System Center 2012 R2 Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard.
|
||||
ms.assetid: 0b069bec-5be8-47c6-bf64-7a630f41ac98
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: deploy, upgrade, task sequence, install
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: mdt
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Create a task sequence with Configuration Manager and MDT
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
In this topic, you will learn how to create a Microsoft System Center 2012 R2 Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard. Creating task sequences in System Center 2012 R2 Configuration Manager requires many more steps than creating task sequences for MDT Lite Touch installation. Luckily, the MDT wizard helps you through the process and also guides you through creating the needed packages.
|
||||
|
||||
For the purposes of this topic, we will use two machines: DC01 and CM01. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard, both of which are members 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-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
## <a href="" id="sec01"></a>Create a task sequence using the MDT Integration Wizard
|
||||
|
||||
|
||||
This section walks you through the process of creating a System Center 2012 R2 Configuration Manager task sequence for production use.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, in the Software Library workspace, expand **Operating Systems**, right-click **Task Sequences**, and select **Create MDT Task Sequence**.
|
||||
|
||||
2. On the **Choose Template** page, select the **Client Task Sequence** template and click **Next**.
|
||||
|
||||
3. On the **General** page, assign the following settings and then click **Next**:
|
||||
|
||||
* Task sequence name: Windows 10 Enterprise x64 RTM
|
||||
|
||||
* Task sequence comments: Production image with Office 2013
|
||||
|
||||
4. On the **Details** page, assign the following settings and then click **Next**:
|
||||
|
||||
* Join a Domain
|
||||
|
||||
* Domain: contoso.com
|
||||
|
||||
* Account: CONTOSO\\CM\_JD
|
||||
|
||||
* Password: Passw0rd!
|
||||
|
||||
* Windows Settings
|
||||
|
||||
* User name: Contoso
|
||||
|
||||
* Organization name: Contoso
|
||||
|
||||
* Product key: <blank>
|
||||
|
||||
5. On the **Capture Settings** page, accept the default settings, and click **Next**.
|
||||
|
||||
6. On the **Boot Image** page, browse and select the **Zero Touch WinPE x64** boot image package. Then click **Next**.
|
||||
|
||||
7. On the **MDT Package** page, select **Create a new Microsoft Deployment Toolkit Files package**, and in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\MDT\\MDT**. Then click **Next**.
|
||||
|
||||
8. On the **MDT Details** page, assign the name **MDT** and click **Next**.
|
||||
|
||||
9. On the **OS Image** page, browse and select the **Windows 10 Enterprise x64 RTM** package. Then click **Next**.
|
||||
|
||||
10. On the **Deployment Method** page, accept the default settings and click **Next**.
|
||||
|
||||
11. On the **Client Package** page, browse and select the **OSD / Configuration Manager Client** package. Then click **Next**.
|
||||
|
||||
12. On the **USMT Package** page, browse and select **the OSD / Microsoft Corporation User State Migration Tool for Windows 8 10.0.10240.16384** package. Then click **Next**.
|
||||
|
||||
13. On the **Settings Package** page, select the **Create a new settings package** option, and in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\Settings\\Windows 10 x64 Settings**. Then click **Next**.
|
||||
|
||||
14. On the **Settings Details** page, assign the name **Windows 10 x64 Settings** and click **Next**.
|
||||
|
||||
15. On the **Sysprep Package** page, click **Next** twice.
|
||||
|
||||
16. On the **Confirmation** page, click **Finish**.
|
||||
|
||||
## <a href="" id="sec02"></a>Edit the task sequence
|
||||
|
||||
|
||||
After you create the task sequence, we recommend that you configure the task sequence for an optimal deployment experience. The configurations include enabling support for Unified Extensible Firmware Interface (UEFI), dynamic organizational unit (OU) allocation, computer replace scenarios, and more.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, select **Task Sequences**, right-click **Windows 10 Enterprise x64 RTM** task sequence, and select **Edit**.
|
||||
|
||||
2. In the **Install** group, select the **Set Variable for Drive Letter** action and configure the following:
|
||||
|
||||
* OSDPreserveDriveLetter: True
|
||||
|
||||
>[!NOTE]
|
||||
>If you don't change this value, your Windows installation will end up in E:\\Windows.
|
||||
|
||||
3. In the **Post Install** group, select **Apply Network Settings**, and configure the Domain OU value to use the **Contoso / Workstations** OU (browse for values).
|
||||
|
||||
4. In the **Post Install** group, disable the **Auto Apply Drivers** action. (Disabling is done by selecting the action and, in the **Options** tab, selecting the **Disable this step** check box.)
|
||||
|
||||
5. After the disabled **Post Install / Auto Apply Drivers** action, add a new group name: **Drivers**.
|
||||
|
||||
6. After the **Post Install / Drivers** group, add an **Apply Driver Package** action with the following settings:
|
||||
|
||||
* Name: HP EliteBook 8560w
|
||||
|
||||
* Driver Package: Windows 10 x64 - HP EliteBook 8560w
|
||||
|
||||
* Options: Task Sequence Variable: Model equals HP EliteBook 8560w
|
||||
|
||||
>[!NOTE]
|
||||
>You also can add a Query WMI condition with the following query: SELECT \* FROM Win32\_ComputerSystem WHERE Model LIKE '%HP EliteBook 8560w%'
|
||||
|
||||
|
||||
|
||||
*Figure 24. The driver package options*
|
||||
|
||||
7. In the **State Restore / Install Applications** group, select the **Install Application** action.
|
||||
|
||||
8. Select the **Install the following applications** option, and add the OSD / Adobe Reader XI - OSD Install application to the list.
|
||||
|
||||
|
||||
|
||||
*Figure 25. Add an application to the Configuration Manager task sequence*
|
||||
|
||||
9. In the **State Restore** group, after the **Set Status 5** action, add a **Request State Store** action with the following settings:
|
||||
|
||||
* Restore state from another computer
|
||||
|
||||
* If computer account fails to connect to state store, use the Network Access account
|
||||
|
||||
* Options: Continue on error
|
||||
|
||||
* Options / Condition:
|
||||
|
||||
* Task Sequence Variable
|
||||
|
||||
* USMTLOCAL not equals True
|
||||
|
||||
10. In the **State Restore** group, after the **Restore User State** action, add a **Release State Store** action with the following settings:
|
||||
|
||||
* Options: Continue on error
|
||||
|
||||
* Options / Condition:
|
||||
|
||||
* Task Sequence Variable
|
||||
|
||||
* USMTLOCAL not equals True
|
||||
|
||||
11. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Request State Store and Release State Store actions need to be added for common computer replace scenarios.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="sec03"></a>Move the packages
|
||||
|
||||
|
||||
While creating the task sequence with the MDT wizard, a few operating system deployment packages were created. To move these packages to the OSD folder, take the following steps.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, in the Software Library workspace, expand **Application Management**, and then select **Packages**.
|
||||
|
||||
2. Select the **MDT** and **Windows 10 x64 Settings** packages, right-click and select **Move**.
|
||||
|
||||
3. In the **Move Selected Items** dialog box, select the **OSD** folder, and click **OK**.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](../deploy-windows-sccm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](../deploy-windows-sccm/add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](../deploy-windows-sccm/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](../deploy-windows-sccm/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](../deploy-windows-sccm/deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
---
|
||||
title: Create a task sequence with Configuration Manager (Windows 10)
|
||||
description: In this topic, you will learn how to create a Microsoft System Center 2012 R2 Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard.
|
||||
ms.assetid: 0b069bec-5be8-47c6-bf64-7a630f41ac98
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
keywords: deploy, upgrade, task sequence, install
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.pagetype: mdt
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Create a task sequence with Configuration Manager and MDT
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
In this topic, you will learn how to create a Microsoft System Center 2012 R2 Configuration Manager task sequence with Microsoft Deployment Toolkit (MDT) integration using the MDT wizard. Creating task sequences in System Center 2012 R2 Configuration Manager requires many more steps than creating task sequences for MDT Lite Touch installation. Luckily, the MDT wizard helps you through the process and also guides you through creating the needed packages.
|
||||
|
||||
For the purposes of this topic, we will use two machines: DC01 and CM01. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 Standard, both of which are members 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-10-with-the-microsoft-deployment-toolkit.md).
|
||||
|
||||
## <a href="" id="sec01"></a>Create a task sequence using the MDT Integration Wizard
|
||||
|
||||
|
||||
This section walks you through the process of creating a System Center 2012 R2 Configuration Manager task sequence for production use.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, in the Software Library workspace, expand **Operating Systems**, right-click **Task Sequences**, and select **Create MDT Task Sequence**.
|
||||
|
||||
2. On the **Choose Template** page, select the **Client Task Sequence** template and click **Next**.
|
||||
|
||||
3. On the **General** page, assign the following settings and then click **Next**:
|
||||
|
||||
* Task sequence name: Windows 10 Enterprise x64 RTM
|
||||
|
||||
* Task sequence comments: Production image with Office 2013
|
||||
|
||||
4. On the **Details** page, assign the following settings and then click **Next**:
|
||||
|
||||
* Join a Domain
|
||||
|
||||
* Domain: contoso.com
|
||||
|
||||
* Account: CONTOSO\\CM\_JD
|
||||
|
||||
* Password: Passw0rd!
|
||||
|
||||
* Windows Settings
|
||||
|
||||
* User name: Contoso
|
||||
|
||||
* Organization name: Contoso
|
||||
|
||||
* Product key: <blank>
|
||||
|
||||
5. On the **Capture Settings** page, accept the default settings, and click **Next**.
|
||||
|
||||
6. On the **Boot Image** page, browse and select the **Zero Touch WinPE x64** boot image package. Then click **Next**.
|
||||
|
||||
7. On the **MDT Package** page, select **Create a new Microsoft Deployment Toolkit Files package**, and in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\MDT\\MDT**. Then click **Next**.
|
||||
|
||||
8. On the **MDT Details** page, assign the name **MDT** and click **Next**.
|
||||
|
||||
9. On the **OS Image** page, browse and select the **Windows 10 Enterprise x64 RTM** package. Then click **Next**.
|
||||
|
||||
10. On the **Deployment Method** page, accept the default settings and click **Next**.
|
||||
|
||||
11. On the **Client Package** page, browse and select the **OSD / Configuration Manager Client** package. Then click **Next**.
|
||||
|
||||
12. On the **USMT Package** page, browse and select **the OSD / Microsoft Corporation User State Migration Tool for Windows 8 10.0.10240.16384** package. Then click **Next**.
|
||||
|
||||
13. On the **Settings Package** page, select the **Create a new settings package** option, and in the **Package source folder to be created (UNC Path):** text box, type **\\\\CM01\\Sources$\\OSD\\Settings\\Windows 10 x64 Settings**. Then click **Next**.
|
||||
|
||||
14. On the **Settings Details** page, assign the name **Windows 10 x64 Settings** and click **Next**.
|
||||
|
||||
15. On the **Sysprep Package** page, click **Next** twice.
|
||||
|
||||
16. On the **Confirmation** page, click **Finish**.
|
||||
|
||||
## <a href="" id="sec02"></a>Edit the task sequence
|
||||
|
||||
|
||||
After you create the task sequence, we recommend that you configure the task sequence for an optimal deployment experience. The configurations include enabling support for Unified Extensible Firmware Interface (UEFI), dynamic organizational unit (OU) allocation, computer replace scenarios, and more.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, select **Task Sequences**, right-click **Windows 10 Enterprise x64 RTM** task sequence, and select **Edit**.
|
||||
|
||||
2. In the **Install** group, select the **Set Variable for Drive Letter** action and configure the following:
|
||||
|
||||
* OSDPreserveDriveLetter: True
|
||||
|
||||
>[!NOTE]
|
||||
>If you don't change this value, your Windows installation will end up in E:\\Windows.
|
||||
|
||||
3. In the **Post Install** group, select **Apply Network Settings**, and configure the Domain OU value to use the **Contoso / Workstations** OU (browse for values).
|
||||
|
||||
4. In the **Post Install** group, disable the **Auto Apply Drivers** action. (Disabling is done by selecting the action and, in the **Options** tab, selecting the **Disable this step** check box.)
|
||||
|
||||
5. After the disabled **Post Install / Auto Apply Drivers** action, add a new group name: **Drivers**.
|
||||
|
||||
6. After the **Post Install / Drivers** group, add an **Apply Driver Package** action with the following settings:
|
||||
|
||||
* Name: HP EliteBook 8560w
|
||||
|
||||
* Driver Package: Windows 10 x64 - HP EliteBook 8560w
|
||||
|
||||
* Options: Task Sequence Variable: Model equals HP EliteBook 8560w
|
||||
|
||||
>[!NOTE]
|
||||
>You also can add a Query WMI condition with the following query: SELECT \* FROM Win32\_ComputerSystem WHERE Model LIKE '%HP EliteBook 8560w%'
|
||||
|
||||
|
||||
|
||||
*Figure 24. The driver package options*
|
||||
|
||||
7. In the **State Restore / Install Applications** group, select the **Install Application** action.
|
||||
|
||||
8. Select the **Install the following applications** option, and add the OSD / Adobe Reader XI - OSD Install application to the list.
|
||||
|
||||
|
||||
|
||||
*Figure 25. Add an application to the Configuration Manager task sequence*
|
||||
|
||||
9. In the **State Restore** group, after the **Set Status 5** action, add a **Request State Store** action with the following settings:
|
||||
|
||||
* Restore state from another computer
|
||||
|
||||
* If computer account fails to connect to state store, use the Network Access account
|
||||
|
||||
* Options: Continue on error
|
||||
|
||||
* Options / Condition:
|
||||
|
||||
* Task Sequence Variable
|
||||
|
||||
* USMTLOCAL not equals True
|
||||
|
||||
10. In the **State Restore** group, after the **Restore User State** action, add a **Release State Store** action with the following settings:
|
||||
|
||||
* Options: Continue on error
|
||||
|
||||
* Options / Condition:
|
||||
|
||||
* Task Sequence Variable
|
||||
|
||||
* USMTLOCAL not equals True
|
||||
|
||||
11. Click **OK**.
|
||||
|
||||
>[!NOTE]
|
||||
>The Request State Store and Release State Store actions need to be added for common computer replace scenarios.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="sec03"></a>Move the packages
|
||||
|
||||
|
||||
While creating the task sequence with the MDT wizard, a few operating system deployment packages were created. To move these packages to the OSD folder, take the following steps.
|
||||
|
||||
1. On CM01, using the Configuration Manager Console, in the Software Library workspace, expand **Application Management**, and then select **Packages**.
|
||||
|
||||
2. Select the **MDT** and **Windows 10 x64 Settings** packages, right-click and select **Move**.
|
||||
|
||||
3. In the **Move Selected Items** dialog box, select the **OSD** folder, and click **OK**.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Integrate Configuration Manager with MDT](integrate-configuration-manager-with-mdt.md)
|
||||
|
||||
[Prepare for Zero Touch Installation of Windows 10 with Configuration Manager](../deploy-windows-sccm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md)
|
||||
|
||||
[Create a custom Windows PE boot image with Configuration Manager](../deploy-windows-sccm/create-a-custom-windows-pe-boot-image-with-configuration-manager.md)
|
||||
|
||||
[Add a Windows 10 operating system image using Configuration Manager](../deploy-windows-sccm/add-a-windows-10-operating-system-image-using-configuration-manager.md)
|
||||
|
||||
[Create an application to deploy with Windows 10 using Configuration Manager](../deploy-windows-sccm/create-an-application-to-deploy-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager](../deploy-windows-sccm/add-drivers-to-a-windows-10-deployment-with-windows-pe-using-configuration-manager.md)
|
||||
|
||||
[Deploy Windows 10 using PXE and Configuration Manager](../deploy-windows-sccm/deploy-windows-10-using-pxe-and-configuration-manager.md)
|
||||
|
||||
[Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
[Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager](../deploy-windows-sccm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md)
|
||||
|
||||
@ -1,96 +1,97 @@
|
||||
---
|
||||
title: Use the MDT database to stage Windows 10 deployment information (Windows 10)
|
||||
description: This topic is designed to teach you how to use the MDT database to pre-stage information on your Windows 10 deployment in a Microsoft SQL Server 2012 SP1 Express database, rather than include the information in a text file (CustomSettings.ini).
|
||||
ms.assetid: 8956ab54-90ba-45d3-a384-4fdec72c4d46
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.pagetype: mdt
|
||||
keywords: database, permissions, settings, configure, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
audience: itpro
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Use the MDT database to stage Windows 10 deployment information
|
||||
|
||||
This topic is designed to teach you how to use the MDT database to pre-stage information on your Windows 10 deployment in a Microsoft SQL Server 2012 SP1 Express database, rather than include the information in a text file (CustomSettings.ini). You can use this process, for example, to add the client machines you want to deploy, specify their computer names and IP addresses, indicate applications to be deployed, and determine many additional settings for the machines.
|
||||
|
||||
## <a href="" id="sec01"></a>Database prerequisites
|
||||
|
||||
MDT can use either SQL Server Express or full SQL Server, but since the deployment database isn't big, even in large enterprise environments, we recommend using the free SQL Server 2012 SP1 Express database in your environment.
|
||||
|
||||
>[!NOTE]
|
||||
>Be sure to enable Named Pipes when configuring the SQL Server 2012 SP1 Express database. Although it is a legacy protocol, Named Pipes has proven to work well when connecting from Windows Preinstallation Environment (Windows PE) to the SQL Server database.
|
||||
|
||||
## <a href="" id="sec02"></a>Create the deployment database
|
||||
|
||||
The MDT database is by default created and managed from the Deployment Workbench. In these steps, we assume you have installed SQL Server 2012 SP1 Express on MDT01.
|
||||
|
||||
>[!NOTE]
|
||||
>Since SQL Server 2012 SP1 Express runs by default on a separate instance (SQLEXPRESS), the SQL Server Browser service must be running, and the firewall configured to allow traffic to it. Port 1433 TCP and port 1434 UDP need to be opened for inbound traffic on MDT01.
|
||||
|
||||
1. On MDT01, using Deployment Workbench, expand the MDT Production deployment share, expand **Advanced Configuration**, right-click **Database**, and select **New Database**.
|
||||
2. In the New DB Wizard, on the **SQL Server Details** page, enter the following settings and click **Next**:
|
||||
1. SQL Server Name: MDT01
|
||||
2. Instance: SQLEXPRESS
|
||||
3. Port: <blank>
|
||||
4. Network Library: Named Pipes
|
||||
3. On the **Database** page, select **Create a new database**; in the **Database** field, type **MDT** and click **Next**.
|
||||
4. On the **SQL Share** page, in the **SQL Share** field, type **Logs$** and click **Next**. Click **Next** again and then click **Finish**.
|
||||
|
||||
|
||||
|
||||
Figure 8. The MDT database added to MDT01.
|
||||
|
||||
## <a href="" id="sec03"></a>Configure database permissions
|
||||
|
||||
After creating the database, you need to assign permissions to it. In MDT, the account you used to run the deployment is used to access the database. In this environment, the network access account is MDT\_BA.
|
||||
1. On MDT01, start SQL Server Management Studio.
|
||||
2. In the **Connect to Server** dialog box, in the **Server name** list, select **MDT01\\SQLEXPRESS** and click **Connect**.
|
||||
3. In the **Object Explorer** pane, expand the top-level **Security** node, right-click **Logins**, and select **New Login**.
|
||||
|
||||
|
||||
|
||||
Figure 9. The top-level Security node.
|
||||
|
||||
4. On the **Login - New** page, next to the **Login** name field, click **Search**, and search for **CONTOSO\\MDT\_BA**. Then in the left pane, select **User Mapping**. Select the **MDT** database, and assign the following roles:
|
||||
1. db\_datareader
|
||||
2. public (default)
|
||||
5. Click **OK**, and close SQL Server Management Studio.
|
||||
|
||||
|
||||
|
||||
Figure 10. Creating the login and settings permissions to the MDT database.
|
||||
|
||||
## <a href="" id="sec04"></a>Create an entry in the database
|
||||
|
||||
To start using the database, you add a computer entry and assign a description and computer name. Use the computer's MAC Address as the identifier.
|
||||
1. On MDT01, using the Deployment Workbench, in the MDT Production deployment share, expand **Advanced Configuration**, and expand **Database**.
|
||||
2. Right-click **Computers**, select **New**, and add a computer entry with the following settings:
|
||||
1. Description: New York Site - PC00075
|
||||
2. MacAddress: <PC00075 MAC Address in the 00:00:00:00:00:00 format>
|
||||
3. Details Tab / OSDComputerName: PC00075
|
||||
|
||||
|
||||
|
||||
Figure 11. Adding the PC00075 computer to the database.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Set up MDT for BitLocker](set-up-mdt-for-bitlocker.md)
|
||||
|
||||
[Configure MDT deployment share rules](configure-mdt-deployment-share-rules.md)
|
||||
|
||||
[Configure MDT for UserExit scripts](configure-mdt-for-userexit-scripts.md)
|
||||
|
||||
[Simulate a Windows 10 deployment in a test environment](simulate-a-windows-10-deployment-in-a-test-environment.md)
|
||||
|
||||
[Assign applications using roles in MDT](assign-applications-using-roles-in-mdt.md)
|
||||
|
||||
[Use web services in MDT](use-web-services-in-mdt.md)
|
||||
|
||||
[Use Orchestrator runbooks with MDT](use-orchestrator-runbooks-with-mdt.md)
|
||||
---
|
||||
title: Use MDT database to stage Windows 10 deployment info (Windows 10)
|
||||
description: This topic is designed to teach you how to use the MDT database to pre-stage information on your Windows 10 deployment in a Microsoft SQL Server 2012 SP1 Express database, rather than include the information in a text file (CustomSettings.ini).
|
||||
ms.assetid: 8956ab54-90ba-45d3-a384-4fdec72c4d46
|
||||
ms.reviewer:
|
||||
manager: laurawi
|
||||
ms.author: greglin
|
||||
ms.pagetype: mdt
|
||||
keywords: database, permissions, settings, configure, deploy
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.localizationpriority: medium
|
||||
ms.sitesec: library
|
||||
audience: itpro
|
||||
author: greg-lindsay
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Use the MDT database to stage Windows 10 deployment information
|
||||
|
||||
This topic is designed to teach you how to use the MDT database to pre-stage information on your Windows 10 deployment in a Microsoft SQL Server 2012 SP1 Express database, rather than include the information in a text file (CustomSettings.ini). You can use this process, for example, to add the client machines you want to deploy, specify their computer names and IP addresses, indicate applications to be deployed, and determine many additional settings for the machines.
|
||||
|
||||
## <a href="" id="sec01"></a>Database prerequisites
|
||||
|
||||
MDT can use either SQL Server Express or full SQL Server, but since the deployment database isn't big, even in large enterprise environments, we recommend using the free SQL Server 2012 SP1 Express database in your environment.
|
||||
|
||||
>[!NOTE]
|
||||
>Be sure to enable Named Pipes when configuring the SQL Server 2012 SP1 Express database. Although it is a legacy protocol, Named Pipes has proven to work well when connecting from Windows Preinstallation Environment (Windows PE) to the SQL Server database.
|
||||
|
||||
## <a href="" id="sec02"></a>Create the deployment database
|
||||
|
||||
The MDT database is by default created and managed from the Deployment Workbench. In these steps, we assume you have installed SQL Server 2012 SP1 Express on MDT01.
|
||||
|
||||
>[!NOTE]
|
||||
>Since SQL Server 2012 SP1 Express runs by default on a separate instance (SQLEXPRESS), the SQL Server Browser service must be running, and the firewall configured to allow traffic to it. Port 1433 TCP and port 1434 UDP need to be opened for inbound traffic on MDT01.
|
||||
|
||||
1. On MDT01, using Deployment Workbench, expand the MDT Production deployment share, expand **Advanced Configuration**, right-click **Database**, and select **New Database**.
|
||||
2. In the New DB Wizard, on the **SQL Server Details** page, enter the following settings and click **Next**:
|
||||
1. SQL Server Name: MDT01
|
||||
2. Instance: SQLEXPRESS
|
||||
3. Port: <blank>
|
||||
4. Network Library: Named Pipes
|
||||
3. On the **Database** page, select **Create a new database**; in the **Database** field, type **MDT** and click **Next**.
|
||||
4. On the **SQL Share** page, in the **SQL Share** field, type **Logs$** and click **Next**. Click **Next** again and then click **Finish**.
|
||||
|
||||
|
||||
|
||||
Figure 8. The MDT database added to MDT01.
|
||||
|
||||
## <a href="" id="sec03"></a>Configure database permissions
|
||||
|
||||
After creating the database, you need to assign permissions to it. In MDT, the account you used to run the deployment is used to access the database. In this environment, the network access account is MDT\_BA.
|
||||
1. On MDT01, start SQL Server Management Studio.
|
||||
2. In the **Connect to Server** dialog box, in the **Server name** list, select **MDT01\\SQLEXPRESS** and click **Connect**.
|
||||
3. In the **Object Explorer** pane, expand the top-level **Security** node, right-click **Logins**, and select **New Login**.
|
||||
|
||||
|
||||
|
||||
Figure 9. The top-level Security node.
|
||||
|
||||
4. On the **Login - New** page, next to the **Login** name field, click **Search**, and search for **CONTOSO\\MDT\_BA**. Then in the left pane, select **User Mapping**. Select the **MDT** database, and assign the following roles:
|
||||
1. db\_datareader
|
||||
2. public (default)
|
||||
5. Click **OK**, and close SQL Server Management Studio.
|
||||
|
||||
|
||||
|
||||
Figure 10. Creating the login and settings permissions to the MDT database.
|
||||
|
||||
## <a href="" id="sec04"></a>Create an entry in the database
|
||||
|
||||
To start using the database, you add a computer entry and assign a description and computer name. Use the computer's MAC Address as the identifier.
|
||||
1. On MDT01, using the Deployment Workbench, in the MDT Production deployment share, expand **Advanced Configuration**, and expand **Database**.
|
||||
2. Right-click **Computers**, select **New**, and add a computer entry with the following settings:
|
||||
1. Description: New York Site - PC00075
|
||||
2. MacAddress: <PC00075 MAC Address in the 00:00:00:00:00:00 format>
|
||||
3. Details Tab / OSDComputerName: PC00075
|
||||
|
||||
|
||||
|
||||
Figure 11. Adding the PC00075 computer to the database.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Set up MDT for BitLocker](set-up-mdt-for-bitlocker.md)
|
||||
|
||||
[Configure MDT deployment share rules](configure-mdt-deployment-share-rules.md)
|
||||
|
||||
[Configure MDT for UserExit scripts](configure-mdt-for-userexit-scripts.md)
|
||||
|
||||
[Simulate a Windows 10 deployment in a test environment](simulate-a-windows-10-deployment-in-a-test-environment.md)
|
||||
|
||||
[Assign applications using roles in MDT](assign-applications-using-roles-in-mdt.md)
|
||||
|
||||
[Use web services in MDT](use-web-services-in-mdt.md)
|
||||
|
||||
[Use Orchestrator runbooks with MDT](use-orchestrator-runbooks-with-mdt.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Beginning your General Data Protection Regulation (GDPR) journey for Windows 10 (Windows 10)
|
||||
description: Use this article to understand what GDPR is and about the products Microsoft provides to help you get started towards compliance.
|
||||
title: General Data Protection Regulation (GDPR) for Windows 10
|
||||
description: Use this article to understand what GDPR is and which products Microsoft provides to help you get started towards compliance.
|
||||
keywords: privacy, GDPR
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Windows 10 & Privacy Compliance Guide
|
||||
description: This article provides information to help IT and compliance professionals understand the personal data policies as related to Windows 10.
|
||||
title: Windows 10 & Privacy Compliance - A Guide for IT and Compliance Professionals
|
||||
keywords: privacy, GDPR, compliance
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Configuring Hybrid key trust Windows Hello for Business - Group Policy
|
||||
title: Configure Hybrid Windows Hello for Business - Group Policy
|
||||
description: Configuring Hybrid key trust Windows Hello for Business - Group Policy
|
||||
keywords: identity, PIN, biometric, Hello, passport, WHFB, Windows Hello, key trust, key-trust
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Using Outlook on the web with Windows Information Protection (WIP) (Windows 10)
|
||||
title: Using Outlook on the web with WIP (Windows 10)
|
||||
description: Options for using Outlook on the web with Windows Information Protection (WIP).
|
||||
keywords: WIP, Windows Information Protection, EDP, Enterprise Data Protection, WIP and OWA configuration, OWA, Outlook Web access
|
||||
ms.prod: w10
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Requirements and deployment planning guidelines for virtualization-based protection of code integrity (Windows 10)
|
||||
description: To help you plan a deployment of Microsoft Windows Defender Device Guard, this article describes hardware requirements for Windows Defender Device Guard, outlines deployment approaches, and describes methods for code signing and the deployment of code integrity policies.
|
||||
title: Deployment guidelines for Windows Defender Device Guard (Windows 10)
|
||||
description: To help you plan a deployment of Microsoft Windows Defender Device Guard, this article describes hardware requirements for Windows Defender Device Guard, outlines deployment approaches, and describes methods for code signing and code integrity policies.
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -21,7 +21,7 @@ ms.author: dansimp
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
Computers must meet certain hardware, firmware, and software requirements in order to take adavantage of all of the virtualization-based security (VBS) features in [Windows Defender Device Guard](../device-guard/introduction-to-device-guard-virtualization-based-security-and-windows-defender-application-control.md). Computers lacking these requirements can still be protected by Windows Defender Application Control (WDAC) policies—the difference is that those computers will not be as hardened against certain threats.
|
||||
Computers must meet certain hardware, firmware, and software requirements in order to take advantage of all of the virtualization-based security (VBS) features in [Windows Defender Device Guard](../device-guard/introduction-to-device-guard-virtualization-based-security-and-windows-defender-application-control.md). Computers lacking these requirements can still be protected by Windows Defender Application Control (WDAC) policies—the difference is that those computers will not be as hardened against certain threats.
|
||||
|
||||
For example, hardware that includes CPU virtualization extensions and SLAT will be hardened against malware that attempts to gain access to the kernel, but without protected BIOS options such as “Boot only from internal hard drive,” the computer could be booted (by a malicious person who has physical access) into an operating system on bootable media.
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Onboard Windows 10 machines using Group Policy to Microsoft Defender ATP
|
||||
title: Onboard Windows 10 devices to Microsoft Defender ATP via Group Policy
|
||||
description: Use Group Policy to deploy the configuration package on Windows 10 machines so that they are onboarded to the service.
|
||||
keywords: configure machines using group policy, machine management, configure Windows ATP machines, onboard Microsoft Defender Advanced Threat Protection machines, group policy
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Accounts Limit local account use of blank passwords to console logon only (Windows 10)
|
||||
title: Accounts Limit local account use of blank passwords (Windows 10)
|
||||
description: Describes the best practices, location, values, and security considerations for the Accounts Limit local account use of blank passwords to console logon only security policy setting.
|
||||
ms.assetid: a1bfb58b-1ae8-4de9-832b-aa889a6e64bd
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Microsoft network client Send unencrypted password to third-party SMB servers (Windows 10)
|
||||
title: Microsoft network client Send unencrypted password (Windows 10)
|
||||
description: Describes the best practices, location, values, policy management and security considerations for the Microsoft network client Send unencrypted password to third-party SMB servers security policy setting.
|
||||
ms.assetid: 97a76b93-afa7-4dd9-bb52-7c9e289b6017
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Network access Do not allow anonymous enumeration of SAM accounts and shares (Windows 10)
|
||||
title: Network access Do not allow anonymous enumeration (Windows 10)
|
||||
description: Describes the best practices, location, values, and security considerations for the Network access Do not allow anonymous enumeration of SAM accounts and shares security policy setting.
|
||||
ms.assetid: 3686788d-4cc7-4222-9163-cbc7c3362d73
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Network security Restrict NTLM Outgoing NTLM traffic to remote servers (Windows 10)
|
||||
title: Network security Restrict NTLM Outgoing traffic (Windows 10)
|
||||
description: Describes the best practices, location, values, management aspects, and security considerations for the Network Security Restrict NTLM Outgoing NTLM traffic to remote servers security policy setting.
|
||||
ms.assetid: 63437a90-764b-4f06-aed8-a4a26cf81bd1
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Shutdown Clear virtual memory pagefile - security policy setting (Windows 10)
|
||||
title: Shutdown Clear virtual memory pagefile (Windows 10)
|
||||
description: Describes the best practices, location, values, policy management and security considerations for the Shutdown Clear virtual memory pagefile security policy setting.
|
||||
ms.assetid: 31400078-6c56-4891-a6df-6dfb403c4bc9
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: User Account Control Only elevate UIAccess applications that are installed in secure locations (Windows 10)
|
||||
title: UAC Only elevate UIAccess apps installed in secure locations (Windows 10)
|
||||
description: Describes the best practices, location, values, policy management and security considerations for the User Account Control Only elevate UIAccess applications that are installed in secure locations security policy setting.
|
||||
ms.assetid: 4333409e-a5be-4f2f-8808-618f53abd22c
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Determine which apps are digitally signed on a reference device (Windows 10)
|
||||
title: Find digitally signed apps on a reference device (Windows 10)
|
||||
description: This topic for the IT professional describes how to use AppLocker logs and tools to determine which applications are digitally signed.
|
||||
ms.assetid: 24609a6b-fdcb-4083-b234-73e23ff8bcb8
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Manage packaged apps with Windows Defender Application Control (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: Manage packaged apps with WDAC (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: Querying Application Control events centrally using Advanced hunting (Windows 10)
|
||||
title: Query Application Control events with Advanced Hunting (Windows 10)
|
||||
description: Learn about Windows Defender Application Guard and how it helps to combat malicious content and malware out on the Internet.
|
||||
keywords: whitelisting, security, malware
|
||||
ms.assetid: 8d6e0474-c475-411b-b095-1c61adb2bdbb
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows Defender System Guard How a hardware-based root of trust helps protect Windows 10 (Windows 10)
|
||||
title: How a Windows Defender System Guard helps protect Windows 10
|
||||
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: Windows Defender System Guard How a hardware-based root of trust helps protect Windows 10 (Windows 10)
|
||||
title: How a Windows Defender System Guard helps protect Windows 10
|
||||
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: Gathering Information about Your Current Network Infrastructure (Windows 10)
|
||||
title: Gathering Info about Your Network Infrastructure (Windows 10)
|
||||
description: Gathering Information about Your Current Network Infrastructure
|
||||
ms.assetid: f98d2b17-e71d-4ffc-b076-118b4d4782f9
|
||||
ms.reviewer:
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Windows Defender Firewall with Advanced Security Deployment Guide (Windows 10)
|
||||
title: Deploy Windows Defender Firewall with Advanced Security (Windows 10)
|
||||
description: Windows Defender Firewall with Advanced Security Deployment Guide
|
||||
ms.assetid: 56b51b97-1c38-481e-bbda-540f1216ad56
|
||||
ms.reviewer:
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user