Packages which force the target computers to reboot during the installation of the original setup can be re-packaged using the DSM Packager and made to reboot in a controlled fashion.
CA Client Automation - All Versions
To ensure that the Packager correctly handles products packaged with the manual procedure (i.e. including "original.sxp") that make a forced reboot you must make sure that the switch "forced reboot" of the original setup is disabled. Additionally, you must set the "BootLevel" parameter to value "3" in the file "info.sxp". After the installation of this package through DSM, with the original setup, the Installer will now force a reboot automatically in a controlled fashion. After the reboot, the installation is finished correctly by the Installer.
Various Boot Levels available:
0 - No boot: This is the default, when the Packaging Computer has not been rebooted during the reference installation.
1 - New login: For Windows NT, Windows 9x, and Windows Me. Boot level 1 requires a user to log off and log on to activate changes to the Windows desktop and registry.
2 - Windows restart: Reserved for Windows 3.1x only. New login is scheduled for all other operating systems.
3 - System reboot at the end of the transaction: For all supported platforms.
This is the default, when the Packaging Computer has been rebooted during the reference installation.
4 - Immediate system reboot: For all supported operating environments. Boot level 4 causes a reboot immediately after the end of the installation or removal of the product.
>4 - None: Reserved.
Note: An sxp package with "original.sxp" must not reboot the system during installation of the original setup, else the installation could be damaged/invalid. The reboot should be always made after the installation of the sxp package when the installation of the original setup needs a mandatory reboot.