/
Hardware System Requirements

Hardware System Requirements

 

 

Aeros ERP

image-20251104-202413.png

 

Aeros CONNECT

image-20251104-202356.png

 

 

Aeros LIVE

image-20251104-202408.png

 

 

To support upgrades, hotfixes, and user acceptance testing without impacting Production, Aeros recommends a dedicated non‑production Application Server (physical or virtual).

Note: You cannot run two versions of the Aeros application on the same Application Server. A separate server is required whenever you need to test a different version.

Purpose

  • Validate new Aeros versions, patches, and configuration changes

  • Test integrations and customizations

  • Provide a safe space for training/UAT

Scope

  • Application Server only. An additional SQL Server is not required.

  • The Test Application Server should connect to a separate test database that resides on the existing SQL Server (e.g., a restored copy of Production with a distinct database name).

Recommended Specifications (Test Application Server)

  • Match the Virtualization/Application Server Installation specs listed above for the number of concurrent test users you expect.

  • For small UAT groups, resources may be scaled down so long as the “1 GB per concurrent user (whichever is greater)” memory guideline is preserved and overall performance is acceptable.

Database Considerations (Using Existing SQL Server)

  • Restore a recent Production backup to a new database name (for example, AerosERP_Test).

  • Ensure all scheduled jobs, alerts, emails, and integrations in the test database are disabled or redirected to non‑production endpoints to avoid unintended production activity.

  • Clearly label the test database and restrict access to appropriate users.

  • If live data is used, follow your organization’s data privacy requirements.

Deployment Notes

  • Use the same Windows Server and RDS/Citrix versions as Production.

  • Keep Test on an isolated VLAN or apply firewall rules as needed.

  • Clearly mark the test desktop/app shortcuts and login banner as TEST to avoid confusion.

Typical Setup

  1. Provision a new Windows Server VM for Aeros Test Application Server.

  2. Install the test version of the Aeros application on this server.

  3. On the existing SQL Server, restore Production to a separate test database.

  4. Point the Test Application Server’s connection strings to the test database.

  5. Disable or redirect outbound integrations, emails, and scheduled tasks.

  6. Grant test users access and perform upgrade/patch validation before moving changes to Production.