Secure Windows Imaging with FileWave IVS

What

Secure Imaging carries Windows imaging data between the device and the Imaging Virtual Server (IVS) through a VPN tunnel on TCP/UDP port 20490. Standard Imaging mounts NFS directly on TCP/UDP port 2049. FileWave introduced the secure mode in 15.5.0. On an IVS installed with FileWave 16.2.0 or later, it is disabled by default; an IVS upgraded from an earlier release may still have it enabled.

When/Why

When to Use

Enable Secure Imaging when image data needs protection in transit, especially when capturing devices that already contain user data. Standard Imaging avoids the tunnel overhead and can provide better throughput on an isolated imaging network. Choose one mode deliberately, account for the current state of upgraded IVS appliances, and align the network firewall with that mode.

How

Enabling Secure Imaging

On FileWave 16.2.0 and later, enable Secure Imaging on the IVS, then reboot:

sudo imaging-control enable secure-mount
sudo reboot

Disabling Secure Imaging

To use Standard Imaging instead, disable Secure Imaging on the IVS, then reboot:

sudo imaging-control disable secure-mount
sudo reboot

Firewall and verification

• Allow TCP and UDP 20490 from imaging client subnets to the IVS when Secure Imaging is enabled.
• Allow TCP and UDP 2049 from imaging client subnets to the IVS when Standard Imaging is enabled.
• Open the required port before changing modes. After the IVS reboots, run a controlled capture or deployment and confirm expected throughput before using the change for a large imaging batch.

Related Content

• Setting up the IVS (Imaging Virtual Server)
• Imaging Speed Test for IVS Performance Verification