Deployment and Imaging Group

Hi since PXE is a site service would it only support the clients in that site? goal is to have multiple pxe server to support the site those are in and clients do not go to a different PXE server if the PXE server in site is not available. 

If you have PXE on the site server and all clients are in the same subnet you do not need to configure anything extra to get PXE to work. Additional positive effect is that when you download the pxe boot image from server it is transfered on the local lan and should be much faster as if you would download from the central.

If you have PXE installed on a central site server you need to configure ip helper to get PXE to work in remote sites. And the negative is that you download the pxe boot image from central which probably take longer time. However, this might be not that big issue because the boot image is not that big and you could still go ahead and have local image store on each site server without them being PXE server.
 

Thanks Stefan, we have multiple sites and a site server at each site with PXE , what we do not want is that Cients in one site going to the other site to get pxe images if the local pxe is down. Does it work this way or we need to do some additioanl configuration. 

To get the clients to use a different PXE than the local you would need to go into the ip helper configuration but I do not even know if there would be an option to have a fall-back configured in the ip helper. So PXE service is down in the site the PXE service is down and you cannot boot from PXE.

The only thing which could lead to problems if you have two PXE servers in the same site / subnet. Because in that case I think you cannot control which PXE server is answering first. But I am sure you do not have this...