Operating systems

Refer to the Product life cycle guide to find out more on compatibility with Microsoft Windows versions.

Processors for physical machines
  • 32-bit processors: at least Intel Pentium 4 2 GHz or the equivalent,
  • 64-bit processors: at least Intel Pentium 4 2 GHz with x86-64 support or the equivalent.

Itanium processors are not supported.

Processors for virtual machines

At least one virtual socket and one 1 GHz core per socket. Stormshield recommends one virtual socket and two 2 GHz cores per socket.

Physical memory At least 1 GB. Or more if the operating system requires it. Stormshield recommends 2 GB.
Disk space
  • At least 100 MB for installation,
  • At least 200 MB for data storage.

These are the disk space requirements for the NTFS file system. More space will be needed for updates and logs.

Network configuration
  • Outgoing communication:
    • TCP 17000 (RPC)
Network bandwidth At least 12 Kbit/s. Lower bandwidth may prevent the agent and agent handler from exchanging data.
Software Framework .NET 4.6.2 or higher.
Display At least 1024X768.

VeriSign Universal Root Certification Authority certificate installed to verify the authenticity of SES Evolution updates.
It must be installed in the Trusted Root Certification Authorities or Third-party Root Certification Authorities certificate store.

You can download it directly in your MyStormshield client area, under Downloads > Stormshield Endpoint Security > Evolution > Resources. With the .bat file in the archive, the certificate can be automatically installed in the certificate store with an administrator account.

Using agents on Microsoft Windows Server Core operating systems

SES Evolution agents can be installed on Windows Server Core 2012 R2, 2016, 2019 and 2022 operating systems.

These operating systems have a reduced graphical interface. The agent's interface does not start automatically when a user session is opened (agent icon icon in the task bar on a 'standard' operating system). To display the agent’s GUI:

In addition, if requests for user confirmation are configured in a security rule, the agent will not open any window, automatically assuming that the answer to the confirmation is "no". There is no way for the user to reply with a "yes".