Jump to content




anyweb

How can I deploy Windows 10 with MDT 2013 Update 2 integrated with System Center Configuration Manager (Current Branch)



Recommended Posts

Introduction

 

At the start of this series of step by step guides you installed System Center Configuration Manager (Current Branch), then you configured discovery methods. Next you configured boundaries to get an understanding of how automatic site assignment and content location works. After that you learned how to update ConfigMgr with new features and fixes using a new ability called Updates and Servicing and you learned how to configure ConfigMgr to use Updates and Servicing in one of these two modes:

To prepare your environment for Windows 10 servicing (this guide) you learned how to setup Software Updates using an automated method (via a PowerShell script) or manually using the ConfigMgr console. Next you used a PowerShell script to prepare some device collections, then you configured client settings for your enterprise and finally you'll deployed the ConfigMgr client agent using the software updates method which is the least intensive method of deploying the Configuration Manager client agent.

 

As System Center Configuration Manager (current branch) is being delivered as a service now, version 1602 was made available (March 11th, 2016) and you used Updates and Servicing to do an in-place upgrade to that version as explained here. Next you learned about how to use the Upgrade task sequence to upgrade your Windows 7, Windows 8 (and 8.1) and even your Windows 10 devices to a later build of Windows 10.

 

You then learned about the new Windows 10 servicing features which use Servicing Plans in ConfigMgr (Current Branch). In this guide you will integrate MDT 2013 update 2. MDT integration with ConfigMgr is useful as it provides additional functionality for operating system deployment scenarios such as Offline Language Package installation or User Driven Integration (UDI).

 

Note: This guide assumes that you have not yet enabled or configured a PXE distribution point or Network Access Account, if you have, then you can skip those steps. In addition, this guide assumes you have created a DHCP scope on your Active Directory Domain Controller and activated it.

 

Step 1. Download MDT 2013 Update 2

Download the MDT 2013 Update 2 x64 MSI from the following link.

 

download mdt2013update2.png

 

In addition to downloading MDT 2013 Update 2, you might want to download the MDT ZIP file (located in the downloads section at the end of this post) which contains pre-created folders and files for use in the Create MDT Task sequence wizard. Simply extract it to the desired sources folder on your ConfigMgr server, for example:

\\<ConfigMgrServer>\sources\osd\

the folders it creates are highlighted below after extraction

 

folders created highlighted below.png

 

Step 2. Install MDT 2013 Update 2

After you've downloaded the msi, it's time to install it. On your ConfigMgr server double-click the MSI and the wizard will appear

 

welcome to the wizard.png

 

accept the EULA and click next

 

EULA.png

 

choose where you want to install MDT, for example on D:\Program Files\Microsoft Deployment Toolkit\

 

custom setup.png

 

select if you want to participate in the CEIP or not

 

ceip.png

 

and then click Install and accept the UAC prompt

 

install.png

 

when complete, click Finish to close the wizard

 

finish.png

 

Step 3. Integrate MDT 2013 Update 2 with ConfigMgr

Now that you have installed MDT you should integrate it with ConfigMgr. You do this to gain access to tools and features that MDT provides from within the ConfigMgr console. In the start screen, locate the newly installed Microsoft Deployment Toolkit application group, right click Configure ConfigMgr Integration shortcut and right click, choose Run as Administrator.

 

run as administrator.png

 

The wizard settings will default to Install the MDT extensions for Configuration Manager the first time you run the integration

 

configure confifmgr integration.png

 

after clicking next you should see output similar to below, if not, make sure you chose Run As Administrator

 

the process completed successfully.png

 

Note: If the ConfigMgr console was open during this process, close it and then open it again to view the MDT integration.

 

Step 4. Add the latest Windows 10 Enterprise x64 media

I'd recommend you use the latest Windows 10 Enterprise x64 media from Microsoft Volume License site (or MSDN for a lab). The latest available media is updated with February Cumulative Updates for 1511. Mount the ISO using Windows File Explorer. After mounting the ISO, copy the contents to somewhere useful like:

\\<ConfigMgrServer>\\Sources\OSD\OS\OSImages\Windows10x64\1511

os image.png

 

to add the operating system do as follows. In the ConfigMgr console, select Software Library, then Operating Systems then Operating System Images. Right click and choose Add Operating System Image.

 

Add operating system image.png

 

Point it to the install.wim file in the sources folder of the Windows 10 Enterprise x64 media you just added

 

install wim.png

 

and fill in some details about the image before continuing through that wizard until completion.

 

windows 10 details.png

 

Note: To make the image available on the network, distribute it to your distribution points by right-clicking and choose Distribute Content.

 

distribute content.png

 

Select one or more distribution points, and continue through that wizard until completion.

 

distributed.png

 

Step 5. Configure a Network Access Account

You'll need to configure a Network Access Account to allow content to be downloaded while in WinPE. To configure the Network Access Account do as follows:

 

In the ConfigMgr Console, Administration workspace, select Site Configuration then Sites and right click on the Primary site listed (P01). Choose Configure Site Components, then Software Distribution.

 

configure site components.png

 

then choose Specify the account that accesses network locations, choose New and enter the credentials of the account you plan on using for Network Access.

 

network access account.png

 

Apply the changes and close the wizard.

 

Step 6. Enable PXE support on the Distribution Point

Note: These actions install Windows Deployment Services files to C:\RemoteInstall, if you want to use a custom path or different drive letter then configure WDS manually before enabling PXE. This step assumes you have already configured a DHCP scope and activated it on your Active Directory domain controller.

 

Enabling PXE support on the distribution point configures Windows Deployment Services automatically. To do this, open the Administration workspace and select a distribution point, right click and choose Properties.

 

dp in administration.png

 

Select the PXE tab and use the following settings:

  • Enable PXE support for clients
  • Allow this distribution point to respond to incoming PXE requests
  • Enable Unknown Computer support
  • Require a Password when computers use PXE <P@ssw0rd>
  • Allow user device affinity with Automatic Approval

PXE settings.png

 

Click Apply when done.

 

Step 7. Create MDT boot image, MDT Toolkit and MDT settings packages

In order to utilize MDT within ConfigMgr, you need to create a few MDT components namely

  • MDT Boot image
  • MDT Toolkit Files
  • MDT Settings

These can be created the first time you create an MDT task sequence. To do that follow this process. In the ConfigMgr console browse to Software Library, Operating Systems, right click on Task Sequences and choose Create MDT Task Sequence.

 

create MDT task sequence.png

 

Choose a Template, there are several provided in the drop down menu listed below:

  • Client Task Sequence
  • Client Replace Task Sequence
  • Microsoft Deployment Custom Task Sequence
  • Server Task Sequence
  • User Driven Installation Replace Task Sequence

choose the default option which is Client Task sequence

 

client task sequence.png

 

give the MDT task sequence a suitable name

 

mdt task sequence name.png

 

enter domain join details and choose an administrator password

 

domain join.png

 

keep the default capture settings

 

default capture settings.png

 

for Specify a boot image package to use, select the second option, create a new boot image package and browse to a previously created empty folder UNC path which contains a folder matching the version of WinPE and the Architecture of the boot image you are about to create, eg:

\\<ConfigMgrServer>\Sources\OSD\boot\WinPE 10 x64

Note: If you used the MDT.ZIP file mentioned in step 1, then this folder will already be present. Also to note, do not place a backslash at the end of the path as ConfigMgr will add that to the path and you won't be able to distribute the boot wim later.

 

create a new MDT boot image.png

 

fill in some details about the boot image

 

general settings.png

 

then select the x64 Architecture and scratch space

 

options.png

 

on the Components screen, browse through the list of components you want added to the boot image, for example if supporting Windows PowerShell add it here.

 

components.png

 

On the Customization screen you get to choose background wallpaper, prestart commands and extrafiles in addition to enabling command support (F8). To enhance the built in logging ability you'll add smsts.ini via Extrafiles. I won't go into more detail about that other than to refer you to this post where everything is explained.

 

Below you can see the smsts.ini file that is copied to an Extrafiles\Windows folder

 

smsts ini file copied to extrafiles windows folder.png

 

and in the customization screen, you point to that previously created path

 

customization.png

 

Next you get to create the MDT Toolkit Files package, so select the Create a new Microsoft Deployment Toolkit Files package option, and point it to a previously created path such as below:

\\<ConfigMgrServer>\sources\osd\MDT\MDT2013u2\Toolkit

create a new microsoft deployment toolkit files package.png

 

fill in details about the MDT Toolkit Files package..be descriptive as it's common to have different versions of MDT Files over time

 

mdt details.png

 

Select your previously added Operating System Image (first option)

 

specify an existing OS image.png

 

For Deployment Method you get to choose the type of task sequence interaction will be used:

  • Perform a zero touch installation os deployment, with no user interaction
  • Perform a user driven installation

if you want your users to have choices then select the UDI option, otherwise select the Zero Touch option to remove choices from the task sequence.

 

zero touch.png

 

for Client Package, select Specify an existing ConfigMgr client package and browse to the one you wish to use.

 

Configmgr client package.png

 

for USMT Package select the User State Migration Tool for Windows 10 package

 

usmt package.png

 

For Settings Package, you need to create a new MDT 2013 Update 2 settings package, therefore select the second option. You only have to do this once for each version of MDT you have installed.

 

Select Create a new settings package and fill in the path to be created as shown below something like:

\\<ConfigMgrServer>\sources\osd\MDT\MDT2013u2\Settings\

mdt settings details.png

 

for Sysprep Package, set No sysprep package is required and continue through to the end of the wizard and after a while you'll get a process completed successfully message.

 

Note: If you want to create the WinPE 10 x86 mdt boot image, repeat the above, except do not create new toolkit and settings packages, and change the architecture of the boot wim for that step.

 

mdt task sequence created.png

 

Step 8. Distribute task sequence content

At this point you are nearly ready to start testing, but first you need to distribute the task sequence content to your distribution points, the easiest way to do that is to right click on the Windows 10 x64 version 1511 - Zero Touch MDT task sequence and choose Distribute Content.

 

distribute content for task sequence.png

 

the Distribute content wizard appears, listing all the packages in the task sequence

 

distribute content wizard.png

 

select one or more distribution points by clicking Add and continue through the wizard until completion

 

distribute content wizard completed.png

 

Step 9. Enable PXE support for the MDT boot image

Browse to Software Library, Operating Systems, Boot images and select the WinPE 10 x64 boot image. Right click and choose Properties, and select the Data Source tab. Place a checkmark in Deploy this boot image from a PXE enabled distribution point.

 

deploy this boot image from the PXE enabled distribution point.png

 

Repeat the above for the WinPE 10 x86 boot image.

 

Step 10 . Deploy the task sequence

Browse to Software Library, Operating Systems, Task Sequences and select the Windows 10 x64 version 1511 - Zero Touch task sequence. Right click and choose Deploy and use the following settings:

 

For collection choose the OSD_Deploy collection (created in this guide)

 

OSD_Deploy.png

 

for Deployment Settings make sure it is set to Available and deployed to Only media and PXE

 

only media and pxe.png

 

and continue through the rest of the wizard until completion.

 

Note: The last task sequence deployed (last in, first out or LIFO) will have an effect on which boot image is offered to PXE clients. If you require the WinPE 10 x64 boot image to 'answer' your clients, make sure it's attached to the last task sequence deployed.

 

Step 11. PXE boot a computer

Now everything is in place for testing a deployment of Windows 10 using an MDT 2013 Update 2 integrated task sequence in Configuration Manager (current branch). Simply PXE boot a computer that is a member of the OSD Deploy collection.

 

While PXE booting, you can verify that the WIM file it's pulling down is indeed your newly created MDT 2013 update 2 boot image by looking at the boot image package id.

 

pxe boot.png

 

after is has completed PXE boot the custom wallpaper is in place and the PXE password prompt is waiting

 

custom wallpaper.png

 

enter the PXE password and choose the appropriate task sequence

 

select a task sequence.png

 

and off it goes...

 

osd in progress.png

 

and you can see the familiar MDT background with information about the stages of deployment

 

mdt deployment details.png

 

and after a while, it's all done !

 

all done.png

 

Summary

Using MDT integrated task sequences is relatively easy once you understand what needs to be put in place beforehand. In a later post you'll see how to use some of the added functionality that MDT integrated task sequences provide within the ConfigMgr console.

 

Related Reading

Downloads

You can download a Microsoft Word copy of this guide here dated 2016/04/30 Deploying Windows 10 with MDT 2013 Update 2 in System Center Configuration Manager (current branch).zip

 

Download a copy of the MDT files and folders used in the Create MDT task sequence wizard here MDT.zip

 

 

 

Share this post


Link to post
Share on other sites


The steps are pretty generic, you should be fine to follow them for Windows 7 although if you are setting up for both OS then some of the steps you wont need to do twice (Installing and integrating MDT, creating a service account, enabling PXE)

Share this post


Link to post
Share on other sites

Hi guys,

 

I get the followinh error message if I boot from Network. I have done the following steps for resolving:

1) I have deleted on the SCCM server "Clear Required OXE Deploment"

2) I have deleted the Client from my Collection and added that again

But no change. Any Idea?

 

post-17658-0-60507200-1473079549.png

Share this post


Link to post
Share on other sites

search for obsolete records matching the mac address.

Share this post


Link to post
Share on other sites

The steps are pretty generic, you should be fine to follow them for Windows 7 although if you are setting up for both OS then some of the steps you wont need to do twice (Installing and integrating MDT, creating a service account, enabling PXE)

Sure that's fair. I guess I should have been more specific, because you are right I don't need to re-install MDT for Windows 7.

 

My question really should have been "what (if anything) should I change when creating a deployment task sequence for Windows 7x64?"

Share this post


Link to post
Share on other sites

simply edit the task sequence and add them somewhere after the Setup Windows and ConfigMgr step

Share this post


Link to post
Share on other sites

you see the Install Software step, that will do for starters or if you plan on doing dynamic applications use the Install Applications group (and steps)

Share this post


Link to post
Share on other sites

Sure that's fair. I guess I should have been more specific, because you are right I don't need to re-install MDT for Windows 7.

 

My question really should have been "what (if anything) should I change when creating a deployment task sequence for Windows 7x64?"

 

Nothing really. Obviously change the driver packs to Windows 7 driver packs. There is a very good guide on this forum for creating and deploying Windows 7 https://www.windows-noob.com/forums/topic/4512-using-sccm-2012-rc-in-a-lab-part-8-deploying-windows-7-x64

Share this post


Link to post
Share on other sites

Anyweb
you see the Install Software step, that will do for starters or if you plan on doing dynamic applications use the Install Applications group (and steps)

I dont see no "install Software"

Share this post


Link to post
Share on other sites

Anyweb

you see the Install Software step, that will do for starters or if you plan on doing dynamic applications use the Install Applications group (and steps)

I dont see no "install Software"

 

In the middle of the second image. There is a folder for 'State Restore', follow that down 9 steps and it is between 'Enable Bitlocker' and 'Restore Groups'

Share this post


Link to post
Share on other sites

I am following from the beginning of the current branch.

How can i add unknown " are new computers consider unknown?" to OSD_Deploy collection?

Thank you,

Share this post


Link to post
Share on other sites

i don't understand your question, did you use my PowerShell script to create the collections ?

Share this post


Link to post
Share on other sites

I did use PS to create collections. And i do see a client in the collection.

That client is in the OSD Deploy collection but has an "X" on the icon, and active under status.

 

Maybe because it was off for some time. Or maybe something else? Not sure how to check the state of the client.

 

Just tried pxe booting again, and downloading boot.wim now.

Thank you very much for all your work.

 

Wanted to ask you something else now related to SCCM, how is the car coming? Any update pictures?

Share this post


Link to post
Share on other sites

Task Sequence finished. But did not joined the domain.

Interesting that c:\windows\sysWOW64\ccm folder is empty and there is no logs folder.

 

Looking at Configuration Manager Properties under site there is no Currently assigned site, Find Site is disabled and i am not able to type one is. Logged in as a local admin.

Under Actions i only see Machine user policy.

 

Do i have client config wrong?

Share this post


Link to post
Share on other sites

Dear Sir/Madam,

 

I found the folder where the files and folders are supposed to be located. It is SMS_PWA\osd\boot\

But I can’t open the folder, because I don’t have the rights to do so. Am I doing something wrong, or is something supposed to happen first?

Share this post


Link to post
Share on other sites

I have made a previous successful MDT TS this way, but when I tried to make another new one, I get the following error:

Can I get some direction on how to resolve this?

Thanks

 

Started processing.

Creating boot image.

Copying WIM file.

Mounting WIM file.

WIM file mounted.

Setting Windows PE system root.

Set Windows PE system root.

Set Windows PE scratch space.

Adding standard components.

Adding component: winpe-netfx

Error while importing Microsoft Deployment Toolkit Task Sequence.



System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.



Server stack trace:

at System.ServiceModel.Channels.CommunicationObject.ThrowIfFaulted()

at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)



Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)

at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)

at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)

Share this post


Link to post
Share on other sites

I went back through and re-created everything from scratch using Windows 10 1607, MDT 8443 and ADK 1607 and everything is working now.

  • Like 1

Share this post


Link to post
Share on other sites

I cant seem to find the following folder?

what file is MDT looking for? How was WinPE 10 x64 added? 

for Specify a boot image package to use, select the second option, create a new boot image package and browse to a previously created empty folder UNC path which contains a folder matching the version of WinPE and the Architecture of the boot image you are about to create, eg:

\\<ConfigMgrServer>\Sources\OSD\boot\WinPE 10 x64

Share this post


Link to post
Share on other sites
On 3/14/2017 at 11:59 PM, su5577 said:

I cant seem to find the following folder?

what file is MDT looking for? How was WinPE 10 x64 added? 

for Specify a boot image package to use, select the second option, create a new boot image package and browse to a previously created empty folder UNC path which contains a folder matching the version of WinPE and the Architecture of the boot image you are about to create, eg:


\\<ConfigMgrServer>\Sources\OSD\boot\WinPE 10 x64

MDT is not looking for any files. 'WinPE 10 x64' is a folder that was created to store the new Boot image that is being created by the MDT Wizard. At this step you just need to fill in the UNC path.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×