Imaging Latitude 5430 troubles
Has anyone successfully imaged a Latitude 5430? They are really new, and I have gone through all the hoops, including working with support and just not getting anywhere. It is getting stuck at "set engine run key", but the device has a Window screen saying "let's connect to a network" and it's ditched the imaging process entirely. Notably the step that applies drivers goes by really fast, like it is not applying any at all. Closer inspection showed an error on this step that said it could not find the drivers at the expected location, but I have read about this being a false error with other models and it is giving it the pass so I am not sure...
Steps I have tried so far include:
Fighting with BIOS settings
injecting new model drivers directly into feed
etc etc etc
If anyone has had success with this model, share the love! Or if you want to give me another path to chase let me know. I am pretty knowledgeable within Kace systems and will try anything.
So it turns out that the original drivers that were for this model were changed to Latitude E5430-vPro (originally had name "latitude latitude 5340") and new ones added with slightly different, but better, name (just "latitude 5430"), requiring it to be installed into the driver share again (and that other one removed). There are also other versions of the same model in there now... I am glad they got it sorted as the step for copy drivers is working as expected now!
The Device will not send the confirmation flag to get pass the "Set Engine Run Key", until it hits the Windows Desktop\Login Screen.
It is unable to do so, because the Windows Setup is not getting there: "but the device has a Window screen saying "let's connect to a network"".
That happens when the Answer File (unattend.xml), is not answering the question in regards what to do with Networking, during the Setup.
I would recommend taking a look at the answer file, or attempt to deploy an older version of Windows 10 to test, like build 2004.
To discard this being a drivers injection related issue, from the KBE, perform Step #3, and pay attention to the screen, if the injection is happening there, then it is happening during the Deployment: