This does present a couple of questions. If the machines were set to pxe boot, they wouldn't have a running image on them for the audit unless someone went back and installed something prior handing the machines over and flipped off the pxe boot in the BIOS. The only way I am familiar with doing a permanent install from pxe is using pxe to load something like a small busybox image which will run a kickstart script to install an OS, like centos for example. We have to assume these are not diskless machines as they are NOT to be networked, and must have the ability to start on their own.

Pxe would be yet another reason to see the router configs. if those machines were set to pxe boot, then you will can check the router to see where it forwards/relays the ports 67, 69 for the bootp request for the actual image these things would pull from.

This definitely would be proof there was outside connectivity.
See part 5 of the Devolution series, which ties in Dominion

This does present a couple of questions. If the machines were set to pxe boot, they wouldn't have a running image on them for the audit unless someone went back and installed something prior handing the machines over and flipped off the pxe boot in the BIOS. The only way I am familiar with doing a permanent install from pxe is using pxe to load something like a small busybox image which will run a kickstart script to install an OS, like centos for example. We have to assume these are diskless machines as they are NOT to be networked, and must have the ability to start on their own.

Pxe would be yet another reason to see the router configs. if those machines were set to pxe boot, then you will can check the router to see where it forwards/relays the ports 67, 69 for the bootp request for the actual image these things would pull from.

This definitely would be proof there was outside connectivity.
See part 5 of the Devolution series, which ties in Dominion