Rebuild WinPE Images With IVANTI EPM

Publié par david le

Start by backing up (or renaming) the WinPE images:

  • C:\Program Files\LANDesk\ManagementSuite\LANDesk\vboot\boot_x64.wim
  • C:\Program Files\LANDesk\ManagementSuite\LANDesk\vboot\boot.wim

You may replace the boot images with your own, but this operation is not recommended.

  • C:\Program Files\LANDesk\ManagementSuite\LANDesk\vboot\clean\boot_x64.wim
  • C:\Program Files\LANDesk\ManagementSuite\LANDesk\vboot\clean\boot.wim

Next, copy the images from C:\Program Files\LANDesk\ManagementSuite\LANDesk\vboot\clean to C:\Program Files\LANDesk\ManagementSuite\LANDesk\vboot.

Run the utility C:\Program Files\LANDesk\ManagementSuite\OSD.Upgrade.exe (as an administrator).

Screenshot of the OSD.Upgrade.exe utility in action

Ref: Ivanti EPM: How to Create/Rebuild the WinPE Boot.wims

Final step, add drivers and customizations to your WinPE: EPM: Management of WinPE

Catégories : EPM
Étiquettes :

Articles similaires

EPM

Framework Issue with EPM

This guide outlines a procedure for addressing Framework errors in LANDESK logs. It includes a specific command to run on the LANDESK server and emphasizes validating the procedure with LANDESK support prior to implementation. The necessary tool is linked for easy access.

EPM

Issue with deleting a EPM task

This guide details how to resolve issues with tasks linked to non-existent packages using SQL Management Suite. It includes steps for identifying task IDs, validating queries, updating the database, and deleting tasks through the LANDESK console. A database backup and contacting support are mandatory.

EPM

Uninstall EPM agent

This documentation provides guidance on using UninstallWinClient.exe, available on the ldmain share of the EPM core server. It details options like /REBOOT, /UI, and /FORCECLEAN, and warns against using certain options on core servers.