This article walks you through the recommended process to deploy Windows 10 to Surface devices with Microsoft deployment technologies.
The process described in this article yields a complete Windows 10 environment including updated firmware and drivers for your Surface device along with applications like Microsoft Office 365 and the Surface app.
To provide network boot for UEFI devices like Surface with WDS, you will need Windows Server 2008 R2 or later.
Note To evaluate the deployment process for Surface devices or to test the deployment process described in this article with the upcoming release of Windows Server 2016, you can download evaluation and preview versions from the Tech Net Evaluation Center.
You can also find these files in the disk image (ISO file) for Windows 10, which you can download from the Volume Licensing Service Center (VLSC).
In this scenario you have no choice but to begin again the manual process of creating your image.
If in this same scenario you had automated the reference image creation process, you could repair the conflict by simply editing a step in the task sequence and then re-running the task sequence.
Although MDT is the tool you will interact with most during the deployment process, the deployment tools found in the Windows ADK perform most of the deployment tasks during the deployment process.
The resources for deployment are held within the MDT deployment share, but it is the collection of tools included in Windows ADK that access the image files, stage drivers and Windows updates, run the deployment experience, provide instructions to Windows Setup, and back up and restore user data.
You can read about how to manage and automate the upgrade process of Surface devices to Windows 10 at Upgrade Surface devices to Windows 10 with MDT.