Problem:

OS Deployment template actions are failing.  To determine the cause of the failures it's helpful to take a look at the log files, but WinPE is loaded onto a RAM drive and the logs disappear when the device reboots.  If you log a support case, LANDesk will ask you for these logs.

Solution:

When you start a provisioning template, the computer boots into WinPE and will stay in WinPE until you get to the Configure Target OS action.  After CTOS, the computer reboots and all logs and files generated in WinPE are lost.  We need to pause the process prior to the CTOS action.  Edit your template and insert a wait action just prior to CTOS.  Specify a wait time in seconds.  Usually 600 seconds (5 minutes) is sufficient.  In LDMS 9.6+, you can continue from the wait action early if you desire.  In LDMS 9.5 you will need to wait out the entire timer, so choose your duration accordingly.

Run your template again, and view the computer you are provisioning.  If it's a remote computer you can use LANDesk Remote Control to view the WinPE environment.  This document shows you how:

Use LANDesk remote control to view a computer in WinPE provisioning

Next we will open a console window to locate and copy the logs to a remote computer:

1. Click the green icon on the bottom left and select New Console
2. Type cd\
3. Type cd ldprovision
4. Type dir *.log to view the log files in this location.  This is the main log location for provisioning within WinPE
5. If you would like to view these logs within WinPE, type "notepad nameoflog.log"
6. We need to map a network drive to copy the files to a shared folder on a remote computer.  Do so using the NET USE command:
       Use the Net Use command to map or disconnect a drive
7. Copy the files to the drive letter you just mapped.  We will assume you mapped the E drive to your remote computer.  The command is:
   xcopy *.log E:
8. You can now access these logs from the remote computer which you mapped as the E: drive.  If you are working with LANDesk support, email these logs to your support representative or attach them to your case.

Troubleshooting OS Provisioning using the log files

Each OS Provisioning template action has a log file.  In addition, the overall template process has a log, called "ldprovision.log".  This should be your first stop.  Open the log file and scroll through.  You are looking for a section of the log similar to this:

     2015-04-17 14:35:38(1404-1408) ldProvision_x64:********************************** Begin processing actions **********************************

This indicates the beginning of the template actions.  You will see the start of each action called out in the log similar to this:

     2015-04-17 14:35:38(1404-1408) ldProvision_x64:*********  Begin an action - Map_toPreferred

You will also see that each action has it's own action handler.  You will see the ldprovision.exe action handler calling additional handlers, similar to this:

     2015-04-17 14:35:39(1404-1408) ldProvision_x64:Launching action handler [MaptoPreferredHandler_x64.exe] with parameters ["]

     2015-04-17 14:35:39(1404-1408) ldProvision_x64:handler launched.

At the end of each action you will see an indication of success or failure, and then the next action starts.  Keep in mind that some actions show failed but do not affect the success of the entire template.  For example the vboot action, or in some cases HII may show failed but the template can continue and ultimately succeed.  Locate the failed action that you are troubleshooting.  Each action handler has it's own log file, so next pull up the log for the specific action handler that failed.  If the name of the handler is "myactionhandler.exe" the log file will be "myactionhandler.log".   If you have difficulty identifying the failed action, press CTR+F to open the Find box, and search for "failed".

The log file specific to the action which failed will give you greater detail into the cause of the failure.  You will also see a failure error code.  Sometimes these codes can be very generic, other times they are quite specific.  Search the LANDesk community for your failure reason and error codes and you should find discussions and documents that help you resolve the failure.  If you are not able to determine the cause of the failure, log a support case with LANDesk and provide the log files to your support rep.