J
jimt
Hi; I have found at least three recipes for deploying a disk-ewf image with
the cloning component. No wonder this topic attracts so many posts.
- XPe Help suggests leaving EWF off until the final target. Then
ConfigureEwf is
manually called to create the EWF partition ("rundll32 ewfdll.dll
ConfigureEwf")
- Sean Liming's "Supplemental Toolkit" has an example where EWF is set in TD
to be
enabled as FBA begins it's first pass. A custom DLL is used to commit any
last
minute changes before fbreseal, and presumably the deployed image comes up
on
the final target with EWF still on.
- The Windows XP Embedded Resource Kit manually enables EWF just before
fbreseal, and then manually recreate the EWF volume using ConfigureEwf
If EWF is enabled when the cloned image is booted on a final target, won't
all the rewritten SIDs on the (in my case) NTFS filesystem be write-cached?
Maybe that is why the official XPe help recipe says to hold off on EWF
startup until the final target is booted off the cloned image.
If you want to deploy a FP2007 disk-EWF cloned image, what recipe do you
use? The goal is to minimize or eliminate manual operations on the final
target machines.
Seems like you would want to run without EWF thru and including the time
when you type "fbreseal", and include a "runonce" script to fire up EWF-disk
on the final target when it first boots. The only question is whether or
not the EWF would start before the SID value was changed and written to the
drive?
Reactions would be most welcome, thank you,
the cloning component. No wonder this topic attracts so many posts.
- XPe Help suggests leaving EWF off until the final target. Then
ConfigureEwf is
manually called to create the EWF partition ("rundll32 ewfdll.dll
ConfigureEwf")
- Sean Liming's "Supplemental Toolkit" has an example where EWF is set in TD
to be
enabled as FBA begins it's first pass. A custom DLL is used to commit any
last
minute changes before fbreseal, and presumably the deployed image comes up
on
the final target with EWF still on.
- The Windows XP Embedded Resource Kit manually enables EWF just before
fbreseal, and then manually recreate the EWF volume using ConfigureEwf
If EWF is enabled when the cloned image is booted on a final target, won't
all the rewritten SIDs on the (in my case) NTFS filesystem be write-cached?
Maybe that is why the official XPe help recipe says to hold off on EWF
startup until the final target is booted off the cloned image.
If you want to deploy a FP2007 disk-EWF cloned image, what recipe do you
use? The goal is to minimize or eliminate manual operations on the final
target machines.
Seems like you would want to run without EWF thru and including the time
when you type "fbreseal", and include a "runonce" script to fire up EWF-disk
on the final target when it first boots. The only question is whether or
not the EWF would start before the SID value was changed and written to the
drive?
Reactions would be most welcome, thank you,