Empirum 24.0.x - System Requirements
Preface
The system requirements below are the minimum requirements for a Matrix42 Empirum v24.0 .xinstallation. Since each customer has individual requirements regarding the number of clients, the work processes and infrastructure, these standard requirements should be deemed guidelines to be used for customer-specific implementation concepts. Requirements relevant for the respective customer installation are dependent on factors such as the following:
- Number of objects in the database
- Number of depot servers in use
- Number of concurrently used management consoles
- Number of packages and operating system versions to be distributed
- Frequency of distributions or operating system installations
- Used functionality
Please refer to the corresponding documents for the system requirements of the Software Asset und Service Management components.
The Matrix42 Empirum v24.0.x release will support all operating systems listed in this document on a 32-bit processor architecture (Intel architecture 32-bit or i386) and a 64-bit processor architecture (AMD64). Other processor architectures (e.g., IA-64, ARM...) will only be supported if explicitly stated accordingly.
- There is NO support for Microsoft Windows operating systems such as the so-called Starter or Home Editions (e.g., Windows 7 Home etc.).
- There is no NO support for Microsoft Core-variants such as Hyper-V Core as the Empirum Master Server.
- There is ONLY support for 64-bit databases (Microsoft SQL).
Only German and English systems are supported as Empirum Master Server and SQL Server.
Important notes regarding the installation of the Microsoft SQL Server
Permissions and access rights
- For the initial creation of Empirum databases (EmpLocations, location database) in an instance the server right CREATE ANY DATABASE or the role dbcreator is required.
- Read access is required for the registry of the SQL server (to scan information from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQLServer).
- Only the dbo role (Database Owner) is required to update the database.
- The SQL role securityadmin is required for creating and editing users in DBUtil.
Collation
- The following setting is required for SQL database collation: Latin1_General_CI_AS
- From SQL Server 2022 the following setting is required: Latin1_General_CP1_CI_AS
Option case sensitive
- The “case-sensitive” option must not be activated when installing Microsoft SQL Server 2017 / 2019 / 2022!
- If “case-sensitive” is activated on an existing server and the EmpLocations database is created on this server, it is not possible to log into this database!
- No additional location databases can be created!
Compatibility level
- The compatibility level of the SQL database must match the SQL server version in use. This also applies for the server’s master DB. Inconsistencies might occur with imported databases and SQL server updates. Please use the sql command perform a check on the SQL server, if necessary:
SELECT NAME, COMPATIBILITY_LEVEL FROM SYS.DATABASES WHERE NAME = 'master'
- For SQL Server 2017, the value must be 140, for SQL Server 2019, the value must be 150 and for SQL Server 2022, the value must be 160. If this is not the case, you can modify the value with the following command:
ALTER DATABASE master SET COMPATIBILITY_LEVEL = 160
When using SQL Server 2019, at least SQL Server 2019 Cumulative Update 2 (CU2) must be installed!
Option "case sensitive" enabled or not
How can I find out on an existing SQL server if the option "case sensitive" is enabled or not?
Start the following query via the Query Analyzer:
Exec sp_helpsort
The following result should be displayed (extract):
... case insensitive
Used Ports and Access to the Internet
Used ports
Matrix42 Empirum requires various ports to communicate with the managed devices and to connect the consoles to the database or the server’s file system. A detailed list can be found in the online help (Manuals > Ports).
Internet access
Some services require access to Internet resources, including the components driver cloud of OS Installer, Patch Management and Remote Control, if applicable. Details can be found in the respective help documentation.
Minimum Requirements
The following minimum requirements are recommended in case all components are hosted on a single server.
- Minimum requirement 2 GHz dual core (quad core recommended), 8 GB RAM (16 GB recommended), 500 GB HDD.
- The .NET 4.7.2. Framework is mandatory for the installation of Matrix42 Empirum.
- Windows Server 2016 / 2019 / 2022 with current service packs.
- Microsoft SQL Server 2017 / 2019 / 2022 with current service packs.
- If Personal Backup shall be stored on this server, additional storage space is required for the backup data.
- Specific services such as DNS and / or WINS are required for name resolution purposes. (If only the TCP/IP protocol is used, the name can only be resolved with the DNS nameresolution in an IP address. If NetBIOS over TCP/IP is used, the NetBIOS and the DNS name resolution can be used).
- Installed WADK (Windows Assessment and Deployment Kit)for OS installations starting with Windows 10 / Server 2016. We recommend the latest available Windows 11 WADK.
- If WinPE is used as boot medium on the Empirum server, at least Windows Server 2016 is required, because Windows PowerShell 5.1 is needed.
Enhanced Installation
Depending on the requirements and infrastructure, very different implementation approaches can be pursued for Matrix42 Empirum. In most cases, smaller installations run completely on one single server. For large-scale installations with many clients or distributed locations several package servers (depot servers) and separate service and database servers are used in many cases.
Empirum Master Server (without Database server)
- Minimum requirement 2 GHz dual core (quad core recommended), 8 GB RAM (16 GB recommended), 500 GB HDD.
- Windows Server 2016/ 2019 / 2022 with current service packs.
- The .NET 4.7.2 Framework is required for installing the services remotely.
- To build a boot configuration, at least a Power Shell version 5.1 or higher is required.
Dedicated Database Server
- Microsoft SQL Server 2017 / 2019 / 2022 with current service pack.
- Minimum requirement 2 GHz dual core (quad core recommended), 16 GB RAM (32 GB recommended), 500 GB HDD.
- Database installations on Windows operating systems according to the support provided by the respective vendor.
- In case that already existing database instances are used: Currently, only database instances with names in capital letters only can be used e.g. 'MYEPIRUMINSTANCE'.
Package Depot (Installations Server and Backup Shares)
- One or more Windows Server 2016 / 2019 / 2022. Furthermore, Windows client operating systems from Windows 10 / 11 (64 bit only). The respective Microsoft restrictions apply here (e.g. maximum of 20 simultaneous connections and only SMB connections).
- Sufficient hard disk space for all software packages, operating system sources, patches and drivers; if Personal Backup backups shall be stored on this server, additional storage space is required for the backup data.
- For a sub depot server a minimum of 8 GB RAM is required.
When using a Windows client operating system as a depot server, authentication via client certificate is not available.
Matrix42 Management Console
The prerequisites for installing the Matrix42 Management Console are:
- Client operating systems starting from Windows 10 with respective current service pack (32-bit / 64-bit) and higher
- Server operating systems starting from Windows Server 2016 with respective current service pack and higher
- To build a boot configuration, at least a Power Shell version 5.1 or higher is required.
Supported Clients
Software Distribution
- Windows
- All Microsoft Windows operating systems 10 & 11 (including Windows 10 IoT Enterprise) and Server 2016 up to 2022 (no Nano) in the versions supported by Microsoft (Feature Upgrades/Service Pack).
- Use the UEM Agent ESR 2006.x for the use of 32-bit Windows systems
- For the use of 64-bit Windows systems, use the UEM Agent SFR or a newer ESR
- All Microsoft Windows operating systems 10 & 11 (including Windows 10 IoT Enterprise) and Server 2016 up to 2022 (no Nano) in the versions supported by Microsoft (Feature Upgrades/Service Pack).
- Red Hat
- Enterprise Linux 5.x to 8.x (32-Bit / 64-Bit)
- Apple
- macOS 11.0 (Big Sur)
- macOS 12.0 (Monterey)
- macOS 13 (Ventura)
- macOS 14 (Sonoma)
Patch-Management
Client
- All Microsoft Windows operating systems 10 & 11 (including Windows 10 IoT Enterprise) and Server 2016 up to 2022 (no Nano) in the versions supported by Microsoft (Feature Upgrades/Service Pack).
- An installed .NET 4.7.2 framework
- The Agent template must have at least the version 22.x.
- The "Server Service" must be running on the computer being scanned.
- The "Windows Update Service" must not be disabled completely. It's possible to set the start type to "Manual".
Server
- A firewall must not block the following URLs including subdirectories:
- When using the master server for patch download, the following URLs must be released. Alternatively, Patch Management can be configured so that depot servers or clients download the patches.
- A group policy (GPO) may not prevent the update of the Root Certificates.
- A list of supported products can be found here
OS Installer
Windows
- All Microsoft Windows operating systems 10 & 11 (including Windows 10 IoT Enterprise) and Server 2016 up to 2022 (no Nano) with respective current service packs (no Windows RT / ARM based).
- Microsoft Windows Server 2016 / 2019 / 2022 (no Hyper-V Core, no Nano).
- Installed WADK (Windows Assessment and Deployment Kit) on the Matrix42 Empirum Server for restore purposes. As a first step, you must download the WADK from Microsoft’s Internet site. We recommend the latest available Windows 11 WADK.
- To build a boot configuration, at least a Power Shell version 5.1 or higher is required.
No IPv6 and accordingly no IPv6 PXE Deployment is supported.
- Red Hat
- Please ask our Matrix42 Support for details.
Disk Imaging
The Multicast functionality of Disk Imaging is released for test environments exclusively. Only with a written agreement with Matrix42 Multicast Disk Imaging can also be used for productive environments. Please note the known issues in the release notes and how-to for the configuration.
For feedback or problems about Multicast Disk Imaging please contact beta_uem@matrix42.com
- Disk imaging is possible starting from Windows 7 and higher
- A VHD was created and prepared for distribution. Create and prepare a VHD before with Sysprep
- Network Hardware with IGMP protocol enabled
- At least one network component that can take the role of an IGMP querier within the multicast group (usually this is a layer 3 switch or a corresponding configured router)
UDP for Multicast Data Transfer - UDP/Multicast Port 9000-9050 (configurable from 1-65535)
- Multicast address 239.42.42.42 (configurable within the valid address range for multicast addresses)
- SMB access to the Empirum Depot Server to load the image from there
Personal Backup
All Microsoft Windows operating systems 10 & 11 (including Windows 10 IoT Enterprise) in the versions supported by Microsoft (Feature Upgrades/Service Pack).
Inventory
Windows
- All Microsoft Windows operating systems 10 & 11 (including Windows 10 IoT Enterprise) and Server 2016 up to 2022 (no Nano) in the versions supported by Microsoft (Feature Upgrades/Service Pack).
- Installed .NET 4.7.2 Framework
Linux
- SuSE Linux Enterprise Server / Desktop 11 / 12 / 15 (AMD64 & Intel 32/64)
- RedHat Enterprise Linux Server / Desktop 6.x / 7.x / 8.x / 9.x (AMD64 & Intel 32/64)
- Ubuntu Server / Desktop 14.04 / 16.04 / 18.04 / 19.10 / 20.04 LTS / 22.04 LTS / 23.10 STS / 24.04 LTS (AMD64 & Intel 64)
- CentOS v6 / v7 / v8 / v8.5 (AMD64 & Intel 32/64) 24.04
- Mint 19.1 Tessa (AMD64 & Intel 64)
- Fedora 29/30/31 (Server Edition) (AMD64 & Intel 32/64)
- Debian GNU/Linux 9.8/10 (AMD64 & Intel 64)
- Deepin 20.2.1
- Elementary OS 5.1.7 Hera
- Manjaro 21.0.5
- Mint 20.1
- OpenSUSE Leap 42.1
All Linux based systems requires the following libraries:
- min. libgcc_s.so.4.4.7
- min. libz.so.1.2.3
- min. libxml2.so.2.7.6
- min. libdl-2.12.so
- min. libm-2.12.so
- glibc min. 2.7
Apple
- macOS 11.0 (Big Sur)
- macOS 12.0 (Monterey)
- macOS 13 (Ventura)
- macOS 14 (Sonoma)
Reporting
- Microsoft SQL Reporting Server
- Microsoft SQL Server 2017 / 2019 / 2022
- Supported versions of the reporting services SSRS 2017 / 2019 / 2022
- Preferred browser: Microsoft Edge. Please ensure that the displayed reports are added to the “trusted sites”.
- Microsoft SQL Reporting Server Services Express does not allow access to distributed environments.
Empirum Web Console
A databank server which running in mixed mode is required for the user log-on (includes the actual SQL server authentication as well as the Windows authentication).
Supported Browser
- Current supportet version of Mozilla Firefox
- Current supportet version of Google Chrome
- Current supportet version of Microsoft Edge
Matrix42 Package Robot
Package Creation
- Supported client operating systems: Windows 10 & 11 (32-bit / 64-bit)
- Supported server operating systems: Windows Server 2016 and higher
- Installation and recording under an account with administrative privileges
- Disabled UAC on Windows 10 / Windows 11 / Windows Server 2016 / Windows Server 2019 / Windows Server 2022 (followed by a reboot)
Package Execution
- Supported client operating systems: Windows 10 & 11 (32-bit / 64-bit)
- Supported server operating systems: Windows Server 2016 and higher
Compatibility UUX for SUEM
Enterprise Service Bus
The correct handling of messages with the Enterprise Service Bus requires that the sender and receiver uses a compatible message model version.
Note the corresponding system requirements.
Middle ware Components
Matrix42 uses various middle ware components for Empirum.
The following middle ware components are used for Empirum and installed, unless they are already available on the respective system:
- .NET Framework
- VCRedist
- VJRedist
- Microsoft Enterprise Library
- RabbitMQ (optional)
The customer is responsible for updating these components; alternatively, a Matrix42 update of a component as a patch / hotfix / service release can be used, if available.
For this purpose, the customer can use the Matrix42 Patch Management module. Updates can also be performed via WSUS or update packages specifically created by the customer.