Thanks for posting to the Ivanti Community.
Sorry that it seems no one has the answer to be able to assist you on this yet. Did you manage to get any further information on this? Please share anything you deem useful and the community may be able to offer some help.
If not then please do consider the other ways to engage with us to get assistance:
Check down the IP of the Windows Boot Manager perhaps?
I would expect that someone is running a Windows / Microsoft PXE rep (in parallel to yours) that's effectively running/causing race-conditions as to which PXE rep is serving a client first?
That's not a good thing .
But should be "just" a matter of educating that person to not be serving your corporate network (surprising how often I see dev-setups "hop over" to be connected to a corporate network ... a lot of "fun" with "rogue" DHCP servers too as one can imagine).
That'd be my first guess. That's not something "we" do .
LuffyChan - if you're running into the exact same issue, then your problem (too) is that someone's running a 2nd (and/or 3rd, 4th...) PXE service on your setup.
The question as to "who gets to boot to it" is purely a race condition on "which PXE responds first" ... that's why the advice above was to disable those PXE servers that aren't being used. PXE is not something that can co-exist with multiple different items. It's a VERY limited // primitive boot-environment, so you have to keep it simple.