Network imaging is supported over Ethernet using the FileWave Imaging Virtual Server (IVS), which provides PXE services for Windows computers and NetBoot services for macOS 10.12 and lower computers. Network imaging via the IVS is not support on macOS 10.12 and higher as explained here. The IVS is a Linux virtual appliance that you can import into VMware, Hyper-V, or VirtualBox.
If you would like to test FileWave's network imaging capabilities during the course of your evaluation please engage your FileWave SE for assistance in setting it up should you run into any issues.
Since DHCP, PXE, and BSDP (used by NetBoot) are UDP-based broadcast protocols, they typically do not traverse subnets. Most network administrators do not allow broadcast packets across subnets. If your IVS and the clients computers to be reimaged are located on the same subnet then you do not need to make any changes to your network configuration, as the clients will discover the IVS via broadcasts on the local subnet. If the client Macs or PCs to be reimaged are on a different subnet, however, then you have to take one of the following steps to be able to network boot and reimage them.
For PXE, Microsoft "does not recommend using DHCP options" and that your "DHCP server does not have DHCP Options 60, 66, or 67 configured" as described here. Setting scope options may actually prevent UEFI computers from UEFI PXE booting properly as explained here. While these articles refer to SCCM, the same principles also apply to other PXE servers such as the FileWave IVS.
If you choose the latter option you will also need to configure the IVS to serve clients on other subnets other than the one it's located on. By default the IVS only responds to PXE boot requests from devices on its local subnet. Please engage your network admin for setting up IP helpers or DHCP scope options. Note that you only have to do one of these. For the purposes of this evaluation we recommend you install the IVS on the same subnet as your client machines to be reimaged to simplify the setup.
The following prerequisites must also be met.
The IVS needs to be able to connect to your FileWave Server on the following ports:
Any subnets with clients to be imaged must be able to reach the following ports on the IVS:
67 (DHCP), 69 (TFTP), 80 (HTTP), 20444 (HTTPS), and 4011 (DHCP PXE service - required for UEFI imaging)
111 (TCP,UDP) and 2049 (TCP,UDP) are used for NFS access
Any machine running the FileWave Admin needs to be able to connect to your IVS on the following Ports:
20010 (Client Monitor), 20444 (Remote Configuration, Shared Keys)
Configuring the IVS
Change the time so that it matches your current time. If you need to look at the logs later for troubleshooting it will be easier if the time matches the time on your FileWave Server and clients.
date -s HH:MM
Next, change the IP address of the IVS to a static IP by running the following command. Follow the prompts to set the IP address, subnet mask, gateway, and DNS server. You will be asked to confirm your changes at the end.
imaging-control networksetup static
By default the IVS only responds to PXE requests originating from clients on its local subnet. If you will be reimaging PCs located on a different subnet than the one hosting your IVS you'll need to to run the following command on the IVS telling it to respond to PXE requests from these other subnets.
imaging-control subnet add
When prompted for an IP address enter the first IP address in that particular subnet, e.g. 192.168.10.1.
Connecting the IVS to the FileWave Server
Creating the NBI (macOS 10.12 and lower only)
To be able to NetBoot Macs you need to provide a Network Boot Image (NBI) across the network to our macOS clients. This NBI is created using an automated NBI creation script from the IVS that can be downloaded via the FileWave Admin. Install the FileWave Admin app on a macOS client machine running a version of macOS that you can use to boot all of your Macs that will be NetBooted. The NBI will be created from the recovery partition of the machine from which the NBI creation script is run. If the script fails, check that your Mac you're running the script on has a recovery partition. If not then consider running the NBI creation script from another Mac that does have a recovery partition. If you have multiple IVS's with each serving a different subnet, you'll need to download and run the NBI creation script multiple times, once for each IVS, as its address is embedded in the NBI.
The script will be named create_nbi_<IVS_IP_address>.sh. Change the permissions on the script and run it.
cd ~/Desktop sudo chmod 755 ./create_nbi_<IVS_IP_address>.sh sudo ./create_nbi_<IVS_IP_address>.sh