Chatee ahora con Soporte
Chat con el soporte

InTrust 11.4.2 - System Requirements

InTrust Server

Architecture

x64

Operating System

Any of the following:

CPU

Min. 4 cores (for example, for evaluation purposes).

For any real-world uses, at least 8 cores are recommended.

Memory

Min. 4GB (for example, for evaluation purposes).

For any real-world uses, at least 8GB is recommended.*

Hard Disk Space

Min. 14GB when installing all components.

10GB out of that is reserved space that is not in constant use. It is needed for temporary storage during activity peaks such as repository cleanup operations.

Additional Software and Services
  • Microsoft .NET Framework 4.6.2 or later, with all updates that are current at the time of this InTrust release
  • Microsoft Visual C++ Redistributable, provided in the Redist folder of your InTrust distribution
  • Microsoft SQL Server Native Client 11.0.6538.0 or later (version 11.0.6538.0 redistributable package of the client is included in the InTrust distribution)
    Important: Install the required version of the client in advance, and only then install InTrust Server.

* This is only an observation. To estimate consumed memory (in gigabytes) more accurately, use the following formula:

<number_of_cores> * 0.26 + 6

Remember that this means memory used by InTrust Server alone on average. During activity peaks (such as data merging and report building), the memory requirements of InTrust increase.

In a virtualized environment

If you deploy InTrust on a virtual machine, make sure the CPU and memory requirements above are met, and do not overload the virtual machine host.

For communication with the server:

Computers that are supposed to run InTrust Server must be configured to allow for incoming connections on the TCP port on which your InTrust Servers are configured to communicate with agents (900 by default), the TCP port used for InTrust Server management (8340 by default) and TCP port 8341.

For the configuration, alert and audit databases:

Any of the following:

  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2008 R2
  • Azure SQL Managed Instance

Notes:

  • If a database is used by InTrust, no other products should modify it.
  • In the case of on-premises SQL Server deployment, a local or remote installation of SQL Server can be used.
  • The collation order must be case-insensitive.
  • Microsoft SQL Server Express Edition is also supported, but you should be aware of the limitations of this edition before InTrust deployment. See SQL Server Express Edition documentation for details.
For reporting jobs:
  • Web server based on Microsoft Internet Information Services (IIS) version 7.0 or later, with ASP.NET*
  • Microsoft SQL Server Reporting Services**

Notes:

* A local or remote installation can be used. Make sure ASP extensions are allowed.

** A local or remote installation of Reporting Services can be used; Microsoft SQL Server Express Edition with Advanced Services is not supported.

For requirements on local or remote installation of Knowledge Portal, refer to the Knowledge Portal documentation.

InTrust Monitoring Console

Server side
Architecture
  • x64
  • x86 where applicable
Operating System Any of the following:
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
  • Microsoft Windows 10
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows 8.1
  • Microsoft Windows Server 2012
  • Microsoft Windows 8
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows 7
Additional Software and Services
  • Microsoft IIS 7.0 or later; make sure ASP extensions are allowed
  • Microsoft .NET Framework 4.6.2 or later, with all updates that are current at the time of this InTrust release
Client side

Internet Explorer shipped with Windows, or an upgraded version of Internet Explorer.

Notes:

Check Internet Explorer security settings as follows:

  1. In the Control Panel, open Internet Options.
  2. On the Security tab, click the Trusted Sites icon and make sure the web site where Monitoring Console runs is included in the list of trusted sites.
  3. Click Custom Level and make sure Misc | Use Pop-Up Blocker is set to Disabled, and Misc | Allow script-initiated windows without size or positioning constraints is set to Enabled.

If you plan to use a web server based on Microsoft IIS 7.0, check that the following role services are installed in addition to default role services of Web Server:

  • IIS 6 Management compatibility
  • Security: Windows Authentication

InTrust Repository Viewer

Architecture
  • x64
  • x86 where applicable

Operating System

 Any of the following:

Additional Software and Services
  • Microsoft .NET Framework 4.6.2 or later, with all updates that are current at the time of this InTrust release
  • Microsoft Visual C++ Redistributable, provided in the Redist folder of your InTrust distribution

InTrust Repository

The requirements for an InTrust repository cannot be stated definitely. This topic outlines the general considerations for choosing the right locations for your repositories.

Disk Space

Disk space requirements depend on many things, and they vary greatly from environment to environment. For some examples, see the following table:

Considerations

Comments

What kinds of events are stored?

Windows event log events are highly normalized and compress very well. In events from lesser-known logs, the field values are less predictable, and the events require more disk space.

What type of environment does the data come from?

Data from non-Windows environments, especially from Syslog, is generally the least compact.

Is the repository indexed?

An indexed repository is roughly twice the size of a non-indexed repository with the same data.

Choice of Hosting Computer

It is recommended that you host your repositories on computers that are not InTrust servers.

Repositories Not Based on Filesystems

InTrust repositories can be hosted by appliances and virtual appliances based on EMC technology. Support for these systems is provided by the use of the CAS SDK in InTrust.

The following solutions are known to be suitable for hosting InTrust repositories:

  • EMC Centera

  • Dell EMC Elastic Cloud Storage (ECS)

 

See also:

Estimating the Resources Required for Indexing

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación