Below are the minimum system requirements for Redbrick to run effectively.
Unfortunately, we cannot provide generic advice on what specs any given firm should run, as all environments are different, but we are happy to work with your chosen IT company or internal IT team to find a suitable solution.
The requirements set out below are those below which Redbrick simply will not run.
However, this is not the same as a recommended spec. Meeting the minimum spec will not necessarily provide the best possible user experience, so we always suggest speaking to us about your individual circumstances.
If you are unclear about any of the below requirements please speak to us, or your IT provider, before committing to purchase. We shall not be held responsible (nor issue any refunds) for poor performance due to the below specifications not being met.
(Please note some of these versions are no longer supported by Microsoft. Redbrick will run on these versions however your system is likely to be compromised from a security perspective if you are running unsupported software.)
Workstation minimum requirements
Microsoft Windows 7 or above.
Microsoft Office 2013 or above (32 bit only)
Microsoft .NET Framework 4.0
(Microsoft .NET Framework 4.5 is required if using Redbrick Searches)
Minimum 8GB RAM
A Monitor supporting a minimum resolution of 1024 x 768
SQL Server Minimum
Microsoft Windows Server 2012 or above. We have tested up to and including Windows server 2019.
Microsoft SQL Server 2008 R2 or higher.
(Given support for 2008 R2 has ended we recommend a higher version.)
At least 8GB available RAM capacity
Microsoft .NET Framework 4.0
Must have at least 10GB spare disk space.
TCP ports 80 and 1433 and 1434 open inbound and outbound to 184.108.40.206
We recommend you regularly check your software and ensure you are running current and supported software. This is something your IT provider should be happy to assist with.
When testing the suitability of an environment for any software a few key principals apply.
- Test the products you are going to use in your environment with your IT provider to ensure appropriate performance, scalability and interoperability with other products in your environment.
Redbrick are very happy to assist any client with reasonable proof-of-concept testing here, pre and post live to ensure our client(s) are getting the most from our product.
- Plan for growth. Just because your system meets your requirements today, it does not mean that in a years’ time, if you have added users or increased your throughput or changed user behaviours that this remains the case.
- Continuous review. Like the legal matters you work on it is important that you (or your IT provider) undertake continuous conscious reviews of your hardware and your environment to ensure continued suitability for the software running on it.
- End user experience will be commensurate with the environment, resources and effort put into the setup and maintenance.
Redbrick does not necessarily need paid versions of SQL. Some clients will (and do) run happily on SQL Server express instances, however many will not. This will depend on multiple factors:
- Size of the firm
- Usage of the product
- Number of concurrent connections
- Load and specs of / on the server
Typically, small firms will be able to run an express instance of SQL and larger firms will require a paid professional licenced SQL instance, however there is no one size fits all.
Redbrick can run side by side on an existing SQL instance if you have one already for another product. Although, we would advise checking with that provider also for compatibility and spare capacity.
Microsoft recommends against running your SQL database on the same physical machine as your Exchange server.
Successful use of our Outlook Add-In requires 32-bit Office to be running.
WE DO NOT CURRENTLY SUPPORT 64-BIT OFFICE INSTALLS.
TCP ports 1433 and 1434 open inbound and outbound to 220.127.116.11 and port 80 outbound.
To send SMS messages from Redbrick Practice Management, we will require details of your static IP address so that we can add a firewall exception on our server.
The Netgear ProSafe range of routers can still block RPM data from being synchronised even with ports 80 and 1433 open, and so are not suitable for use with RPM.