1 of 1 people found this helpful
One thing you can check real quick is to make sure the WinPE images are on your PXE rep.
Look under C:\Program Files\LANDesk\PXE\System\Images and make sure there is a peboot.img and prov_winpe.img
Also on your core server under configure services and the OSD Validation button under the General tab, make sure you are validated for WinPE
EDIT: Request to have thread changed to not answered yet
I've gotten further than before following the article below but I'm still having problems with WinPE Menu. I get the errors listed above.
If I use Linux PE Menu I can see the two sets of scripts that I have scheduled.
I can load the DOS PXE Menu and the client sits and waits for "Waiting for command..."
The information below got me to the point I'm at now above.
I think I actually found the answer to my problem and am testing that from these documents here.
The directions on this site seem to show that we weren't following all of the steps needed. I'll post with a follow up shortly.
Message was edited by: n0manarmy
I can't even get the Linux PE imaging to work. I can select it from my PXE menu and it'll boot up but there's a blink of text and then Linux PE proceeds to reboot. Is it possible to slow down or pause the process to see what the actual error is?
Once you are booted up, you could try to see if it is in dmesg but I have never tried.
Press Alt-f2 (maybe it is Alt-f4 or something) and you get a command prompt.
Then type this:
Anyway, you can at least check if there is a Network card loaded with this command:
Basically once you are at a command prompt, hopefully you are good to go troubleshooting on your own.
One of the problems I found with both the Linux and the DOS tools was that I didn't have my permissions set right on the folder that contained imaging tools and where we were placing the images. I ended up giving "everyone" full control, both security and permissions, and I was finally able to launch both the Linux and the DOS tools to capture an image off a machine. I've yet to try the Win PE through this method, I'll update tomorrow.
How did you go with the WinPE area of this? im still having issues. Just keen to see if you got it working for you?
Usually all you have to do is install the PXE Rep and PXE booting to WinPE just works with no other configuration. You may have to add drivers to WinPE but that is much later in the process.
1. Remove all PXE Representatives
2. See if you can PXE Boot.
- If you can, there is some other PXE device in the network
- If you cannot then
3. Install the PXE Rep on a clean device (so you don't have to worry about problems with VPN clients or existing TFTP servers)
It was possibly one of three factors that got this issue working for me. At the time that it started working for us I had done a combination of installing service pack 5, making another machine our PXE rep, and our WinPE license had failed so I reinstalled it.
I had initially had Server A as our PXE rep and that wasn't working so I rebuilt an older box (server B) to make it our PXE rep. LanDesk reported that it succeeded in becoming a PXE rep but it still wasn't working. In frustration, about the time that we were installing SP5 and reinstalling the license for WinPE, I pushed the PXE rep back to server A and everything started working with WinPE.
Now we just have to get it working with only grabbing one partition instead of both the Dell utility parition and the normal partition.
If you only want to capture one partition (and not the Dell partition), then you may want to boot to WinPE and manually capture the image. Since you are only capturing once, it's not that big of a hassle, and the imagew.exe wizard is easy.
Once you're in WinPE, just map a drive to the location where imagew.exe is located and the location where you want to store your image. Make sure you map the drives with the appropriate credentials. Then simply run imagew.exe manually. You can select just the partition you want, ignoring the other.
When you create an OS Deployment script, at the end you see the command line and it calls Backall.bat. Backall.bat automatically captured all partitions on the drive.
Instead you want to input your own custom ImageW.exe script to only capture the desired partition.