after updating to Snap Deploy 3329, cant deploy/create image
We recently updated to Acronis Snap Deploy 3329. Our server has been working for 2 or so years perfectly up until we updated, now we can no longer create images or deploy images from the server. I’ve tried images on about 15 different PCs with different motherboards and hard drives, and have confirmed the Hard drives are the correct size (most of the PC’s are brand new, some are not)
The only thing that works so far is creating images and deploying images from an External HD using the Stand alone utility. I’ll just start with our deployment problem since I’ve gathered the wireshark and acronis logs for that already.
Here’s the steps we go through to deploy an image from the Acronis server using a boot disk :
1. Drop the station we want to image from the domain, put the Acronis Snap Deploy boot disk into the drive and boot to it.
2. Select Snap deploy and it goes into the screen awaiting the image with the loading bars
3. From the Acronis Server I then run Snap Deploy Management Console
4. Click Manual deployment, and select the PC that is awaiting the image
5. Click create new template, select the image file and click through the windows just using all the default settings.
Once finished going thru all the settings and starting the deployment, It acts as if it starts to deploy, going to about 7% total or something similar (same % everytime though), and hanging there at 7% for exactly a minute before giving the error about not being able to contact the PC (A client (IP) does not respond)
Watching the PC awaiting the image while all this happens, it just appears to reboot. Heres a clip of what I’m talking about
8:14:05 – Deploy server started
8:15:29 – Host (IP) with Mac Address .. queries for deployment
8:15:30 – Session ‘default’ : Join client ‘pc’s IP’
3,407,873(0x740001) 8:17:06 – A client ‘pc’s IP’ does not respond
I've attached the Wireshark log, the AcronisInfo, the Deploy Server Operations Log and the Agent Operations log. If you need anything else just let me know, I just gathered all this stuff from reading other posts. NOTE : I had to rename the file extension on the wireshark log so I could attach it, I changed it from .pcap (i think that was it) to .txt
Thanks in advance!!
Anhang | Größe |
---|---|
Wireshark_Log.txt | 970.54 KB |
AcronisInfo.zip | 457.39 KB |

- Anmelden, um Kommentare verfassen zu können

All of our programs are 3.0.3329 (OS Deploy Server, Snap Deploy Mngmnt Console)- except the Acronis License Server (2.0.18) and Acronis PXE Server (3.0.1100) Would either of these be causing a problem or is there a newer version?
- Anmelden, um Kommentare verfassen zu können


Hello Larry,
Thank you very much for your post. I will do my best to assist you.
To answer your last question first, all these product versions are up to date, even though the numbers are different from the main build 3329. I apologize for the inconvenience.
If you are absolutely certain that this problem began after updating to the latest build of Acronis Snap Deploy 3, then we can proceed the following way in updating the software, because it is very likely some components did not update properly.
Perform a full uninstall of the software:
1. Add/remove programs from Windows.
2. Please delete these folders:
C:\Documents and Settings\All Users\Application Data\Acronis
C:\Program Files\Acronis
C:\Program Files\Common Files\Acronis
3. Remove these registry keys only:
HKEY_CURRENT_USER\SOFTWARE\Acronis
HKEY_LOCAL_MACHINE\SOFTWARE\Acronis
4. Reboot and re-install the program.
5. Create 1 template and select unicast in the Network utilization options, the default is multicast. See if this resolves the problem. Please check page 63 of our user guide for additional information.
If none of the solutions work, please submit a support request with the information you have and our Support team will resolve this issue for you.
Please let me know if you need additional assistance.
Thank you.
- Anmelden, um Kommentare verfassen zu können

Hi Larry,
I was having a similar issue.
I updated the PXE server to the latest build and then discovered that in the new version the PXE server and os deploy server could not reside on the same machine.
Hope this helps (you or someone else stumbling on this thread)
- Anmelden, um Kommentare verfassen zu können