fbreseal headaches



BattleAngel444
07-09-2005, 10:25 PM
Hi Gang

ok soooo ever since i ve added the system cloning component to my image
all i'm running into a few technical hurdles by running the fbreseal
command

Hurdle #1) after a make an iamge and booting it up the first time on
the target machine... if i use ewfmgr d: -enable then seal my image i
won t be able to get a unquie system name, which is why i needed system
cloning to begin with. so my work around is to fbreseal -autologon
-keepdoman -keepnet -keppuser -keepmounted then run ewfmgr d: -enable.
is this how you're supposed to do it?

Hurdle #2)In my image i have put a default webpage under
inetpub/wwwroot and before i every run reseal i can get to teh webpage
easily from and computer just by typing http://computers_ip_address
but when i reseal and boot again i can not get to that page on the test
machine? i remember having to punch a hole in the firewall to get to
the webpage. but those changes i made to the windows firewall
component should still have persisted... right? does resealing turn
off IIS by default?

Hurdle #3) when i do a reseal and i get a unique name i get the oem
name with an append unique identifer. is there a way for it to append
the computer name?

thanks again for the help
-Garvin

KM
07-09-2005, 10:26 PM
Garvin,

> Hurdle #1) after a make an iamge and booting it up the first time on
> the target machine... if i use ewfmgr d: -enable then seal my image i
> won t be able to get a unquie system name,

You will get a unique name one every reboot next to seal until you commit the change.

> which is why i needed system
> cloning to begin with. so my work around is to fbreseal -autologon
> -keepdoman -keepnet -keppuser -keepmounted then run ewfmgr d: -enable.
> is this how you're supposed to do it?

What type of EWF you use in your image?
I'd do the cloning with EWF disabled and then, after the cloning phase happens on every deployed device, enable EWF manually or
automatically (automatic implementation would depend on your image components included - you can use Run/RunOnce key, StartUp item,
etc.).

> Hurdle #2)In my image i have put a default webpage under
> inetpub/wwwroot and before i every run reseal i can get to teh webpage
> easily from and computer just by typing http://computers_ip_address
> but when i reseal and boot again i can not get to that page on the test
> machine? i remember having to punch a hole in the firewall to get to
> the webpage. but those changes i made to the windows firewall
> component should still have persisted... right? does resealing turn
> off IIS by default?

So, did you:
- check the firewall settings? Open ports (http, etc.)? (after reseal)
- check whether ipconfig shows the same ip after resea as it was before the reseal?
- check if you can ping the ip?

Hope you don't launch fbreseal more than one time.

> Hurdle #3) when i do a reseal and i get a unique name i get the oem
> name with an append unique identifer. is there a way for it to append
> the computer name?

There is currently no way to intercept or change the way how FBA (cloning) generates the unique names but you can create your own
algorithm and use SetComputerName[Ex] API to change the name as needed.
Some more info you may find in this thread:
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/browse_frm/thread/1bc763ec0a7a527f/b07c92afd1346b65#b07c92afd1346b65

KM


fbreseal headaches