Well this helped me to recall something...
There was an issue being addressed by Microsoft regarding to SCCM deployment with Win10 image. The issue seems to be SCCM mistakely blocked the image with OEM product key. This is an industry problem not only impact HP product.
"On non-IoT versions of Windows, Setupcomplete.cmd is blocked when an OEM product key is used in order to provide customers a good out of box experience on new PCs. This block is not intended for IoT versions of Windows but is currently there due to a confirmed bug. Microsoft initially was planning to fix this bug only in Redstone-2"
Microsoft has provided a workaround and passed the first verification within HP - sorry I can't share that much details here.
The latest update I got is:
Microsoft is currently working on a blog which will document the workaround publically.
Maybe the blog with the workaround will fix your issue.
