MDT 2010 Methods
I am trying to find out the best method for building a LiteTouch deployment for Windows 7 using MDT 2010. Does anyone have a step-by-step guide on this? Here are a few questions I’d like answered if anyone can help.
When you import an image into MDT 2010 we want to import a custom .WIM file. But should you run sysprep /generalize /oobe /shutdown /unattend:unattend.xml “before†you run your imagex /capture on your .WIM file?
Or do you import a Windows 7 image straight from the CD into MDT 2010 and then use the Edit Unattend.xml feature from within that tool?
What we are trying to do is create a LiteTouch that will only ask the Service Tech 2 questions: Computer Name and Time Zone.
The problem with this approach is we can't customize the DEFAULT user behavior. Or can you?
Any hints or real world experience would be great.
When you import an image into MDT 2010 we want to import a custom .WIM file. But should you run sysprep /generalize /oobe /shutdown /unattend:unattend.xml “before†you run your imagex /capture on your .WIM file?
Or do you import a Windows 7 image straight from the CD into MDT 2010 and then use the Edit Unattend.xml feature from within that tool?
What we are trying to do is create a LiteTouch that will only ask the Service Tech 2 questions: Computer Name and Time Zone.
The problem with this approach is we can't customize the DEFAULT user behavior. Or can you?
Any hints or real world experience would be great.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Lucid
14 years ago
There are all sorts of guides for MDT out on the web (http://blog.augustoalvarez.com.ar/2009/01/31/microsoft-deployment-toolkit-2010-beta-1-using-mdt-to-prepare-install-and-capture-customized-windows-7-images-part-i/). And I think Microsoft even has some on their site.
When you ask about the DEFAULT behavior, what exactly are you asking about? Are you talking about wanting to customize the default user profile so that new users have custom settings when they log in?
My suggestion is to first build and capture a basic install. That way you have the minimums down. Then make a list of customizations you want to do and start hitting them one by one. There's a lot of good info out there, but usually you have to jump around from site to site because everyone customizes different things...
When you ask about the DEFAULT behavior, what exactly are you asking about? Are you talking about wanting to customize the default user profile so that new users have custom settings when they log in?
My suggestion is to first build and capture a basic install. That way you have the minimums down. Then make a list of customizations you want to do and start hitting them one by one. There's a lot of good info out there, but usually you have to jump around from site to site because everyone customizes different things...
Posted by:
mhsl808
14 years ago
When you ask about the DEFAULT behavior, what exactly are you asking about? Are you talking about wanting to customize the default user profile so that new users have custom settings when they log in?
Yes, that is exactly what we want to do. We want a custom .WIM file that we can apply via MDT or straight from a USB boot drive. So we have been doing what you said.......step-by-step-by-step ;-)
Yes, that is exactly what we want to do. We want a custom .WIM file that we can apply via MDT or straight from a USB boot drive. So we have been doing what you said.......step-by-step-by-step ;-)
Posted by:
vandrd
14 years ago
First you need to import the source files from the DVD that you want to create your custom image for. Then, create a task sequence that will capture that deployed reference image. and create your custom .wim from that (yes, you want MDT to do that sysprep and capture of this image)
If you want to customize your image, you can either change the settings in the unattend.xml, or put those changes directly in your image (before the sysprep runs), or script them using scripts and applications.
If you want to customize your image, you can either change the settings in the unattend.xml, or put those changes directly in your image (before the sysprep runs), or script them using scripts and applications.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.