Where can you get the Fudo Enterprise installation image?

This is one of the first questions that comes up during testing and deployment.

The Fudo Enterprise installation image can only be obtained through an authorized Fudo partner. If you want to start testing the solution, contact us at infoprotector@infoprotector.pl – we will prepare the image for you and help you go through the first deployment steps.

This is the simplest way if you want to launch a test environment, demo, or PoC and immediately see what the first Fudo Enterprise implementation in VMware looks like.

What does the video show?

The video walks through the first technical stage of deploying Fudo Enterprise in a virtual environment. We show the import of the ready-made OVA image into VMware and the basic elements that need to be configured along the way.

In this material, you will see:

• where the installation image comes from,
• in what format the appliance is delivered,
• how to begin creating a machine from an OVF/OVA file in VMware,
• how to check whether the correct file has been selected,
• how to indicate the installation location and resources,
• how to assign a network to the machine,
• what happens after the import is completed.

The video ends at the stage where the machine has been successfully imported into the VMware environment and is ready to be started and moved on to the next configuration steps.

First installation of Fudo Enterprise in VMware – step by step

1. Receiving the image from a partner
   The process begins by obtaining the installation image from an authorized partner. In this scenario, we work with a ready-made appliance image prepared for deployment in a virtual environment.

This is important because Fudo Enterprise is not installed here like a regular application. Instead of building the environment from scratch, we import a ready-made image.

2. Importing the OVA image
   The installation image is provided in OVA format, which is a convenient format for deploying ready-made appliances in virtual environments. This makes the first installation simpler and faster, because there is no need to manually create the entire machine from scratch.
3. Logging in to VMware and creating a new machine
   In the next step, we log in to VMware and begin creating a new virtual machine from an OVF/OVA file. We then select the correct image file and make sure that we are choosing the correct release.

This may seem like a detail, but it is very important – already at this stage it is worth checking whether we are working with the correct appliance version.

4. Selecting the installation location and resources
   Next, we indicate the installation location and the resources the machine will use. This is the moment when we prepare the environment for the next system startup stage.
5. Network configuration
   The next step is assigning the network to which the virtual machine will be connected. In a simple test scenario, one network interface is fully sufficient to move on to the first startup and further testing.
6. Importing the appliance into the hypervisor
   After confirming the settings, VMware imports the image and creates the ready virtual machine. This is where the first stage of deployment ends – the machine is now ready to be started and further configured.

What is worth knowing before the first installation?

If you want to launch Fudo Enterprise for the first time, it is worth remembering a few practical points:

• the installation image can only be obtained through an authorized Fudo partner,
• if you want to test the solution, contact us at infoprotector@infoprotector.pl,
• the image is delivered as a ready-made appliance, so there is no need to build the environment from scratch,
• before importing, it is worth making sure that you are selecting the correct release file,
• from the very beginning, it is worth having the network and the basic VM resources prepared,
• after the import is completed, the environment is ready to start, but this does not yet mean that the full configuration is finished.

Environment requirements for Fudo Enterprise

In Fudo’s official documentation, the vendor provides virtual machine requirements depending on the planned number of concurrent sessions. For 100 concurrent sessions, the recommendation is 6 CPU cores at 3.60 GHz, 32 GB RAM, and 24 TB of data storage. For 200 concurrent sessions – 20 CPU cores at 2.40 GHz, 64 GB RAM, and 96 TB of storage. For 300 concurrent sessions – 28 CPU cores at 2.60 GHz, 128 GB RAM, and 288 TB of storage. The vendor also lists target virtualization environments such as VMware Tools, VirtualBox, Proxmox, Hyper-V, and in newer documentation also Azure.

It is worth remembering that these values apply to target environments and real workloads. The vendor notes that these assumptions were calculated for an environment in which 30% of sessions are FullHD 32-bit graphical sessions and 70% are terminal connections, while disk space was estimated based on an average of 50 sessions per day, of which 70% are RDP FullHD 32-bit and 30% are SSH.

For testing, demo, or a simple PoC – as shown in the video – it is of course possible to run a smaller machine than the configurations recommended for production environments. Such a setup works well when the goal is to become familiar with the interface, perform the first deployment, verify how the solution works, and go through the basic configuration. However, it should be treated as a test environment, not a target production deployment. This conclusion follows from comparing the vendor’s official requirements with the purpose of a lightweight test environment.

From the perspective of the first startup, the basic network requirements are also important. The documentation states that system administration is performed over 443/TCP, administrative SSH connections use 65522/TCP, and by default 22/TCP and 3389/TCP are also used at startup. In addition, the system requires correct time configuration and the ability to handle user connections to Fudo and from Fudo to target systems.

Why is this deployment model convenient?

Importing a ready-made image into VMware simplifies the first contact with the solution. Instead of manually installing the system and building the environment step by step, you can move directly to deploying the appliance and preparing the environment for further work.

This approach offers several practical benefits:

• it reduces the time needed to get started,
• it simplifies the first deployment,
• it makes it possible to prepare a test environment more quickly,
• it organizes the entire deployment process,
• it makes it easier to move on to the next configuration stages.

Summary

If you want to see what the first installation of Fudo Enterprise in VMware looks like, this material walks you through exactly that stage – from the image received from a partner, through importing the OVA file, to a ready virtual machine prepared for startup.

If you are planning Fudo Enterprise tests and need the installation image, contact us at infoprotector@infoprotector.pl. As an authorized partner, we will help you obtain the image, prepare the environment, and go through the first deployment steps