Thanks for posting to the Community.
Are you still experiencing this issue? Please share any information you have here.
A bit more description is usually a good idea.
- The SMBIOS driver not starting may be a thing, but I don't think it's your actual problem.
- If you check your log, you'll notice that we're attempting (and failing) 40 times to communicate with the provisioning www-service. You can see that from entries like the following block of lines:
2017-05-09 22:56:44(1820-1824) ldProvision:Retry count 36 of 40
2017-05-09 22:56:47(1820-1824) ldProvision:Start TryallWebService Attempt:0.
2017-05-09 22:56:47(1820-1824) ldProvision:End TryallWebService Attempt:0. ExitCode:0
2017-05-09 22:56:47(1820-1824) ldProvision:Computer ID: 5404
... but since we're not able to talk to the www-service, provisioning gives up (it gets instructions on "what to do" from the www-service).
Check on the Core-side (IIS logs) whether the client is even registered in the logs (based on IP). My expectation is that the Core never sees anything from the client, so you're likely to have a DNS problem to contend with as far as Win PE is concerned (and you may want to edit the image to include HOSTS entries to combat that).
... the SMBIOS failing to start isn't really crucial to get Provisioning to work. The failure of talking to the Core (and thus, not being able to pick up the "do these things" lists) is your actual problem.
This should be a conversation / call with support, normally.
<Also moving this thread into the OS Provisioning section...>