Cloning

[Richard]

The article below states that after FBA runs, you reseal, then can copy your
post FBA image to other devices for deployment. Then it states that FBA
will run (Item 3). Why does FBA have to run again if it already has? Is it
to change the IDs and stuff? Here's the biggie, is it a full blown FBA that
takes 2 hours or is it a little quicker since FBA ran on the original image.



After the run-time image is configured for cloning, resealed, and ready for
deployment, create a master image of the run-time. The master run-time image
is used to deploy onto your devices. You can use any backup method to create
your master run-time image, from creating a CD-ROM to saving it to tape.

To create a master run-time image for cloning

1.. Create the master run-time image by backing it up to an archival
media, CD-ROM, or tape.
2.. After the master run-time image is created, copy the master run-time
image to your devices.
3.. Boot the device and allow the First Boot Agent (FBA) phase to run.
After the FBA phase completes, the target is ready to be deployed.

 

[Richard]

I guess I found the answer, a subset of FBA is used. So this means it's
fairly quick and simple. Will I have to power up each device before it's
deployed or will FBA run on it's own and be done.

 

[KM]

Richard,

You include "System Cloning Tool" in to your image and deploy the image to your target. First FBA runs to install all components
(usually a long phase).
Then you reseal the image (fbreseal) - reseal phase usually . You capture your image and clone it to all target devices you have.
Whenver you boot up the devices (first time) the system cloning phase happens to set up device parameters (machine names, SIDs,
etc.). It is again FBA window but the window appears for a little while (usually a few seconds) so you don't have to be really
concerned about this FBA phase.

You should have probably read the next section after the one you mentioned:
http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconConfiguringResealPhase.asp