Fortinet distributes its virtual appliances as pre-packaged images for various hypervisors. The .out.kvm.zip package is the standard deployment format for KVM. When you download and extract the file referenced in the keyword, you should find a single, crucial file inside: the . This .qcow2 file contains the entire operating system and FortiAnalyzer software.
4 CPUs, 8 GB RAM, and 500 GB disk storage (typical for v6.x) How to Deploy the KVM Package
Step 2: Define the Domain via CLI or Virtual Machine Manager fazvm64kvmv6build1183fortinetoutkvmzip
Note that build1183 would date back to FortiAnalyzer version (circa 2016–2017). If you are looking for modern features (SD-WAN monitoring, compliance packs, AI-based analytics), you should target version 7.0 or higher.
: If you are using this specific build to recover an old backup or migrate a legacy node, check the official Fortinet Training and Support portal to find the supported step-by-step upgrade path (e.g., upgrading from 6.2.2 →right arrow →right arrow →right arrow : If you are using this specific build
This specific file corresponds to , released on October 25, 2019 . It is an older, legacy version of the software, as FortiAnalyzer has since moved through several major releases including 6.4, 7.0, and 7.4. Version: 6.2.2 Build Number: 1183 Platform: KVM
The deployment involves extracting the package, configuring the virtual machine, and initializing the appliance. 1. Download and Extract Moving Off Build 1183
Short for FortiAnalyzer , Fortinet’s centralized logging and compliance platform.
: FortiGate appliances running newer releases (such as FortiOS 7.0.x, 7.2.x, or 7.4.x) will fail to establish secure log channels with an instance running Build 1183. Moving Off Build 1183