Johan Arwidmark, Setup & Deployment MVP, just finished working on his Version 2.0 Deployment CD. It contains the following step-by-step guides and video tutorials:
MDT 2010 Lite Touch Deployments (deployment without ConfigMgr 2007 SP2 R2, just the free tools)
- LTI01 – Installing the server for MDT 2010 Lite Touch
- LTI02 – Creating a Windows 7 reference image using Lite Touch
- LTI03 – Deploying a Windows 7 image using Lite Touch
- LTI04 – Dynamic Settings, creating and using the deployment database
MDT 2010 Zero Touch Deployments (deployment with ConfigMgr 2007 SP2 R2)
- ZTI01 – Installing the server for MDT 2010 Zero Touch and ConfigMgr 2007 SP2
- ZTI02 – Creating a Windows 7 reference image using ConfigMgr 2007 SP2
- ZTI03 – Deploying a Windows 7 image using ConfigMgr 2007 SP2
- ZTI04 – Dynamic Settings, creating and using the deployment database
- E01 – New features in MDT 2010
- E02 – Upgrading MDT 2008 to MDT 2010
- E03 – Migrating Windows XP to Windows 7
And guess what? He’s offering the CD for free to everybody who needs and wants it. You can register for a free download at www.deploymentcd.com.
A few days ago I had to make an image with Windows XP SP3 with all needed applications for lite touch installation.
Everything went well and I was happy until I entered the mini-setup phase on the first computer with that image applied on it. I received an error regarding the product key. I guess I tried a dozen of product keys but none of them worked. After reading the message again and more careful, I realized that the problem was with my Windows XP media – it was not a VL media. And I realized this because the message said to look for a product key on the Certificate of Authenticity (COA) sticker and not my License Agreement…
Got another media with Windows XP SP3 VL and made a repair. During the repair phase, I provided the VL product key and it worked. Next time I entered the mini-setup, I filled in required info and that was it.
Here is another error related to Task Sequence and MDT 2008. After creating and advertising a task sequence, most probably you will run it :). Make sure you have the latest version of your packages on the distribution point, otherwise you will receive an error while running the task sequence. This will be something like “Task Sequence: your task sequence name has failed with the error code (0x80091007). For more information, please contact you system administrator or helpdesk operator.”
In the log file you will find this: “The hash value is not correct.”
What you can do to resolve this? Two things:
- to update your distribution point with the latest version of the packages. To be sure the package was updated successfully, you can put a txt file somewhere and verify if it is on the DP.
- modify the advertisement to not download the files locally but access the files directly from the DP, although I’d not recommend it.