I have run into an issue using the inbuilt 'Boot to Managed WinPE' action on remote sites with low bandwidth connections as this tries to download the boot.wim from the core sevrer. The download takes so long that this actions times out and the task fails.
I have grabbed the old vboot template from http://community.landesk.com/support/docs/DOC-9980 so I change the download boot.wim step to grab this from the local preferred server which works but when the client reboots to WinPE it is coming up with the OSD virtual X: drive rather than provisioning so my template doesnt continue.
I know in PXE you need to load the correct statrom.0 file to get WinPE into provisioning mode but how can you force this for a vboot action? Does the boot.img have anything to do with this?
Attached is a picture of my template which maps drives based on the preferredserver.dat then does the vboot steps including downloading the boot.wim locally.
vboot.png 23.7 K