Hi
This task sequence works on some devices, but on some physical devices it bombs out right after the WIM is applied and Windows goes into OOBE setup phase.
So whilst there are issues with the Unattend.xml we are using (on this new 1709 TS) - This does not break the task sequence on other models of device, or Hyper-V. On devices failing to run this TS, they are not joined to the domain.
I would head straight to the NetSetup.log for reasons why the domain join failed, but it seems that log file is binary now?? Does anyone else have experience of NetSetup.log on Windows 10? I tried extracting the .etl trace file but its garbage, with no log entries, so of no use.
There are also no CCM logs so no help there.
There are a number of things I can guess at when might be the cause, however I would rather see some evidence of the failing to point me in the correct direction but i dont see any information locally that can achieve that.
Any ideas?