MDT doesn’t recognize your WIM file? Well, ImageX didn’t either.

I’ve talked to a few people that have mentioned that when they import a new operating system into the MDT 2010 Deployment Workbench, it never shows up – it’s in the deployment share, but it never shows up in Workbench.  So what happened? Well, if you are the geeky type, you can watch the import…

6

ConfigMgr Driver Management: A New Development

As part of the “ConfigMgr Driver Management: The Novel” blog postings (see http://blogs.technet.com/b/mniehaus/archive/2010/04/29/configmgr-2007-driver-management-the-novel-part-1.aspx for the first part) and in various presentations I mentioned that most of the challenges with driver management in ConfigMgr stemmed from the way drivers are imported into the ConfigMgr driver store:  duplicate drivers are ignored, so they don’t get put into…

4

MDT 2010 Update 1: Fix to make ConvertBooleanToString available again

In MDT 2008, we had various functions in the ZTIUtility.vbs script that could be used in CustomSettings.ini – not that we really intended for that to be the case, but because the “Gather” process can call any global VBScript function, so it just works. In MDT 2010, we rearranged the logic in ZTIUtility.vbs into different…

1

MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

Some people noticed that during an OS deployment task sequence, performed either by MDT 2008 Lite Touch or by ConfigMgr, could capture sensitive information (from unattend.xml, variables.dat, etc.) as part of the automatic System Restore snapshot process that happens whenever a new driver, application, security update, etc. is installed. To address that issue, we added…

11

MDT 2010 Update 1: Fixed Slow Driver Injection in Lite Touch

During Lite Touch deployments, the task sequence runs ZTIDrivers.wsf, which needs to figure out what drivers are needed for the computer, based on the PnP IDs found on the computer and the available drivers on the deployment share.  For every match, the driver files are copied to the computer. It’s possible (especially with chipset drivers)…

4

MDT 2010 Update 1: Added Support for ConfigMgr R3 Prestaged Media

In MDT 2010 (and earlier versions), we provided some task sequence templates to perform what we called an “OEM preload” scenario, where you could send a disk image to an OEM for them to preload on each new machine they manufactured for you.  But due to some limitations in ConfigMgr (and our requirement to not…

6

MDT 2010 Update 1: Fixes to ConfigMgr State Migration Point Scenarios

When using MDT task sequence templates for ConfigMgr, we expect to keep user state locally if you are refreshing existing machines.  But if you are replacing a computer, the user state needs to be stored on a ConfigMgr state migration point.  In that setup, you would run two different task sequences: SCCM_ClientReplace.xml.  This task sequence…

3

MDT 2010 Update 1: Fixes to ConfigMgr Task Sequence Template Error Handling

In MDT 2010, we restructured the ConfigMgr task sequence templates so that they had a common structure to them, with two main groups: Execute Task Sequence This group contained all the actual deployment tasks Gather Logs and StateStore on Failure If any of the steps in the main “Execute” step failed, this group would handle…

5

MDT 2010 Update 1: Task Sequences Changed

MDT 2010 also includes a variety of task sequence templates.  When you upgrade from MDT 2010 to MDT 2010 Update 1, your existing task sequences won’t be changed.  So, you have to decide if any of the changes that we’ve made are of value to you, and if they are, you’ll need to create new…

2

MDT 2010 Update 1: Scripts Changed

Since MDT 2010 Update 1 was released, I’ve been intending to write a series of blog postings talking about the changes that have been made.  While my intentions were good, I’ve been too busy to really act on them.  So I’m going to force myself to do this one posting, and hope that encourages me…

6