System Requirements

System Requirements

The minimum system requirements for AssetExplorer:

No of Nodes
Hard Disk Type
RAM
Processor
OS
250-2000
500GB SDD
16GB
1.7GHz to 2.4GHz;
10MB to 12MB Cache;
4 cores to 8 cores
or any entry-level server grade processor.

E.g
Intel Xeon Scalable -
Windows Server OS (2019-2022)


RedHat Linux (RHEL) 7 and above

Ubuntu 20 and above

Cent OS 8 and above

Debian 10 and above
2000-10000
1TB - SDD
16GB
2.4GHz to 3.0GHz;
12MB to 20MB Cache;
6 cores to 8 cores
or equivalent technology.

E.g
Intel Xeon E Family
10000-30000#
2TB/3TB* - SDD
16GB
3.0GHz to 4.5GHz;
12MB to 30 MB Cache;
10 cores to 20 cores
or equivalent technology.

E.g
Intel Xeon Scalable Gold/Platinum
 * PostgreSQL bundled is configured as a database.
If you have more than 30k scannable nodes, it is recommended to have separate remote servers for every 30k nodes to minimize the load on the central server.
Non-GUI Windows machines (or server core installation) are not supported. 

Requirements for Scanning Assets

AssetExplorer uses Endpoint Central agent to scan assets. Endpoint Central is auto-installed in the same folder as AssetExplorer, by default.

Disk Space
Maximum of 1GB free space is required in the folder where AssetExplorer and Endpoint Central is installed.
Server OS
Endpoint Central can be installed only on a Windows server.

If AssetExplorer is installed on a Linux server, install EndpointCentral manually in a Windows server and integrate it with AssetExplorer under Admin > Integrations > UEM Products.
 
If EndpointCentral is purchased separately, please refer here for detailed hardware requirements based on the number of assets purchased.

Refer to the below link for more details on the EndpointCentral agent: EndpointCentral Agent in AssetExplorer.

Additional Requirements 

Supported Browsers   

We recommend you update to your browsers to the latest version for better performance and security. AssetExplorer can be accessed from the following browsers:
  1. Mozilla Firefox
  2. Google Chrome
  3. Microsoft Edge
Recommended screen resolution: 1366 x 768 pixels.
Post upgrade to build 6977, AssetExplorer will not be accessible in Internet Explorer 11. 

MSSQL  

If AssetExplorer runs on MSSQL setup, ensure the database server is hosted in a separate machine under the same network as the application server. The database server configuration solely depends on number of databases configured and usage. Consult with your DBA or Microsoft MSSQL support for system requirements.

Supported MSSQL Versions: 2012, 2014, 2016, 2017, 2019, and 2022.

Enable Read Committed Snapshot Isolation (RCSI)  

Enable read committed snapshot isolation (RCSI) to prevent MSSQL lock issues from affecting AssetExplorer's performance.
It is recommended to schedule this activity over a weekend since it takes time to complete and involves service downtime.
  1. Stop AssetExplorer application.
  2. Log in to SQL Management studio.
  3. Take the AssetExplorer database offline by executing:
  1. USE master
  2. GO
  3. ALTER DATABASE <db_name> SET OFFLINE WITH ROLLBACK IMMEDIATE
  4. GO
  1. Enable the read committed snapshot by running
  1. ALTER DATABASE <db_name> SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE
  2. GO
  1. Bring the database online using
  1. USE master
  2. GO
  3. ALTER DATABASE <db_name> SET ONLINE
  4. GO
  1. Check if you have enabled RCSI successfully by running the following query                                                                
  1. SELECT is_read_committed_snapshot_on FROM sys.databases WHERE [name] = '<db_name>'
  2. If the query output is 1, RCSI is successfully enabled. You can start the application.
For more information on MSSQL databases and RCSI, go here.

Benefits of enabling the MSSQL Snapshot Mode

  1. Simultaneous user-querying of the database without any delay or disruption (although load on the application might exceed the usual limits).
  2. User querying records will be maintained in a separate tempdb, which will not be affected by other user queries occurring in parallel or subsequently.
  3. Database tables will be updated only after a transaction reaches completion.

MSSQL Database Configuration  

We strongly recommend you to have an initial database capacity of at least 5GB and extend it periodically by monitoring the current database file size to avoid triggering auto-growth event unnecessarily. This will ensure optimum application performance and smooth data processing.

To configure fIle autogrowth for the database file, click here.

Creating Database:

Run the following query to create a database:

  1. USE master;
  2. GO
  3. CREATE DATABASE <dbname>
  4. ON(
  5. NAME=<dbname>,
  6. FILENAME='D:\AE\<dbname>.mdf',
  7. SIZE=5GB);
  8. GO



Extending Database Size:

  1. Find the current database size by running the query below

  1. USE master;
  2. GO
  3. select (size*8)/(1024*1024) from sys.master_files where DB_NAME(database_id)=assetexplorer and physical_name like '%.mdf%';
  4. GO

  1. Run the following query to add 5 GB to the current database size
  1. USE master;
  2. GO
  3. ALTER DATABASE assetexplorer 
  4. MODIFY FILE
  5. (NAME = <dbname>,
  6. SIZE = <currentdbsize+5GB>);
  7. GO



Configure File Autogrowth Settings   

Default autogrowth settings in the SQL Server engine may lead to disk fragmentation and performance issues. We recommend that you configure default values as fixed values instead of percentages to ensure optimum application performance.

Autogrowth Settings
Default Value
Recommended Value
Data File
1MB
256MB
Log File autogrowth
10%
128MB
 


Follow these steps to configure File Autogrowth:
  1. Log in to SQL Management studio and run the following query:
  1. USE <db_name>
  2. EXEC sp_helpfile
  3. GO

  1. If the configured growth values for Data (.mdf) and Log (.ldf) files are less than the recommended values, run the following query:

  1. USE master
  2. GO
  3. ALTER DATABASE <db_name>
  4. MODIFY FILE ( NAME = N'<db_name>', FILEGROWTH = 256MB )
  5. GO
  6. ALTER DATABASE <db_name>
  7. MODIFY FILE ( NAME = N'<db_name>_log', FILEGROWTH = 128MB )
  8. GO
  1. Re-run the query in step 1 and check if the autogrowth values now correspond to the recommended values.
​

PostgreSQL (Applicable for versions 10.0 and earlier)   

Since PostgreSQL 9.2 requires users to modify kernel resources to allot required resources for Postgres server,

  1. Add the the below mentioned entry in /etc/sysctl.conf

  1. kernel.shmmax=536870912
  2. kernel.shmall=131072

  1. Execute sudo sysctl -p /etc/sysctl.conf to reload the configured change.
 This is only applicable for Linux OS installations that use bundled Postgres. 

Anti-virus Scan Exemption   

Any anti-virus software such as Symantec running on the same system as AssetExplorer can affect the performance of your application. If you have any anti-virus software set up in your system, we recommend you exempt AssetExplorer directories from the antivirus scan or be cautious about using anti-virus software on the same system.

    • Related Articles

    • System Log Viewer

      View the error logs generated by AssetExplorer. To view performance logs and to schedule performance monitoring click on performance monitoring tool View Error Logs Click the Community tab in the header pane. Click System Log Viewer under ...

    • Configure User Additional Fields

      Based on your requirements, the default user record can be customized using different types of additional fields. This is useful to capture user-related additional information. Role Required: SDAdmin Go to Admin > Organizational Details > Roles. ...

    • Endpoint Central for Agent-Based Scan

      AssetExplorer uses Endpoint Central agents (from build ≥ 6900) for scanning Windows, Linux, and Mac machines. About Endpoint Central ManageEngine Endpoint Central (formerly Desktop Central) is a unified endpoint management system. Agents from ...

    • Exclude CIs from Scan

      Exclude certain CIs from being scanned during automated or scheduled scan. Use case: CIs in restrictive environments or with unique configuration requirements can be excluded from scanning. On the CI list view, select the preferred assets. Go to ...

    • Set Local Authentication Password

      Role Required: SDAdmin LDAP allows users to use their LDAP credentials while logging in to AssetExplorer. You can set a default local authentication password for users imported through LDAP. Users can change this password after the first login. To ...