SCIF 2.0 Specification - Design Change Requests Centralization of “Reboot to PXE” functionality

Issue Description:

The current code base has the "Reboot to PXE" functionality replicated into multiple instances, one for each vendor supplying an integration. This functionality does not make sense to be replicated and actually becomes confusing when customers create task sequences involving multiple OEMs' custom steps. The reason why it was separated was because it integrated with the templated task sequence creation process and relied on certain WMI class names that are specific to each OEM's customized step. This can all be overcome by modifying the control flow of the code, and should be done to create a better user experience.

Changes Needed:

  • Modify the Reboot to PXE/USB code so that it is not tied to a specific installation and can be used independently of an OEM task sequence or be used by multiple vendors.
  • Create a new task sequence editor menu group for non-vendor-specific tools and place this step (and future custom steps) in the group.
  • Modify the base OEM custom task step code so that it understands the new "generic" Reboot To PXE step.
  • Modify the installation process so that the Reboot To PXE component is installed only if if doesn't currently exist, or if it is an older revision, and is not placed in an OEM-specific location, and create new registry keys associated with the component.

Change Description: New XML Configuration File:
The code will be modified so that the default properties and actions of the Reboot to PXE action can be modified via an XML configuration file. This XML configuration file will be a common, multiple-user file similar to the common XML file controlling the right-click menu actions. The XML file will be default contain two configuration sets:
  1. A template-based configuration that provides the base structure of a series of groups with variable conditions and the task steps necessary to control those variables. This would be similar to an existing task sequence template without the OEM steps added (just the reboot to PXE steps and groups added).
  2. A single reboot step to be added to an existing task sequence.

The XML schema will have defined specific elements and attributes to define where any particular selection is enabled or disabled (for instance, adding a single reboot step to an empty task sequence would not be permitted). The XML would also define the strings to be displayed (localizable), other steps that would be included, and other information as needed. Changes to RunFirstLoadActions():
RunFirstLoadActions() will be modified to read the new XML configuration file. When the code loads the XML file, a dialog is displayed to allow the user to choose their desired configuration. After selecting, the code continues.

Example Scenario:

Last edited Sep 3, 2009 at 8:00 PM by rhearn, version 1


No comments yet.