FBReseal.exe

[=?iso-8859-1?Q?Grabher_G=FCnter?=]

After FBA und all necessary changes I executed
FBReseal.exe and got the message "System resealed -
reboot" as expected.

After copying the whole stuff via Norton-GHOST to another
disk i started the system with this new disk.

Surprise 1
----------
The steps 12000... from FBA didn't ececute

Surprise 2
----------
EWFMgr informed me "Unable to find an ewf volume" but ewf
was enabled. Additionally -commit was impossible (Error 87)


Any ideas, suggestions, to save pain ?

 

[Gianluca Facca]

Was the ewf partition disabled when you execute FBReseal.exe?
I think that if ewf is enabled FBReseal has no effect.

 

[Doug Hoeffel]

Use -commitanddisable with ewfmgr.

As for Ghost, you need certain switches (SZEE, FDSP, IR, etc.) so that the
EWF partition will be cloned. Search old posts for this.

HTH... Doug

 

[Tony Camilli]

I can't speak to Surprise 1. For suprise 2, it looks
like you were originally using RAM-based EWF, but in the
process of ghosting the image, you lost the type 45
partition that should be on the end of the drive. When
ghosting an XPe image using RAM-based EWF, make sure you
are ghosting the entire drive, not just the partition.
Also, if you are going to be deploying to different size
media, you may want to allow EWF to completely re-create
the overlay partition. You can do this by deleting the
original overlay partition before ghosting using
etprep.exe -delete. To prevent kicking-in to registry-
based EWF, you will also have to delete the following reg
keys before resealing:

HKLM\System\ControlSet001
\Services\EWF\Parameters\Protected\Volume0

HKLM\System\CurrentControlSet\Services\EWF\Parameters\Prot
ected\Volume0

HTH,
Tony

 

[Slobodan Brcin \(eMVP\)]

And to add to this.
If you are planning not to use extra config partition.
Then you can skip it's creation if first place.
For description and solution of this download
http://www.xpefiles.com/a_file.cfm?custid=Components&fileid=ramewf.zip&group
Name=Other

This will save you few extra MB of disk space and you wont have any problems
related to disk copy and EWF.

Regards,
Slobodan

 

[Dan Simpson [MS]]

Hi Grabher,

Here's a section out of new EWF docs I'm working on wrt using EWF and
Cloning. There's certain considerations to make when you use EWF and
cloning.

Like Slobodan suggested, you should probably consider using EWF RAM Reg
overlay type-- this precludes the need for an additional EWF volume (as all
of the EWF configuration information is stored in the registry.) You can
find information on how to use EWF RAM Reg overlay here:

http://msdn.microsoft.com/library/en-us/dnxpesp1/html/XPESP1_CF_EWF.asp



Design Considerations for Using EWF with Cloning
If you use both the Enhanced Write Filter and Cloning components in your
run-time image, there are additional configuration steps that you need to do
to successfully clone your write-protected image. Keep in mind the following
steps when building your run-time image.

1. In Target Designer, configure the following components to support
cloning.

· Set the EWF component to start Disabled.

· Set the System Cloning Tool component cmiResealPhase to 0.

2. Build and deploy your target image. Allow FBA to complete. Boot your
run-time image and verify that EWF is properly configured by reviewing the
FBA log in Windows\FBA\FBALOG.txt.

3. Install applications or make additional configurations to your
run-time image.

4. When you are ready to create your gold master, enable EWF on the
next reboot by using the ewfmgr commit command.

ewfmgr c: -enable

5. After EWF is enabled, reseal the run-time image with the
fbreseal.exe command. For example,

fbreseal.exe

6. Use the run-time image to create your Gold Master. Depending on the
EWF overlay types, you will need to create the partitions for your run-time
image and EWF volume on the devices you are mass-deploying to.

· EWF RAM Overlay

Create new partitions on your device for the run-time image and the EWF
volume. You can use Windows PE and diskpart to see the exact sizes of your
partition layout. Then, copy the run-time image and the EWF Volume to your
gold master image media. For more information, see Using Windows PE and
Diskpart to Configure a Hard DrivexehowUsingDiskpartToConfigureHardDrive.

· EWF RAM REG Overlay

Create the partition for the run-time image on your device. Copy only the
run-time volume to your gold master image media.

· EWF Disk Overlay

Create new partitions on your device for the run-time image, the EWF volume,
and the EWF overlay. You can use Windows PE and diskpart to see the exact
sizes of your partition layout. Then, copy the run-time image volume, the
EWF volume and the EWF disk overlay volume to your gold master image media.
For more information, see Using Windows PE and Diskpart to Configure a Hard
DrivexehowUsingDiskpartToConfigureHardDrive.

7. Mass Deploy your run-time image to the devices. During the FBA
phase, a unique System Identifier is assigned to the system. If the Enhanced
Write Filter is enabled, the System ID must be committed to the system using
ewfmgr.

You can either commit the new System ID to the system manually with the
ewfmgr c: -commit command, or you can create a batch file that you can set
to run during FBA that will commit the System ID.

After running the ewfmgr command, restart your device.





Dan

 

[Guest]

Thanks for all your high-quality answer on EWF plus cloning

I independently came to the following solution

1. Using EWF RAM REG Overlay means avoiding this strange 45-partition
whic
is a problem for most cloning tools. This simplifies a lot
2. I do not use the cloning component anymor
3. I prepare the Gold Master wit

a) copying newsid form sysinternals to system3
b) providing a run-once registry-key with "newsid.exe /a
c) providing a run-once registry-key with "ewfmgr c: -commit