Skip to main content
Mitratech Success Center

OpRiskControl System Requirements v5.4.0.0


Minimum System Requirements & Installation Prerequisites

OpRiskControl v5.4.0.0

Document Date: 14th March 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 OpRiskControl implementation.

OpRiskControl, 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/2008 R2 Enterprise or Standard or Microsoft SQL Server 2012 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.

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 Mozilla Firefox, or the latest version of Google Chrome.
  • Microsoft Office 2007, 2010 or 2013 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.

User Management and Integration

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

OpRiskControl Server Installation In-depth

(This assumes the Server meets the current minimum requirements as stated above.)

Server Specification, Including Preloaded Items

  • Microsoft IIS 7 or 8.
  • Internet Explorer 11, or the latest version of Mozilla Firefox, or the latest version of Google Chrome.
  • Microsoft .NET Framework v2, v3.5 SP1 and v4.5.2 with ASP.NET 4.
  • SQL Server 2008/2008 R2* or SQL Server 2012*.
  • OpRiskControl uses software licences on a per-server basis. This is based on the name of the server.

* The Server owner needs to provide a legally licensed installation of this product.

Windows Security

  • A dedicated OpRiskControl Windows User should be set up with access to the Active Directory (if utilising AD import) and SQL Server.
  • Was this article helpful?