Reseal Phase
5/10/2007
The reseal phase is used to reset a run-time image for cloning. Before you can deploy the run-time image to mass systems, you must run First Boot Agent (FBA) to configure the run-time image. By resealing the run-time, a subset of FBA runs when the image is deployed on mass systems. This subset identifies new devices and resets the computer security ID (SID). For more information, see Cloning Overview.
A run-time image is typically resealed after the FBA phase has finished and any modifications are made to the run-time image. Specifically, the run-time image is resealed during FBA phase 12,000, when FBA calls the cmiResealPhase function. You can set the phase when the reseal occurs; however, only phases 0 and 12,000 are supported. If the phase is set too early, it may interfere with other FBA operations and produce unpredictable results, such as a nonfunctional run-time image. For more information, see Customizing the Reseal Phase.
If you set this property to 0, only the cloning tools are copied to the run-time image and the cloning phase does not occur. By delaying the reseal phase, you can make additional updates to your run-time image after FBA. Applications can be installed, or other changes can be made to your run-time image. If the reseal phase is set to 0, you must manually use the Fbreseal.exe utility to start the reseal phase. The utility is located in the %Windir%\system32 directory. For information on running the fbreseal command, see FBRESEAL Commands.
When the reseal phase completes, a message box appears. Choose Shutdown to shut down the system or Reboot to reboot it.
See Also
Tasks
Concepts
Cloning Overview
How to Create a Run-Time Image for Mass Deployment
Product Updates