Error on post-install process
Wondering if anybody could help me resolve this issue, we're going to use Snap Deploy to roll out Windows 10.. but whilst testing the OS, we're running into a problem.
The OS seems to deploy OK, but the follow-up jobs such as configuration and shutdown are not getting applied, instead Snap Deploy just goes to the waiting for deployment screen.. Checking the logs, we see the following message:
Host '10.75.100.15' has failed the deployment. Additional info: -------------------- Error code: 1 Module: 52 LineInfo: 6934824D6BD2F69E Fields: $module : "osd_server_vs_3124" Message: Host '10.75.100.15' has failed the deployment. -------------------- Error code: 8 Module: 51 LineInfo: EE5A8D016447D65 Fields: $module : "osd_server_vs_3124" Message: Failed to create Acronis Snap Deploy script.
- both the Linux PE and Windows PE
- booting both from ISO and PXE..
- Reinstalling Windows 10 using v1511 and v1607
- Recapturing the image several times
But the same issue always occurs. Yet it seems to work fine with Windows 7.
Any advise or suggestions would be welcome.
What model systems are you deploying too? I suspect that once PXE boot has initiated, your missing the drivers necessary for the newer Intel Nics which are not available in SD5 v1660. I'll PM you a link to 1666 beta. Essentially, it is exactly the same as 1660 but 1662 brought better NIC driver support and 1666 then brought NVME PCIE hard drive support as well. FYI, after upgrading over the top of 1660, some are needing to remove the PXE server componet completely and then re-install just that portion as well.
I've given up on the Snap Deploy PXE server, its too flakey. I've got it running on a VMWare ESXi host using a VM of Server 2012R2, I'm deploying it to another VM on the same host (for ease of PoC) and tried it running a E1000, E1000E and VMNET3 NICs. I've also had problems on with the PXE not booting in UEFI mode.. I had some more success running OSDeployer (whitelabelled Snap Deploy).
In the end I've installed Windows ADK, created a Windows PE with Snap Deploy and loaded it onto the WDS PXE server, which seems more useable.. so we still get the main benefits.
We had issues running it from a VM as well. Never did figure it out, it would work fine for awhile and then not. We moved it to a physical server and haven't had any trouble since. At least you found a work-a-round. OSD is decent too and if you can PXE boot the image that way, do what works the easiest/best.