It sounds like you are booting into the Proviioning PE. Try this, once under WinPE menu, open a command prompt and type pxementstart.cmd. What happens?
Make sure you are selecting WinPE menu, not WinPE Provisioning.
The command wasn't found. Is the normal path X:\Windows\System32 ?
Not sure of the exact path but I believe it is in X:\LDClient
I didn't find that command in that path but I did find pxemenustart.cmd which I started. The results from that were
"ERROR: Donwloading http:///landesk/files/dosmenu.cfg (11)" That repeated several times until quiting with the final message "Failed to get menu. Verify any network drivers, DHCP settings, and name resolution for ." I verified that I can ping the gateway and LANDesk server and name resolution does work. It seems to me that the client doesn't know the hostname of the server. Where should the client get the hostname from?
I'm a noob at this and didn't setup the server so I'm probably asking obvious questions.
If the provisioning template is coming up and you are certain you've selected one of the non-provisioning actions then I would say you have probably overwritten your boot.wim file with your bootMedia.wim file. Difference is that bootMedia.wim is more or less hardcoded to run provisioning. To find out, PXE boot into WinPE, open a command prompt, browse to X:\Windows\System32 and run dir *.reg. If you have all.reg and nothing else you are in boot.wim. If you have all.reg and WinPE20ProvBootOpt.reg (or something equally horrifically named) then you are in bootMedia.wim and we are essentially overwriting your boot option with instructions to just run provisioning.
That is the only reason I can think that makes sense. Let me know if you find that .reg file when in WinPE.
You are correct, I do have both all.reg and WinPE20ProvBootOpt.reg. Is there a way to recreate the boot.wim file or some other way to fix this?
Found other boot.wim file in the update package dir. I'm going to try replacing the current one, reinject the drivers and try again.
Sorry about the delay. If you try what you are referring to you will end up with a WinPE image that doesn't have your certificate or corename, etc. put into it.
Do you know how to mount .wim files? There's an article that talks about how to use ImageX to do it, or you can mount the Wim using DISM. DISM is already there if your core is Server 2k8 R2.
To use DISM follow these instructions:
1 - Copy boot.wim as bootMedia.wim inside your \ldmain\landesk\vboot directory. If it's already there, don't worry too much about it.
2 - Make a temporary directory to mount the boot.wim image. I use C:\winpetemp because I lack imagination. [-8
3 - Open a command prompt and browse to the \ldmain\landesk\vboot directory.
4 - Run the command dism.exe /mount-wim /wimfile:boot.wim /index:1 /mountdir:c:\winpetemp
Note: Obviously replace the mountdir location with whatever folder you created.
5 - Go to the temp folder you created and you should see your WinPE file/folder structure. Go to Windows\System32 and delete the WinPE20ProvBootOpt.reg file
6 - At the command prompt run the command dism.exe /unmount-wim /mountdir:c:\winptemp /commit
Note: See note on step 4
Note 2: If you make a mistake and want to start over run the unmount-wim command but with a /discard option instead of /commit
7 - Make sure the boot.wim file is replicated to all your PXE reps (or redeploy PXE reps)
If you're familiar with mounting wims this can be summed up as:
I tried to break it out into smaller steps in case anyone who isn't super familiar with wims can follow it.
Let me know if that helps.
I did what I mentioned before you replied, unfortunately with the outcome you mentioned. It doesn't know the name of the core. I'll redo it with your input and update with results.
Thanks for your help.
I mounted the boot.wim that I copied in from the update package. It didn't have the WinPE20ProvBootOpt.reg file, only the ALL.reg file was there. So if I commit like you mentioned without changing anything, will the boot.wim file have the core name after unmounting?
1 of 1 people found this helpful
Delete that boot.wim. Make a copy of bootMedia.wim, name it boot.wim and follow the steps above. Should work for you.
That worked!!! Thank you!!
Glad to hear that worked for you!
I am having the same issue, but I am not able to find DISM.exe under vboot folder.We have LANDesk SP2.