We have an IVS and Booster at each of our schools across our WAN. It definitely makes it easier and quicker when imaging at those sites.
To net/pxe boot across subnets you have to put IP helpers in place. Also, since the IVS is a DHCP server, if you have DHCP snooping in place on your network you will have to white list the IVS. Setting a static IP for the machine is also pretty much a must do since you have to point the IP helpers to the specific machine.
You will have to add the subnets you want the IVS to listen for using the imaging-control subnet add command as well.
An easy/quick way to test the subnets is to take a Mac around to each different subnet, plug it in, and option boot. If you see FileWave as an option you know that subnet is working. That way you don't have to netboot and try to image each time you move to a different subnet.
I hope this helps!
IVS: Recommend multiple IVS installations?
23 Aug 2016 22:15 #2361
Just to add to this, by helpers he means the network guy needs to add helpers to the switches. Also, in DHCP (we use Microsoft's) I had to configure the scope options, 066 Boot Server Host Name and put the IP address of the IVS there. And also 067 Bootfile Name and make that pxelinux.0