It's more than just the boot.wim file...
It might be for example that there is fragmentation on your disk which interferes.
Try to do the same VBOOT with an OSD script. All the VBOOT commands are in the first part of the script, before BEGINWINPE=TRUE, so you can schedule the script on your working Win7 device and you will have a step-by-step result of the VBOOT preparation in the logfiles.
This is an known issue with LANDesk 9.5 with the Elitepad patch which upgrades to Winpe4. It has been logged and I believe they indicated it will be fixed in SP1. In my testing it only effects the 7000 series of HP where it was discovered through many hours of beating my head against a wall. I would log a ticket with support. Reference Ticket 00632251 it is an issue with bootmgr. You can test by using a windows 8 copy of bootmgr. I believe this is how they are planning on fixing this one.
zman: Oh my... unfortunately it's weekend for now, but I'll check this out at monday, as soon as I'm at the office!
Frank: thanks for your comment, I tried the OSD but the script failed somewhere in the middle In addition, McAfee seemed to block the ldprovision.exe process, so now I'm not sure why the script stopped. Hopefully you can guide me in the right direction wednesday when you're at our site
I tried some things, but it dind't work out well.
I assume I have to modify the BootMedia.wim file, because that is the file that's copied to the C-drive when deploying a OSD task to a PC running in OS-state.
Can you clarify what file(s) exactly should be replaced in the LANDesk WIM?
This is definitely fixed for SP1.
Just wanted to make everyone aware of that. As ZMan pointed out this seems to be affecting a very small number of hardware platforms at this time. In fact, when we shipped we hadn't found any hardware that didn't work. VMware had some problems, but we chalked that up to a VMware thing (because "real" hardware didn't fail) and opened a ticket with them with inquiries.
At any rate, we've got a solution in place that will ship with SP1 and fix this issue. I'm sorry for any difficulties in the meantime!
As SP1 is still a month away, is there a workaround we can test in the meantime? We are starting a large migration soon and wouldn't like to run around to do a PXE boot everywhere
1 of 1 people found this helpful
Never mind, found it
Open the boot.img file and replace the bootmgr file within. Replace the BCD file in the Vboot folder. Both should be the Windows8 versions (and the files replaced are the ones without extention!)
PXE doesn't use these files, so no possible conflict there.
I tried replacing the bootmgr in the boot.img and the bcd file in vboot and the boot ISO still will not boot in a VM. Even replaced the bootmgr file in the vboot folder as well. (of course after making backups of the files).
Any other suggestions or functional workarounds?
i have a similar problem in our LANDesk 9.5.
If I boot with F12 and PXE the provisioning works fine. But if I create a boot Stick or a BootCD I cannot run a provsioning task. The Problem is, the computer boots from the stick/bootCD loads the driver, and the last message is "The LANDesk Remote Control Service service was ...." and the all windows are closed ?!?!
any Ideas ?
I have the exact same behaviour here (But if I create a boot Stick or a BootCD I cannot run a provsioning task. The Problem is, the computer boots from the stick/bootCD loads the driver, and the last message is "The LANDesk Remote Control Service service was ...." and the all windows are closed).
What needs to be done to get the USB drives working again?
Go to C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot\ on the Core Server and extract the WinPE20ProvBootOpt.reg from C:\Windows\System32 from BootMedia.wim. You need to inject the reg file into your boot.wim (also in C:\Windows\System32) on the USB drive. Works perfect for me.
I extracted the reg file using 7-Zip and changed the boot.wim with ImageX.