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 computers. The IVS is a Linux virtual appliance that you can import into VMware, Hyper-V, or VirtualBox.
Because of the complexity of network imaging, the IVS is not normally accessible to evaluation customers. If you would like to test FileWave's network imaging capabilities during the course of your evaluation please engage your FileWave SE to request access and for assistance in setting it up.
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.
- Put an IVS on every subnet that you may need to reimage clients on.
- Configure IP helpers on the routers for every subnet that you may need to reimage clients on.
- Windows clients only - Set DHCP scope options for every subnet that you may need to reimage clients on.
If you choose either of the last 2 options 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 network 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.
- There is nothing else using PXE or NetBoot on your network.
- DHCP is enabled on the network segment where your Windows reference computer and client computers reside.
- You are creating clean images using OS installation media from the OS vendor and not using the hardware manufacturer installed OS configuration.
- You must set aside a static IP address for the IVS.
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)
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
- Import the IVS Linux virtual appliance into your virtualization software of choice. Some basic instructions are available in the Server & Admin Installation section. Instead of importing the FileWave Server virtual appliance import the IVS virtual appliance instead. If your VM host is VMware ESXi 6.5+ please take a look here for info on how to import the IVS via the VMware HTML 5 web client.
- Note that the IVS has 2 virtual NICs and both of them need to be enabled.
- The VHD version of the IVS is only compatible with Hyper-V on Windows 2012 R2 and higher.
date -s HH:MM
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
- Log into the FileWave Server with the FileWave Admin console.
- Open the preferences, go to the Imaging tab, and click the plus sign on the left.
- Enter the static IP address of the IVS into the Server Address field, ensure that Generate new key on Save is checked, wait for the red dot next to the Port field to turn green, and click OK.
- Click OK again to close the Filewave Admin Preferences window.
- Open the preferences again and return to the Imaging tab.
- Select the your IVS and click the Status button. The status lights should be all green with the exception of NBI for macOS Imaging. If there are more red dots or all status dots are yellow then close all preference windows, wait 5 minutes and check again. If the any of the other status dots except for "NBI for macOS imaging" remain red after 10 minutes, please contact your assigned FileWave SE for assistance.
Creating the NBI
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 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.
- Open the FileWave preferences, go to the Imaging tab, select the IVS you are going to boot your clients from, and click the Download NBI file button. Save the NBI creator script to your desktop.
- The script will be named create_nbi_<IVS_IP_address>.sh. Change the permissions on the script and run it.
sudo chmod 755 ./create_nbi_<IVS_IP_address>.sh