Skip to main content

Surface Pro 4 Deployment Working?

Thread needs solution

Is deployment on Durface Pro 4's working for anyone? I have not been able to successfully deploy an image to any SP4's and was told by Acronis tech support that it is not supported and might be in the future build.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Zeeshan Imam,

Thank you for your posting! Surface Pro 4 devices are not officially supported yet. I would recommend using WinPE-based bootable media with this device, it might be successfull.

Thank you,

Hi Ekaterina,

Do you have any update on a newer build that supports the Surface Pro 4 yet? Even if it's in beta, I'll willing to test it out and see if it works for us.

Thanks.

 

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Zeeshan,

I've submitted a request for the custom build with the support of NVMe devices. I will keep you posted.

Thank you,

Hello Ekaterina

Do you have now an update that supports Surface Pro 4? I’m still waiting for it.

Thanks!

Martin

Attachment Size
348078-127693.jpg 454.48 KB

Hi,

I have been struggling with this for several months now... been using WDS as a bridge, but would prefer to use snap-deploy for several reasons. I have been able to get it to start the deploy using WINPE, but still have not had it successfully recognise hd and deploy to it.like The lastest efforts have the deployment restarting every second or so... like it see's the hd but cannot write to it... 

Latest attempts bring up read-only error followed by a SIGKILL command

 

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello all,

the custom build 1666 for better support of NVMe devices is ready! Please PM me for the link.

Thank you,

I have about 65 Surface Pro 4's to roll out, and was planning to buy SnapDeploy to image them.  Unfortuantely, I can't get the Stand Alone deploy utility to see the disk in the Surface Pro 4.  I'm pretty new to Snap Deploy so I'm not sure if it's me, but Tech Support told me that the Surface Pro 4 is not currently supported with Snap Deploy.  I don't know if that means I need a completely different product, or if I can perhaps use snap deploy in a some limited way (like stand-alone) in order to get the job done.

Is there any timeframe for Surface Pro 4 support?   Or is there a newer build than 1660 that will let me move forward?  Right now I'm using a trial version as we're still in the evaluation stage.  Unless I'm able to make some headway, I'm going to have a hard time recommeding we purchase this software.

 

 

Hello, Doug Good

Please PM Ekaterina to get the link to the new build 1666.

Best regards.

Using build 1666 I was able to create new stand-alone boot media that did indeed recognize the drive in the Surface Pro 4.  I just completed blowing down a test image and it worked.  I'd love to be able to use the PXE boot on the Surfaces, but stand-alone is better than nothing at all.  One issue I ran into was the Surface Pro 4 keyboard and built-in track pad didn't work when booting with the stand alone media, but a USB mouse did work.

Thanks to Ekaterina for the link to the new build and to AlexanderK for the help here!  I have one other issue I've run into with my testing but I'll make that a new thread so as not to hijack this one.

 

 

After a little more playing around, I was able to get a Surface Pro 4 to install an image using PXE boot in Unicast with build 1666.  I'd like to try Multicast but I think I've burned up my 5 trial licenses by testing.  I know the official line is that the Surface Pro 4 isn't currently supported, but from what I'm seeing progress is definitely being made toward that end.

1666 is working for me with NVME drives as well.  No problems using image creator in SD5 to back it up and stand-a-lone to deploy the image back.  

Doug, I have trouble with 64-bit bootable recovery not detecting trackpads and touchscreens on different systems. Using a keyboard and mouse works fine though.  I have picked up some USB 3.0 gigabit ethernet adapters with an extra 3 USB ports on them as well to make this easier without needing to use a Surface dock.

Alternatively, I found that you can easily edit the boot64.xml file on the default media and just bring over the 32-bit information into it.  You can then boot the 32bit version from the 64-bit UEFI menu and it works just fine.  32-bit seems to function better on most devices with trackpads and touchscreens (for me).  I have not tried on a Surface Pro 4 though.

See my post in ATIH 2016 about this.  http://forum.acronis.com/forum/118384#comment-357638

The same will apply to Snap Deploy media.