Not seen this before, but never tried to PXE boot this many. Looking at the PXEConfig utility, I see a maximum number of addresses that will be serviced, so perhaps this is related. Isn't 11 though. See screenshot.
PXE Config Tool is found in the PXE Rep installation directory.
Verismic Software - http://www.verismic.com
Precision Engineering for Systems Management
- PC Power Management Software
- LANDesk Historical Analysis
- Self-Service Password Reset
- LANDesk to Service Desk Integrations
PXEConfig.jpg 77.6 K
Let me see if I understand what you are saying.
If I understand correctly, you are saying that you can only get 11 devices to PXE boot, which means downloading the WinPE image, at the same time.
So only 11 devices can boot to WinPE from one PXE Rep. Which would be a TFTP problem.
Or are you are not saying that you cannot run the imaging tool to multiple devices, so if you have more than 11 devices, the imaging application, be it ImageW or Ghost or ImageX, fails on any machine after the 11th machine.
I think you mean the first one...can you verify. If the issue is with the first one, then you could add a second PXE Rep to the subnet and maybe you would see it increase to 22.
If you have to only have one PXE Rep, then hear is more info:
A long time ago when we first started using WinPE this problem was reported, but we worked on our TFTP service to improve performance, and this is the first compaint of this I have heard since. To fix this in the past, they followed these steps to disable the default PXE Rep's TFTP server:
Then they added their own TFTP server. I am not sure if the TFTP server is the bottleneck or not.
As it turns out, the problem was that I was mapping my imaging tool from an XP share, which is limited to 10 connections. I switched the mapping to a Windows 2003 share, and the limitation is now gone.
Thanks for the responses!
Ok, so the problem wasn't with the amount of machines could PXE boot at once, so it is not a TFTP problem...yeah!