Skip to main content

Snap Deploy 5 - Surface Pro 3 w/ Windows 8.1 - Standalone deployment not completing

Thread needs solution

Snap Deploy 5 v5.0.0.1656

I have been trying to deploy a Master Image to a Surface Pro 3 w/ Windows 8.1 for several days now and I can not get Acronis Snap Deploy 5 to work. I am creating the master image and deploying to the same computer to test whether Acronis is a viable solution for my client. They currently use Snap Deploy 4 for their Windows 7 environment.

I have captured 1, 2 and all 4 partitions from the Surface Pro 3 Win8.1 device, and have tried deploying 1, 2 and/or all 4 partitions to the same computer.

No matter what option sequence I use with Standalone Utility, the deployment starts, and in less than 1 minute it says it completed. It does wipe all partitions, but creates none.

Would Acronis supply step-by-step instructions for Creating the Master Image and Deploying the Image back to the same Surface Pro 3. Including which partitions to capture in the Master Image, and which are required to deploy the image.

I had previously contacted support via on-line chat, but the support person was unable to provide any assitance.

I am reposting this question from a previous topic to this new subject for better resolution.

0 Users found this helpful

This product should easily work "out of the box" if you do exctly what was required in the nanual (follow the RDFM rule).

But it doesn't.

Too many problems with various scenarios that do not work, drivers missig, uncontrolled actions (like your case), etc...

Acronis has two big problems this time:

1. The QA was not wide enough and as a result - too many problems with Snap Deploy.

2. THe Support (level 1) has no real experience with this product so that are only screening the problems. In my case it took quite a long time to escalate the issue to a higher support instance.

We will have to wait ... or give up.

 

MK

Jeff, as a stand-a-lone deployment, this should work fine.  I've deployed images using the v1660 to Surface Pro's without issue. See my response to your other post here:  http://forum.acronis.com/forum/109465#comment-356686

Moty, see my post about your issue in your thread and defintitely reach out to gaidar with your thread, support case and the other thread references i put in your post.  I have a feeling he will make things right and hopefully v1662 will help in your situation (once you're finally able to get your hands on it).  

Also keep in mind the comments from the orginal poster about v1662, in regards to removing the PXE components and re-installing them again after getting v1662.

"After bouncing around support for a day, i finally spoke to a L2 engineer who steered me to a new Build:  1662 

I installed this build, removed and re-added my PXE components, and now i am all set. So clearly 1662 includes drivers for many newer computers.

***Note as of 4-25-2016, the latest build on the website is 1660, so you will need to contact support and ask for an FTP link to build 1662"