Cloning XP Embedded Systems

[Juergen Striegel]

> disk. Propagate this image to the multiple cloned machines. The next time
> this image boots the cloning phase begins, the computer's SID from the
> master device is replaced with a unique SID.

We have to change a lot of the settings after generating a new build, e.g.
disbaling Time from being updated by a timeserver, changing background
colors, setting some folder options. How can we manage this in the
production process if we start going through the final fba sequence where
there is no chance to do all these settings before? Is there a mechanism
that individualizes the system after some 'handmade' settings are done? It's
too time intesive to do that for each device separatly. Or perhaps there's a
way to fine-tune the system from td by being able to adjust (all) registry
entries to custom values before building?
On NTE we used NewSID from sysinternals after making a full working master.

Juergen

[Andy Allred [MS]]

Read the subject of "cloning" in the help files. Before you actually clone
the runtime to a master disk you go through a reseal phase after FBA which
allows you to do any tweaking necessary before you finalize the image. After
that shut it down, clone it and you're good to go from there.

Andy

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Juergen Striegel" <j...@jstriegel.de.nospam> wrote in message
news:u8im8URxBHA.608@tkmsftngp05...

[Antoine EMERIT]

"You can also customize the start behavior of the reseal application using
the cmiResealPhase extended property in the System Cloning Tool component.

This property specifies at which FBA phase the reseal operation occurs. By
default, this property is set to 12,000. If this value is set to 0, you must
start the reseal phase manually. You can specify phases other than 0 and
12,000 but only these two phases are supported. If the phase is set too
early, it may interfere with other FBA operations and produce unpredictable
results including a non-functional run-time image. If you set this property
to 0, only the cloning tools will be copied to the run-time image and the
cloning phase will not occur. To manually complete the cloning phase, open a
command prompt, navigate to the %Windir%\Fba directory, and then type
Fbreseal.exe."

Regards

"Juergen Striegel" <j...@jstriegel.de.nospam> a écrit dans le message de news:
u8im8URxBHA.608@tkmsftngp05...

[Juergen Striegel]

> This property specifies at which FBA phase the reseal operation occurs. By
> default, this property is set to 12,000. If this value is set to 0, you
must
> start the reseal phase manually. You can specify phases other than 0 and

That was it. Thanks!