ewf + fba reseal

[Guest]

so.. i build an image, copy to a ntfs partition, and boot up on that
partition. it does the FBA, and because i set the cloning tool to run the
reseal in phase 0, not 12000, it doesnt seal it up.

now, i reboot and am in the xp embedded system. i install the remaining
stuff i need, and all is good. im ready to wrap it all up.

now, this is where i'm a bit confused. im wanting to use EWF that is either
ram or ramreg mode, havent decided yet. the confusion sets in here:

do i reseal and then boot back up and enable EWF? after i enable ewf, i take
the image and blast it onto a ton of disks? or am i supposed to reseal, blast
hte image to disks, and then on each machine run and enable the EWF?

the second choice (enable EWF on each machine) seems right, otherwise the
resealing wont have a chance to generate a unique SID for each machine: it
wont be able to write to disk since EWF is enabled.

the problem with the second choice is that i have to do a weird multi-boot
thing.. the first time it boots, it only does EWF on, but subsequent times,
it runs my shell app.

any pointers for me?

 

[Sean Liming \(eMVP\)]

Here is a start:
You can create a custom DLL that FBreseal calls to commit changes to the
drive automatically. Then you can copy the image to other drives and each
drive will generate a new SID on boot. The problem is a SID will be
generated each boot until a comit is made.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.

 

[Guest]

hrm.. that wasnt exactly what i was asking.. here is what im thinking now,
does this seem right:

on first boot after the fba, ill set up a program to run that enables the
ewf and reboots. the next time, the program will notice that ewf is on, and
not reenable it, and instead run the app for the device