Purpose
Two questions we are asked regularly, answered in one place: how long a release of the ENow Management System stays supported, and which versions of Windows Server it runs on.
Version support: N-2
ENow supports the current generally available release and the two releases before it.
As releases ship, the window moves. When a new release becomes generally available, it becomes the current release, the previous two remain supported, and the release that was third-oldest drops out of support.
With 8.7 as the current GA release, that means 8.7, 8.6 and 8.5 are supported.
What this means in practice
If you are running a release inside the window, you are supported and can raise a case normally.
If you have fallen outside it, the first step in any case will be to bring you back into the window, because we cannot investigate defects against a release we no longer maintain. That is not a refusal to help — it is that a fix, if one is needed, will only ever be delivered in a supported release.
Two things worth planning around:
- Do not let yourself drift more than two releases behind. The further back you are, the more likely it is that catching up needs a stepped upgrade rather than a single jump.
- If you are several versions behind, check the upgrade path before you start. Going straight to the current release is not always possible. Raise a case and we will tell you the route.
Windows Server compatibility
Windows Server 2025 is supported on all 8.0 and later releases of the ENow Management System.
No specific minimum release is needed for 2025 — if you are on 8.0 or above, it is supported.
For the full list of supported Windows Server versions, along with the .NET, WMF, IIS and SQL Server requirements that go with them, work from the prerequisites guide for the release you are installing rather than from memory. Those requirements change between releases in a way the Windows Server support statement does not.
If you are moving operating system and upgrading at the same time
Both are supported, but do them as separate pieces of work where you can. If something goes wrong after a combined OS migration and version upgrade, you have two candidate causes and no easy way to tell them apart. Doing them in sequence costs an extra change window and saves considerably more than that when something needs diagnosing.
A note on GALsync and contactSync
This article covers the ENow Management System. GALsync and contactSync have their own release and platform support, documented in the Quick Start Guide for the release you are running. Do not read the statements above as applying to them.
Comments
0 comments
Please sign in to leave a comment.