LDMS 9.5
PXE boot fails to resolve core name when using provisioning template to reboot into WinPE (vboot)
ISSUE:
Schedule provisioning template with first action to reboot machine to WinPE (vboot) and start task.
WinPE loads and fails with error Could not resolve core server name.
WinPE Command:
X:\Windows\system32\wpeinit
X:\Windows\system32\wpeinit /unattend=x:\ldclient\setpeoptions.xml
X:\Windows\system32>\cba8\LDDrvLoad.exe
[LDDrvLoad]: This is not a valid folder name, cFileName = .
[LDDrvLoad]: This is not a valid folder name, cFileName = ..
[LDDrvLoad]: Driver Folder List is empty
[LDDrvLoad]: Fail to get Driver Inf File List
The command completed successfully.
X:\Windows\system32\reg import all.reg
The operation completed successfully.
The operation completed successfully.
.......
VBoot artition not found on disk
The operation completed successfully.
IP address xx.xx.xx.xx 127.0.0.127
resolving core server name (corename)......
Could not resolve core server name.
resolving core server name (corename)......
Could not resolve core server name.
Solution:
Manual F12 PXE boot uses the boot.wim from the PXE Representative. When you PXE boot using vboot, the PXE Rep will call the bootmedia.wim file from the core under Managementsuite\landesk\vboot. If the core name cannot be resolved you need to make sure both the boot.wim and bootmedia.wim on the Core have the FDQN on the corename.txt file and all.reg file.(Refer to Error: "resolving core server name (%mycoreserver%)" when booting into WinPE). If you make changes on the boot.wim, redeploy the PXE rep.
NOTE: Modifying the bootmedia.wim does not require redeployment to the PXE Rep.