Here is an example, your folder structure may be different to mine.

found this another post, but remember its not supported. Some of the forum members are using it close to two years already without issues, except for one point when using rapideploy in multicast. The account used had read/write on the altiris express share and should only have read so the rdeploy.exe is not locked.

copy any win7 drivers you will need in the winpe boot file to d:\driver

DISM /image:d:\mount /add-driver /driver:d:\driver /recurse

DISM /unmount-wim /mountdir:d:\mount /commit

copy the following cab files (winpe-wmi.cab, winpe-scripting.cab, winpe-hta.cab) from C:\Program Files\Windows AIK\Tools\PETools\x86\winpe_fps -> D:\package

copy C:\Program Files\Windows AIK\Tools\PETools\x86\winpe.wim -> D:\Program Files\Altiris\express\Deployment Server\WAIK\Tool\PETools\winpe.wim

Install WAIK 3.0 and update with WAIKS 3.1.

DSIM /mount-wim /wimfile:D:\Program Files\Altiris\express\Deployment Server\WAIK\Tool\PETools\winpe.wim /index:1 /mountdir:d:\mount

DISM /image:d:\mount /add-package /packagepath:d:\package

Now use PXE config manager to create a new winpe boot image. It will utilise the new winpe3.1 winpe.wim file and create the "winpe2.1" image from that. Once all is finshed, as long as pxe config manager shows that the boot file is winpe2.1 then all should be good. If pxe config manager only shows the boot file as "winpe", then it wont show up as a valid selectable winpe boot image. The only way around it I have found is to reinstall DS. This has been tested on DS 6.9 SP4 & SP5.