Skip to main content

Snap Deploy 5 - Client always shows as "not ready"

Thread needs solution
Beginner
Posts: 8
Comments: 4

Hi,

I'm running snap deploy 5 - 5.0.1.808

When I install the agent on my clients they always display as "not ready"

I've tried the following client versons...

5.0.1780

5.0.1808

The Server and Client are both on the same network and subnet.

How long should it take for a Client to show as ready?

 

0 Users found this helpful
Forum Hero
Posts: 68
Comments: 8106

#1

Should happen pretty quickly.

Are there any GPOs or AV products limiting firewall access on the clients or servers?

Is the client service running (nit stopped or disabled) after installing and rebooting?

Can you boot a Client with rescue media and push a standalone backup or take a backup of it and save it to a network share from the receipt media?

 

Beginner
Posts: 8
Comments: 4

#2

Hi,

Thanks for the reply

No there's no AV on this PC, I've setup a fresh PC to test this issue. The Acronis Remote Agent service is also running on the client.

I can create an image of the PC ok but If I try to deploy an image the deployment taks gets stuck on "waiting for machines" forever because the PC is not ready I guess.

If I run the task using PXE boot it runs and after that the machine shows as ready.

That's a pain for me though as I have a remote office full of PCs that don't have PXE boot enabled.

 

Forum Hero
Posts: 68
Comments: 8106

#3

I wonder if it's a driver issue.  The default recovery from the SnapDeploy console is Linux based.  There seem to be some newer systems that aren't picking up newer Intel adapters - you'll see a lot of these threads.  Such as

https://forum.acronis.com/forum/acronis-snap-deploy-5/image-creator-lenovo-m720-only-not-allowing-network-location-save

 

PXE boot is pre-OS and typically connects to the deployment server just fine.  But, when Acronis actually loads up into its pre-boot environment, it needs it's own drivers to keep communicating in that OS environment at that point.

As a test, try the offline rescue media Linux version and see if it is getting a network address or not, and if not, then create a WinPE offline rescue media and see if it gets a network address instead (it should in WinPE). You can add drivers into the WinPE too - just in case, but if you're building WinPE with Windows 10 ADK, it should work out of the box unless you have a custom NIC like KillerEthernet or something like that. 

Check out the MVP custom media builder tool as well.  You can just drop your drivers into the custom folder and it will add them in automatically for you. Plus, the finished product is more user friendly with a GUI and explorer.

Beginner
Posts: 8
Comments: 4

#4

If I boot from into the linux environment via the agent it gets an IP and immediately appears as ready on the console.

I tried creating an winpe image from the snap deploy console and then uploading the boot.wim it created to the PXE server. Clients failed to boot from that entirely though, I'm not sure I did it correctly.

Whatever drivers the agent uses in the linux boot env seem to be fine, it's when the PC is booted from windows that the agent is failing to register as ready.

Thanks for your help

 

Beginner
Posts: 2
Comments: 8

#5

Not sure if this helps, but I had a very similar issue and it related to the IP address held in the registry on the client machines.

Go here on the clients -> HKEY_LOCAL_MACHINE\SOFTWARE\Acronis\SnapDeploy\ManagementAgent

2 causes I know of that will report not ready:

1. the value for the server IP is wrong, if so change it to the correct IP address

2. the string value for Server is not there, if so create a new string value and give it the correct IP address