Surface Tools for IT Update for Surface Pro and Surface Laptop

We are pleased to announce that today we've released new versions of the Surface Tools for IT Pros with support for the new Surface Pro and Surface Laptop. This update includes new versions of the Surface Enterprise Management Mode (SEMM) tools Surface UEFI Configurator and Surface UEFI Manager, Surface Dock Updater (SDU), Surface Data Eraser (SDE), and Surface Deployment Accelerator (SDA). You can download these updated tools from the Surface Tools for IT page in the Microsoft Download Center.

Click the download to select the following files for each of the Surface Tools for IT:

  • Surface_Deployment_Accelerator_v2.0.8.0.msi
  • Surface_Data_Eraser_v3.2.36.msi
  • Surface_Dock_Updater_v2.1.15.0.msi
  • SurfaceUEFI_Configurator_v1.0.74.0.msi
  • SurfaceUEFI_Manager_v2.2.21.msi

See the below list for notes on the individual updates for each specific tool:

Surface Deployment Accelerator

  • Surface Deployment Accelerator v2.0.8.0 supports deployment of the new Surface Pro.

Note: Surface Deployment Accelerator v2.0.8.0 provides support only for Surface Pro and does not replace Surface Deployment Accelerator v1.96.0405 which supports Surface 3, Surface Pro 3, and Surface Book.

Surface Data Eraser

  • Surface Data Eraser v3.2.36 adds support for the storage devices of Surface Studio, Surface Pro, and Surface Laptop.

Note: The Surface Data Eraser USB creation utility cannot run in a Windows 10 S environment. To erase the storage device of a Surface Laptop with Windows 10 S, you must first create the Surface Data Eraser USB drive using another computer with a Windows 10 Pro or Enterprise environment.

Note: Surface Pro devices with 1TB storage are not currently supported by Surface Data Eraser.

Surface Dock Updater

  • Surface Dock Updater v2.1.15.0 adds support for Surface Pro and Surface Laptop.

Note: The Surface Dock Updater utility cannot run in a Windows 10 S environment. Surface Dock devices connected to Surface Laptop with Windows 10 S will receive firmware updates through Windows Update and do not require the Surface Dock Updater to stay up-to-date. If you wish to check the firmware version of a Surface Dock, or to manually update a Surface Dock, connect the Surface Dock to a Surface device with a Windows 10 Pro or Enterprise environment.

Surface Enterprise Management Mode

  • Surface UEFI Configurator v1.0.74.0 adds support for Surface Pro and Surface Laptop and a new ability to generate a USB drive with WinPE that can be used to enroll a device in Surface Enterprise Management Mode.
  • Surface UEFI Manager v2.2.21 adds for Surface Pro and Surface Laptop.

Note: The Surface UEFI Configurator and Surface UEFI Manager cannot run in a Windows 10 S environment. Surface Laptop devices running Windows 10 S can be enrolled in SEMM using the USB drive generated by the Surface UEFI Configurator, or otherwise can be enrolled by upgrading the device to Windows 10 Pro or Windows 10 Enterprise.

Comments (12)

  1. Ben Duan says:

    Thanks, Brandon

    Can I ask ou a question regarding Surface Laptop running Windows 10 S? I’d like to double check with you if we can upgrade Surface Laptop from Windows 10 S to Windows 10 Enterprise for free. I have been advised by Surface Support team that it is the case.

    I would also like to know with the surface enthernet adapter, if the surface laptop can be imaged through pxeboot into SCCM deployment environment?

    Thanks for your help.
    Ben Duan
    Client Services (Domain) | Information Technology Services | University of Tasmania

  2. Ben Duan says:

    Hi, Brandon

    Not sure what happened to the comments I posted yesterday, which was to see if you can help clarify the upgrade possibility/path from Windows 10 S on Surface Laptop to Windows 10 Enterprise in the corporate environment, and also if the new Surface laptop will support pxe netboot for SCCM imaging process?

    It would be even better if the answer to this is already published somewhere on Microsoft website.

    Your advice will be greatly appreciated.

    Ben Duan
    Senior Client Services (Domain) | Information Technology Services | University of Tasmania

    1. Yes, PXE boot is available on Surface Laptop.

      Regarding the upgrade path, both reimaging and product key upgrade scenarios are supported (manual or via MDM). There are licensing considerations, as Window 10 S is not a qualifying operating system for Windows 10 Pro or Windows 10 Enterprise upgrade licenses. You will first need to provide a qualifying operating system before you can upgrade to Windows 10 Enterprise, for example, by upgrading the device to Windows 10 Pro via the Windows Store. Other options may be available depending on your volume license agreement. I recommend you reach out to your source for volume licenses to determine what options are available.

  3. Patrick says:

    When I click on the link for Surface IT tools above and click download, I get a list of files, but I can’t select any of them. So, can’t download anything. Is there something else I need to do to get these files?

    1. From what you describe, this sounds like a browser issue, you should try downloading in a different browser or in an InPrivate session or equivalent.

      The correct behavior is as you expected, you should be able to check the box next to each of these files and then click next at the bottom of the list to begin the downloads.

      1. Matthias says:

        If it’s a browser issue, then Microsoft Edge isn’t the right browser for the job…

        1. It was determined that this was an issue with the site causing the checkboxes to render incorrectly on browsers other than Internet Explorer. This issue was remedied and the checkboxes should once again appear as expected.

  4. Brian Hoyt says:

    Regarding Surface Deployment Accelerator – 1.96.0405 supports Surface 3 and Pro 3, now supports Pro (2017). Is there no support for Pro 4?

  5. rufociliatus says:

    Hi Brandon,

    Surface Dock Updater v2.1.15.0 makes passive DP-DVI adapters obsolete.
    I’m running an older DP firmware version, 04915A70 and my colleague is running 0499A170. I’m using miniDP to DVI (Startecg MDP2DVI3) which runs perfectly fine,, and my colleague had to get a miniDP to DP adapter.
    Can you tell if there are plans to restore DP++ functionality, and if the change was intended?



  6. WebAsh says:

    This stuff is such a mess… is there somewhere I can provide this feedback formally?
    – The v1.9xx builds don’t work as currently available on Microsoft Download centre, because the officedeploymenttool URL included fails to download correctly; replacing this in the PowerShell script with a newer URL manually allowed installation to finish without an error… but it took diving through log files to discover this
    – Once installed, booting from the included boot.wim through WDS shows the SDA logo briefly, before the machine reboots; it seems its crashing on boot. This is within a Hyper-V VM, so there’s not a lot I can change to make this work. I’ve also tried on a Surface Book and a Surface Pro for both v1.9xx and v2.0.8.0
    – All the MDT steps are VBS scripts with very little documentation or configuration items to tweak without diving into the VBS code.
    – v2.0 can’t even install, because the ‘create Windows Deployment’ step won’t accept any Local Path for the Windows Source Files. You manually type or browse, and then it will clear the entry immediately after and show a red x to the left of the box which doesn’t explain what the problem is.
    – The documentation on the site doesn’t even acknowledge the v2.0 version, so there is no explanation for what the prereqs/installation process should be
    – The v2.0 installation process [after unticking the deployment setup option] doesn’t offer any explanation on what it means on the MDT Integration page: ‘download and unpack drivers and applications for manual import into MDT’… does this mean it won’t do anything if I don’t tick this? Is there an automatic option?
    – Attempting to revive the v2.0.8.0 installation by manually running the PowerShell script with the necessary inputs (after some trial and error and reading the script) seemed to work, but still the image wouldn’t boot; the same as v1.9xx
    – and also, v2.0 (which you would naturally think to be a successor to old versions) is only relevant to *some* Surface devices? *SIGH*

    I notice that the installer is vastly different for v2.0… does this suggest that all of the above and hopefully more are being rectified with a top-to-bottom refresh of the tool?

    For something that is supposed to be an ‘accelerator’, I wasted a few days last week trying to get this to work to no avail. Is there something the documentation isn’t saying that I’m therefore missing? Is it just not tested much? Is it just this finnicky?

    1. I’ve conveyed your message to the Surface Tools for IT and Surface Deployment Accelerator teams. Thank you for your feedback, we will look to address these concerns in future releases and efforts.

Skip to main content