Zoomed Image
USA
800 691 9120
UK
01225 704844

System Requirements

xAssets Configuration Guide
Deployment and Administration

System Requirements

This page lists the server, client, and network requirements for deploying xAssets. Meeting these requirements ensures stable operation and full functionality across all modules.

Application Server Requirements

The xAssets application server hosts the web application, the API, the batch service, and all server-side processing.

Component Requirement
Operating System Windows Server 2016 or later (Windows Server 2019 or 2022 recommended)
Web Server Internet Information Services (IIS) 10.0 or later
Runtime .NET Framework 4.8 or later
Processor 2 cores minimum; 4 or more cores recommended for environments with more than 5,000 managed assets or frequent batch processing
Memory 8 GB minimum; 16 GB or more recommended for larger environments
Disk Space 2 GB minimum for application files; additional space required for discovery data, backups, and temporary files. Plan for 10 GB or more in active environments.

Tip: For hosted or cloud deployments, a Windows Server VM with at least 8 GB of RAM and 2 vCPUs is recommended as a starting point. Increase to 16 GB and 4 vCPUs for environments with more than 5,000 managed assets or heavy batch processing. Adjust based on the number of managed assets and concurrent users.

Database Server Requirements

xAssets stores all data in a relational database. The database server can run on the same machine as the application server or on a dedicated server.

Component Requirement
SQL Server Microsoft SQL Server 2016 or later (SQL Server 2019 or 2022 recommended). Express, Standard, and Enterprise editions are all supported.
MariaDB MariaDB 10.5 or later (alternative to SQL Server)
Disk Space Varies by data volume. A typical installation with 10,000 managed assets requires approximately 5-10 GB. Discovery data, audit history, and software recognition data are the largest consumers of space. Plan for growth and allow at least 20 GB for active environments.
Collation SQL Server: a case-insensitive collation is recommended (e.g. SQL_Latin1_General_CP1_CI_AS)
Recovery Model Full recovery model is required if using the failover system (log backups are shipped to the failover server). Simple recovery model can be used if failover is not configured.

Warning: SQL Server Express has a 10 GB database size limit. This is sufficient for small deployments but may be exceeded in environments with large numbers of discovered assets or extensive audit history. Monitor database size and plan to upgrade to Standard edition if the limit is approached.

Collection Server Requirements

The Collection Server is only required when discovering machines on networks that cannot reach the application server directly. See Collection Server Architecture for details.

Component Requirement
Operating System Windows Server 2016 or later, or Windows 10/11 Professional
Disk Space Sufficient space for the PCAnalyser folder and accumulated discovery files. A few hundred MB is typical for the base installation; allow 1-5 GB for the netdiscover folder depending on the number of discovered machines and scan frequency.
Network SMB (port 445) access from discovered machines; HTTPS (port 443) access to the application server

Client Requirements

xAssets is a web application accessed through a browser. No client software installation is required.

Component Requirement
Browser A modern, evergreen browser: Microsoft Edge, Google Chrome, Mozilla Firefox, or Apple Safari. The latest two major versions of each browser are supported.
JavaScript Must be enabled in the browser
Screen Resolution Minimum 1280 x 720. The interface is responsive and adapts to larger screens.
Cookies Must be enabled for session management
Network HTTPS (port 443) or HTTP (port 80) access to the application server

Tip: Internet Explorer is not supported. If users are accessing xAssets with Internet Explorer, they should switch to Microsoft Edge or another supported browser.

Network Requirements

Ports Used

Port Protocol Direction Purpose
443 HTTPS Client to server Web application access (recommended)
80 HTTP Client to server Web application access (not recommended for production)
1433 TCP App server to DB server SQL Server database connection (if on separate servers)
3306 TCP App server to DB server MariaDB database connection (if on separate servers)
445 SMB Discovered machines to Collection Server Discovery agent file sharing
25 / 587 TCP App server outbound SMTP email delivery (see Email Configuration)

Bandwidth

xAssets is a single-page application (SPA) that loads once and then communicates with the server via lightweight API calls. After the initial page load, bandwidth requirements are minimal. Discovery data uploads from Collection Servers are also small (a few KB per discovered machine per scan).

IIS Configuration

The xAssets application runs as an IIS website or virtual application. Key IIS configuration points:

  1. Application Pool -- create a dedicated application pool running under the .NET 4.x CLR. Use an application pool identity that has access to the database and the CustomerData file system.
  2. Authentication -- configure either Windows Authentication or Anonymous Authentication depending on your authentication strategy. See Securing the Web Server.
  3. HTTPS Binding -- bind an SSL certificate to port 443. See Securing the Web Server for details.
  4. Static Content -- ensure the IIS Static Content feature is installed for serving CSS, JavaScript, and image files.