Skip to main content

Snap Deploy remote installation

Thread needs solution

Hello Forum Members,

I started working with Acronis Snap Deploy product several days ago. I read through documentation and after that I installed software listed below on dedicated backup server:

Acronis Snap Deploy PE Builder
Bootable Rescue Media Builder
Acronis License Server
Acronis OS Deploy Server

After that I tried to install Acronis Snap Deploy Management Agent on one of workstations (from dedicated backup server) and I get error:
Connection to remote computer is broken. (0x45000A) Tag=0xXXXXXXXXXXXXXX

Workstation is pinging, host files are updated on both machines properly.

I found an topic on this forum:
http://forum.acronis.com/forum/10251
But it is not solving my problem.

Agents can be installed locally but I have a lot of workstations and I would like to install agents on all of them remotely.

I will be gratefull for any help.

Kindest Regards,
Greg

0 Users found this helpful

Hello Greg,

Thank you very much for posting and welcome to the forum. I will definitely help you.

It is very difficult to say what exactly causes this issue at first glance. We will need to investigate it.

If there is another Acronis Management Console installed on the backup server, there could be a conflict.

When contacting our support, kindly include the following reports:

1. AcronisInfo report from source and target machines.

2. Screenshots from the remote installation wizard.

If you have additional questions, please let me know.

Thank you.

For anyone else experiencing the error referenced in the first post:

For me, although the same "connection broken" error appears after each remote installation, the agent actually installs just fine. Attempts to connect to the remote PC are a success and I can push/pull images just fine. If you are taking the error at its word that the connection is broken, try connecting the console to the remote machine anyway.

I'm not suggesting that this is the fix; something else is going on here that I'd like to see resolved, but if you're working on a time sensitive project it would seem the product is still usable. Again, this may be specific to my setup, but worth a shot for you regardless.

As a side note, the error did not start occurring until after I had upgraded to 2008 R2 SP1 from 2008 RTM Standard. Hope this info can help someone.

Update: To speed things up I installed a Snap Deploy console on another server, running 2003 SP2 x86. The remote install went off without a hitch. In my case, this seems to be a problem with 2008 R2 SP1. I upgraded directly from 2008 Standard to 2008 R2 SP1, so I cannot say if the error occured in R2 without SP1.