Skip to end of metadata
Go to start of metadata

Guide for networking imaging v5 with FileWave


The following Steps will assist you in the setup and implementation of your Imaging Virtual Server (IVS)
If you already have your Imaging sever up and running please look at these guides for how to image macOS and Windows devices.
*Please note: This Document assumes you have already setup your FileWave Management Server.


Prepare and download all needed parts


Before starting be sure you have:

  • Downloaded the latest Imaging Virtual Server (IVS) linked here
  • A running FileWave server with clients enrolled (or with placeholders)
  • FileWave Admin installed on your workstation
  • Valid serial numbers for each macOS machine in FileWave and/or a MAC Address for each Windows machine
  • Virtual Environment (e.g. ESXI, Virtualbox, VMware Fusion)
  • If imaging macOS devices, have access to the same hardware you are wanting to image with a recovery partition
  • No Firewall between your VLANS or access to the Inter-VLAN Firewall to open Ports specified below

IVS v5 capabilities:

  • UEFI compatibility
  • Multiple partitions per image
  • GBT and MBR disks can be imaged
  • Image a blank disk
  • macOS 10.7 - 10.12 (NetBoot supported hardware - including MacBook Pro 11.4+)
  • Windows 7, 8, 8.1, 10 (including non-UEFI, UEFI with CSM and native UEFI machines)
  • Multiple netboot servers allowed on the network
  • Option boot to select FileWave netboot server
  • Check if Windows partition is in hibernated or fast restart state before creating master image
  • Imaging logs are now copied to IVS in order to ease imaging issues troubleshooting

Network Considerations

Subnets

The FileWave network imaging solution is unicast so there will need to be some preparation on your end if you intend to image across multiple subnets. The two options will be:

  1. Install a separate FileWave Imaging Virtual Server (IVS) on each subnet you are planning to image from and connect them all to the FileWave server by following the "Connecting IVS to FileWave Server" section in this document.
  2. Setup "Helper IPs" on your layer 3 devices (e.g. routers, routing switches) that will point the broadcast requests for PXE and Netbooting to your single FileWave IVS. Once this has been completed you will need to make a change on the IVS. To do this either open the console for this server in your virtual environment or ssh into the server with Putty (Windows) or terminal (macOS):
    1. Open terminal (If on Windows you can use Putty linked here and use the credentials root/filewave then skip to step 3 below)
    2. Type in the following command

      replace IVS-IP-Address with the IP the IVS
      ssh root@IVS-IP-Address 


      when prompted for a password use: filewave

    3. Then type in this next command to add subnets

      Imaging-control subnet add
    4. This will prompt for a valid IP address from the subnet and subnet mask
      Note: use command imaging-control subnet remove to remove a subnet

terminalsubnetadd puttysubnetadd

Firewall

The IVS needs to be able to connect to your FileWave Server on the following Ports

  • 20015
  • 20017
  • 20443
  • 20445

Any client(s) subnets where imaging should work must be able to reach the following Ports on the IVS:

  • 67 (DHCP), 69 (TFTP), 80 (HTTP), and 20444 (HTTPS)
  • Ports 111 (TCP,UDP) and 2049 (TCP,UDP) are used for NFS access

Any machine running FileWave Admin needs to be able to connect to your IVS on the following Ports:

  • 20010 (Client Monitor), 20444 (Remote Configuration, Shared Keys)

Starting the Imaging Appliance for the first time:

  1. Download the latest Imaging Virtual Server (IVS) linked here
  2. Import the Imaging Virtual Appliance (IVS) into your virtual environment or use a player to start up the machine. Note: If you need help on this please use the help guide linked here
  3. When the server starts up it will display the IP address, be sure to make a note of this. Should the machine get stuck during boot, showing a white bar at the bottom please send a CTRL-ATL-DEL to the machine. The second boot should be much quicker.
  4. It is recommended that you log into the machine (either console or SSH) and change the default password from what is currently filewave to your own.
    1. Open terminal (If on Windows you can use Putty linked here and use the credentials root/filewave then skip to step 3 below)
    2. Type in the following command

      ssh root@IVS-IP-Address 


      when prompted for a password use: filewave

    3. Then type passwd
    4. Enter new password


      IVSsetup-passwordchange

  5. Next, change the IP address of the Imaging Virtual Appliance (IVS) to a static IP. If you are not using a DHCP reservation then run the following command on the Imaging Virtual Appliance. 
    imaging-control networksetup static

    Follow the prompts:
    1. Enter a valid IP
    2. Enter a valid subnet mask
    3. Enter a valid gateway
    4. Enter a valid DNS IP
  6. You will be asked to confirm your changes at the end and the network server will restart.
    Note: If you ssh into the server with terminal or putty then change the IP address, you will need to reconnect because the your current connection will be lost.


    IVSsetup-staticnetwork


Connecting IVS to the the FileWave Server:

  1. Open and connect your FileWave Admin to your FileWave server
  2. Open the preferences and go to the "Imaging" tab
  3. Hit the "+" at the bottom left of the blank pane


    IVSsetup-adminprefsplussign

  4. Enter the IP address of the IVS into "Preference for Imaging"
  5. Make sure the box marked "generate new key" is now checked and click "OK"


    IVSsetup-newserver

  6. When the Imaging Monitor opens specify your FileWave Server Address and Port 20015. Confirm by clicking "Ok" to finish configuration of your IVS.


    IVSsetup-ivsprefs

  7. Restart the Imaging Virtual Server (IVS)
  8. Open the preferences and go to the "Imaging" tab again
  9. Select the server in the pane and click the status button below. Status lights should be all green with the exception of "NBI for macOS Imaging:" (If there are more red lights and clicking the refresh button doesn't help, please contact support)


    IVSsetup-ivsstatus

  10. If you are wanting to image macOS devices, type in the following command in terminal on an identical machine as you are wanting to image, repleaceing the IP_of_IVS with the actual IP address if your imaging server:

    curl -k https://IP_of_IVS:20444/imaging/osx/get_nbi_creator_script/ > create_nbi.sh && sudo sh create_nbi.sh

    This will download, run the NBI script, and upload to the FileWave Imaging server automatically. This has to be ran for every IVS you create. 
    *Troubleshooting: If you get a different machine from what the NBI was created on and it is not imaging, try to run the NBI on that machine and image again. 



Congratulations, you have successfully setup and configured your FileWave Imaging server! You are now ready to image macOS and Windows devices with the help of these guides: 

  • No labels