Someone from Broadcom did reply with…
Thank you for the evidence, as per screenshots, it seems that iPXE is actually sending all files, and when you're getting the BlueScreen - that's when WinPE is actually trying to load already.
Might it be related to Secure Boot being enabled?
We assume same client machine being tested, and so when this client loading TFTP PXE boot with same Secure Boot or/and TPT settings?
The error 0xc000000f is related directly with the Boot Manager values, and maybe Winpe files sent through iPXE are not "signed" properly?
Original Message:
Sent: Mar 08, 2022 02:22 AM
From: avi kroparo
Subject: ghost 12 3.3 ru9
can some one from broadcom can investigate this issue ?
Original Message:
Sent: Feb 17, 2022 04:22 AM
From: avi kroparo
Subject: ghost 12 3.3 ru9
i did my own testing same results every time.
Original Message:
Sent: Feb 16, 2022 10:29 AM
From: JOHN FRY
Subject: ghost 12 3.3 ru9
Hi,
This is news to me... Were did you get this information from?
Thanks
Original Message:
Sent: Jan 26, 2022 05:00 AM
From: avi kroparo
Subject: ghost 12 3.3 ru9
this version and prveious are not backward compatiable with images created with older version of symantec ghost im talking about the soultion suite 3.3
until version 589 i was able to deploy images but from later versions i couldnt it always fails at 99%.
i made my images with the split=0 switch to resolve this issue i have to deploy my images with the old version of symatec and save them with the new broadcom version.
why there is no backward compatibily for images created with older version?