How To:
This is quick guide on how to automatically copy the WinPE Provisioning .LOG and .TXT files that are used when troubleshooting action handlers in WinPE provisioning. The logs that are generated during WinPE are removed once the device reboots and moves onto the "System Configuration" section of the provisioning template. This configuration will make it so you don't have to babysit the provisioning task, add a wait before CTOS, remote in, and manually copy/review the log files when troubleshooting action handlers. This will allow you to "set it and forget it" and review the logs when it's convenient for you.
The configuration outlined below is best for a single device provisioning test since the logs will be overwritten when targeting multiple devices. If you are troubleshooting an action failure, make sure the action that is failing doesn't stop processing the rest of the template or else the log files will not be copied.
Step by Step:
1. Create a copy of the template you are troubleshooting.
2. Add the following 4 actions after the action that you are trying to troubleshoot, or add them BEFORE the "Configure Target OS" action in the Post-OS Installation step (If you are using a template that uses CTOS).
I used the LDLogon Share with a custom folder I created for this configuration. Change these settings to be applicable to your environment and verify that the share settings and account are configured properly to access that share.
For the "Map Drive" action, I opted to use the L: Drive. Verify the drive you use in your configuration is not already being used in the template.
3. Once those actions are added to the template, run the template and allow it to complete the copy file actions.
4. Verify that the logs were copied over to the share that you configured in the "Map Drive" section. If everything was configured correctly, you should see your logs and .TXT files like so:
Attached below is the template that I used when creating this document. I used public variables for the user account/password and the CoreName variable. If you would like to use those variables as well, make sure you configure those for your environment.