I actually got the legacy and efi to boot to fog without using the script. I put undionly.kpxe in the scope policy and ipxe in the scope options…it seems to work…i just wanted to see if it would make a difference. It Works!
@george1421 nevermind i found what i was looking for…this is all i wnated to do
FOG image queue size too small
By default, FOG unicast is set to image no more than 10 machines at a time. Other devices will be placed in a queue and wait for another machine to complete. If you want to increase this queue number, you have to do it in two places.
First, under Storage Management > Select your Default Member > Change the figure in Max Clients to the desired number.
Second, under FOG Settings > Expand General Settings > Change the figure in FOG_QUEUESIZE to the desired number.
@george1421 with fog .92 or previous versions i just went in to fog configurations and set the max limit to 20 and i was able to image more than 10 machines at a time. i have fog setup in my dhcp in each scope i am using so it can get to each subnet. can i just not change the number of nodes aloud to image?
can get to the fog gui with this machine. running the lastest fog version.
this is my output from the laptop
station ip is X.X.X.X server ip is x.x.x.x nbp file is ipxe.efi nbp file size is 1003488 bytes downloading nbp file
then it jumps to network not found error
ok i finally got it to give me an ip address, now it is giving me nbp is to big, so do i have to set up the vendor class and dhcp policy 66 and 67 pointing to ipxe.efi? from this article?
if so, which binary would be best used…its an intel networking card … arch:00000?