SnapDeploy 5 won't boot to PE image
I have about 70 machines that use SnapDeploy on a regular basis to reimage and recently they all stopped booting into the imaging environment correctly. I think this may have coincided with an update on the image to Windows 21H2 (though I can't be sure about that). We use a WinPE image as the necessary network drivers are missing from the Linux boot image.
We use the agent installed on all the machines to tell them to boot into the PE environment, and don't use PXE as have found it to be unreliable, and slow when it works.
I updated to the latest v5 on the server and have created a new PE boot image since then - neither this nor the old image will now boot, but the old PE image used from a USB key will boot quite happily still and connect to the server (though I'm still having issues here, that could be to do with leaving the USB disk in place so need to investigate more).
When rebooting the machines for imaging using the agent, the followimg message appears in the logs, and the machine boots into the Linux media.
<event code="0" id="198" level="3" message="Failed to detect the WinPE-based bootable media architecture. The machine will be rebooted into the Acronis bootable media." module="52" time="1643284476" />
We get this with both the old and newly created PE images.
The default settings have the correct path for the PE image (.wim file) under Online Deployment.
Unfortunately the machines are remote (hence the need for this to work without USB/keystrokes), so getting there to test is not something I can do every day.
I've tried everything I can find at this point, so any help gratefully received.

- Log in to post comments

Hi Ekaterina,
It seems to have gone away now which is sort of annoying to be honest as I still don't know what caused it.
I did take a new master image to deploy, and didn't include the PE boot in that image, but don't see how that can matter since that was not on the target machine when it was being deployed.
It would be good to have some documentation about which boot image is used in what circumstances and where in the process it is sourced. Obviously USB and PXE boots this is sort of obvious, but I can't figure it out when the machine is rebooted by the agent and there's no USB or PXE involved - there's too many possible places it could come from.
- Log in to post comments