Snap Deploy Hangs after Imaging
I am using Snap Deploy 5 version 126.96.36.1997
I create a Master Image, it is saved on the same machine where snap deploy is. I create a template (I have done over 200 machines the past two years).
I am restoring the same model pc/hardware.
The machine hangs on the System is being configured screen.
Hard to say without more to go on. Is this the same type of hardware you've deployed to in the past as well?
In most cases, some of the newer systems seem to have a newer driver requirement for the NIC that is not in the default Linux version. You can start the PXE boot with it, but then when the temp OS kicks in, the driver doesn't exist there so the connection fails. Likewise, this can be the case if the system is using a PCIe NVME drive since most vendors set the SATA mode to RAID in the bios.
I would create WinPE rescue media and attempt a stand-a-lone deployment on the system with it, making sure it can see your network share and authenticate to it. If it can, drivers are likely the issue. But, to really know, you probably need to capture the log and submit to Acronis for verification.
A possible cause of such behavior could be that system patching usually takes somewhere from five to ten minutes to complete and may require several (two or three) reboots, after which the deployed system starts successfully.
How long does your machine hang? What happens after a reboot?
Please collect and share with us the OS_patcher logs for analysis:
Logs of the patcher, the names of which are similar to os_patcher[dd.mm.yy].log and are located in the %Windows%\System32\ folder
The system was hanging for a couple of days which is not normal.
Now the issue I am having is that the deployment fails.
The error message is failed to register Acronis Snap Deploy
Frank, did you send Acronis the logs? No idea what the issue is in particular here. My guess is still the lack of drivers - did you try stand-a-lone deployment with WinPE rescue media to test my theory? I still have a hunch that the PXE environment connects to the deployment server, but the NIC driver is missing in the Acronis recovery environment after that. Ultimately, though, your logs should help Acronis determine the actual issue.