Upgrade prep Step 1: MC 2025
Requirements

This list is tentative:

Any versions not listed in here, we have no information on.

Windows server compatibility

Windows Server 2016: Yes

We recommend this at this time, unless you are using the MCe relay/reliability server, in which case we instead recommend Windows Server 2022

End of life Jan 2022, Extended end of life Jan 2027

https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2016

Windows Server 2019: Recommended

End of life January 2024, Extended end of life January 2029

We run some of our servers with this.

Windows Server 2019 - Microsoft Lifecycle | Microsoft Learn

Windows server 2022: Conditional

Using the MCe relay/reliability server, Accruent's MC is compatible with Windows server 2022. Without this or some other solution, the email sending is not compatible with Windows server 2022. Talk to us about costs and benefits (there are server beyond just compatibility with Windows server 2022) of setting up the MCe relay/reliability server.

End of life Oct 2025, Extended End of life Oct 2031

We run some of our servers with this

https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2022

Windows server 2025: No

At time of writing, according to our contacts in Accruent, Accruent has not tested any versions of MC on Windows Server 2025, but given the next comment, we expect they will be testing their latest on it in the near future.

In general, industry standards are 'Do not use any version of Windows server until it has been out for at least 1 year and at least one patch version'. Prior to that, it should be treated as a preview for companies like ourselves and Accruent to test, not for deployment.

When Accruent gives us the green light, we will upgrade our dev and sales servers to Windows 2025 to start testing with it.

End of life Nov 2029, Extended end of life Nov 2034

https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2025

SQL Server compatibility

MS SQL Server 2012: Conditional

If you are on this version, this version is currently acceptable, however it reached extended end of life in 2022 so we recommend not using this on any new installations. At some point Accruent will require a newer version.

MS SQL Server 2014

We never tested Accruent's MC on this version, not recommended for new installations. Likely ok if you have it running MC 2022 to upgrade to MC 2025.

https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2014

MS SQL Server 2016 SP3: Conditional

If you are on this version, this version is currently acceptable, will reach end of life July 2026 and extended end of life is set for July 2026 so we recommend not using this on any new installations. At some point Accruent will require a newer version.

If you are running with a lower service patch, you need to upgrade to SP3

https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016

The collation sequence:

  • on the SERVER
  • on the reg database
  • on the ent database(s)

Must be set to the US standard collation SQL_Latin1_General_CP1_CI_AS.

This SQL_Latin1_General_CP1_CI_AS collation is defined by the following characteristics:

  • Latin1: Uses the Latin 1 character set (ASCII) with Code Page 1252.
  • CI (Case Insensitive): Treats uppercase and lowercase letters as equal (e.g., 'A' equals 'a').
  • AS (Accent Sensitive): Treats accented characters as distinct from their non-accented counterparts (e.g., 'A' differs from 'Ä').

Must NOT be set to any other collation, not in the server, not in the databases. Cannot even be set to the "rest of the world" English collations "Latin1_General_CI_AS" or "Latin1_General_100_CI_AS".

How to check, run this SQL:

SELECT SERVERPROPERTY('collation') AS ServerCollation;

MS SQL Server 2019: Yes

We currently recommend this version for new installations.

Mainstream end of life was February 2025, extended end of life is January 2030

We have upgraded most of our servers to this version. We occasionally test with other versions, but not heavily or often anymore.

https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2019

The collation sequence:

  • on the SERVER
  • on the reg database
  • on the ent database(s)

Must be set to the US standard collation SQL_Latin1_General_CP1_CI_AS.

This SQL_Latin1_General_CP1_CI_AS collation is defined by the following characteristics:

  • Latin1: Uses the Latin 1 character set (ASCII) with Code Page 1252.
  • CI (Case Insensitive): Treats uppercase and lowercase letters as equal (e.g., 'A' equals 'a').
  • AS (Accent Sensitive): Treats accented characters as distinct from their non-accented counterparts (e.g., 'A' differs from 'Ä').

Must NOT be set to any other collation, not in the server, not in the databases. Cannot even be set to the "rest of the world" English collations "Latin1_General_CI_AS" or "Latin1_General_100_CI_AS".

How to check, run this SQL:

SELECT SERVERPROPERTY('collation') AS ServerCollation;

MS SQL Server 2022: No

There are problems with CLI that Accruent MC 2025 currently relies on.

https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2022

MS SQL Server 2025: No

There are problems with CLI that Accruent MC 2025 currently relies on

https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2025

Browser compatibility

MC 2025 upgrade, like all current versions of MC, affected by the Chromium deprecation that started March 10, 2026, is not compatible with Chromium versions 146 and forward. There is a fix that makes Chromium versions to Sept 21st 2026 compatible, for details see: Chromium issues with unload event

Next steps

Once you know the environment is correct, you can prepare for the upgrade/install: Prep Step 2