Introduction
Provisioning is one of the many features of LANDesk Management Suite. Often due to an incorrect configuration or other different type of issues, provisioning fails.
If provisioning uses WinPE to deploy actions defined within the previously scheduled template and it fails before the OS is deployed, the user may decide to look at the provisioning logs in WinPe to identify the problem which causes the failure.
Environment
LANDesk Management Suite (Provisioning through WinPE)
Review Date
30/07/2015
Assumptions
This document will not explain how to configure and boot into WinPE. It is assumed that the user has already scheduled a template and that the template failed before booting in the OS.
It is also assumed that the provisioning template is configured in order to keep the provisioning folder during the deployment.
How to:
To collect provisioning logs in WinPE in order to troubleshoot an issue. If the failure occurs after booting into the Operating System, the logs will be located into the root location of the selected hard drive eg: C:\ldprovision .
Step by step
- When the failure occurs, please click on the green button located at the bottom left hand side of the screen.
- Select the option “New Console”
3. Afterward, please write in the console the following command: “cd /ldprovision”
4. In this folder will be presents all the logs files generated during the provisioning process.
For e.g. If you need to take vision of the ldprovision.log, please use the command:“/ldprovision/ldprovision.log”
If support asked you to provide the provisioning logs please collect of the content of the ldprovision folder.
Note: If the system has already booted into the Operating System, the logs will be located into the root folder of the drive. E.g. C:\ldprovision
For more information about troubleshooting provisioning, please refer to this page : https://community.landesk.com/support/docs/DOC-23470#jive_content_id_Troubleshooting_this_Component