EWFMGR reports STATE DISABLED after commiting

  • Thread starter Thread starter ottanobetta
  • Start date Start date
O

ottanobetta

This all started when I upgraded to Feature Pack 2007.

On the first boot after the FBA I execute the command EWFMGR c: -commit
-all, then I execute the fbreseal command. The machine reboots, it finishes
reseal. It all looks normal except when I enter EWFMGR -all. The report
says STATE is DISABLED, and Current Level is N/A. I used the same sequence
of commands before I upgraded to Feature Pack 2007 and it was always
successful.

The image appears to be write protected, any new files created are gone at
next boot. The regisrty appears to have all the correct entries. I am just
not convinced the EWF is working. Has anyone else ever had this problem?

For the record the EWF is configured RAM (Reg), Start EWF is not selcted,
number of protected volumes is 1.
 
I am turning it on using the command "EWFMGR c: -commit -all" in cmd console.
The repsonse always comes back saying the Boot Command is COMMIT.

I am using a SLX that built before I upgraded with this feature pack. Most
of the parameters I am using defaulted when I did the upgrade configuration.

Is there some setting I am missing?
 
The -all doesn't enable EWF. It only performs the COMMIT for all volumes. If
EWF is disabled, the overlay is not being used, and nothing really gets
commited to the volume. EWFMGR c: -enable and a reboot will enable EWF. Then
you can use EWFMGR c: -commit -all to commit the overlay.

-Sean
 
I understand that the -all is not required to commit the overlay. What I am
trying to say is that I manually activate the EWF using the procedure I used
before upgrading with FP07 and now it doesn't work. I tried substituting the
enable command for the commit and then the reseal was not worknig correctly.
I get a window box that says resealing in progress at every subsequent boot.

Should I select the Start EWF Enabled in TD? What should my EWF partition
size be?

I really appreciate your help.
 
I am just not sure how EWF become enabled with that call. It does't make
sense. If it was a bug than it is fixed in the latest release.

One idea to do cloning and EWF in the is case:
1. is to leave EWF disabled
2. perform FBReseal.
3. On each clone, enable EWF,

-Sean
 
The commit command was the recommended way to enable the EWF before FP07.

Thanks for the suggestion but it's not practical with my product. I need to
deploy a write protected image that can come up on a network with a unique
identifier.

I would submit to you that this is a bug. My old process would allow the
fbreseal to complete, deleting its files, and then enable the EWF. It
appears that with FP07 the EWF turns on before the fbreseal files can be
deleted.

I have tried to rebuild the image in many variations and I have not been
able to get fbreseal to work with the EWF enabled. I was hoping that someone
 
No offense but your example did not work for me. My target is a RAM(Reg)
that runs out af a CF. My target has very few Windows utilities so many of
the things you suggest are not possible for me to do. I have tried several
configurations of the EWF settings but I still can't get the cloning to work
with EWF like it did before FP07.

BTW: checking the start EWF Enabled box seems to have no effect on the
build. The EWF still has to be manually started.
 
Back
Top