Recommended configuration for the installation of ADM sites and services on a server, considering the following characteristics and specifications:

ADM Console Server

Server Server

⚠ Important: The address IP or the name DNS on the server where it is installed ADM and the ConServer it must remain fixed.
If the IP or the DNS change after installation, agents they will lose connectivity, being necessary Reinstall or reconfigure them to re-establish communication.

⚐ Bear in mind:

1. In Windows Server 2019 and 2022, a maximum limit of 10,000 devices per ConServer to ensure optimal performance, considering the characteristics of the server and ensuring that CPU usage does not negatively affect its operation.
2. When installing a conserver on the same server as the ADM console, a maximum limit of 3,500 devices is recommended.
3. If agents connect directly to an onpremises Repserver, a maximum limit of 3,000 devices is recommended.
4. The conserver is compatible with installations of Windows 11 client operating systems, with a maximum limit of 500 devices. This machine must be dedicated exclusively to the use of the conservator and connected via Ethernet cable to the LAN network.
5. The minimum supported version of the TLS cryptographic protocol is 1.2. Make the appropriate settings on the server so that only protocols 1.2 or higher are enabled.

Database Server

⚐ Note: If the database is hosted in Azure SQL Database, creating or updating the database requires a Tier S3 service plan, configured with a minimum of 100 DTUs within an elastic pool. The service plan is required because the processes make intensive use of the plan’s capabilities, such as performance, processing capacity, and I/O resources, necessary to ensure a proper execution of the installation or upgrade. Once the database creation or update process is complete, you can adjust the size of the service and change it to the minimum required plan, according to operational and resource consumption needs.

⚐ Note: SQL Server Enterprise is recommended because ADM is a business-critical application and requires high availability, scalability, and advanced architectural features.
If you are using SQL Server Standard, be aware of the limitations of this edition, including:

• Support for up to 24 CPU cores, which can become a bottleneck in high-load scenarios.
  
• Limited functionality in high availability; You can participate in Always On, but it doesn’t support advanced availability groups or scenarios with more than two instances for true high availability.
  
• It does not include enterprise-level capabilities, such as: Automatic Tuning, Advanced performance optimization and Other features oriented to mission-critical environments.

⚐ Note: See Exceptions

Workstation Agent

The operating system versions supported by this agent are:

Windows

⚐ Note:

The (32-bit) label in Task Manager indicates that the process is running in compatibility mode via the Windows WOW64 subsystem, which allows you to run 32-bit applications on 64-bit systems.

Note that depending on your computer and operating system version, this label may not appear. For example, on computers with 32-bit architecture, this ID is not displayed.

The ADM Agent for Windows systems is compiled in x86 (32-bit) format to ensure compatibility on both 64-bit and 32-bit computers. Therefore, it is installed in the C:\Program Files (x86) path.

This condition does not affect the operation of the agent nor does it have implications for its performance or characteristics.

Mac

⚐ Note:
1. The following processors are supported: Intel and Apple Silicon M1, M2 and M3
2. The agent is not supported for 32-bit versions of MacOs.

Linux

⚐ Note:

1. Ubuntu versions are supported for both server and desktop in LTS versions.
2. The agent is not supported for 32-bit Linux distributions.