Skip to main content
Mitratech Success Center

OpRiskControl System Requirements v5.5.0.0


Minimum System Requirements & Installation Prerequisites

OpRiskControl v5.5.0.0

Document Date: 16th November 2016

Note: This document is subject to change and will be superseded by the Project Implementation Document (PID) provided during the planning phase of the implementation. These prerequisites cover both OpRiskControl and Incident Manager.

Minimum System Requirements

Server Side

  • Web Server with at least 8GB RAM; minimum screen resolution 1024x768; hard disk size depends on the expected size of the system.
  • Windows Server 2008 and IIS 7, or Windows Server 2012 with IIS 8.
  • Domain user account with local administration privileges for installation and configuration.
  • Domain Account for the OpRiskControl services and websites to run under.
  • Microsoft SQL Server 2008 R2, 2012 or 2014 Enterprise or Standard.
  • SQL Server Management Studio installed on OpRiskControl server.
  • Microsoft .NET Framework v2, v3.5 SP1 and v4.5.2 with ASP.NET 4.
  • Internet Explorer 11, or the latest version of Microsoft Edge, Mozilla Firefox, or Google Chrome.

Note: OpRiskControl uses software licences on a per-server basis. This is based on the name of the server.

Client Side

  • Windows Client with at least 4GB RAM; minimum screen resolution 1024x768; 40GB+ free hard disk space.
  • Internet Explorer 11, or the latest version of Microsoft Edge, Mozilla Firefox, or Google Chrome.
  • Microsoft Office 2007, 2010, 2013 or 2016 in order to view document attachments or data exported to Excel or Word format.
  • Adobe PDF Reader v10.0 or later in order to view reports exported to PDF.

rn_image

5001 Plaza on the Lake, Suite 111, Austin, TX 78746
p: 512.382.7322
e: support@mitratech.com

www.mitratech.com

User Management and Integration

  • Standard integration to an administered Microsoft Active Directory Service if utilising AD Integration.

Windows Security

  • A dedicated OpRiskControl Windows User should be set up with access to the Active Directory (if utilising AD import) and SQL Server.
  • This user will be used for the OpRiskControl website login on the OpRiskControl Server. The user must be in the Domain, with privileges to read the Active Directory (if utilising AD import).
  • Was this article helpful?