* Updated deployment-vdi-windows-defender-antivirus.md * Updated deployment-vdi-windows-defender-antivirus.md * Updated deployment-vdi-windows-defender-antivirus.md * updates for new vdi stuff * Adding important note to solve #3493 * Update windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> * Typo "<"→"<", ">"→">" https://docs.microsoft.com/en-us/windows/application-management/manage-windows-mixed-reality * Issue #2297 * Update windows/security/identity-protection/hello-for-business/hello-identity-verification.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> * Clarification * Update windows/security/identity-protection/hello-for-business/hello-identity-verification.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> * Update windows/security/identity-protection/hello-for-business/hello-identity-verification.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> * update troubleshoot-np.md * update configure-endpoints-gp.md * Removing a part which is not supported * Name change * update troubleshoot-np.md * removed on-premises added -hello * Added link into Domain controller guide * Line corections * corrected formatting of xml code samples When viewing the page in Win 10/Edge, the xml code samples stretched across the page, running into the side menu. The lack of line breaks also made it hard to read. This update adds line breaks and syntax highlighting, replaces curly double quotes with standard double quotes, and adds a closing tag for <appv:appconnectiongroup>for each code sample * Update windows/security/identity-protection/hello-for-business/hello-identity-verification.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> * Update windows/deployment/update/waas-delivery-optimization-reference.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> * Update windows/deployment/update/waas-delivery-optimization-reference.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> * corrected formating of XML examples The XML samples here present the same formatting problems as in about-the-connection-group-file51.md (see https://github.com/MicrosoftDocs/windows-itpro-docs/pull/3847/) Perhaps we should open an issue to see if we have more versions of this code sample in the docs * corrected formatting of XML example section In the XML example on this page, the whitespace had been stripped out, so there were no spaces between adjacent attribute values or keys. This made it hard to read, though the original formatting allowed for a scroll bar, so the text was not running into the side of the page (compare to https://github.com/MicrosoftDocs/windows-itpro-docs/pull/3847 and https://github.com/MicrosoftDocs/windows-itpro-docs/pull/3850, where the uncorrected formatting forced the text to run into the side menu). * update configure-endpoints-gp.md * Fixed error in registry path and improved description * Update windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> * Removing extra line in 25 Suggested by * update windows-analytics-azure-portal.md * re: broken links, credential-guard-considerations Context: * #3513, MVA is being retired and producing broken links * #3860 Microsoft Virtual Academy video links This page contains two links to deprecated video content on Microsoft Virtual Academy (MVA). MVA is being retired. In addition, the Deep Dive course the two links point to is already retired, and no replacement course exists. I removed the first link, as I could not find a similar video available describing which credentials are covered by credential guard. I replaced the second link with a video containing similar material, though it is not a "deep dive". Suggestions on handling this problem, as many pages contain similar links, would be appreciated,. * removed link to retired video re: #3867 Context: * #3513, MVA is being retired and producing broken links * #3867, Microsoft Virtual Academy video links This page contains a broken link to deprecated video content on Microsoft Virtual Academy (MVA). MVA is being retired. In addition, the Deep Dive course is already retired, and no replacement course exists. I removed the whole _See Also_ section, as I could not find a video narrowly or deeply addressing how to protect privelaged users with Credential Guard. The most likely candidate is too short and general: https://www.linkedin.com/learning/cism-cert-prep-1-information-security-governance/privileged-account-management * addressing broken mva links, #3817 Context: * #3513, MVA is being retired and producing broken links * #3817, Another broken link This page contains two links to deprecated video content on Microsoft Virtual Academy (MVA). MVA is being retired. In addition, the Deep Dive course the two links point to is already retired, and no replacement course exists. I removed the first link, as we no longer have a video with similar content for a similar audience. The most likely candidate is https://www.linkedin.com/learning/programming-foundations-web-security-2/types-of-credential-attacks, which is more general and for a less technical audience. I removed the second link and the _See Also_ section, as I could not find a similar video narrowly focused on which credentials are covered by Credential Guard. Most of the related material available now describes how to perform a task. * Update deployment-vdi-windows-defender-antivirus.md * typo fix re: #3876; DMSA -> DSMA * Addressing dead MVA links, #3818 This page, like its fellows in the mva-links label, contains links to a retired video course on a website that is retiring soon. The links listed by the user in issue #3818 were also on several other pages, related to Credentials Guard. These links were addressed in the pull requests #3875, #3872, and #3871 Credentials threat & lateral threat link: removed (see PR #3875 for reasoning) Virtualization link: replaced (see #3871 for reasoning) Credentials protected link: removed (see #3872 for reasoning) * Adding notes for known issue in script Solves #3869 * Updated the download link admx files Windows 10 Added link for April 2018 and Oct 2018 ADMX files. * added event logs path Referenced : https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-exploit-guard/event-views-exploit-guard * Update browsers/internet-explorer/ie11-deploy-guide/administrative-templates-and-ie11.md Suggestions applied. Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> * Update browsers/internet-explorer/ie11-deploy-guide/administrative-templates-and-ie11.md Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> * Update deployment-vdi-windows-defender-antivirus.md * screenshot update * Add files via upload * update 4 scrrenshots * Update deployment-vdi-windows-defender-antivirus.md * Update browsers/internet-explorer/ie11-deploy-guide/administrative-templates-and-ie11.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> * Update browsers/internet-explorer/ie11-deploy-guide/administrative-templates-and-ie11.md Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com> * Re: #3909 Top link is broken, #3909 > The link here does not work: > Applies to: Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP) The link to the pdf describing MDATP was broken. Thankfully, PR #2897 updated the same link in another page some time ago, so I didn't have to go hunting for an equivalent * CI Update * Updated as per task 3405344 * Updated author * Update windows-analytics-azure-portal.md * added the example query * Updated author fields * Update office-csp.md * update video for testing * update video * Update surface-hub-site-readiness-guide.md line 134 Fixed video link MD formatting * fixing video url * updates from Albert * Bulk replaced author to manikadhiman * Bulk replaced ms.author to v-madhi * Latest content is published (#371) * Added 1903 policy DDF link and fixed a typo * Reverted the DDF version * Latest update (#375) * Update deployment-vdi-windows-defender-antivirus.md * Update deployment-vdi-windows-defender-antivirus.md
9.1 KiB
title, description, ms.assetid, ms.reviewer, manager, ms.author, keywords, ms.prod, ms.mktglfcycl, ms.localizationpriority, ms.pagetype, ms.sitesec, author, ms.date, ms.topic
title | description | ms.assetid | ms.reviewer | manager | ms.author | keywords | ms.prod | ms.mktglfcycl | ms.localizationpriority | ms.pagetype | ms.sitesec | author | ms.date | ms.topic |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Create a task sequence with Configuration Manager and MDT (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. | 0b069bec-5be8-47c6-bf64-7a630f41ac98 | laurawi | greglin | deploy, upgrade, task sequence, install | w10 | deploy | medium | mdt | library | greg-lindsay | 07/27/2017 | 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.
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.
-
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.
-
On the Choose Template page, select the Client Task Sequence template and click Next.
-
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
-
-
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>
-
-
-
On the Capture Settings page, accept the default settings, and click Next.
-
On the Boot Image page, browse and select the Zero Touch WinPE x64 boot image package. Then click Next.
-
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.
-
On the MDT Details page, assign the name MDT and click Next.
-
On the OS Image page, browse and select the Windows 10 Enterprise x64 RTM package. Then click Next.
-
On the Deployment Method page, accept the default settings and click Next.
-
On the Client Package page, browse and select the OSD / Configuration Manager Client package. Then click Next.
-
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.
-
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.
-
On the Settings Details page, assign the name Windows 10 x64 Settings and click Next.
-
On the Sysprep Package page, click Next twice.
-
On the Confirmation page, click Finish.
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.
-
On CM01, using the Configuration Manager Console, select Task Sequences, right-click Windows 10 Enterprise x64 RTM task sequence, and select Edit.
-
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.
-
In the Post Install group, select Apply Network Settings, and configure the Domain OU value to use the Contoso / Workstations OU (browse for values).
-
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.)
-
After the disabled Post Install / Auto Apply Drivers action, add a new group name: Drivers.
-
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
-
-
In the State Restore / Install Applications group, select the Install Application action.
-
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
-
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
-
-
-
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
-
-
-
Click OK.
[!NOTE] The Request State Store and Release State Store actions need to be added for common computer replace scenarios.
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.
-
On CM01, using the Configuration Manager Console, in the Software Library workspace, expand Application Management, and then select Packages.
-
Select the MDT and Windows 10 x64 Settings packages, right-click and select Move.
-
In the Move Selected Items dialog box, select the OSD folder, and click OK.
Related topics
Integrate Configuration Manager with MDT
Prepare for Zero Touch Installation of Windows 10 with Configuration Manager
Create a custom Windows PE boot image with Configuration Manager
Add a Windows 10 operating system image using Configuration Manager
Create an application to deploy with Windows 10 using Configuration Manager
Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
Deploy Windows 10 using PXE and Configuration Manager
Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager