Deploy failed "No Acronis Snap Deploy 5 License Server installed on..."
Had to create new Acronis installation server due to HW failure. Followed previous threads and 1) installed license server first, 2) imported all my licenses into it. 3) Installed Snap Deploy Agent, Console, OS deployment server. Snap deploy console sees licenses fine.
Had to use PE USB boot disk for Lenovo T460 (due to no Linux drivers) Set up deployment job and it starts to deploy to target. But fails after a few seconds with error:
Host '10.0.3.147' has failed the deployment.
Additional info:
--------------------
Error code: 1
Module: 52
LineInfo: 6934824D6BD2F69E
Fields: $module : "osd_server_vs_1660"
Message: Host '10.0.3.147' has failed the deployment.
--------------------
Error code: 2
Module: 100
LineInfo: 876D9AA543F78CF4
Fields: $module : "osd_server_vs_1660"
Message: No Acronis Snap Deploy 5 License Server installed on ''.
All licenses appear in Snap deploy as available. Deployment server is Windows 10. Using Acronis build 1660.
Thanks in advance for any advice.

- Anmelden, um Kommentare verfassen zu können

Christopher. Let's make sure you can first make access to the backup files on the server...
Have you given the network share on the new server enought access rights for the clients to be able to reach them and/or used the correct credentials in the deployment template?
As a test for credentails, build the default bootable media in Linux and boot to the stand-a-lone version first. Then attempt to navigate to the share where the backup image is already stored and supply the same credentails you put in your deployment template. Can you connect to the share and see the backup .tib files? If so, try deploying the image to the machine with the stand-a-lone and see if it completes.
Once that is working, if you have already installed the pxe boot components on the deployment server and all services are running, you should be able to PXE boot your system from the NIC and at least get to the initial Acronis menus for deployment and image creation. Once there, start teh deployment method and go from there. You can also try creating an image this way to make sure there are enough access rights to be able to create an image this way and save them where your other image repository is at.
If you can't do any of this, you may need to go back and look at your image repository share permissions. Perhaps you created local access rights, but forget to share them out too?
- Anmelden, um Kommentare verfassen zu können

You may also want to ensure that the Windows firewall has access for the following ports and thta windows file sharing is enabled.
https://kb.acronis.com/content/47403
- File and Printer Sharing must be enabled on the remote machine:
- Windows Vista, Windows Server 2008, Windows Server 2012 Windows 7, Windows 8: Control panel -> Windows Firewall -> Network and Sharing Center -> Change advanced sharing settings
- Acronis Snap Deploy 5 uses TCP ports 445 and 25001 for remote installation. Make sure that these ports are added to exceptions in the firewall settings on the remote machines. TCP port 445 is added to exceptions automatically by Windows Firewall when you enable File and Printer Sharing.
I know it says for the remote systems, but I would ensure that file sharing is turned on and the ports are open on the server too.
- Anmelden, um Kommentare verfassen zu können

These may come in handy too.
47445: Acronis Snap Deploy 5: Creating Master Image (Online)
47475: Acronis Snap Deploy 5: Creating Master Image (Offline)
I just re-read your note that you have to use WinPE because no drivers found for your system with the default 1660. If you minimize Acronis windows in winPE, are you able to run "ipconfig /all" and verify you have an IP address? Can you ping the deployment server?
As a test, can you use netuse command to map your backup .tib folder as well? Example:
- The username you authenticate with on the remote machine is HTG
- The password for the HTG account is Pa$$word
- you are mapping the share as S:\
net use s: \\tower\movies /user HTG Pa$$word
- Anmelden, um Kommentare verfassen zu können

Sorry, one last note. There is a Beta v1662 version that has networking in the default Linux version already. Please send a PM to Acronis support engineer, Ekaterina and requst the download so that you can try it out as I think it will resolve your issue with the default Linux bootable media not working with this device NIC.
Alternatively, I highly recommend getting a few cheap USB 3.0 to Gigabit ethernet adapters. They are well worth the money and come in very handy for scenarios like this. I like this one since it has some extra USB ports as well and is nice for tablets like the Surface Pros, or any tablet that has no ethernet and mimimal USB ports. Or if you just need a standard USB to ethernet adapter, these have worked well for us.
- Anmelden, um Kommentare verfassen zu können

I have the exact same issue as Christopher, and have worked through all of these suggestions with no luck. My situation is a bit further unique because I'm having to use PE due to an unrecognized NVMe hard drive, which requires loading in a driver.
Is there anything else I might try? There is a batch of computers here needing images and I'm running out of ways to stall...
- Anmelden, um Kommentare verfassen zu können

I can only assuem the beta was the help that Christopher needed, since he never responded back. There is a newer beta 1666 that has newer NIC drivers and NVME support by default (if the system SATA mode is AHCI - if it's a single disk that shipped in RAID mode by the OEM, you can safely switch to AHCI in the bios first before booting recovery media, create or deploy an image and then return to RAID mode... or just stick with AHCI mode if need be).
If you're upgrading from 1660 to 1666, after the upgrade, I'd suggest removing the PXE component completely, rebooting and reinstall the PXE component fresh as well.
I'll send you a PM with the download link for 1666.
**Also, when you created your WinPE, what ADK did you use? You should use the Windows 10 1511 ADK as that is the most recent that Snap Deploy 5 is capable of using, but has better default drivers than ADK 4.0 or 5.0 or earlier versions of 10.0. In some cases, if the drivers aren't there for the hard drive or NIC (tested easily with the offline recovery media), then you'd still have to inject drivers from the manufacturer using ADK DISM commands or a tool like DISMGUI.
- Anmelden, um Kommentare verfassen zu können

The solution for me was that there were missing registry entries when the licensing server was installed. Tech support was able to populate the corrent ones and I have been fine.
Sincerely,
Chris
- Anmelden, um Kommentare verfassen zu können