Jump to content


Photo

using SCCM 2012 RC in a LAB - Part 17. Using MDT 2012 RC1 within Configuration Manager 2012


  • Please log in to reply
8 replies to this topic

#1 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 5,654 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 17 March 2012 - 11:25 PM

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 and now we will configure it to see what it can do with that integration by using the UDI Wizard designer to configure the default Custom XML file used in a UDI task sequence namely UDIWizard_Config.xml.

Step 1. make the MDT boot image PXE bootable
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

After integrating MDT with ConfigMgr we created a MDT Task Sequence and as part of that wizard we created a MDT Boot image. This boot image gives us additional power and functionality over a standard ConfigMgr boot image (for example, we can display HTA's with this boot image without having to mount/unmount the boot.wim file and add additional support).

Locate your MDT boot image in Software Library, Operating Systems, Boot Images, right click on it and choose Properties

mdt boot image right click.png

When the properties screen appears, click on the Data Source tab, place a check-mark in Deploy this boot image from the PXE service point.

MDT deploy this boot image from the pxe service point.png

click OK when done.


Step 2. Modify the UDIWizard_Config xml file using the UDI Designer Wizard.
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

As we will be creating a User Driven Installation Task Sequence in the next part, we first want to customise what our users will see when that wizard appears and to do so we need to use the UDI Designer Wizard. So click on Start, Programs, Microsoft Deployment Toolkit, and select the UDI Wizard Designer from the menu.

UDI wizard designer.png

The UDI Wizard Designer starts and you'll be presented with the new gui, we can use this gui to make changes to the built in UDI templates, they are simply XML files stored in the scripts folder of our MDT Files package.

welcome to the udi wizard designer.png

We could click on New to create a new XML file but let's import that one that the standard UDI Task Sequence uses namely UDIWizard_Config.xml. So let's load up that file from the copy we have in our MDT Files package, if you remember in Part 16 we created that package in \\sccm\sources\os\mdt\2012_rc1\files so let's click on Open in the UDI Wizard ribbon to browse to that location.

udi wizard open.png

type in the path to our MDT Files package namely \\sccm\sources\os\mdt\2012_rc1\files and click on the Scripts folder highlighted in the screenshot below

scripts folder.png

a long list of xml files appears, scroll down to UDIWizard_Config.xml and click on it then click on open

UDIWizard_Config xml file.png

once the xml file is loaded you'll notice the wizard changes look, this is an overview of each page that the User Driven Installation task sequence wizard is capable of showing and here is where we configure them. But first, how do we make sense of this gui, i'll try and explain it briefly, in the Red box below you have the three main scenarios that we'll encounter during deployments sorted into StageGroups

udi wizard designer flow designer.png
  • New Computer
  • Refresh
  • Replace
If you expand New Computer you'll see a whole bunch of thumbnails for that StageGroup (and you'll also see New Computer.Prestaged below it), those thumbnails are what the User will see when the wizard kicks off later... note that depending on the scenario you are in, you'll be presented with different pages of the wizard.




new computer stagegroup.png

In the Left pane of the wizard you'll see the available pages listed alphabetically in the page library (not in the same order as they are presented to the end-user). Double click on one and you'll see the configurable options for that page (you can single click and you might see those options depending on whether or not you are in Flow or Configure mode, that's those two tabs in the right pane...)

udi left pane.png

Click on Install Programs in the Left Pane, the number 3 in the right is the number of stages this Page is available in (you can hover your mouse over it to see what they are).

install programs udi.png

Notice there is a Configuration Manager button in the ribbon, click on it.

site settings.png

This brings up the Site Settings box, fill in your Configuration Manager site server name and site code and click on Validate Site.

site settings validated.png

Note: The message states that this is required to add software items. To make application(s) available on the software page, applications must be targetted at the provided collection namely All Systems. The All Systems collection is a Device collection (for your computers..) so please deploy a few applications to that collection.

Double click on Install Programs or click on the Configure tab

configure tab.png

next, click on General Software in order to see a menu we need (you can also right click on General Software to see a menu)

click on General Software.png

Now that we have these extra options let's click on the big blue plus sign to add software to group

add software to group.png

the Add Software to Group wizard appears, select I want to add an application and click next

i want to add an application.png

now the Software Selection Wizard appears (another wizard within a wizard), click on Select to search for an application (why not call it search..?)

select.png

and that brings up another wizard to search applications.. if you know the name of your application type it in here or click on search, after clicking on search, any applications deployed to the All Systems collection and with the Allow this application to be installed from the Install Application task sequence action instead of deploying it manually setting set in the applications properties will appear in the list.

search apps.png

The application setting is here...

allow this application.png

select one application from the list and click on Finish

select and finish.png

you're newly added application appears in the list

select it.png

repeat the above process until you've added all your cool apps...

all cool apps.png

and finally right click on the Sample Application from the list and click on Remove Item

remove item.png

Next, Click on the LanguagePage in the left pane and add the Swedish Language (or whatever language(s) you want)

add swedish.png

and finally configure our Wizard config by clicking on Wizard Config in the ribbon. The Edit Wizard settings diaglouge box appears, you can customize the name and the background (banner), the default bmp file itself is located in the path where you installed Microsoft Deployment Toolkit in the Templates\Disitribution\Tools\X64 or X86 folders.

edit wizard settings.png

make your changes and click ok.

edit wizard settings done.png

Ok now that we've done some basic configuration of our UDI template let's save it.

save my udi.png

if all went well you'll see File Save Complete.

file save complete.png

you can verify that the XML file itself has changed by it's date/time

udiwizard config file saved.png

Step 3. Update your MDT Files package.
Note: Perform the following on the ConfigMgr 2012 server as SMSadmin

now that you've made changes to your UDIWizard_Config.xml you will want to update the MDT Files package so that we have access to those changes in the next part of this series where we'll create and deploy a User Driven Installation Task Sequence.

In Software Library click on Packages and locate your MDT Files package. Right click on it and choose Update Distribution Points

update dps for mdt files.png



thats it for this part, see you next time when we will create a UDI task sequence and deploy it ! and see what happens on the client side.
Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#2 nry

nry

    Advanced Member

  • Members
  • PipPipPip
  • 70 posts

Posted 23 May 2012 - 08:44 AM

I want to ensure that our Windows 7 computers are deployed as UK English, not the US English default that appears to be the only English option on Win 7 Pro.

We will shortly be licenced for Windows 7 Enterprise which so far as I can tell, includes multiple language packs (unlike Pro which has one?).

If I run through these guides using Win 7 Enterprise, will this give me the option to ensure that UK English can be set as the OS language, and save me having to manually change this once the OS has been installed?

#3 Yuma

Yuma

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 29 May 2012 - 12:33 PM

Where do you change the keyboard settings?
I live in Belgium so for me the language is nl-BE and the keyboard is Belgian Period, (azerty).

Also is there a guide for ZTI (zero touch install) for SCCM 2012 and MDT?

edit: I think I found it by browsing the web and this site. So I created an unattend.xml where I set the keyboard settings to nl-BE. Than I edited the MDT task sequence, in the Install folder there is Apply Operating System Image here is you can select Use an unattended or sysprep answer file for a custom installation, the package you select is Microsoft MDT settings or how you called it.

Than I edited the unattended.xml file by browsing to it via windows explorer, and changed the input settings from en-US to nl-BE.

I tested it the keyboard was nl-BE after the install.

Now I am looking for a way to set a default pcname for a new install, but I think I saw this somewhere in this tutorial so I am gonna check that again.

Also the Format and Partition Disk 6.1,6.0,5.x. have me a little puzzled, am I correct to think they are hidden partitions for the endprotection files for the clients?

#4 Joohan

Joohan

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 12 June 2012 - 10:59 PM

"any applications deployed to the All Systems collection and with the Allow this application to be installed from the Install Application task sequence action instead of deploying it manually setting set in the applications properties will appear in the list." - deploying to All Systems means the applications will show up in the Software Center on each and every computer, right? Instead I created a new collection, named it "MDT Applications", set it as Application Catalogue, and deployed my "cool apps" to that - this seems to work fine, but I'm curious whether it is a recommended solution??

#5 Iroqouiz

Iroqouiz

    Advanced Member

  • Members
  • PipPipPip
  • 323 posts
  • Gender:Male

Posted 25 June 2012 - 10:35 AM

"any applications deployed to the All Systems collection and with the Allow this application to be installed from the Install Application task sequence action instead of deploying it manually setting set in the applications properties will appear in the list." - deploying to All Systems means the applications will show up in the Software Center on each and every computer, right? Instead I created a new collection, named it "MDT Applications", set it as Application Catalogue, and deployed my "cool apps" to that - this seems to work fine, but I'm curious whether it is a recommended solution??


When you deploy the app to the All Systems collection, just choose not to display it in the Software Center.

#6 Special Ed

Special Ed

    Member

  • Members
  • PipPip
  • 24 posts
  • Gender:Male
  • Location:Denver, CO

Posted 16 October 2012 - 09:25 PM

Do you have any guidance on how to customize the UDI options? For example, within the default UDI the state store options do not allow selecting the state migration point as an option. How could you modify the UDI so that it will use an SMP?

#7 aengel80

aengel80

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 18 October 2012 - 02:05 AM

Hey Guys!

Quick Q. I'm a tad confused when it comes to Part 8: Deploy Windows 7 x64 and this current section, Part 17: Using MDT 2012 RC1 within Configuration Manager 2012.

My question is, are both methods of deploying Windows just a preference of the user? Say, I like to deploy Windows 7 using the methods in Part 8 over Part 17 and vice versa. Or, was Part 8 simply the prerequisite to using the preferred way of deploying Windows 7 which is using MDT in Part 17?

Thanks in advance and sorry for my confusion!

-OH, awesome guides!


#8 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 5,654 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 18 October 2012 - 04:53 AM

yes you could say that they are a preference of the user, as MDT is optional and provides additional functionality,
you could also note that these guides (part 17) are based on the Release Candidate version of Configuration Manager whereas the other guides are based on the RTM version (current)

I will update the RTM guides with MDT relevant content when time permits
Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#9 manuverma

manuverma

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 31 January 2014 - 06:53 PM

Hi,

 

How can we make 3 partition using mdt task sequence in sccm 2012.

Please help me on this issue.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Locations of visitors to this page