MDT LTI preparation CustomSettings.ini question and more

[J.R.]

I have created a master computer thick client of which I wish to obtain and
image. I am using Microsoft Deployment Toolkit 2008 LiteTouch and am
editiing the properites of my Deployment Point. On Rules tab under Default
(CustomSettings.ini file) is OSInstall=Y. It is recommended that I treat
this as Read-Only. However, I don't want to lose all my work creating the
Vista Master computer with core apps and all patches and drivers installed
since all computers being deployed are identical models and makes purchased
at same time as Master computer which one one of those purchased.

Yet, I need to create the WinPE/ImageX ISO by updating in MDT 2008 and then
capture the image on the Master computer. I've never done this before and am
remote (500 miles away). I also have set up SQL database in Deployment
Workbench if that is a useful option at this point.

I need to capture the Master image and then deploy to computers through LTI
PXE boot process with virtually no user intervention. Volume licenses so
will be using KMS and desire MDT 2008 to make that easier. I wish the imaged
computers to boot up joined to the domain and ready to use. I have
UUIDs/GUIDs for pre-staging in Active Directory and/or deployment database if
that is where it is done.

Really new to Vista, MDT 2008, WAIK, WDS, and this kind of mass deployment
process. I've used Ghost on a 1 to 3 (Max) basis in the past when I was
local but Ghost Suite proved unreliable as it would not recognize some
computers after client was installed. Abandoned that approach and desire to
go Windows method of deployment and management.

Don't have SMS or other management tools other than MDT 2008, WAIK, and WDS.
They are set up on 64-bit Windows 2003 R2 server with plenty of room, memory
and power and MS SQL installed and MDT database set up.

Willing to pay Microsoft via Technical IT Professional Support call or other
expert in Vista deployment with MDT for mentoring or more direct guidance.

[unknown]

Well, I wouldn't even try to image a physical machine remotely (unless
the machine has an ILO card etc..)... I use virtual machines to create
my reference images...

To create an image (for later import in MDT), you can run sysprep
manually, boot into a generic WinPE boot image, and use imagex to
capture the machine to an image... You can also use a Task sequence
that do capture only, you can find a sample on my blog.

Capture only Task Sequence for MDT 2008 (Lite Touch)
http://www.deployvista.com/Home/tabid/36/EntryID/77/language/sv-SE/Default.aspx

If the machines are exactly the same you can configure unattend.xml
not to wipe the drivers during the sysprep process (the setting is
PersistAllDeviceInstalls)


Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by J.R.
I have created a master computer thick client of which I wish to obtain and
image. I am using Microsoft Deployment Toolkit 2008 LiteTouch and am
editiing the properites of my Deployment Point. On Rules tab under Default
(CustomSettings.ini file) is OSInstall=Y. It is recommended that I treat
this as Read-Only. However, I don't want to lose all my work creating the
Vista Master computer with core apps and all patches and drivers installed
since all computers being deployed are identical models and makes purchased
at same time as Master computer which one one of those purchased.
Yet, I need to create the WinPE/ImageX ISO by updating in MDT 2008 and then
capture the image on the Master computer. I've never done this before and am
remote (500 miles away). I also have set up SQL database in Deployment
Workbench if that is a useful option at this point.
I need to capture the Master image and then deploy to computers through LTI
PXE boot process with virtually no user intervention. Volume licenses so
will be using KMS and desire MDT 2008 to make that easier. I wish the imaged
computers to boot up joined to the domain and ready to use. I have
UUIDs/GUIDs for pre-staging in Active Directory and/or deployment database if
that is where it is done.
Really new to Vista, MDT 2008, WAIK, WDS, and this kind of mass deployment
process. I've used Ghost on a 1 to 3 (Max) basis in the past when I was
local but Ghost Suite proved unreliable as it would not recognize some
computers after client was installed. Abandoned that approach and desire to
go Windows method of deployment and management.
Don't have SMS or other management tools other than MDT 2008, WAIK, and WDS.
They are set up on 64-bit Windows 2003 R2 server with plenty of room, memory
and power and MS SQL installed and MDT database set up.
Willing to pay Microsoft via Technical IT Professional Support call or other
expert in Vista deployment with MDT for mentoring or more direct guidance.

[J.R.]

I understand your use of virtual machines now. When I began this process, I
did not know that one could use them to create an image for deployment. I
work remotely from our office but have a person who I guide to do the
physical operations necessary so I will not be imaging the physical machine
remotely.

I have followed your steps but I have several questions about your Capture
Only Task Sequence on your blog:
1. What files from where do I copy to C:\Sysprep if I am going to run the
script from the local machine?
2. After the files have been copied, do I simply login as local
administrator on the reference computer and run the vbs script?
3. Where is the image after I run the script, on the local machine as if I
used imaqex or on the MDT 2008 server? If on the server, I assume it would
be in the Captures folder you had us enter in following your instuctions.
4. After a successful capture with your script is the image ready to
deploy? Using WDS or MDT 2008?
5. Is it possible to pre-stage the computer accounts as managed computers
in Active Directory and assign them the computer names we desire since I have
the UUIDs/GUIDs of each computer? In this process would the computers then
be named as desired and joined to the domain ready to use?

Concerning the alternate run sysprep manually approach:
1. Do I use this command?
C:\Windows\System32\Sysprep\Sysprep.exe /oobe /generalize /shutdown
2. What is the location of the PersistAllDeviceInstalls setting in the
unattend.xml?
3. Where do I create the unattend. xml file and with what?
4. Where does the unattend.xml file go after it is created?
5. After running Sysprep, can I use the WinPE LT disc created iso when I
updated in MDT 2008 after performing your Capture only Task Sequence for MDT
2008 (Lite Touch) steps to boot the reference machine and run imagex to
capture the image?

I apologize for the depth of my ignorance. I've very new to this type of
deployment and to Vista. Thanks for your responses.
--
J. R. Wade
Manager of Information Technology
Office of Criminal District Attorney
Hidalgo County, TX

Post by unknown
Well, I wouldn't even try to image a physical machine remotely (unless
the machine has an ILO card etc..)... I use virtual machines to create
my reference images...
To create an image (for later import in MDT), you can run sysprep
manually, boot into a generic WinPE boot image, and use imagex to
capture the machine to an image... You can also use a Task sequence
that do capture only, you can find a sample on my blog.
Capture only Task Sequence for MDT 2008 (Lite Touch)
http://www.deployvista.com/Home/tabid/36/EntryID/77/language/sv-SE/Default.aspx
If the machines are exactly the same you can configure unattend.xml
not to wipe the drivers during the sysprep process (the setting is
PersistAllDeviceInstalls)
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by J.R.
I have created a master computer thick client of which I wish to obtain and
image. I am using Microsoft Deployment Toolkit 2008 LiteTouch and am
editiing the properites of my Deployment Point. On Rules tab under Default
(CustomSettings.ini file) is OSInstall=Y. It is recommended that I treat
this as Read-Only. However, I don't want to lose all my work creating the
Vista Master computer with core apps and all patches and drivers installed
since all computers being deployed are identical models and makes purchased
at same time as Master computer which one one of those purchased.
Yet, I need to create the WinPE/ImageX ISO by updating in MDT 2008 and then
capture the image on the Master computer. I've never done this before and am
remote (500 miles away). I also have set up SQL database in Deployment
Workbench if that is a useful option at this point.
I need to capture the Master image and then deploy to computers through LTI
PXE boot process with virtually no user intervention. Volume licenses so
will be using KMS and desire MDT 2008 to make that easier. I wish the imaged
computers to boot up joined to the domain and ready to use. I have
UUIDs/GUIDs for pre-staging in Active Directory and/or deployment database if
that is where it is done.
Really new to Vista, MDT 2008, WAIK, WDS, and this kind of mass deployment
process. I've used Ghost on a 1 to 3 (Max) basis in the past when I was
local but Ghost Suite proved unreliable as it would not recognize some
computers after client was installed. Abandoned that approach and desire to
go Windows method of deployment and management.
Don't have SMS or other management tools other than MDT 2008, WAIK, and WDS.
They are set up on 64-bit Windows 2003 R2 server with plenty of room, memory
and power and MS SQL installed and MDT database set up.
Willing to pay Microsoft via Technical IT Professional Support call or other
expert in Vista deployment with MDT for mentoring or more direct guidance.

[unknown]

Hi,

1. When deploying Vista you should not add any files to C:\Sysprep...
In fact you shouldn't even have a C:\Sysprep folder... This is only
for XP/2003 Deployments...

2. Yes

3. On the server (specified in the "Set Image Folder" action in the
Capture Only Task Sequence)

4. Yes (to support additional hardware, you need to import their
drivers into MDT)

5. Not by default in MDT, you will have to create a custom script, a
stored procedure or a web service that will do that lookup... As a
starting point I recommend using the MDT deployment database instead
for pre-staging...


Manual Capture

1. Yes

2. Check the Unattend.chm help file (the setting is in
Microsoft-Windows-PnpSysprep). A better approach (IMHO) is to skip
this, and instead import the drivers into the MDT drivers repository

3. Using WSIM (Windows System Image Manager)

4. Copy the unattend.xml file to C:\Windows\Panther\Unattend,
C:\Windows\Panther, C:\Windows\System32\sysprep or C:\ (the validation
script checks all those locations), Pick one :)

5. Yes, just don't start the deployment :) Instead select the
Administrator cmd prompt, net use to the server, and use imagex to
capture the image... do Not forget to add the /flags command (with the
correct flag), or deployment will fail...

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by J.R.
I understand your use of virtual machines now. When I began this process, I
did not know that one could use them to create an image for deployment. I
work remotely from our office but have a person who I guide to do the
physical operations necessary so I will not be imaging the physical machine
remotely.
I have followed your steps but I have several questions about your Capture
1. What files from where do I copy to C:\Sysprep if I am going to run the
script from the local machine?
2. After the files have been copied, do I simply login as local
administrator on the reference computer and run the vbs script?
3. Where is the image after I run the script, on the local machine as if I
used imaqex or on the MDT 2008 server? If on the server, I assume it would
be in the Captures folder you had us enter in following your instuctions.
4. After a successful capture with your script is the image ready to
deploy? Using WDS or MDT 2008?
5. Is it possible to pre-stage the computer accounts as managed computers
in Active Directory and assign them the computer names we desire since I have
the UUIDs/GUIDs of each computer? In this process would the computers then
be named as desired and joined to the domain ready to use?
1. Do I use this command?
C:\Windows\System32\Sysprep\Sysprep.exe /oobe /generalize /shutdown
2. What is the location of the PersistAllDeviceInstalls setting in the
unattend.xml?
3. Where do I create the unattend. xml file and with what?
4. Where does the unattend.xml file go after it is created?
5. After running Sysprep, can I use the WinPE LT disc created iso when I
updated in MDT 2008 after performing your Capture only Task Sequence for MDT
2008 (Lite Touch) steps to boot the reference machine and run imagex to
capture the image?
I apologize for the depth of my ignorance. I've very new to this type of
deployment and to Vista. Thanks for your responses.

[J.R.]

Thank you for your rapid, clear, responsive post.

This answers my questions thus far.

In answer 5 of the Manual approach I assume by "/flags command" your are
referring to /capture in this situation.

Please let me know when your tutorial is available. I welcome the
opportunity to learn this process more deeply.
--
J. R. Wade
Manager of Information Technology
Office of Criminal District Attorney
Hidalgo County, TX

Post by unknown
Hi,
1. When deploying Vista you should not add any files to C:\Sysprep...
In fact you shouldn't even have a C:\Sysprep folder... This is only
for XP/2003 Deployments...
2. Yes
3. On the server (specified in the "Set Image Folder" action in the
Capture Only Task Sequence)
4. Yes (to support additional hardware, you need to import their
drivers into MDT)
5. Not by default in MDT, you will have to create a custom script, a
stored procedure or a web service that will do that lookup... As a
starting point I recommend using the MDT deployment database instead
for pre-staging...
Manual Capture
1. Yes
2. Check the Unattend.chm help file (the setting is in
Microsoft-Windows-PnpSysprep). A better approach (IMHO) is to skip
this, and instead import the drivers into the MDT drivers repository
3. Using WSIM (Windows System Image Manager)
4. Copy the unattend.xml file to C:\Windows\Panther\Unattend,
C:\Windows\Panther, C:\Windows\System32\sysprep or C:\ (the validation
script checks all those locations), Pick one :)
5. Yes, just don't start the deployment :) Instead select the
Administrator cmd prompt, net use to the server, and use imagex to
capture the image... do Not forget to add the /flags command (with the
correct flag), or deployment will fail...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by J.R.
I understand your use of virtual machines now. When I began this process, I
did not know that one could use them to create an image for deployment. I
work remotely from our office but have a person who I guide to do the
physical operations necessary so I will not be imaging the physical machine
remotely.
I have followed your steps but I have several questions about your Capture
1. What files from where do I copy to C:\Sysprep if I am going to run the
script from the local machine?
2. After the files have been copied, do I simply login as local
administrator on the reference computer and run the vbs script?
3. Where is the image after I run the script, on the local machine as if I
used imaqex or on the MDT 2008 server? If on the server, I assume it would
be in the Captures folder you had us enter in following your instuctions.
4. After a successful capture with your script is the image ready to
deploy? Using WDS or MDT 2008?
5. Is it possible to pre-stage the computer accounts as managed computers
in Active Directory and assign them the computer names we desire since I have
the UUIDs/GUIDs of each computer? In this process would the computers then
be named as desired and joined to the domain ready to use?
1. Do I use this command?
C:\Windows\System32\Sysprep\Sysprep.exe /oobe /generalize /shutdown
2. What is the location of the PersistAllDeviceInstalls setting in the
unattend.xml?
3. Where do I create the unattend. xml file and with what?
4. Where does the unattend.xml file go after it is created?
5. After running Sysprep, can I use the WinPE LT disc created iso when I
updated in MDT 2008 after performing your Capture only Task Sequence for MDT
2008 (Lite Touch) steps to boot the reference machine and run imagex to
capture the image?
I apologize for the depth of my ignorance. I've very new to this type of
deployment and to Vista. Thanks for your responses.

[J.R.]

Operating system deployment did not complete successfully. 2 errors and 1
warning.

Unattend.xml not found in any standard locations ...(locations your script
searched), aborting. ZTI Error - by Z-CaptureOnlyValidation, rc =1
Non-zero return code executing command "C\MININT\Tools\x64\TemBootstrap.exe"
/env:SAStart, rc=2147467259.

I'm assuming from the errors thrown the process is looking for an
unattend.xml file which I saw nowhere mentioned in your post or the reponses
except as related to the Manual Capture.

Do you have recommendations on what that unattend.xml should contain in the
way of values set? I must assume the locations for it to reside are the
same as for the Manual Capture explanations in answer 4.

I did not understand from your post or the answers to it, that an
unattend.xml file would be needed. I expect you assume facts not in evidence
as we say in the legal world. The facts being my having deeper knowledge of
the processes and requirements than I do.

Does the PersistAllDeviceInstalls need to be in this unattend.xml answer
file as well?

Thanks,
--
J. R. Wade
Manager of Information Technology
Office of Criminal District Attorney
Hidalgo County, TX

Post by unknown
Hi,
1. When deploying Vista you should not add any files to C:\Sysprep...
In fact you shouldn't even have a C:\Sysprep folder... This is only
for XP/2003 Deployments...
2. Yes
3. On the server (specified in the "Set Image Folder" action in the
Capture Only Task Sequence)
4. Yes (to support additional hardware, you need to import their
drivers into MDT)
5. Not by default in MDT, you will have to create a custom script, a
stored procedure or a web service that will do that lookup... As a
starting point I recommend using the MDT deployment database instead
for pre-staging...
Manual Capture
1. Yes
2. Check the Unattend.chm help file (the setting is in
Microsoft-Windows-PnpSysprep). A better approach (IMHO) is to skip
this, and instead import the drivers into the MDT drivers repository
3. Using WSIM (Windows System Image Manager)
4. Copy the unattend.xml file to C:\Windows\Panther\Unattend,
C:\Windows\Panther, C:\Windows\System32\sysprep or C:\ (the validation
script checks all those locations), Pick one :)
5. Yes, just don't start the deployment :) Instead select the
Administrator cmd prompt, net use to the server, and use imagex to
capture the image... do Not forget to add the /flags command (with the
correct flag), or deployment will fail...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by J.R.
I understand your use of virtual machines now. When I began this process, I
did not know that one could use them to create an image for deployment. I
work remotely from our office but have a person who I guide to do the
physical operations necessary so I will not be imaging the physical machine
remotely.
I have followed your steps but I have several questions about your Capture
1. What files from where do I copy to C:\Sysprep if I am going to run the
script from the local machine?
2. After the files have been copied, do I simply login as local
administrator on the reference computer and run the vbs script?
3. Where is the image after I run the script, on the local machine as if I
used imaqex or on the MDT 2008 server? If on the server, I assume it would
be in the Captures folder you had us enter in following your instuctions.
4. After a successful capture with your script is the image ready to
deploy? Using WDS or MDT 2008?
5. Is it possible to pre-stage the computer accounts as managed computers
in Active Directory and assign them the computer names we desire since I have
the UUIDs/GUIDs of each computer? In this process would the computers then
be named as desired and joined to the domain ready to use?
1. Do I use this command?
C:\Windows\System32\Sysprep\Sysprep.exe /oobe /generalize /shutdown
2. What is the location of the PersistAllDeviceInstalls setting in the
unattend.xml?
3. Where do I create the unattend. xml file and with what?
4. Where does the unattend.xml file go after it is created?
5. After running Sysprep, can I use the WinPE LT disc created iso when I
updated in MDT 2008 after performing your Capture only Task Sequence for MDT
2008 (Lite Touch) steps to boot the reference machine and run imagex to
capture the image?
I apologize for the depth of my ignorance. I've very new to this type of
deployment and to Vista. Thanks for your responses.

[J.R.]

For your Capture Only Task Sequence for MDT 2008 Lite Touch should the
unattend.xml file be based on boot.wim or install.wim. I expect it should be
boot.wim but am not totally sure and don't want to mess this up.

Also are there any other critical settings in the unattend.xml that I should
address for my capture only task other than the PersistAllDeviceInstalls?
--
J. R. Wade
Manager of Information Technology
Office of Criminal District Attorney
Hidalgo County, TX

Post by unknown
Hi,
1. When deploying Vista you should not add any files to C:\Sysprep...
In fact you shouldn't even have a C:\Sysprep folder... This is only
for XP/2003 Deployments...
2. Yes
3. On the server (specified in the "Set Image Folder" action in the
Capture Only Task Sequence)
4. Yes (to support additional hardware, you need to import their
drivers into MDT)
5. Not by default in MDT, you will have to create a custom script, a
stored procedure or a web service that will do that lookup... As a
starting point I recommend using the MDT deployment database instead
for pre-staging...
Manual Capture
1. Yes
2. Check the Unattend.chm help file (the setting is in
Microsoft-Windows-PnpSysprep). A better approach (IMHO) is to skip
this, and instead import the drivers into the MDT drivers repository
3. Using WSIM (Windows System Image Manager)
4. Copy the unattend.xml file to C:\Windows\Panther\Unattend,
C:\Windows\Panther, C:\Windows\System32\sysprep or C:\ (the validation
script checks all those locations), Pick one :)
5. Yes, just don't start the deployment :) Instead select the
Administrator cmd prompt, net use to the server, and use imagex to
capture the image... do Not forget to add the /flags command (with the
correct flag), or deployment will fail...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by J.R.
I understand your use of virtual machines now. When I began this process, I
did not know that one could use them to create an image for deployment. I
work remotely from our office but have a person who I guide to do the
physical operations necessary so I will not be imaging the physical machine
remotely.
I have followed your steps but I have several questions about your Capture
1. What files from where do I copy to C:\Sysprep if I am going to run the
script from the local machine?
2. After the files have been copied, do I simply login as local
administrator on the reference computer and run the vbs script?
3. Where is the image after I run the script, on the local machine as if I
used imaqex or on the MDT 2008 server? If on the server, I assume it would
be in the Captures folder you had us enter in following your instuctions.
4. After a successful capture with your script is the image ready to
deploy? Using WDS or MDT 2008?
5. Is it possible to pre-stage the computer accounts as managed computers
in Active Directory and assign them the computer names we desire since I have
the UUIDs/GUIDs of each computer? In this process would the computers then
be named as desired and joined to the domain ready to use?
1. Do I use this command?
C:\Windows\System32\Sysprep\Sysprep.exe /oobe /generalize /shutdown
2. What is the location of the PersistAllDeviceInstalls setting in the
unattend.xml?
3. Where do I create the unattend. xml file and with what?
4. Where does the unattend.xml file go after it is created?
5. After running Sysprep, can I use the WinPE LT disc created iso when I
updated in MDT 2008 after performing your Capture only Task Sequence for MDT
2008 (Lite Touch) steps to boot the reference machine and run imagex to
capture the image?
I apologize for the depth of my ignorance. I've very new to this type of
deployment and to Vista. Thanks for your responses.

[unknown]

You should use an unattend.xml for configuring at least the sysprep
generalize settings, but normally also the later passes (specialize,
oobe etc)... When using WSIM to create one you always select an
operating system image.

PersistAllDeviceInstalls in unattend.xml shold only be used when
restoring the image to the exact same type of hardware...

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by J.R.
For your Capture Only Task Sequence for MDT 2008 Lite Touch should the
unattend.xml file be based on boot.wim or install.wim. I expect it should be
boot.wim but am not totally sure and don't want to mess this up.
Also are there any other critical settings in the unattend.xml that I should
address for my capture only task other than the PersistAllDeviceInstalls?

[J.R.]

This Capture Only Task Sequence for MDT 2008 that I am trying accomplish
requires the PersistAllDeviceInstalls as you indicated in a previous answer.
You also indicated that if I didn't include /flags the process would fail. I
do not know what flags to which you are referring and have tried to find
those in the on-line imagex command line. Are these needed if running your
script from the reference computer?

How do I know which of the Components are required for running the Capture
Only script and in which passes they occur or are supposed to be chosen.
This is the problem with the whole Vista deployment issue. The options are
so many and so varied it is virtually impossible for someone to mine through
the thousands of pages of documentation and actually find what is supposed to
be included where for what. I have literally spent days looking just to try
to get the Capture Only Task Sequence to run and fear that if it is not done
correctly my reference computer will have to be created all over again. I
understand your recommendation about virtual machines for imaging but I
already have the reference computer created for the third time and
desperately need some help to complete the image capture task on this
computer.

Where can one find someone that has the experience and knowledge to
accurately guide one through this process the first time to do all possible
to avoid more failures?

I cannot find the amd64-??? and wow64-??? settings that I have showing on
Windows Image Management using the Windows Vista Enterprise install.wim that
I am using.

Where is the documentation that tells you what components should be included
for what kinds of processes and which passes?

Johan, I sure wish I could purchase some of your time on the phone or
directly via email. You are the only one I've found in much search engine
use that has both the knowledge and experience and has tried to share that
on-line.

I've been doing this work for 25 years and have never been more frustrated.
Helps me understand why more corporate level Vista deployments have not been
done.
--
J. R. Wade
Manager of Information Technology
Office of Criminal District Attorney
Hidalgo County, TX

Post by unknown
You should use an unattend.xml for configuring at least the sysprep
generalize settings, but normally also the later passes (specialize,
oobe etc)... When using WSIM to create one you always select an
operating system image.
PersistAllDeviceInstalls in unattend.xml shold only be used when
restoring the image to the exact same type of hardware...
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by J.R.
For your Capture Only Task Sequence for MDT 2008 Lite Touch should the
unattend.xml file be based on boot.wim or install.wim. I expect it should be
boot.wim but am not totally sure and don't want to mess this up.
Also are there any other critical settings in the unattend.xml that I should
address for my capture only task other than the PersistAllDeviceInstalls?