I made an errand succession utilizing the "Autopilot for Existing
Devices" wizard utilizing the orders here:I have numerous autopilot
provisioning profiles and have traded the JSON straightforwardly to my
MECM organization share utilizing this order:...
As per the article that ishboo3002 linked to, removing the "prepare for
capture" step, which syprep /generalizes the machine and removes the
JSON file in doing that, and replacing with with a command step "sysprep
/oobe /reboot, took care of my issue...