Cookies, which are files created by websites youve visited, and your browsers cache, which helps pages load faster, make it easier for you to browse the web. Search the worlds information, including webpages, images, videos and more. Google has many special features to help you find exactly what youre looking for. Deploy Windows 1. Surface devices with Microsoft Deployment Toolkit SurfaceApplies to. Surface Studio. Surface Pro 4. Surface Book. Surface 3. Windows 1. 0This article walks you through the recommended process to deploy Windows 1. Surface devices with Microsoft deployment technologies. The process described in this article yields a complete Windows 1. Surface device along with applications like Microsoft Office 3. Surface app. When the process is complete, the Surface device will be ready for use by the end user. You can customize this process to include your own applications and configuration to meet the needs of your organization. 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 reimaging. Reimaging will erase and overwrite the existing environment on your Surface devices. This process allows you to rapidly configure your Surface devices with identical environments that can be configured to precisely fit your organizations requirements. 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 1. You can read about how to manage and automate the upgrade process of Surface devices to Windows 1. Upgrade Surface devices to Windows 1. TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/74/72/metablogapi/8664.Capture_thumb_44B45CFE.png' alt='How To Update Kms Client Information Template' title='How To Update Kms Client Information Template' />MDT. The goal of the deployment process presented in this article is automation. By leveraging the many technologies and tools available from Microsoft, you can create a process that requires only a single touch on the devices being deployed. OVCX5vK0CY/Vbey-DtrBqI/AAAAAAAAG84/9JmVzMWkOZ4/image_thumb%25255B3%25255D.png?imgmax=800' alt='How To Update Kms Client Information Template' title='How To Update Kms Client Information Template' />The automation can load the deployment environment format the device prepare an updated Windows image with the drivers required for the device apply that image to the device configure the Windows environment with licensing, membership in a domain, and user accounts install applications apply any Windows updates that were not included in the reference image and log out. By automating each aspect of the deployment process, you not only greatly decrease the effort involved, but you create a process that can be easily repeated and where human error becomes less of a factor. Take for example a scenario where you create a reference image for the device manually, but you accidentally install conflicting applications and cause the image to become unstable. 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. The deployment process described in this article leverages a number of Microsoft deployment tools and technologies. Office 365 Germany is a differentiated option from the Office 365 services already available across Europe. It helps address the needs of the most. 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. The Microsoft Deployment Toolkit MDT is the primary component of a Windows deployment. It serves as a unified interface for most of the Microsoft deployment tools and technologies, such as the Windows Assessment and Deployment Kit Windows ADK, Windows System Image Manager Windows SIM, Deployment Image Servicing and Management DISM, User State Migration Tool USMT, and many other tools and technologies. Each of these is discussed throughout this article. Backup Software Lotus Domino Server Administration there. The unified interface, called the Deployment Workbench, facilitates automation of the deployment process through a series of stored deployment procedures, known as a task sequence. 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 deployment share. You can download and find out more about MDT at Microsoft Deployment Toolkit. Windows Assessment and Deployment Kit. 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 download and find out more about the Windows ADK at Download the Windows ADK. Before you can perform a deployment with MDT, you must first supply a set of operating system installation files and an operating system image. These files and image can be found on the physical installation media DVD for Windows 1. You can also find these files in the disk image ISO file for Windows 1. Volume Licensing Service Center VLSC. Features Manual Changelog FAQ Support Contact Resources About Deutsch Frequently Asked Questions Contents NonYaTQA issues. These have nothing to do with YaTQA at. Note. The installation media generated from the Get Windows 1. VLSC, in that it contains an image file in Electronic Software Download ESD format rather than in the Windows Imaging WIM format. Installation media with an image file in WIM format is required for use with MDT. Installation media from the Get Windows 1. Windows deployment with MDT. Windows Server. 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. To provide network boot for UEFI devices like Surface with WDS, you will need Windows Server 2. 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 2. Tech. Net Evaluation Center. Windows Deployment Services. Windows Deployment Services WDS is leveraged to facilitate network boot capabilities provided by the Preboot Execution Environment PXE server. The boot media generated by MDT is loaded onto the Surface device simply by pressing Enter at the prompt when the device attempts to boot from the attached network adapter or Surface Dock. Hyper V virtualization platform. The process of creating a reference image should always be performed in a virtual environment. When you use a virtual machine as the platform to build your reference image, you eliminate the need for installation of additional drivers. The drivers for a Hyper V virtual machine are included by default in the factory Windows 1. When you avoid the installation of additional drivers especially complex drivers that include application components like control panel applications you ensure that the image created by your reference image process will be as universally compatible as possible. Note. A Generation 1 virtual machine is recommended for the preparation of a reference image in a Hyper V virtual environment. Because customizations are performed by MDT at the time of deployment, the goal of reference image creation is not to perform customization but to increase performance during deployment by reducing the number of actions that need to occur on each deployed device. The biggest action that can slow down an MDT deployment is the installation of Windows updates.