Jump to content


using SCCM 2012 RC in a LAB - Part 18. Deploying a UDI Client Task Sequence with MDT 2012 RC1 integrated in Configuration Manager 2012

Recommended Posts

In Part 1 of this series we got our AD and SCCM servers ready, and then we installed System Center 2012 Configuration Manager as a standalone Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles necessary for the following Configuration Manager 2012 functionality, Software Update Point (SUP) and Operating System Deployment. In Part 3 we configured the server further by Enabling Discovery methods and creating Boundary's and Boundary Groups. In Part 4 we configured Client Settings, Added roles and Distributed the Configmgr Client to our Computers within the LAB, then in Part 5 we enabled the Endpoint Protection Role and configured Endpoint Protection settings and targeted a collection called All Windows 7 Computers with these settings and policies.

In Part 6 we configured our SUP further to Deploy software updates to our All Windows 7 Computers and Build Windows 7 X64 collections. In Part 7 we used the Build and Capture process to create our Base Windows 7 X64 wim image. In Part 8 we created a USMT 4 package to migrate the users data using hardlinking and then we imported the captured image into ConfigMgr and created a Deploy Windows 7 X64 task sequence. We created a Deploy Windows 7 X64 Collection and set some User Device Affinity collection variables.

In Part 9 we created an Application, and created a deployment type for that application to only install if the Primary User was True for that device (User Device Affinity), we then copied our Task Sequence (duplicated it), deployed the new Task Sequence, added a computer to the new collection and then PXE booted the computer to the Deployment Menu. In Part 10 we monitored the Deployment process in a lot of detail to how UDA sent state messages and we verified that our application installed on the users Primary Device, in addition we modified our collection variables, and added a prestart command to our boot image to prompt for the SMSTSUdaUsers. In Part 11 we setup the Reporting Services Point Role and verified that reporting was working.

In Part 12 we demonstrated a new feature in ConfigMgr which allows us to Patch operating system WIM images using Offline Servicing. This means that you can apply Windows Updates by using Component-Based Servicing (CBS) to update the your previously captured WIM images. In Part 13 we looked at how Role Based Administration is used within ConfigMgr and we created a new custom role to allow a user (or users within a Security Group) to view Software Update Reports. This is useful because you will probably want one team to take care of configuring and deploying software updates, and to grant another (Management etc) the capability of reviewing Compliance Reports. In Part 14 we performed a side-by-side migration from Configuration Manager 2007.

In Part 15, we deployed Windows 8 Consumer Preview to see if it was possible, and indeed it was (it's not supported by Microsoft however). In Part 16 we integrated MDT 2012 RC1 with Configuration Manager 2012 RC2. In Part 17 we configured MDT 2012 and used the UDI Wizard designer to configure the default Custom XML file used in a UDI task sequence. Now we will configure that XML file some more before creating a new MDT Task sequence to Deploy a User Driven Installation Client Task Sequence. We will then edit that task sequence to add Offline Language support and finally deploy it and monitor a client progress.

Tip: This post is long and may take you some time to complete so do please give yourself plenty of time to go through it all.

Step 1. Remove the prompt for Computername in our MDT boot image
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

In it's current state, when we boot our MDT boot image it will prompt the end user to enter a computername as you can see in the screenshot below

computername being prompted for.png

we don't need this functionality as we will use the computer naming ability within the UDI wizard itself, so let's disable this. To remove the prompt locate your MDT Boot image in the boot images node, right click and choose properties

mdt boot image properties.png

Click on the Customization tab,the prestart command will look like this

prestart commandline before.png

edit it so that it just reads


then click apply as in this screenshot

prestart command after.png

answer yes to update the boot image to your distribution points, continue through that wizard to completion.

dp update required.png

Step 2. use the UDI Wizard Designer to configure network settings and other changes
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

We already edited our UDIWizard_Config.XML file in the previous part but we need to make some additional changes to make it more user friendly and functional, so let's start up the UDI Wizard Designer again (start, programs, Microsoft Deployment Toolkit, UDI Wizard Designer).

start the UDI wizard designer.png

when the UDI Wizard Designer starts, click on the file ribbon and select our recently edited UDIWizard_Config.XML file.

recent document.png

Select the BitLockerPage and remove the checkmark so that we are not prompted to enter any BitLocker info

BitLocker changes.png

Next, double click on the New Computer Details Page and expand Network Details, select Domain

New Computer Details.png

scroll down further to Domains and OUs, click on the blue Plus symbol to add a domain

add domain.png

when the Create or edit Domain Information window pops up

create or edit domain information.png

enter your domain info and friendly text something like below..

server2008r2 domain name added.png

click ok when done, to add a default OU right click on the added domain and choose Add OU Manually

add ou manually.png

now you get the chance to add your OU information, so add it using the Distinguished name (which you can get from Active Directory)

no firewall OU.png

click ok when done, it should now appear something like this

server2008r2 details added.png

scroll down to Domain Join Credentials and add your domain join user account (I use one called Domjoin)

domain join credentials.png

Next open the Languages Page and add a few more languages (i'm using the scandinavian ones...) if you want,

add language packs.png

and then scroll down to the Volume page and select the User data and settings option, place a checkmark in the Format box...

user data combo behaviour.png

ok that's us done in the UDI Wizard designer so save your UDIWizard_Config.XML file to the Scripts folder of your MDT Toolkit Files package, and once done don't forget to Update your distribution points for the MDT Toolkit Files package.

update dp for mdt toolkit files.png

Step 3. Create Language Packs
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

If you have read my Customizing Windows 7 series you'll have seen that we added language packages offline using MDT 2010 update 1 in Configuration Manager 2007, we will use similar functionality here in Configuration Manager 2012 RC2 but with MDT 2012 RC1. But before we do, we need some language packages added. I will add Danish here and I expect you to add whatever languages you are interested in.

In the ConfigMgr console click on Packages , select Create Pacakge from the ribbon or right click and select Create Package.

create package language.png

give the language pack some useful name like Windows 7 X64 SP1 Danish Language Pack and details so that it's easy to find in the task sequence later on...click on Browse and select the folder where you have your Danish langauge pack (eg: \\sccm\sources\os\Windows 7 X64 Language packs\Windows 7 X64 - Danish)

danish language package details.png

click next and then select Do not create a program

do not create a program.png

click your way through the rest of that wizard.

Note: when the package is created add it to your distribution points and update it to the dp's. Repeat the above for all language packs you intend to use in your UDI task sequence.

once done we should have all the Language Packages we need and intend to use created and distributed like below:-

language packages added.png

Step 4. Create a MDT based UDI Client Task Sequence
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

We need to create a new MDT Task Sequence which leverages a User Driven Installation template, we will then edit it slightly before deploying to a Deploy Windows 7 X64 collection.
So right click on Task Sequences and choose Create MDT Task Sequence

create MDT task sequence udi.png

when prompted to choose a template, select User Driven Installation Task Sequence from the drop down menu


choose template.png


Note: In later versions of Configuration Manager 2012/MDT 2012 the wording in the template is changed from the screenshot above from User Driven Installation Task Sequence to Client Task Sequence and the option to select a User Driven Installation comes from within the Create MDT Task Sequence wizard, specifically when you get to the Deployment Method screen, choose User Driven Installation at that point to get a true UDI task sequence. See screenshot below for that setting.

Perform a User Driven Installation.png

give the task sequence a name like UDI Client Task Sequence

UDI client task sequence name.png

Enter domain details and Windows settings, nothing new here in fact we'll be using our UDI xml file to replace the network settings later...

network and windows details.png

Select This task sequence will never be used to capture an image...

mdt udi capture settings.png

select our previously created MDT boot image

mdt boot image udi.png

and our previously created MDT Toolkit Files package

mdt toolkit package udi.png

Next you get to specify the Windows 7 X64 image we captured in Part 7.

specify existing image.png

specify the Configuration Manager Client upgrade package which we also created in Part 7 (Step 5.).

specify client package.png

and then specify the USMT 4 package

usmt 4 package udi.png

and next we specify our MDT Settings package, have patience we are getting there :-)

mdt settings package udi.png

click next through to the confirmation message

confirmation udi.png

click Finish

Step 5. Edit the Task Sequence to add Language packs
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

Language pack installation steps are not included in our UDI task sequence, so we have to add those steps, to do so right click on our newly created task sequence and choose Edit

edit udi task sequence.png

scroll down to the Post Install stage and to the Set Status 3 step (which occurs just before the Setup windows and configmgr step). This is where we need to add our new step(s) to install language packs offline.

set status 3.png

In the top left corner of your task sequence, click on Add, scroll down to MDT and choose Install Language Pack offline, these options are only available after MDT is integrated with ConfigMgr

add mdt step.png

click on Browse and select your Swedish Language pack (or whatever language you are adding)

install language packs offline step.png

click on the options tab for that step and add the following options, Task Sequence variable UIlanguage equals SV-SE

uilanguage equals sv-se.png

Note: repeat the above process to add a new Install Language Pack Offline step for each Language you want to add, rename each step to correspond to the language you are installing and obviously the SV-SE task sequence variable in the options tab will have to correspond to the correct language, eg DA-DK for Danish etc..

install 4 languages.png

click Apply and then ok the save the changes to your Task Sequence.

Step 6. Deploy the Task Sequence
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

Right click the Task Sequence, choose Deploy

deploy ts udi.png

choose the Deploy Windows 7 X64 collection

deploy win7 collection.png

set it to Available and make it available to boot media and PXE, continue through the rest of the wizard.

availbe udi ts.png

once done, add a new virtual machine to your Deploy Windows 7 X64 collection, you can use this process if you wish.

Step 7. PXE Boot a client and review the UDI process
Note: Perform the following on virtual machine as a testuser

After PXE booting our new virtual machine


we get to see the list of available task sequences, note the really cool background ;-)

select udi task sequence.png

after some moments of downloading the MDT Toolkit package, the UDI wizard appears !

welcome to the deployment wizard.png

and you can click your way (as a user driven installation is supposed to be done, by the end-user) through the wizard, the first screen after the welcome screen is the BItlocker screen, it's not enabled as we removed that option

bitlocker screen.png

next we see the Volume screen, notice that Partition and format disk is selected already, we did that in the UDI Wizard Designer above.


This is a new computer so we are not restoring any data, so click next at that screen

no data to restore.png

the Deployment Readiness screen appears, this changes depending on New computer or refresh scenario and just lists the checks it performs you can retry checks in the event that you forgot to connect power to a laptop or whatever..

deployment readiness.png

next you get the User Device Affinity screen, enter a primary user if you wish and click next, i guess you could call this the UDI UDA user screen

udi uda user.png

and we can choose domain/OU based on what we entered in our UDI Wizard designer, enter the Domain Join credentials (password) to continue..

domain join creds.png

enter the local administrator password and specify a user (or users) to add to the local administrators group

admin pass.png

select your language and regional settings, notice how there are as many languages *listed to install* as you added in the UDI Wizard designer

language udi.png

for the Install programs screen, you can see the apps we added earlier, you can select or deselect them and click next to continue, cool huh ?

install programs udi screen.png

click next at the summary and let the installation begin, note how it shows you what stage it's on via a changing background picture

install image.png

and after some time the language pack you selected is installed

Installing swedish language pack.png

and finally when the Deployment is complete you see the following,

deployment complete.png

click on start windows to logon to windows

Swedish Windows :-) job done..

swedish windows.png

cheers !



Share this post

Link to post
Share on other sites

No big deal, but perhaps it can save somebody else some time? Everything worked according to instructions - except that the language pack (sv-se) wasn't installed...


Turned out I used an old lp.cab file from pre-SP1 days, once it was replaced with the correct one - Voila, right on!


And, of course, a big thank you to you Niall!!

  • Like 1

Share this post

Link to post
Share on other sites

Am I missing the option to set things up for UK English?

I couldn't find an option in the UDI Wizard for UK English, so in the end I added a step to the Task Sequence to set InputLocale to "en-GB." That seemed to work for me!

Share this post

Link to post
Share on other sites


When following the guide CLOSELY, but using rhe latest Win7 x64 SP1



AND Languagepack



from Microsoft Volume Licensing Service Center.


The language package install starts, but then skips after a few seconds.


We do not get any errors and do not have "Continue on error" set. And the installation is not interrupted or anything. The languagepack just isn't installed.

Do you have any ideas?

Share this post

Link to post
Share on other sites


Actually todd9774 nailed it for me!!


Here it is:

DO NOT point to the lp.cap folder directly.

If your language pack is contained in the in the folder structure \\"servername"\sources\languagepacks\da-dk\lp.cap

you should point to





BUT be ware; EVERYTHING in the \\"servername"\sources\languagepacks\ folder will be copied to the distibution point!!

So if you want to use one or more languagepacks please do as Niall: create a folder for each language, da, de, ch, etc and put the corresponding language folders da-dk, de-de, etc, in there.





THEN point to the da, de, etc.folders in the individual packages in System Center.






Works like a charm

/Thomas Ehler

  • Like 1

Share this post

Link to post
Share on other sites


When re-deploying a workstation that has failed, the "Unknown" workstation in "Devices" just stays there.

It doesn't move into "All Unknown Computers" or another collection.

In other words it is now "known" but not a member of any collection so it will not be offered any installation.


WHAT to do?

Share this post

Link to post
Share on other sites

I have a problem with getting the client to join the domain through the UDI.


I have double-checked all the settings and can't fin anything different from this guide. Also it does not install my applications.

However if i join the domain manually everything is as it should be.


Any ideas?

  • Like 1

Share this post

Link to post
Share on other sites

I couldn't find an option in the UDI Wizard for UK English, so in the end I added a step to the Task Sequence to set InputLocale to "en-GB." That seemed to work for me!


Could you expand on how you did that please?

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.