James
2009-04-17 16:24:20 UTC
Hello,
using mdt 2008 to deploy server 2008....
there are 2 parts... the unattended build and capture, and then the second
part is deploying that captured wim. Each part has its own task sequence and
an unattend.xml file available for use. I'm trying to get clear on what its
doing here so I know what to configure and where...
sysprep has a switch which is used to specify the answer file to be used
with mini-setup, but using mdt, you don't call sysprep manually, its done
via the mdt LTI process...
- is it specifying the answer file you configure for the build and capture
when calling sysprep to prepare the image? further, if so, does it take care
of putting that file where it needs to be within the wim file so it can be
used when deploying that wim? and if so, then whats the unattend.xml
available with the second part of the process then (the one for the task
sequence that deploys the custom wim)? If you specify settings there does it
overide settings from the build and capture one?
using mdt 2008 to deploy server 2008....
there are 2 parts... the unattended build and capture, and then the second
part is deploying that captured wim. Each part has its own task sequence and
an unattend.xml file available for use. I'm trying to get clear on what its
doing here so I know what to configure and where...
sysprep has a switch which is used to specify the answer file to be used
with mini-setup, but using mdt, you don't call sysprep manually, its done
via the mdt LTI process...
- is it specifying the answer file you configure for the build and capture
when calling sysprep to prepare the image? further, if so, does it take care
of putting that file where it needs to be within the wim file so it can be
used when deploying that wim? and if so, then whats the unattend.xml
available with the second part of the process then (the one for the task
sequence that deploys the custom wim)? If you specify settings there does it
overide settings from the build and capture one?