We are aware of some limitations when imaging the Microsoft Surface Pro tablet and are working on resolving them.
The following problems have been observed during cloning attempts:
The root cause of the issues is being investigated currently and we expect to release an update with full support as soon as the issues are resolved. Some of the following known reasons for issues have been found:
Testing of the Surface pro machines has raised some issues and these will need to be addressed before we can offer full support. This is a high priority for the team and this article will be updated as more information becomes available.
In the interim limited testing has shown that local cloning with a USB flash drive and external USB HDD has been successful Here are some suggestions that may help
Some customers have also reported that using a special PXE dongle from Microsoft in a PXE environment has allowed these machines to be successfully cloned. Please contact Microsoft for details as this process is outside of Symantec's control.
Note: Do not use deployanywhere after an image deployment. Rather take and restore your images from the Surface pro 3 to a Surface pro 3 and eliminate the need for deployanywhere.
Note: Surface pro 3 & 4 For networking drivers please see the following blog post for locating surface pro drivers
Note: Surface Pro 4 For hard drive support the heci driver files that are downloadable from Microsoft at https://www.microsoft.com/en-us/download/details.aspx?id=49498 and is titled SurfacePro4_Win10_161521_0.zip The heci.inf and .cat must be copied from the extracted \Drivers\System\ManagementEngine\ to the \SurfacePro4_Win10_161521_0\Drivers\System\ManagementEngine\x64 folder. All 6 files will need to be in the same folder to be added to ghost as a custom driver. See HOWTO60456 on how to add this custom driver manually to the Ghost Boot Disk driver list as it is not properly formatted to be added using the Boot Disk GUI.
Note: Surface Pro 4 For the Surface Pro 4 you may need to change the Secure Boot configuration "Secure Boot certificate keyset" from "Microsoft only" to "Microsoft & 3rd party CA."