- 04 Nov 2023
- Print
- PDF
SysAid System Requirements for New Installations
- Updated on 04 Nov 2023
- Print
- PDF
SysAid server
If you are using Patch Management, make sure to also consider the requirements in the Patch Management table.
Component | Requirements | |
---|---|---|
Minimum | Recommended | |
Computer and processor | 2.0GHz | Quad-Core Xeon or equivalent |
RAM | 4 GB | 8 GB |
HD Space | 16 GB | 32 GB |
Display resolution | 1280x1024 display or above | |
Operating system (x64) |
| Windows Server 2012 and above (Server 2016 and 2019 are supported) |
Database*** |
| MS SQL Server 2019 |
- Windows 10, and Windows 8 can be used for test environments.
- .NET Framework 3.5 SP1 or higher is required.
**When the SysAid server is installed on a Linux server, manual agent deployments and RCG require the SysAid RDS (on a Windows machine).
SysAid supports the following OS versions:
- Centos - 7
- Debian - 9 stretch, buster 10
- Ubuntu - 16.04 Xenial Xerus, 18.04 Bionic Beaver, 19.10 Eoan Ermine, 20.04 Focal Fossa
*** For production environment it is recommended to use a separate machine for the database.
**** MS SQL Express requires an additional 1 GB of RAM, if running on the same machine, and can contain up to 10 GB of data (expected DB growth - dependent on number of assets and modules used, approx. 2-5 GBs per year).
***** Oracle is not supported in versions 21.4 or higher.
Security guidelines and instructions to follow:
- Make sure you are installing the latest version of SysAid and are regularly following our website for updates.
- Make sure the server you are running SysAid on is updated to the latest OS versions and security patches.
- Make sure access to the Server where SysAid is installed on is accessible only from your local network or VPN and via 2FA
- Make sure you security controls such as EDR (Endpoint Detection and Response) and WAF installed on your SysAid server like any other application in your network that needs to be
- It is strongly recommended to block access from the outside world to your SysAid Server, if for business reasons you need access to the server from the outside world make sure to take actions like installing a WAF and other security measures. Consider our Cloud SaaS solution which is secured by following the highest security industry standards.
SysAid Agent
Component | Requirements |
---|---|
Computer and processor | 1.5 GHz |
RAM | 512 MB |
HD space | 50 MB* |
RAM usage | 20 MB |
Operating system (x64, x86) |
|
* To enable Patch Management capabilities, an additional 1.5 GB is required
**.NET Framework 3.5 or above must be installed
*** For inventory feature only
**** Through a third-party tool. Please contact our support team for more information
SysAid RDS
If you are using Patch Management, make sure to also consider the requirements in the Patch Management table.
Component | Requirements | |
---|---|---|
Minimum | Recommended | |
Computer and processor | Dual-Core | Quad-Core |
RAM* | 4 GB | 8 GB |
Network connectivity | There must be a network connection available to the SysAid server | |
HD space | 2 GB | |
Operating system (32-bit* or 64-bit) | Windows 10, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 |
* The amount of RAM determines the RDS's ability to manage a large number of agents and LDAP users.
**.NET Framework 3.5 or above must be installed.
*** The 32-bit installation of the RDS can be upgraded, but is not available for new installations.
For optimal performance, we recommend that networks with 20 assets or more use RDS nodes. An individual RDS node should be used for up to 2000 assets. For more information, see the SysAid Remote Discovery Service Guide.
The RDS should be installed on a machine dedicated for SysAid.
Integration
Component | Minimum Requirement |
---|---|
Email Outbound | SMTP/S |
Email Inbound | Supported protocols:
|
LDAP | Supported LDAPs:
|
API | Requires an integrated development environment (IDE) that supports generating objects from a wsdl file |
SMS |
|
SSO |
|
Exchange (Calendar) | Supported with MAPI protocol for Microsoft Exchange only. |
Office 365 (Calendar) | Supported with EWS protocol. |
Report editing | Requires iReport version 3.7.6 |
*Formerly known as EWS
User interface
Component | Minimum Requirement |
---|---|
Supported browsers for admins | Microsoft Edge, Chrome, Firefox, Safari* |
Supported browsers for accessing the End-user Portal | Microsoft Edge, Chrome, Firefox, Safari* |
Supported browsers for accessing the Self-Service Portal | Microsoft Edge, Chrome, Firefox, Safari* |
Display resolution | 1280x1024 display or above |
Remote Control using RCG, My Desktop | Requires an HTML 5 compatible browser (Edge*, Firefox*, and Chrome*) |
- Basic functionality has been tested.
Patch Management
If you are using the SysAid server and/or the RDS, make sure you also consider the requirements in the SysAid server requirements and the RDS requirements.
Example 1: Let's say you are using the SysAid server to manage 600 assets, and 300 of them are Patch Management enabled. Aside from the 2 GB of RAM and 4 GB of HD space required for the SysAid server, you also require an additional 4 GB of RAM and 10 GB of HD Space for Patch Management capabilities. In total, you would require 6 GB of RAM and 14 GB of HD space for the SysAid Server.
Example 2: Let's say you are using SysAid RDS in one of your branches to manage 200 assets, and 100 of them are Patch Management enabled. Aside from the required 2 GB of RAM and 400 MB of HD space required for the RDS, you will also need an additional 4 GB of RAM and 10 GB of HD Space for Patch Management capabilities. In total, you would require 6 GB of RAM and 10 GB + 400 MB of HD Space for the SysAid RDS.
Component | Minimum Requirement | ||
---|---|---|---|
1-100 Assets | 100-500 Assets | 500-1000 Assets | |
RAM | 4 GB | 4 GB | 8 GB |
HD space | 5 GB | 10 GB | 20 GB |
Internet Connection Bandwidth | 1544 kbps | 1544 kbps | 1544 kbps |
If your RDS is using SysAid Patch Management, ensure port 1070 is opened for communication on the RDS for the target assets.
For other prerequisites for using Patch Management, see the Patch Management Guide.