Microsoft Deployment Toolkit Team BlogOfficial blog for MDT 2010
We have received a number of emails and questions on how to receive support from Premier Support for Microsoft Deployment. There have been several of you who have been routed to the incorrect support person while trying to receive support for Microsoft Deployment. We apologize for your frustration and inconvenience.
To get routed to the correct support person, follow these instructions. Please note that support for Microsoft Deployment is done on via callback with response times generally ranging between 1 and 4 hours depending on the severity of your issue and the other issues in the queue.
To receive support:
a) Call the support number (1-800-936-3500) http://www.microsoft.com/services/microsoftservices/srv_premier.mspx) or
b) Submit a web incident http://support.microsoft.com/select/default.aspx?target=assistance&c1=508&
c) Clearly state that you have a BDD/MDT issue. (If you talk about deployment they will be routed to a different queue. ).
Thank you and please let us know if you have any problems receiving support in the future.
Some of your favorite deployment guys including Ben Hunter, Richard Smith, Adam Shepherd, Daniel Oxley and more have teamed up to create a blog called Deployment Guys. They are just getting started but already have some good information on their blog. Make sure you subscribe to:
http://blogs.technet.com/deploymentguys
Microsoft Deployment has been released for a little over three months and we now have had enough questions and support calls come in to generate a FAQ. You might want to bookmark this post because we plan on updating this list as additional questions are asked.
Q: Is it possible to change the text IT Organization in the task sequence dialog box?
A: Yes! You can set the variable _SMSTSORGNAME in the custom settings.ini to match the text you want to use. For example to set the text to Microsoft Corporation, add the following line to your customsettings.ini:
_SMSTSORGNAME = Microsoft Corporation
Q: What is the purpose of each of the task sequence templates?
A: In BDD 2007 we supported only the installation of a client Operating System and did not technically support using task sequences for anything other than deploying an Operating System. With Microsoft Deployment we now support deploying server Operating Systems as well as running customized task sequences that can perform any number of operations. Here is a list of the templates we provide and their purpose:
Q: For the Client Replace task sequence, how do I make the task sequence wipe the disk?
A: Set the variable WipeDisk = TRUE in the customsettings.ini
Q: In BDD 2007 I modified ztidiskpart.txt to create partitions. How do I do this in Microsoft Deployment?
A: Microsoft deployment does not use the ztidiskpart.txt file to create the partitions. Now, this disks are configured run time based on the task sequence parameters in the Format and Partition Disk step. This step allows you to create multiple partitions across several disks. If you do not want a partition formatted you can create your own custom script that calls diskpart /s and provide your own diskpart.xt file
Q: When trying to add a custom Vista WIM to the workbench, I receive the following error: Error during wizard processing An unexpected error occurred while processing the wizard results. Collection was modified; enumeration operation may not execute.
A: There is a hotfix available that will fix this problem. See the following KB article for more information and to retrieve the hotfix:
http://support.microsoft.com/kb/941595
Q: How do I use the media hook capabilities in Microsoft Deployment to deploy to unknown computers?
A: Michael Niehaus has a great blog entry and screencast on how to set up and configure this feature: http://blogs.technet.com/mniehaus/archive/2008/01/19/microsoft-deployment-configmgr-boot-media-unknown-computers-web-services.aspx
Q: How do I configure my task sequence to capture a reference image?
A: In the standard client task sequence there are a series of steps at the end of the task sequence that prepare the system for imaging, reboot to Windows PE, and then captures an image of the computer. To enable these steps the following variable should be set in the customsettings.ini, Microsoft Deployment Database, ConfigMgr variables, or task sequence variables:
DoCapture = YES
Q: Do I need to use the Microsoft Deployment database with ConfigMgr 2007?
A: It depends. We have made Microsoft Deployment flexible enough for you to use the Microsoft Deployment Database, customsettings.ini, ConfigMgr 2007 Task Sequence variables, Web Services, or Collection or Computer variables. If you already have a populated database from using BDD 2007, you have the ability to use that database in conjunction with Microsoft Deployment and ConfigMgr by customizing the customsettings.ini to make the database connection. If you choose to use the Microsoft Deployment database (or any other database) then you will need to use the Import Microsoft Deployment Task sequence to create a custom Windows PE image that includes ADO support
Q: What is install updates offline and how do I use it?
A: Install Updates offline is a step that can be added to the task sequence that will install Vista and Windows Server 2008 patches to the Operating System prior to the Operating System booting for the first time. To use this step in the task sequence, you first need to create an updates package inside of ConfigMgr: http://technet.microsoft.com/en-us/library/bb680701.aspx. After creating your updates package you need to add the Install Updates Offline step in the task sequence in the PostInstall section immediately prior to the Configure step
A: Yes! Due to how the task sequencing engine works with SMS 2003 OSD, the process is slightly different than for Lite Touch.
Create a variables.dat file in your package source and distribute it to your SMS 2003 Distribution Points. The contents of that variables.dat file should be the following:
<?xml version="1.0"?>
<MediaVarList Version="4.00.5345.0000"><var name=”_SMSTSORGNAME”>My CorpName</var></MediaVarList>