Skip to content

FIDS — FOG Imaging Deployment System

International Recyclers

Revision 3f5 — April 24, 2026 Authored and designed by Jeremy Delk for Scott Industries LLC.

Credentials not stored here

Login credentials for every FIDS component (ProxMox, pfSense, FOG, Cisco Catalyst) are not published on this site. Admins keep them in the internal password manager / on the owner's workstation. Contact Dan or Greg if you need access.

Overview

FIDS is a segmented imaging network that provides controlled PXE booting, OS deployment, and system provisioning without interfering with the primary production network. It boosts device throughput in the eBay department by allowing multiple systems to be imaged, configured, and prepared in parallel.

The system isolates imaging traffic while still allowing controlled WAN access when needed. FIDS is built around a dedicated FOG server, managed routing/switching, and a controlled client staging area for repeatable workflows.

Core Components

Virtualization Host — ProxMox VE

  • LAN IP: 192.168.10.2:8006 (Web UI)
  • WAN IP: 192.168.1.65:8006 (Web UI)
  • Login: see internal credentials store
  • Role: Hosts all virtual infrastructure
    • pfSense
    • FOG
    • General mass storage
  • Access: Web UI via HTTP
  • Notes:
    • Dual-NIC configuration
    • WAN uplink: vmbr0 — NIC 1 (VE) / NIC 2 (device)
    • LAN: vmbr1 — NIC 3 (VE) / NIC 4 (device)

Firewall / Router — pfSense

  • LAN IP: 192.168.10.1
  • Must be managed through the ProxMox VM or through the switch access port (port 2).
  • Login: see internal credentials store
  • Role:
    • DHCP server for PXE client assignment
    • Default gateway for PXE clients
    • Network segmentation between WAN and LAN
  • Responsibilities:
    • Provision dynamic IP assignment to all clients on the network
    • Keep PXE clients separate from the primary network
    • Route outbound traffic for internet access
  • Key behavior: Imaging network operates independently unless explicitly routed.

Imaging Server — FOG Project

  • Management URL: http://192.168.10.101/fog/management
  • Must be managed through the ProxMox Web UI or the switch access port (port 2).
  • Web login + user login: see internal credentials store
  • OS: Debian (FOG-Debian user environment)
  • Role:
    • PXE boot server
    • Image storage and deployment
    • Host management and inventory
  • Services provided:
    • PXE boot
    • TFTP
    • NFS / FTP
    • Web UI management
  • Storage path: /images/

Network Switching — Cisco Catalyst 3850

  • Login: see internal credentials store
  • Role:
    • Layer 2/3 switching for imaging
    • Future station deployments and expansion
    • Can isolate imaging from VLAN if needed
    • Dedicated access port for system management
  • Notes: Supports PoE and SFP+ for future expansion.

Networking Architecture

Segment Purpose Subnet
WAN External / internet / production 192.168.1.0/24
LAN Imaging network / eBay 192.168.10.0/24

Switch Layout

Ports 1–12

1 (FROM_SERVER) 2 (ACCESS) 3 4 5 6 7 8 9 10 11 12
FROM_SERVER PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT

Ports 13–24

13 14 15 16 17 18 19 20 21 22 23 24
PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT PXE_CLIENT GEN_NET

Ports 25–48 — CLOSED (reserved for future expansion).

  • Port 2 is the management access port for direct switch/pfSense/FOG access.
  • Port 24 breaks out to the general network (GEN_NET).

FIDS Image Update — Procedure

Build a hardware-neutral base image that boots on any platform. Perform this after every major security update.

  1. Use a USB stick with an up-to-date Windows ISO.
  2. Use a relatively modern device (within the last 5–7 years).
  3. The device must be at the welcome screen when the process finishes — the end user must agree to Microsoft's EULA themselves.
  4. Do not run or start the Microsoft Store.
  5. Ensure storage media is not partitioned. (See note below.)
  6. Boot the device into BIOS with the flash drive inserted.
    • Enable PXE Boot.
    • Turn Secure Boot OFF.
    • Set the USB boot device at the top of the boot priority list.
    • Turn Fast Boot OFF if available.
  7. Continue through the initial Windows setup.
  8. Press Ctrl + Shift + F3 (hold Fn on some devices) to enter Audit Mode.
  9. Connect to Ethernet and fully update Windows. Reboot as many times as needed to install all updates, including optional ones.
  10. Run sysprep:
    • It is usually already running. If not, open CMD as Administrator: 
      cd sysprep
sysprep.exe
    • Check Generalize and click Run.
  11. Restart with shutdown -r /t 0.
  12. Capture the image with FOG:
    • Ensure Ethernet connection.
    • PXE boot (enable in BIOS; set NIC IPv4 at top of boot priority).
    • Register the device — this is required for the next step.
    • Assign & capture: Host → Select Registered Machine → Select OS to Capture → Tasks → Task Capture Image → task assignment should show Successful.
    • Boot the device in PXE — it should start capturing the image.

Partition note

Clearing partitions normally isn't strictly required, but it prevents conflicts with BitLocker or other pre-existing formatted partitions.

Image a Machine With FIDS — Procedure

Imaging a system with FIDS greatly improves throughput for eBay sales and installs an up-to-date OS with all security updates, reducing prep time.

  1. Ensure storage media is not partitioned. (See note above.)
  2. Press the manufacturer's BIOS key immediately after startup.
  3. Enable PXE Boot.
  4. Set Secure Boot OFF.
  5. Set Fast Boot to Auto or Off.
  6. Ensure Ethernet connection to the network.
  7. Boot the device.
  8. Press the boot menu hotkey (e.g. F10 on Dell).
  9. Select PXE Boot IPv4.
  10. Wait for the PXE FOG menu to appear. (See note below.)
  11. Quickly tap the down arrow once PXE begins logging, then repeatedly tap down once the PXE menu appears.
  12. Select Register & Inventory — makes the machine visible on the FOG network.
  13. Select Image.
  14. Select your image from the screen — quickly: FOG gives you exactly 5 seconds before defaulting to the top entry.
  15. FOG login prompts for credentials — see the internal credentials store.

Failsafe BIOS

Sometimes FOG will roll over into a failsafe BIOS. Reboot the device if this happens.

Get Machine Specifics Without a Local Account — Procedure

Used to gather device specifics without interfering with OOBE, and to confirm functionality before listing.

  1. Boot the machine into the Windows Manager.
  2. Press Ctrl + Shift + F3 (with Fn on some devices).
  3. Gather device specifics:
    • CPU
    • RAM
    • SSD storage
    • Battery health
    • Update status (see note below)
  4. Ensure functionality — see the Functionality Process Manual.
  5. Run sysprep:
    • It is usually already running. If not: 
      cd sysprep
sysprep.exe
    • Check Generalize and click Run.
  6. Reboot and confirm the OOBE menu appears.

EULA integrity

The end user must accept the EULA on OOBE — it must remain intact until the end user acquires the device.

Security updates

If there are security updates queued, an image update on the FOG server is required before continuing.