Hi gesloan,
Looking at the ldprovision.log it shows the failure came when it called captureimagehandler.log:
2015-03-09 15:55:15(1864-1868) ldProvision:Launching action handler [CaptureImageHandler.exe] with parameters ["]
No user logged in, change CurrentTokenWithInteraction to CurrentToken
2015-03-09 15:55:59(1864-1868) ldProvision:handler launched.
2015-03-09 15:55:59(1864-1868) ldProvision:Reporting action status: 5 to core
The smbios stuff you're seeing doesn't look to be a problem, so I wouldn't worry too much about that specifically.
The most common thing that I see cause this is that ldprovision.exe calls CaptureImageHandler.exe which in turn calls MaptoPreferredHandler.log and there ends up being some kind of authentication error.
I would suggest tracing the order of handlers to find which handler is actually failing.
Related documents:
Video - How to Troubleshoot Provisioning Template Actions
How to troubleshoot Provisioning Template Actions
If still unsure about the failure, post all of the *.log files from X:\ldprovision and we can get a better idea of what's going on.