Troubleshooting Provisioning
Get a copy of any an all templates involved. These can be exported. If an unattend or sysprep file is used, obtain a copy of that as well.
Right click on the failed device and click View Provisioning History. This will display what action failed. First verify that this is the proper action at the proper place and if so, troubleshoot only that action until it is successful.
Run ldprovision.exe in debug mode or with a greater verbosity.
ldprovision.exe -c [Core Server] -V 255*
NOTE: To manually run ldprovision.exe from WinPE, open a CMD window and change directory to x:\ldprovision. Then run the command listed above. This will increase the verbosity of the ldprovision.log file.
The provisioning logs are located in two locations. On the core server, the log is at \coreserver\ldlogon\provisioning.
On the client, in the WinPE environment the provisioning log is located in the x:\ldprovision directory.
Verify that the amount of memory is 100 MB greater than the size of the PXE image. The PXE image is about 160 MB so about 260 MB is needed. So 256 MB is not enough.
Provisioning does not automatically reboot to continue to another WinPE task, a Reboot action must be created. Verify that this action exists and is in the correct location.
For PXE issues, check that the PXE Representative has the prov_winpe.img file in the c:\program files\Landesk\PXE\System\images directory.
On the PXE Representative the boot files for the provisioning image must be present. The files are located at:
C:\Program Files\LANDesk\PXE\System\images\x86pc\provwin
The files needed to boot to the WinPE provisioning image are:
startrom.0
ntldr
ntdetect.com
winnt.sif