fbreseal corrupts IIS

[Eric Johnson]

Coninuing a thread of last week...

0) I build a nice, functioning XPe system with my apps
and IIS web / ftp sites. Everything works.
1) I run fbreseal.
2) I shutdown.
3) I reboot.
a) Machine has a new name
b) Machine has a new IP address
4) I run inetmgr
a) It is 'connected' to the new mahcine's name
b) The IIS version (posted in the right pane) is
"V22147.59039". It should be V5.1 ?!?!?!?
c) Metabase.bin is 608 bytes.
d) The saved versions of Metabase.bin are 191,xxx bytes.
e) Attempts to restore saved Metabases all generate
an error:
"The data is (sic) invalid"
f) Attempts to RESTART IIS generate the error:
"The system cannot find the file specified."
g) Invoking MetaEdit.exe generates the error:
"An unknown error was encountered in a calling
function, the error message passed was:

"A fatal error occured trying to
connect to LOCALHOST""


If anybody has any idea what fbreseal is doing to IIS
stuff, I'd really appreciate a tip....

TIA,

ej

 

[Doug Hoeffel]

Eric:

I don't know if this will matter or not but I don't generate a new IP or
Computer Name after the reseal.

Maybe you can try keeping everything the same before and after the reseal
(except the SID of course), i.e. use the -keepall switch on the reseal.

HTH... Doug