The Touch Firmware should never be loaded in a Win PE environment on Surface Pro 3.
These Windows Installer packages can be deployed with utilities that support application deployment, including the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager.
This solution allows for centralized deployment and for administrators to test and review firmware updates before they are deployed.
On Surface devices, the firmware is exposed to the operating system as a driver and is visible in Device Manager.
This allows a Surface device firmware to be automatically updated along with all drivers through Windows Update.
Windows Power Shell Another method you can use to update the firmware when Windows Updates are managed in the organization is to install the firmware from the firmware and driver pack by using Power Shell.
This method allows for a similar deployment experience to the Windows Installer package and can similarly be deployed as a package by using System Center Configuration Manager.
Each Surface device that receives Windows Updates directly will separately download each update rather than accessing a central location, which increases demand on Internet connectivity and bandwidth.
Updates are also provided automatically to devices, without being subjected to testing or review by administrators.
Windows PE and Surface firmware and drivers A best practice for deployment with any solution that uses the Windows Preinstallation Environment (Win PE), such as System Center Configuration Manager or MDT, is to configure Win PE with only the drivers that are required during the Win PE stage of deployment.
These usually include drivers for network adapters and storage controllers.
This best practice helps to prevent errors with more complex drivers that rely on components that are not present in Win PE.