FBResealing... and Manual reseal

[ViceGrip]

My latest image is displaying a FBResealing... windows during boot up
on the target machines. By allowing the target system to reboot after
resealing the FBResealing window went away, however, now I get the
"duplicate names" on network dialog.

I am using the manual resealing method, where I build the image, boot
the image on the target system, install other software, run FBReseal
with -autologin and -keepuser switches, shutdown the system and deploy
what is left on the drive. cmiResealPhase is set to 0.

From emails with Lynda at MS, she said I must allow the system to
reboot in order for the resealing to finish, however, everything from
MSDN that I have read leads me to believe that allowing the system to
reboot is bad.

I have also read a post on here that there was a bug in the FP2007
FBReseal.exe?

What is the procedure for a manual reseal?

 

[Matt Kellner \(MSFT\)]

Hi there. The correct procedure for using FBReseal is to run it when you're
ready, then let the system shut down. Do *not* let it reboot back into the
runtime at this point - the period between when the system has shut down
after fbreseal.exe is run, and the next boot, is when you should deploy the
runtime to your final devices. The next boot is the one on which the
individual computer receives its unique identifier and computername.

There should be no visible message on the screen about "resealing" when the
final device boots. If you are seeing such a message, it may very well be a
bug, or some other problem with your configuration. Please let us know if
you're still seeing it after following the steps given above, and we'll see
if we can reproduce it here. Thanks.

 

[ViceGrip]

Hi there.  The correct procedure for using FBReseal is to run it when you're
ready, then let the system shut down.  Do *not* let it reboot back intothe
runtime at this point - the period between when the system has shut down
after fbreseal.exe is run, and the next boot, is when you should deploy the
runtime to your final devices.  The next boot is the one on which the
individual computer receives its unique identifier and computername.

There should be no visible message on the screen about "resealing" when the
final device boots.  If you are seeing such a message, it may very wellbe a
bug, or some other problem with your configuration.  Please let us knowif
you're still seeing it after following the steps given above, and we'll see
if we can reproduce it here.  Thanks.

--
Matt Kellner
SDET, Microsoft Windows Embedded Team

This message is posted AS-IS, without any warranty, and confers no rights..

I am still seeing the FBResealing window in my images. Takes the
image 3 extra minutes to boot.

Could this be a corrupted version of the FBResealing tool? I did not
have this issue prior to installing several XPE updates: (update
rollup 1.0 x13-82297 and several others dating all the way back to
June of 2005)?

 

[Mike Warren]

There should be no visible message on the screen about "resealing"
when the final device boots.

After running fbreseal and clicking on the "Shutdown" button, I see a
message "Resealing in progress..." the next time the machine is
switched on. I don't remember this in SP2 builds.

For me, the process adds a few extra seconds to the first boot after
sealing.

I have another new problem related, it seems, to fbreseal.

1/ Perform FBA and config on one device and the run fbreseal.

2/ Transfer the files to another device (identical hardware).
* Unit boots (shows the Resealing.. message) and works fine.

3/ Reboot the unit.
* USB no longer works.

If I then connect the same hard drive to the the original device, USB
works fine.

This happens if I use generic drivers or install the correct drivers
from the CD. I never had any problems like this with SP2 builds on the
same hardware.

If I don't run fbreseal, USB works fine, no matter what hardware I
transfer the image to, but EWF will not work.

All this behaviour is very different from SP2. Does anyone know if it's
possible to install FBWF manually on an SP2 build. I'm thinking about
trying to revert back to SP2. This is going to cause problems because I
am otherwise happy with the size/functionality compromises of the
FP20007-RU1 build.

Another possible work-around: Is it possible to install EWF manually?

It's unfortunate that Slobodan and Konstantin are no longer around
here. They were an excellent resource for the XPE community.

 

[Mike Warren]

I have another new problem related, it seems, to fbreseal.

This gets stranger, and goes some way to explaining why I didn't notice
it before.

I have 2 machines here with identical hardware, let's call them A and B.

If I perform FBA and fbreseal on A, the image will work fine on B

If I perform FBA and fbreseal on B, USB fails to work when the image is
transfered to A.

These are 3 year old devices which worked with several previous SP2
builds.

I'll try to find a couple more of these machines to see if I can make
more sense of it.

I feel a significant point is that the machine which fails will work
fine on the first boot after fbreseal.