Partilhar via

Upgrading to Microsoft Deployment Toolkit (MDT) 2008 - Zero Touch with ConfigMgr 2007

  • Artigo

If you are running the original version of Microsoft Deployment with System Center Configuration Manager 2007 and are looking to upgrade to MDT 2008, here are the basic steps that you need to follow:

  1. Make sure you have a backup of your environment.  While I don't expect anything to go wrong, it's always a good practice to have a backup :-)
  2. Install the new MSI.  This will automatically upgrade the existing installation files, e.g. C:\Program Files\Microsoft Deployment Toolkit.
  3. Make sure the ConfigMgr console isn't running, then run the "Configure ConfigMgr Integration" wizard.  This will copy the new DLLs into the ConfigMgr console installation directory (e.g. C:\Program Files\Microsoft Configuration Manager Console\AdminUI\bin) and will update the WMI classes needed for the MDT custom task sequence actions (done by compiling a new MOF).

Now at this point, all existing task sequences continue to work and are unchanged.  For any new task sequences that you create, you should create a new MDT tools package to use with those new task sequences.  (If you want, you can update existing task sequences to use the new MDT tools package too, but you'll have to create a new task sequence before you can do that since there's no way to just create a new MDT tools package.)

MDT 2008 does not require Windows AIK 1.1 if you are using only Windows Vista RTM or Windows XP; Windows AIK 1.0 is fine for these.  But if you are using Windows Vista SP1, you need to upgrade to Windows AIK 1.1.  (If you don't, as soon as you add a Windows Vista SP1 image, you'll start seeing warning dialogs.  They won't go away until you do upgrade.)  The steps needed to upgrade to Windows AIK 1.1 are:

  1. Uninstall Windows AIK 1.0.
  2. Reboot.
  3. Install Windows AIK 1.1.

When Windows AIK 1.1 is installed on the computer that you are using to run the ConfigMgr console, then the MDT "Import Microsoft Deployment task sequence" wizard will create Windows PE 2.1 boot images (instead of the Windows PE 2.0 boot images created from Windows AIK 1.0).

The ConfigMgr team is working on instructions for installing Windows AIK 1.1 for use with ConfigMgr 2007.  The basic steps above shouldn't cause any issues (uninstall, reboot, install), but there are some additional steps needed to replace the existing default boot images that ConfigMgr 2007 created when it was first installed.  (To move to ConfigMgr 2007 SP1, Windows AIK 1.1, or more specifically Windows PE 2.1,will be required.)

Comments

  • Anonymous
    January 01, 2003
    PingBack from http://4sysops.com/archives/microsoft-deployment-toolkit-mdt-2008-why-so-many-tools-why-not-just-one/

  • Anonymous
    January 01, 2003
    The Microsoft Deployment Toolkit (MDT) 2008 was recently released. It is the update to BDD 2007 and adds

  • Anonymous
    January 01, 2003
    There are a couple of ways to install Windows Server 2008. When you're lucky enough to get your hands

  • Anonymous
    January 01, 2003
    I met you lastnight in CWUG and talked to you about imaging a PC using sysprep. First of all, I would like to say thank you for tips/help you have given me. I truly appreciate it. I still have a questions/concerns on capturing an image when PC has been customized. For example, I have deployed a PC with Windows XP and I have customized to how I want it. Now, how would I get the same customized to image using MDT 2008. I have tried sysprepping it but it did not save all settings. Since this is Windows XP, and it’s not GUI based like Vista where you can manipulate the unattended.xml files. Is there a way I can modify the unattended file in Windows XP? If capturing the image by sysprep, what steps should be done? Please let me know if you can guide/walk me through. Once again thank you. Sincerely, Leo Gorospe

  • Anonymous
    January 01, 2003
    The comment has been removed