The Deployment Guys

Helping to deploy your world automagically...

MDT 2008 and BDD 2007 Update 2 Released

MDT 2008 and BDD 2007 Update 2 Released

  • Comments 15
  • Likes

So - The latest update to Microsoft Deployment Toolkit and BDD 2007 make them both Windows Vista SP1 and Windows Server 2008-Ready!

Microsoft Deployment Toolkit 2008-Unified Tools and Guidance for Desktop and Server Deployment Automation. Download here!

We announced on Friday the release of Microsoft Deployment Toolkit (MDT) 2008. This is an update to Microsoft Deployment, released in November 2007.

MDT 2008 extends existing functionality to deploy Windows Vista SP1 and Windows Server 2008 for both Lite Touch and Zero Touch deployments using Systems Management Server 2003* and Microsoft System Center Configuration Manager 2007. This release of MDT supports Windows AIK 1.1 and configuration of Active Directory® directory service, DNS, and DHCP server roles. To learn more and download the latest content, go to http://www.microsoft.com/deployment.

* ZTI with SMS 2003 does not support deployment of server operating systems

Business Desktop Deployment 2007 Update 2-Automate Deployment of Windows Vista SP1. Download here!

This update to Business Desktop Deployment (BDD) 2007 adds support to deploy Windows Vista SP1 for both Lite Touch Installation and Zero Touch Installation using Systems Management Server 2003. This release requires Windows AIK 1.1. To learn more and download the latest content, go to Microsoft Download Center.

This post was contributed by Richard Smith a Senior Consultant with Microsoft Services, UK.

  • Can I install MDT 2008 on top of my existing MDT 1.0?  What happens to my deployment workbench and everything I have built out?

    Rich

  • Yes - you can install MDT 2008 over the original release of MDT - the deployment workbench will be upgraded and the next time you enter the deployment workbench and access the Distribution Point - MDT 2008 will prompt you to update the Distribution Point with new scripts and files (you are given the opportunity to backup the original files first).

    Michael Niehaus has done a number of MDT 2008 upgrade releated posts on his personal blog at http://blogs.technet.com/mniehaus/ that are excellent especially if you are upgrading ZTI based installations that use SMS or SCCM2007

  • Hi

    I updated to MDT 2008 and tried to build a new deployment point. The difference is that comparing to the previous version, this doesn't work. The server name(in this case my pc named HARDKORN) is not recognized. I get a red exclamation mark "Server is invalid or unreachable". This didn't come up with the previous version. None of the deployment point types work.

    Can you help me out here?

    Greets

  • Anyone aware of any current (or) future books being published by MSFT or other vendors that will document MDT in more detail?  

  • Hi Ben

    I am asking for your expertise again.

    I am running the latest MDD2008  and nothing works as it should be. The deployment point(Media) update process hangs and I get: "An unexpected error occurred while updating the deployment point.  IMAGEX capture failed, rc=2 See c:\Documets and Settings\username\Locals~1\Temp\DeployUpdates_x86.log for more information.

    I checked the log file, googled a little bit and stumbled upon a forum where someone said to disable "8.3 Name Creation". No go.

    I'm running MDT 2008 under Windows XP SP3 build 5508. I'm thinking this might be the cause as "Forefront Client Security Filter Manager QFE for Windows XP/SP2(KB914882) can't be installed under XP+SP3.

    Is this the case? Do I have to get back to SP2?

  • Hi Atolica,

    I am not sure if that is the issue. what does the log say? - c:\Documets and Settings\username\Locals~1\Temp\DeployUpdates_x86.log

    Thanks,

    Ben

  • Hi Atolica,

    Your name resolution issue is most likely caused by a name resolution issue.

    The wizard is trying to execute this WMI query:

    Select * from Win32_PingStatus Where Address = 'HARDKORN'

    It could be that WMI isn’t working, or that there is some local name resolution issue.

    Thanks,

    Ben

  • Image Capture fails on german Windows Vista. Seems there is a localization bug in the ZTIBCDUtility.vbs. It checks for the pattern "sucessfully" using regexp to make sure bcdedit has run without errors. Unfortunatly bcdedit says "erfolgreich" when running on a german installation. Is there a supported fix?

  • Can anyone help me with this error?

    "An unexpected error occurred while updating the deployment point.

    PEIMG failed, rc=1603. See <locaction> for more information."

    So I checked the log file and this is what i found:

    ----Beginning of Log------

    Checking share Distribution3 on \\ACTISERVER

    Share \\ACTISERVER\Distribution3 created.

    Starting: copy "C:\Program Files\Windows AIK\Tools\PETools\x86\bootmgr" "J:\Distribution\\Boot\x86\bootmgr" /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

           1 file(s) copied.

    Exit code = 0

    Starting: mkdir "J:\Distribution\\Boot\x86\Boot" >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    A subdirectory or file J:\Distribution\\Boot\x86\Boot already exists.

    Exit code = 1

    Starting: xcopy "C:\Program Files\Windows AIK\Tools\PETools\x86\Boot" "J:\Distribution\\Boot\x86\Boot" /s /e /i /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\bcd

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\boot.sdi

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\bootfix.bin

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\etfsboot.com

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\chs_boot.ttf

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\cht_boot.ttf

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\jpn_boot.ttf

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\kor_boot.ttf

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\wgl4_boot.ttf

    9 File(s) copied

    Exit code = 0

    Starting: xcopy "C:\Program Files\Microsoft Deployment Toolkit\Bin\x86\msxml6*.*" "J:\Distribution\\Servicing\x86" /y /d >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    0 File(s) copied

    Exit code = 0

    Starting: copy "C:\Program Files\Windows AIK\Tools\PETools\x86\bootmgr" "\\ACTISERVER\Distribution3\Boot\x86\bootmgr" /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

           1 file(s) copied.

    Exit code = 0

    Starting: mkdir "\\ACTISERVER\Distribution3\Boot\x86\Boot" >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    A subdirectory or file \\ACTISERVER\Distribution3\Boot\x86\Boot already exists.

    Exit code = 1

    Starting: xcopy "C:\Program Files\Windows AIK\Tools\PETools\x86\Boot" "\\ACTISERVER\Distribution3\Boot\x86\Boot" /s /e /i /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\bcd

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\boot.sdi

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\bootfix.bin

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\etfsboot.com

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\chs_boot.ttf

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\cht_boot.ttf

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\jpn_boot.ttf

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\kor_boot.ttf

    C:\Program Files\Windows AIK\Tools\PETools\x86\Boot\fonts\wgl4_boot.ttf

    9 File(s) copied

    Exit code = 0

    Starting: xcopy "C:\Program Files\Microsoft Deployment Toolkit\Bin\x86\msxml6*.*" "\\ACTISERVER\Distribution3\Servicing\x86" /y /d >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    C:\Program Files\Microsoft Deployment Toolkit\Bin\x86\msxml6.dll

    C:\Program Files\Microsoft Deployment Toolkit\Bin\x86\msxml6r.dll

    C:\Program Files\Microsoft Deployment Toolkit\Bin\x86\msxml6r.dll.mui

    3 File(s) copied

    Exit code = 0

    Starting: xcopy "J:\Distribution\Scripts" "\\ACTISERVER\Distribution3\Scripts" /s /e /i /d /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    J:\Distribution\Scripts\Autorun.inf

    J:\Distribution\Scripts\BackButton.JPG

    J:\Distribution\Scripts\BackButton.PNG

    J:\Distribution\Scripts\BDD.reg

    J:\Distribution\Scripts\BDD_Autorun.wsf

    J:\Distribution\Scripts\BDD_Welcome_ENU.xml

    J:\Distribution\Scripts\Credentials_ENU.xml

    J:\Distribution\Scripts\Credentials_scripts.vbs

    J:\Distribution\Scripts\DeployWiz_Definition_ENU.xml

    J:\Distribution\Scripts\DeployWiz_Initialization.vbs

    J:\Distribution\Scripts\DeployWiz_Validation.vbs

    J:\Distribution\Scripts\ListOfLanguages.xml

    J:\Distribution\Scripts\LiteTouch.vbs

    J:\Distribution\Scripts\LiteTouch.wsf

    J:\Distribution\Scripts\LTIApply.wsf

    J:\Distribution\Scripts\LTICleanup.wsf

    J:\Distribution\Scripts\LTICopyScripts.wsf

    J:\Distribution\Scripts\LTIGetFolder.wsf

    J:\Distribution\Scripts\LTISysprep.wsf

    J:\Distribution\Scripts\minusico.gif

    J:\Distribution\Scripts\NICSettings_Definition_ENU.xml

    J:\Distribution\Scripts\plusicon.gif

    J:\Distribution\Scripts\SelectItem.jpg

    J:\Distribution\Scripts\Summary_Definition_ENU.xml

    J:\Distribution\Scripts\Summary_scripts.vbs

    J:\Distribution\Scripts\Whiteness.jpg

    J:\Distribution\Scripts\Wizard.css

    J:\Distribution\Scripts\Wizard.hta

    J:\Distribution\Scripts\Wizard.ico

    J:\Distribution\Scripts\WizUtility.vbs

    J:\Distribution\Scripts\ZeroTouchInstallation.vbs

    J:\Distribution\Scripts\ZeroTouchInstallation.wsf

    J:\Distribution\Scripts\ZTIApplications.wsf

    J:\Distribution\Scripts\ZTIAppXmlGen.wsf

    J:\Distribution\Scripts\ZTIAuthorizeDHCP.wsf

    J:\Distribution\Scripts\ZTIBackup.wsf

    J:\Distribution\Scripts\ZTIBCDUtility.vbs

    J:\Distribution\Scripts\ZTIBde.wsf

    J:\Distribution\Scripts\ZTIBIOSCheck.wsf

    J:\Distribution\Scripts\ZTIBIOSCheck.xml

    J:\Distribution\Scripts\ZTICoalesce.wsf

    J:\Distribution\Scripts\ZTIConfigure.wsf

    J:\Distribution\Scripts\ZTIConfigure.xml

    J:\Distribution\Scripts\ZTIConfigureADDS.wsf

    J:\Distribution\Scripts\ZTIConfigureDHCP.wsf

    J:\Distribution\Scripts\ZTIConfigureDNS.wsf

    J:\Distribution\Scripts\ZTIConfigureIIS.wsf

    J:\Distribution\Scripts\ZTIConfigureTS.wsf

    J:\Distribution\Scripts\ZTIConfigureWDS.wsf

    J:\Distribution\Scripts\ZTIConfigureWINS.wsf

    J:\Distribution\Scripts\ZTIConnect.wsf

    J:\Distribution\Scripts\ZTICopyLogs.wsf

    J:\Distribution\Scripts\ZTIDeterminePartition.wsf

    J:\Distribution\Scripts\ZTIDiskpart.cmd

    J:\Distribution\Scripts\ZTIDiskpart.txt

    J:\Distribution\Scripts\ZTIDiskpart.wsf

    J:\Distribution\Scripts\ZTIDiskUtility.vbs

    J:\Distribution\Scripts\ZTIDrivers.wsf

    J:\Distribution\Scripts\ZTIGather.wsf

    J:\Distribution\Scripts\ZTIGather.xml

    J:\Distribution\Scripts\ZTIGroups.wsf

    J:\Distribution\Scripts\ZTIInstallWSV.wsf

    J:\Distribution\Scripts\ZTILangPacksOnline.wsf

    J:\Distribution\Scripts\ZTIMoveStateStore.wsf

    J:\Distribution\Scripts\ZTINextPhase.wsf

    J:\Distribution\Scripts\ZTINICConfig.wsf

    J:\Distribution\Scripts\ZTINicUtility.vbs

    J:\Distribution\Scripts\ZTIOSRole.wsf

    J:\Distribution\Scripts\ZTIPackages.wsf

    J:\Distribution\Scripts\ZTIPatches.wsf

    J:\Distribution\Scripts\ZTIPrereq.vbs

    J:\Distribution\Scripts\ZTISCCM.wsf

    J:\Distribution\Scripts\ZTISetVariable.wsf

    J:\Distribution\Scripts\ZTIStorageDrivers.wsf

    J:\Distribution\Scripts\ZTIStorageDriversSysprep.wsf

    J:\Distribution\Scripts\ZTISupportedPlatforms.xml

    J:\Distribution\Scripts\ZTITatoo.mof

    J:\Distribution\Scripts\ZTITatoo.wsf

    J:\Distribution\Scripts\ZTIUserState.wsf

    J:\Distribution\Scripts\ZTIUtility.vbs

    J:\Distribution\Scripts\ZTIValidate.wsf

    J:\Distribution\Scripts\ZTIWindowsUpdate.wsf

    J:\Distribution\Scripts\ZTIWipeDisk.wsf

    83 File(s) copied

    Exit code = 0

    Starting: xcopy "J:\Distribution\Tools" "\\ACTISERVER\Distribution3\Tools" /s /e /i /d /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    J:\Distribution\Tools\x64\BDDRun.exe

    J:\Distribution\Tools\x64\CcmCore.dll

    J:\Distribution\Tools\x64\CcmUtilLib.dll

    J:\Distribution\Tools\x64\EXTRACT.EXE

    J:\Distribution\Tools\x64\Microsoft.BDD.PnpEnum.exe

    J:\Distribution\Tools\x64\Microsoft.BDD.Utility.dll

    J:\Distribution\Tools\x64\Smsboot.exe

    J:\Distribution\Tools\x64\SmsCore.dll

    J:\Distribution\Tools\x64\TsCore.dll

    J:\Distribution\Tools\x64\TSEnv.exe

    J:\Distribution\Tools\x64\TsManager.exe

    J:\Distribution\Tools\x64\TsmBootstrap.exe

    J:\Distribution\Tools\x64\TsMessaging.dll

    J:\Distribution\Tools\x64\TsProgressUI.exe

    J:\Distribution\Tools\x64\TsResNlc.dll

    J:\Distribution\Tools\x64\xprslib.dll

    J:\Distribution\Tools\x64\00000409\tsres.dll

    J:\Distribution\Tools\x86\BDDRun.exe

    J:\Distribution\Tools\x86\CcmCore.dll

    J:\Distribution\Tools\x86\CcmUtilLib.dll

    J:\Distribution\Tools\x86\EXTRACT.EXE

    J:\Distribution\Tools\x86\InstallUSMT301_x86.msi

    J:\Distribution\Tools\x86\Microsoft.BDD.PnpEnum.exe

    J:\Distribution\Tools\x86\Microsoft.BDD.Utility.dll

    J:\Distribution\Tools\x86\Smsboot.exe

    J:\Distribution\Tools\x86\SmsCore.dll

    J:\Distribution\Tools\x86\TsCore.dll

    J:\Distribution\Tools\x86\TSEnv.exe

    J:\Distribution\Tools\x86\TsManager.exe

    J:\Distribution\Tools\x86\TsmBootstrap.exe

    J:\Distribution\Tools\x86\TsMessaging.dll

    J:\Distribution\Tools\x86\TsProgressUI.exe

    J:\Distribution\Tools\x86\TsResNlc.dll

    J:\Distribution\Tools\x86\xprslib.dll

    J:\Distribution\Tools\x86\00000409\tsres.dll

    35 File(s) copied

    Exit code = 0

    Starting: xcopy "J:\Distribution\Boot\*.WIM" "\\ACTISERVER\Distribution3\Boot" /d /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    File not found - *.WIM

    0 File(s) copied

    Exit code = 0

    Starting: xcopy "J:\Distribution\Boot\x86" "\\ACTISERVER\Distribution3\Boot\x86" /s /e /i /d /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    0 File(s) copied

    Exit code = 0

    Starting: xcopy "J:\Distribution\Control" "\\ACTISERVER\Distribution3\Control" /s /e /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    J:\Distribution\Control\Applications.xml

    J:\Distribution\Control\Bootstrap.ini

    J:\Distribution\Control\CustomSettings.ini

    J:\Distribution\Control\Databases.xml

    J:\Distribution\Control\Deploy.xml

    J:\Distribution\Control\DriverGroups.xml

    J:\Distribution\Control\Drivers.xml

    J:\Distribution\Control\OperatingSystems.xml

    J:\Distribution\Control\PackageGroups.xml

    J:\Distribution\Control\Packages.xml

    J:\Distribution\Control\TaskSequences.xml

    J:\Distribution\Control\TS.XML

    J:\Distribution\Control\Version.xml

    J:\Distribution\Control\DELL_XP_SP2\OldTS.XML

    J:\Distribution\Control\DELL_XP_SP2\Sysprep.inf

    J:\Distribution\Control\DELL_XP_SP2\TS.xml

    J:\Distribution\Control\DELL_XP_SP2\Unattend.txt

    J:\Distribution\Control\FULLXP\OldTS.XML

    J:\Distribution\Control\FULLXP\Sysprep.inf

    J:\Distribution\Control\FULLXP\TS.xml

    J:\Distribution\Control\FULLXP\Unattend.txt

    J:\Distribution\Control\SERVER2003\Sysprep.inf

    J:\Distribution\Control\SERVER2003\TS.xml

    J:\Distribution\Control\SERVER2003\Unattend.txt

    J:\Distribution\Control\{1467d7b3-f103-4466-9b39-ccdadc3404e1}\Bootstrap.ini

    J:\Distribution\Control\{1467d7b3-f103-4466-9b39-ccdadc3404e1}\CustomSettings.ini

    J:\Distribution\Control\{30b955de-f35a-4cd5-a48a-687be54d1319}\Bootstrap.ini

    J:\Distribution\Control\{30b955de-f35a-4cd5-a48a-687be54d1319}\CustomSettings.ini

    28 File(s) copied

    Exit code = 0

    Starting: xcopy "J:\Distribution\$OEM$" "\\ACTISERVER\Distribution3\$OEM$" /s /e /i /d /y >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    0 File(s) copied

    Exit code = 0

    Copying C:\Program Files\Windows AIK\Tools\PETools\x86\WINPE.WIM to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\winpe.wimMounting image to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\PE20_mount.x86Installing optional components.

    Starting: "C:\Program Files\Windows AIK\Tools\PETools\peimg.exe" "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\PE20_mount.x86\windows" /install=*Scripting* /quiet >> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log" 2>&1

    Preinstallation Environment Image Setup Tool for Windows

    Copyright (C) Microsoft Corporation. All rights reserved.

    Lang  | Version       | Ins | Name

    ------+---------------+-----+-----------------------------------------------

    en-US |6.0.6001.18000 |  +  | WinPE-Scripting-Package

    ------+---------------+-----+-----------------------------------------------

         |6.0.6001.18000 |  +  | WinPE-Scripting-Package

    The installation of the previous package failed with status 0x80070643.

    Full package name: [WinPE-Scripting-Package~31bf3856ad364e35~x86~~6.0.6001.18000]

    Installed 1 package(s).

    PEIMG failed to complete the operation with status code 0x80070643.

    Exit code = 1603

    Exception occurred generating Windows PE image:

    System.Exception: PEIMG failed, rc = 1603.  See C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\DeployUpdates_x86.log for more information.

      at Microsoft.BDD.ConfigManager.PEManager.Generate()

    ----End of Log------

    Any help will be greatly appreciated! Thank you in adavance!

  • Hi Richard,

    The error you are getting is probably due to the WIM still being mounted.  If you unmount the boot.wim are you still getting the original error message?

    Thanks,

    Ben

  • How do you guys position MDT vs BDD?  I'm working on an MCITP exam study guide and the 70-624 content focuses on the older BDD and SMS 2003 OSD bits.  I'm looking for the official word to include in the text.

  • Hi Colin,

    BDD is dead - there will be no further developement work carried out on it. MDT is the futuer and customers should be encouraged to use it. If they do not have BDD or MDT they should only go MDT. If they have BDD you should encourage them to go to MDT. MDT will work with SCCM and will have further dev work to offer more features and funcitonality.

    Obviously this is not the 'offical word' for that you need the deployent team blog link on the left hand side.

  • hi i am trying to install a program from verizon.net which is called starz play package but it wont download bcuz of this error 1603.net framework what do i need to do thanks ernie

  • Hi. I can't seem to find any info on ZTIStorageDriversSysprep.wsf being fixed in this update, but it seems you have added the "or Type = 'hdc'" without mentioning it in the script's revision history nor the release notes for Update 1.

    Does this mean that I can start using the StorageDriverSysPrepGroup property when building my image instead of having to put the drivers in $OEM$ and editing sysprep.inf manually? I'm using LTI to build and deploy Windows XP SP3.

  • Sorry, I posted that in the wrong place. My comments are refering to MDT 2008 Update 1.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment