Proper Installation Order for WinPE Optional Packages in Deployment Solution 8.7 and Later

Products

• IT Management Suite
• Deployment Solution

Issue/Introduction

When configuring Windows Preboot (WinPE) environments in Deployment Solution (DS), administrators may encounter errors during the environment rebuild process. These issues typically occur because the optional components (packages) selected for the WinPE image were not added in the correct sequence to satisfy their internal dependencies.

WinPE default and optional packages in ITMS 8.7+ are not independent; many rely on "foundational" packages to be present before they can be successfully injected into the Boot WIM. The order in which the packages are listed in the "Preboot Environment Settings" determines the sequence in which they are loaded. If a high-level package is processed before its prerequisite, the build process fails.

Environment

ITMS 8.7.x, 8.8.x
Deployment Solution (DS) 8.7.x, 8.8.x
Windows Preinstall Environment (WinPE) 10/11

Cause

The Microsoft ADK (Assessment and Deployment Kit) requires foundational components to be "staged" in the WIM file linearly.

• WinPE-WMI is the most common prerequisite and must almost always be first.

• WinPE-PowerShell has the most complex requirements, needing WMI, NetFX, and Scripting present beforehand.

Resolution

To resolve rebuild errors, you must manually sort the default and optional packages in the Preboot Configuration settings using the following hierarchy.

1. Dependency Mapping Summary

Based on Microsoft documentation, use this table to understand which packages must be higher in the list than others:

Optional Component	Required Dependencies (Must be listed above)
WinPE-WMI	None (This is the Base Foundation).
WinPE-NetFX	WinPE-WMI
WinPE-Scripting	WinPE-WMI
WinPE-HTA / ADO	WinPE-Scripting
WinPE-PowerShell	WinPE-WMI > WinPE-NetFX > WinPE-Scripting
WinPE-DismCmdlets	WinPE-WMI > WinPE-NetFX > WinPE-Scripting > WinPE-PowerShell
WinPE-StorageWMI	WinPE-WMI > WinPE-NetFX > WinPE-Scripting > WinPE-PowerShell
WinPE-SecureStartup	WinPE-WMI
WinPE-PlatformID	WinPE-WMI > WinPE-SecureStartup
WinPE-SecureBootCmdlets	WinPE-WMI > WinPE-NetFX > WinPE-Scripting > WinPE-PowerShell

2. Recommended Package Order

For a configuration including common components like PowerShell, HTA, and ADO, use the following sequence:

1. WinPE-WMI (Always at the top)

2. WinPE-NetFX

3. WinPE-Scripting

4. WinPE-HTA

5. WinPE-ADO

6. WinPE-EnhancedStorage
   

7. WinPE-PowerShell

8. WinPE-DismCmdlets (and other high-level cmdlets)

3. Step-by-Step Configuration

1. In the Symantec Management Console, navigate to:

   • Settings > All Settings > Deployment > Preboot Configurations

2. Select the specific Preboot Configuration you wish to modify.

3. Click on the Preboot Environment Settings tab. 

4. In the Optional Packages section, select a package and use the Up/Down arrows to move it into the correct position based on the hierarchy above.
   
   

5. Click Apply.

6. Click Recreate (or Rebuild) to regenerate the Preboot environment.
   
   

4. Automation Folder Validation

If you use Automation Folders, simply rebuilding the environment in the console is not enough:

1. Wait for the Rebuild task to complete on the Site Server.

2. Uninstall the existing Automation Folder from the client machines.

3. Reinstall the newly generated Automation Folder package to the clients.

Additional Information

https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-add-packages--optional-components-reference?view=windows-11

DS 8.7 - Preboot Configurations - Update failed. Exit code 27

Add WinPE optional packages so that Powershell, DISM and SecureBoot can be used, and error BDC_ERR_WIM_INSERT_PACKAGE

Adding Powershell package to WinPE using Preboot Configuration settings

Add a WinPE package to an Automation Folder configuration

Installing WinPE11 ADK for use in Deployment Solution 8.x