Sigh... fbreseal nukes policy and registry changes, does random s

[Guest]

No EWF, system cloning tool and fbreseal have/are run with the correct
settings to retain everything except the computer name. I delay resealing so
that I can add some additional software and make changes. I set up one user
account with a custom shell (via registry settings) and the admin account
with an explorer shell. I add a bunch of icons to the admin account desktop
and change some policy settings using gpedit.msc. I run "fbreseal -autologon
-keepdomain -keepnet -keepuser –keepmounted" and turn off the computer after
reboot during POST. I use Ghost 2k3 to clone the drive. I then put that
cloned "gold" image on five machines and turn them on. I would assume that
each one should finish the reseal phase and boot into the custom shell. All
settings that I changed should remain. However, random stuff happens. I
might get a machine that acts exactly as I would expect, with all settings
remaining. I will also get a machine that loses its custom shell, icons on
the desktop and policy changes. Then I'll get a machine that has its custom
shell, but when I log into the admin account and then reboot, the custom
shell disappears. WTF? FBALOG.TXT doesn't show anything out of the
ordinary. What could cause random behavior like this? Why is FBRESEAL
nuking my registry changes? I'm goin nuts, baby! HALP!

 

[Guest]

Does this have something to do with the fact that fbreseal changes the
computer name? is there any way around this????

 

[Brad Combs]

Hello William,

To disable the computer name change open your configuration, highlight
"System Cloning Tool", in the right pane click "Advanced", in the "Advanced
Component Properties" double click "cmiGenerateComputerName" and change the
value to 0, click OK. Rebuild and after FBA run fbreseal.

HTH,
Brad

 

[Guest]

or type fbreseal -keepall

(or some other options appropriate)