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.

The goal of the deployment process presented in this article is automation.

The deployment process described in this article leverages a number of Microsoft deployment tools and technologies.

Some of these tools and technologies are included in Windows client and Windows Server, such as Hyper-V and Windows Deployment Services (WDS), while others are available as free downloads from the Microsoft Download Center.

You can also follow the guidance provided in this article to integrate deployment to Surface devices into existing deployment strategies.

By following the procedures in this article, you can create an up-to-date reference image and deploy this image to your Surface devices, a process known as .

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.

An alternative to the reimaging process is an upgrade process.

The upgrade process is non-destructive and instead of erasing the existing environment on your Surface device, it allows you to install Windows 10 while retaining your user data, applications, and settings.

Each of these is discussed throughout this article. Along with these task sequences and the many scripts and tools that MDT provides, the resources for a Windows deployment (driver files, application installation files, and image files) are stored in a network share known as the .

You can download and find out more about MDT at Microsoft Deployment Toolkit.

Although MDT can be installed on a Windows client, to take full advantage of Windows Deployment Services’ ability to network boot, a full Windows Server environment is recommended.