M
Mark K Vallevand
I've been having problems with fbreseal in SP2. It works differently from
SP1. We've had no problems with SP1. We do things correctly, AFAIK.
Include System Cloning Tool. Reseal phase 0. Other advanced flags set as
we want them.
Boot thru FBA on HD.
Create CF with RAM REG EWF.
Boot CF. Configure and adjust OS. Install our applications. Commit EWF,
reboot, test. Repeat until golden.
Commit EWF. Fbreseal. Shutdown. Capture CF image.
Duplicate CF image.
Boot duplicated image at customer site or in factory during customer's
personal setup..
First boot takes a longer time because the SID change is occurring.
Fbreseal.exe self-deleted.
Commit EWF, reboot, perform the customer-unique setup.
Using SP2, when the first boot of a duplicated image is done, the
fbreseal.exe file is still present. The first boot takes a long time and
the SID change seems to occur. But, fbreseal didn't self-delete.
*** Did a SID change occur? ***
*** Why is fbreseal.exe still present? ***
If you commit EWF and run fbreseal again, it behaves correctly. The first
boot takes a long time and the SID change seems to occur and fbreseal.exe is
deleted.
I've been told that running fbreseal with EWF enabled isn't a good idea. If
so, how do you clone? It probably won't hurt the CF to disable EWF,
fbreseal, enable. But, that takes a couple of reboots. The
commitanddisable live feature causes a BSOD, so I'm not considering that
seriously yet. Sysinternals's NewSid is attractive, but broken. NewSid
doesn't update COM security information correctly.
I'm considering releasing CF with fbreseal run twice.
SP1. We've had no problems with SP1. We do things correctly, AFAIK.
Include System Cloning Tool. Reseal phase 0. Other advanced flags set as
we want them.
Boot thru FBA on HD.
Create CF with RAM REG EWF.
Boot CF. Configure and adjust OS. Install our applications. Commit EWF,
reboot, test. Repeat until golden.
Commit EWF. Fbreseal. Shutdown. Capture CF image.
Duplicate CF image.
Boot duplicated image at customer site or in factory during customer's
personal setup..
First boot takes a longer time because the SID change is occurring.
Fbreseal.exe self-deleted.
Commit EWF, reboot, perform the customer-unique setup.
Using SP2, when the first boot of a duplicated image is done, the
fbreseal.exe file is still present. The first boot takes a long time and
the SID change seems to occur. But, fbreseal didn't self-delete.
*** Did a SID change occur? ***
*** Why is fbreseal.exe still present? ***
If you commit EWF and run fbreseal again, it behaves correctly. The first
boot takes a long time and the SID change seems to occur and fbreseal.exe is
deleted.
I've been told that running fbreseal with EWF enabled isn't a good idea. If
so, how do you clone? It probably won't hurt the CF to disable EWF,
fbreseal, enable. But, that takes a couple of reboots. The
commitanddisable live feature causes a BSOD, so I'm not considering that
seriously yet. Sysinternals's NewSid is attractive, but broken. NewSid
doesn't update COM security information correctly.
I'm considering releasing CF with fbreseal run twice.