|
- Windows
- Windows 7 32/64-bit with KB2999226 and KB2533623 updates installed
- Windows 8/8.1 32/64-bit with KB2999226 update installed
- Windows 10 32/64-bit
- Windows 11 64-bit
- Windows Server 2008 R2 SP1 64-bit (Standard editions) KB2533623 and with KB2999226 installed.
- Windows Server 2012 64-bit & Windows Server 2012 R2 64-bit with KB2999226 update installed
- Windows Server 2016 64-bit
- Windows Server 2019 64-bit
- Windows Server 2022 64-bit
- Home editions of Windows are not supported.
- Windows 10 Embedded (Windows IoT) is not supported.
- Windows Server 2016 64-bit, Windows Server 2019 64-bit, and Windows Server 2022: The PCSM agent will work on Server Core with limited remote takeover capabilities.Windows Server 2022 64-bit.
- macOS
- The PCSM agent has been certified on macOS Monterey and macOS Ventura.
- Limited support for macOS Catalina 10.15 and macOS Big Sur 11.0 (including ARM M1 processors) is included.
- If not already installed, Rosetta 2 is required for M1 macOS support.
- The Systems Management Agent requires that a full runtime version of an open source tool set called Mono is installed on each macOS device. Supported Mono versions: Mono 4.8 and later. If Mono is already installed on the device, the installation script will not attempt to install it. However, if the already installed Mono version is not supported, the Agent will not work.
- Linux
- The PCSM agent requires Mono libraries (mono-devel package) version 4.8 and higher. If Mono is not installed on the device, the installation script will download and install it automatically. However, if Mono is already installed on the device, and the installed version is not supported, the PCSM agent will not update it and will not work. You can install Mono manually from EPEL.
- The PCSM agent can be installed and may function as expected on other operating systems that are not listed in this document. However, support is only provided for the operating systems outlined above.
- Fedora: Version 33 and higher with yum-utils package.
- Debian: Version 10 and higher with libicu-dev, libssl-dev, libcurl4, and yum-utils packages
- CentOS: Version 7 and higher with libicu package.
- Ubuntu: Version 18.04 and version 20.04 and higher with libicu-dev and libssl-dev packages.
- Red Hat Enterprise Linux: Version 7 and higher.
Administration requirements for VMWare ESXi
VMware servers are managed via devices with the Network Node role. It is not necessary that the Network Node device resides on the same subnet as the ESXi server.
- The account used to connect to the ESXi server must be a root account.
- We recommend that the device designated as a Network Node to monitor the ESXi server does not reside on the ESXi server.
- The Network Node device must run on a Windows operating system.
- It must have Microsoft .NET Framework version 4.7 or higher.
- It must not be hosted on an ESXi server targeted for monitoring.
Panda Systems Management supports ESXi versions 4.1, 5.0, 5.1, 5.5, 6.0, 6.5, 6.7, and 7.0.
In the case of VMware ESXi 6.5 and later versions, you need to establish an SSH connection in order to enable CIM access.
- Enable the SSH service on the ESXi server.
- Make an SSH connection to the ESXi server. Use PuTTY or a compatible program.
- Run the following commands:
esxcli system wbem set --enable true
/etc/init.d/sfcbd-watchdog start
Internet Protocol
The PCSM Agent communicates with the platform using the IPv4 protocol.NOTE: IPv6 connections are not supported at this time.
Related information
Consider reviewing the following Support articles:
