Palo Alto Networks has fundamentally changed how users deploy Expedition. While it was previously available as a pre-built virtual appliance, the official OVA has been deprecated. Modern installations now require manually setting up a base Ubuntu server and running an installer script. Preparation & System Requirements
Before starting, ensure your hypervisor (VMware ESXi, Workstation, or Fusion) meets the following minimum specifications:
Operating System: Ubuntu 20.04 LTS (64-bit AMD). Do not use Ubuntu 22.x, as it is currently unsupported by the installer.
CPU: 4 Cores (8 Cores recommended for Machine Learning features). RAM: 8 GB (16 GB or more for large-scale log analysis). Storage: 40 GB minimum (SSD preferred). Step 1: Download & Provision the Base OS
Since a direct OVA is no longer provided, you must first create your own Virtual Machine:
Download the Ubuntu Server 20.04 LTS ISO from the official Ubuntu website.
In your hypervisor, create a new VM and attach the ISO to begin the installation.
Follow the standard prompts to install Ubuntu. Ensure the VM has internet access to download necessary dependencies during the next step. Step 2: Install Expedition via Script
Once your Ubuntu server is ready and you have logged in, use the following steps to install the Expedition software:
Download the Installer Script:Use wget to pull the latest installer directly to your server:
wget https://conversionupdates.paloaltonetworks.com/expeditionInstaller.tgz Use code with caution. Copied to clipboard
(Note: If the above link is inactive, check the latest documentation on Palo Alto LIVEcommunity for updated repository links.)
Extract and Run:Unpack the file and execute the script with root privileges: tar -zxvf expeditionInstaller.tgz sudo ./install.sh Use code with caution. Copied to clipboard
The script will automatically install required components like MariaDB, Apache, and RabbitMQ. Step 3: Initial Access & Configuration
Web Interface: Open a browser and navigate to https://.
Default Credentials: The initial login for the web UI is typically admin / paloalto (though you should change this immediately upon first login).
Updates: Once logged in, navigate to Settings > Software Updates to ensure you are running the latest hotfix, such as version 1.2.102. Important Support Notice
Palo Alto Networks has deprecated the official standalone OVA Expedition . The current supported method is to Ubuntu Server 20.04 LTS (64-bit AMD) and run an installer script to deploy the application Palo Alto Networks LIVEcommunity Current Installation Steps Deploy Ubuntu VM : Download the Ubuntu 20.04 LTS Server ISO and install it on your hypervisor. Download Installer : On the Ubuntu VM, download the Expedition installer script Run Script
: Unpack and execute the script to install the Expedition application and its dependencies (MariaDB, Apache, etc.). tar -zxvf expedition1_Installer_latest.tgz Palo Alto Networks LIVEcommunity System Requirements
To ensure stability, provision your VM with the following minimum resources: Palo Alto Networks LIVEcommunity : 8 Cores (especially for 6+ firewalls) : 16–32 GB : 500 GB (SSD recommended) Legacy & Community OVA Options
If you specifically need an OVA file for a lab environment, there are unofficial or legacy community-provided versions: Community OVA
: A popular community-maintained OVA is available through the LIVEcommunity discussions , though it may be outdated. Support Portal
: Official software updates for registered devices can be found on the Palo Alto Customer Support Portal (CSP)
, though Expedition-specific OVAs are no longer the primary delivery method. Palo Alto Networks LIVEcommunity
Need OVA file for Expedition to install on VMware. Please help!
Note: You will need a valid Live Community account to access the files. 2. Import to Hypervisor VMware ESXi Workstation File > Deploy OVF Template Browse to the downloaded file and follow the import wizard. Resources: Ensure you allocate at least 100GB Disk for stable performance. 3. Initial Configuration Power on the VM and log in with the default credentials expedition static IP address using the standard Ubuntu networking commands ( ) to ensure the web interface remains accessible. 4. Access the Web UI Open your browser and navigate to:
Once upon a time in a bustling network security operations center, a junior engineer named Alex stared at a blinking cursor. The challenge: migrate a tangled mess of legacy firewall rules into a clean Palo Alto Networks policy. The answer, everyone said, was Expedition—a migration tool that lived inside an OVA.
Alex’s search began: “download palo alto expedition ova install”.
Access the Palo Alto Support Portal
https://support.paloaltonetworks.comNavigate to Software Updates
Locate Expedition
Choose the Correct Version
expedition_1.2.5, expedition_1.3.0). Always download the latest stable release unless you have legacy compatibility needs.Expedition-<version>-vm.ova
Example: Expedition-1.3.0-vm.ovaDownload the OVA
.md5 or .txt file). This verifies the integrity of your download.Troubleshooting Download: If you cannot find Expedition, use the search bar inside the support portal and type "Expedition download". Direct links often change, so relying on search within the portal is safest.
If you plan to migrate >10,000 rules or objects:
| Feature | Description | |---------|-------------| | One-click download | Embed secure session to fetch OVA directly | | Auto-deploy | Detect hypervisor and deploy with default settings | | Health check | After boot, validate all services (MongoDB, Redis, Celery) | | Snapshot & backup | Create initial clean snapshot after setup | | Version rollback | Download and deploy older Expedition versions |
Browser → https://<static-ip>:8443. Self-signed cert warning? Accept. The Expedition dashboard loaded. Alex changed the default password, uploaded a config backup from the old Check Point gateway, and let Expedition parse, normalize, and suggest App-ID–based rules.
Console output scrolled, then stopped at a login prompt. Alex used the default credentials (expedition/expedition) from the docs. A quick ip addr showed DHCP had failed—so they set a static IP via nmtui.
VBoxManage import Expedition.ova --vsys 0 \
--vmname Expedition \
--memory 8192 \
--cpus 4
Palo Alto Networks has fundamentally changed how users deploy Expedition. While it was previously available as a pre-built virtual appliance, the official OVA has been deprecated. Modern installations now require manually setting up a base Ubuntu server and running an installer script. Preparation & System Requirements
Before starting, ensure your hypervisor (VMware ESXi, Workstation, or Fusion) meets the following minimum specifications:
Operating System: Ubuntu 20.04 LTS (64-bit AMD). Do not use Ubuntu 22.x, as it is currently unsupported by the installer.
CPU: 4 Cores (8 Cores recommended for Machine Learning features). RAM: 8 GB (16 GB or more for large-scale log analysis). Storage: 40 GB minimum (SSD preferred). Step 1: Download & Provision the Base OS
Since a direct OVA is no longer provided, you must first create your own Virtual Machine:
Download the Ubuntu Server 20.04 LTS ISO from the official Ubuntu website.
In your hypervisor, create a new VM and attach the ISO to begin the installation.
Follow the standard prompts to install Ubuntu. Ensure the VM has internet access to download necessary dependencies during the next step. Step 2: Install Expedition via Script
Once your Ubuntu server is ready and you have logged in, use the following steps to install the Expedition software:
Download the Installer Script:Use wget to pull the latest installer directly to your server: download palo alto expedition ova install
wget https://conversionupdates.paloaltonetworks.com/expeditionInstaller.tgz Use code with caution. Copied to clipboard
(Note: If the above link is inactive, check the latest documentation on Palo Alto LIVEcommunity for updated repository links.)
Extract and Run:Unpack the file and execute the script with root privileges: tar -zxvf expeditionInstaller.tgz sudo ./install.sh Use code with caution. Copied to clipboard
The script will automatically install required components like MariaDB, Apache, and RabbitMQ. Step 3: Initial Access & Configuration
Web Interface: Open a browser and navigate to https://.
Default Credentials: The initial login for the web UI is typically admin / paloalto (though you should change this immediately upon first login).
Updates: Once logged in, navigate to Settings > Software Updates to ensure you are running the latest hotfix, such as version 1.2.102. Important Support Notice
Palo Alto Networks has deprecated the official standalone OVA Expedition . The current supported method is to Ubuntu Server 20.04 LTS (64-bit AMD) and run an installer script to deploy the application Palo Alto Networks LIVEcommunity Current Installation Steps Deploy Ubuntu VM : Download the Ubuntu 20.04 LTS Server ISO and install it on your hypervisor. Download Installer : On the Ubuntu VM, download the Expedition installer script Run Script
: Unpack and execute the script to install the Expedition application and its dependencies (MariaDB, Apache, etc.). tar -zxvf expedition1_Installer_latest.tgz Palo Alto Networks LIVEcommunity System Requirements Palo Alto Networks has fundamentally changed how users
To ensure stability, provision your VM with the following minimum resources: Palo Alto Networks LIVEcommunity : 8 Cores (especially for 6+ firewalls) : 16–32 GB : 500 GB (SSD recommended) Legacy & Community OVA Options
If you specifically need an OVA file for a lab environment, there are unofficial or legacy community-provided versions: Community OVA
: A popular community-maintained OVA is available through the LIVEcommunity discussions , though it may be outdated. Support Portal
: Official software updates for registered devices can be found on the Palo Alto Customer Support Portal (CSP)
, though Expedition-specific OVAs are no longer the primary delivery method. Palo Alto Networks LIVEcommunity
Need OVA file for Expedition to install on VMware. Please help!
Note: You will need a valid Live Community account to access the files. 2. Import to Hypervisor VMware ESXi Workstation File > Deploy OVF Template Browse to the downloaded file and follow the import wizard. Resources: Ensure you allocate at least 100GB Disk for stable performance. 3. Initial Configuration Power on the VM and log in with the default credentials expedition static IP address using the standard Ubuntu networking commands ( ) to ensure the web interface remains accessible. 4. Access the Web UI Open your browser and navigate to:
Once upon a time in a bustling network security operations center, a junior engineer named Alex stared at a blinking cursor. The challenge: migrate a tangled mess of legacy firewall rules into a clean Palo Alto Networks policy. The answer, everyone said, was Expedition—a migration tool that lived inside an OVA.
Alex’s search began: “download palo alto expedition ova install”. Access the Palo Alto Support Portal
Access the Palo Alto Support Portal
https://support.paloaltonetworks.comNavigate to Software Updates
Locate Expedition
Choose the Correct Version
expedition_1.2.5, expedition_1.3.0). Always download the latest stable release unless you have legacy compatibility needs.Expedition-<version>-vm.ova
Example: Expedition-1.3.0-vm.ovaDownload the OVA
.md5 or .txt file). This verifies the integrity of your download.Troubleshooting Download: If you cannot find Expedition, use the search bar inside the support portal and type "Expedition download". Direct links often change, so relying on search within the portal is safest.
If you plan to migrate >10,000 rules or objects:
| Feature | Description | |---------|-------------| | One-click download | Embed secure session to fetch OVA directly | | Auto-deploy | Detect hypervisor and deploy with default settings | | Health check | After boot, validate all services (MongoDB, Redis, Celery) | | Snapshot & backup | Create initial clean snapshot after setup | | Version rollback | Download and deploy older Expedition versions |
Browser → https://<static-ip>:8443. Self-signed cert warning? Accept. The Expedition dashboard loaded. Alex changed the default password, uploaded a config backup from the old Check Point gateway, and let Expedition parse, normalize, and suggest App-ID–based rules.
Console output scrolled, then stopped at a login prompt. Alex used the default credentials (expedition/expedition) from the docs. A quick ip addr showed DHCP had failed—so they set a static IP via nmtui.
VBoxManage import Expedition.ova --vsys 0 \
--vmname Expedition \
--memory 8192 \
--cpus 4
© 2026 Nova Vine Guide. All rights reserved.