System cloning fails after you change core OS component (256407)
The information in this article applies to:
- Microsoft Windows NT Embedded 4.0
This article was previously published under Q256407 SYMPTOMS
After you change the Core operating system (OS) component in a configuration that contains the System Cloning component, the embedded run-time image that is generated does not perform system cloning.
CAUSE
Both the Minimal OS and Standard OS components contain default values for the HKLM\System\ControlSet001\control\Session Manager\Boot Execute registry key. When the System Cloning component is added, it runs a Target Designer Extension (TDX) file, which adds a "SETUPCL.EXE" string to the HKLM\System\ControlSet001\control\Session Manager\Boot Execute key. This key value enables the system cloning operation at the first boot of the target computer.
When you change Core OS components between Standard OS and Minimal OS, the default value for the Boot Execute key overwrites the value added by the System Cloning TDX.
RESOLUTION
After you change the Core OS component, remove the System Cloning component and then add it again to run the appropriate TDX file, which will add the Boot Execute key value.
STATUS
This behavior is by design.
Modification Type: | Minor | Last Reviewed: | 6/21/2004 |
---|
Keywords: | kbprb KB256407 |
---|
|