Salta al contenuto principale

Snap Deploy 5 agent being removed from installed programs on Win 8.1

Thread needs solution

Hi,

I've just recently setup a UAT lab with version 5.0.1.416.

I've successfully taken images of all operating systems from Win 7 > Server 2016.

However, I've noticed that whenever I deploy a Win 8.1 image, I have to remotely re-install the SD agent again as it has vanished from the list of installed programs on that image.

Install agent remotely > agent is visible in installed programs > create image > deploy image > agent not installed anymore

I only experience this issue on Win 8.1 on all PCs, all other operating system are fine and do not require the agent to be re-installed.  The deployment tasks all have the same settings.

I've had a quick search about and couldn't see anything specific to this, unless I missed it.

Just fyi:

  • firewall/UAC disabled
  • file/printer sharing enabled
  • Admin hidden share enabled

Anyone have any ideas?

Thank you

 

0 Users found this helpful

I'd contact tech support for this one. You're using an older version though. Try the 1666 instead.

https://forum.acronis.com/forum/127579

Thanks for the reply.

I'll give the update a go and see what happens.

Failing that, I'll have to get someone here to renew our support contract lol

Cheers

Any luck with 1666?

ok... well it seems 1666 has resolved my original problem and all Win 8.1 images are now retaining the SD agent in the installed programs.

However, I'm left with 2 annoyances.

  1. This is one is pre-existing - Lets say I deploy an image, get the latest windows updates applied and then take a new image.  If I use the same file name and choose to overwrite it, it always fails as the AcronisAgent service still has a hold of the file.  I always have to stop the service, delete the original file and then start the service again
  2. This one only started after updating to 1666 - all of my deployment tasks are set to restart the machine at the end.  Since updating to 1666, despite the fact the tasks are still set to restart, they shut down instead.  Creating a brand new task with the same settings works fine, so I'm guessing something to do with the update has had a knock effect to all pre-existing deployment tasks

 

Iain Barlow wrote:

ok... well it seems 1666 has resolved my original problem and all Win 8.1 images are now retaining the SD agent in the installed programs.

However, I'm left with 2 annoyances.

  1. This is one is pre-existing - Lets say I deploy an image, get the latest windows updates applied and then take a new image.  If I use the same file name and choose to overwrite it, it always fails as the AcronisAgent service still has a hold of the file.  I always have to stop the service, delete the original file and then start the service again
  2. This one only started after updating to 1666 - all of my deployment tasks are set to restart the machine at the end.  Since updating to 1666, despite the fact the tasks are still set to restart, they shut down instead.  Creating a brand new task with the same settings works fine, so I'm guessing something to do with the update has had a knock effect to all pre-existing deployment tasks

1. Yes, I don't think there's a way around that because the console is actively using the file name to have it ready in the template.  Only other option would be to create a different image name and either update the task to use that, or create a new task for the new image.  Stop and start is probably the best

2. I haven't used SD5 in awhile, but don't remember it doing that.  Bummer, but at least you know the work-a-round and hopefully you don't have too many tasks to recreate.