Preparing for deployment
This documentation assumes that before deploying the FortiProxy‑VM on the Microsoft Hyper‑V virtual platform, you have addressed the following requirements:
Virtual environment
|
For best performance, install FortiProxy‑VM on a “bare metal” hypervisor. Hypervisors that are installed as applications on top of a general-purpose operating system (Windows, Mac OS X, or Linux) host and have fewer computing resources available due to the host OS’s own overhead. Hardware-assisted virtualization (VT) must be enabled in the BIOS. |
You have installed the Microsoft Hyper‑V software on a physical server with sufficient resources to support the FortiProxy‑VM and all other VMs deployed on the platform.
If you configure the FortiProxy‑VM to operate in transparent mode, or include it in an high availability (HA) cluster, configure any virtual switches to support the FortiProxy‑VM's operation before you create the FortiProxy‑VM.
|
VM Environment |
Tested Versions |
|---|---|
|
Hyper-V |
Hyper-V Server 2008 R2, 2012, 2012R2, 2016, and 2019 |
Management software
If you plan to use the GUI to manage the Microsoft Hyper‑V server remotely, ensure that the management software is installed on a computer with network access to the Hyper‑V server.
Options for remote management of Microsoft Hyper‑V include:
|
Platform |
Management software |
|---|---|
|
Open Microsoft Hyper‑V |
Virtual Machine Manager |
|
Citrix Microsoft Hyper‑V Server |
Microsoft Hyper‑VCenter |
Connectivity
The FortiProxy‑VM requires an internet connection to contact FortiGuard to validate its license.