Microsoft Deployment Toolkit Team BlogOfficial blog for MDT 2010
We've received a number of questions over the past few days on the best way to upgrade from MDT 2008 to MDT 2008 Update 1 without losing any settings. The most common problem that has been seen is that the Deployment Points are no longer present after installing MDT 2008 Update 1. The following instructions will allow you to upgrade and maintain all of your existing settings:
1. Before installing MDT 2008 Update make a backup of the Deploy.XML file. The file is located by default in C:\Program Files\Microsoft Deployment Toolkit\Control
2. Install the MDT 2008 Update 1 MSI
3. Launch the Deployment Workbench and right click on Distribution Share and choose Create distribution share directory
4. A wizard will then be presented. Choose Upgrade an existing distribution share and type or browse to the path of your existing distribution share. Check the check box to Backup existing scripts and configuration files and click on Finish (the files will be backed up to the Distribution\Backup folder)
5. Close the Deployment Workbench and restore the Deploy.xml that was backed up earler to C:\Program Files\Microsoft Deployment Toolkit\Control, overwriting the existing file
6. Launch the Deployment Workbench, navigate to the Deployment Points and your Deployment Points should now be visible.
7. Right click on each Deployment Point and choose Update. This will update all of the Windows PE images with the correct version of the scripts
8. If you are using WDS, you will now need to replace your boot image in WDS with the updated Lite Touch WIM file
Some folks are experiencing issues with upgrading MDT 2008 to Update 1, so the folks at Microsoft have
What’s New in MDT 2008 Update 1? MDT 2008 Update 1 includes new capability for OEM preload scenarios,
I have noted an issue after applying update 1 where if I try to update two deployment points in sucession without closing the workbench in between, I receive the following error: "An unexpected error occured while updating the deployment point. The process cannot access the file 'C:\Distribution\\Tools\x86\wimgapi.dll' because it is being used by another process."
Clicking on "Show the error details" produces the following:
Assembly: mscorlib Assembly Version: 2.0.0.0 File Version: 2.0.50727.42 (RTM.050727-4200)
Assembly: Microsoft.ManagementConsole Assembly Version: 3.0.0.0 File Version: 5.2.3790.2612
Assembly: MMCFxCommon Assembly Version: 3.0.0.0 File Version: 5.2.3790.2612
Assembly: System Assembly Version: 2.0.0.0 File Version: 2.0.50727.42 (RTM.050727-4200)
Assembly: System.Windows.Forms Assembly Version: 2.0.0.0 File Version: 2.0.50727.42 (RTM.050727-4200)
Assembly: System.Drawing Assembly Version: 2.0.0.0 File Version: 2.0.50727.42 (RTM.050727-4200)
Assembly: System.Configuration Assembly Version: 2.0.0.0 File Version: 2.0.50727.42 (RTM.050727-4200)
Assembly: System.Xml Assembly Version: 2.0.0.0 File Version: 2.0.50727.42 (RTM.050727-4200)
Assembly: Microsoft.BDD.Workbench Assembly Version: 3.0.0.0 File Version: 4.2.523.40
Assembly: Microsoft.BDD.ConfigManager Assembly Version: 3.0.0.0 File Version: 4.2.523.40
Assembly: System.Data Assembly Version: 2.0.0.0 File Version: 2.0.50727.42 (RTM.050727-4200)
Assembly: System.Management Assembly Version: 2.0.0.0 File Version: 2.0.50727.42 (RTM.050727-4200)
Assembly: Microsoft.ComponentStudio.ComponentPlatformInterface Assembly Version: 6.0.0.0 File Version: 6.0.6001.18000 (longhorn_rtm.080118-1840)
Assembly: Microsoft.ComponentStudio.Common Assembly Version: 6.0.0.0 File Version: 6.0.6001.18000 (longhorn_rtm.080118-1840)
System.IO.IOException: The process cannot access the file 'C:\Distribution\\Tools\x86\wimgapi.dll' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
at System.IO.File.Copy(String sourceFileName, String destFileName, Boolean overwrite)
at Microsoft.BDD.ConfigManager.DeployItem.GetTools(String platform, PEManager peManager, String deployPointDest)
at Microsoft.BDD.ConfigManager.DeployItem.Generate(String platform, String localLogFile, Boolean skipPE)
I noticed that after upgrading to MDT 2008 Update 1, I no longer have the job aids that were once available. I understand that everything is now supposed to be within the help .chm file but we seem to no longer have things like project process & team Guidance, templates, etc. that were once located within the BDD or MDT "wheel" in the Workbench Documentation node. Is this by design or will they be back? Are these gone for good now?
132 Microsoft Team blogs searched, 66 blogs have new articles in the past 6 days. 149 new articles found searching from 04-Aug-2008 to 09-Aug-2008
hmm.
http://www.microsoft.com/downloads/details.aspx?FamilyID=3bd8561f-77ac-4400-a0c1-fe871c461a89&DisplayLang=en
Microsoft Deployment Toolkit (MDT) 2008 Update 1
Version: 4.2
Date Published: 9/4/2008
what's new eh?
I guess, only print-ready docs are added (since the bins are all the same).
Infrastructure Development & Operations · Microsoft Exchange Server 2007 Protocol Documentation
I understand that everything is now supposed to be within the help .chm file but we seem to no longer have things like project process & team Guidance, templates, etc.
Thx..
Just one question: i can't find the
How to upgrade to MDT 2008 Update 2 in your blogging.
Can you show me the link?
Matt
This is very good news was well informed that the followers of the issue I am. Thank you ...
After upgrading to MDT 2008 Update 1, I do not have the support of the work once available. I understand that everything is now assumed that within the aid. Chm, but no longer seem to have things like project process and team guidance, templates, etc. that were previously located within the BDD or MDT "wheel" in the Workbench documentation node. Is this by design or go back? Are these gone for good now?