Keeping OpenText GroupWise healthy: upgrades, security and the long-term plan most SMEs do not have

If you have decided to keep GroupWise running — whether for data residency, predictable cost, or because the migration is genuinely not viable right now — the platform still has to be looked after on a disciplined cadence. OpenText publishes two release tracks in parallel: a quarterly track (currently 24.3 with 24.4 close behind) and a long-term support track (currently 23.4 LTS). Picking the right track and then executing the upgrade, patching and recovery work around it is most of what "running GroupWise well" actually looks like.

LTS versus quarterly: the trade-off

The LTS track gives you fewer mandatory upgrades, longer support windows and a more predictable change calendar, in exchange for slower access to new features. The quarterly track gives you nearer-term access to new capabilities at the cost of an upgrade every few months and a faster end-of-support horizon. For most SMEs with a small IT team and no appetite for constant change, LTS is the right call — version 23.4 is the LTS to be on in 2026, and the expectation is that the next LTS branch will be available when this one approaches its end of committed support. For SMEs with a competent in-house team and genuine feature need, quarterly is fine, provided the team genuinely has the calendar to keep up with it.

Upgrades without surprises

• Plan upgrades around your business cycle, not around the vendor release schedule. Quarterly does not mean "do it the day it ships".
• Read the OpenText release notes end to end before scheduling the upgrade. Most surprises in GroupWise upgrades come from changed default behaviour, not from broken behaviour.
• Stage the upgrade in a lab post office that mirrors production. Run a representative set of clients — Windows client, Web Access, mobile — against it for at least a week.
• Take a verified, restorable backup immediately before the cutover. Verify the backup by actually restoring a sample mailbox, not by trusting the backup software's success message.
• Schedule the production upgrade in a planned outage window. GroupWise is still email: any downtime is felt by the whole business.

Security posture in 2026

GroupWise in 2026 sits inside an estate that almost certainly has Microsoft 365 or Google Workspace for at least some workloads, modern endpoints, and a managed firewall. The security job is to make sure GroupWise does not become the weakest link. That means enforcing MFA on the identity store in front of GroupWise — typically eDirectory combined with Entra ID or a third-party SSO bridge — turning on TLS for SMTP, IMAP and Web Access with current ciphers, restricting Web Access by source network where practical, and making sure the GroupWise Anti-Spam and Anti-Virus modules are running with current rulesets. None of this is complicated in principle; all of it tends to drift in practice without a named owner.

Disaster recovery and backups

Most ageing GroupWise estates we encounter have a backup product running and a recovery plan that nobody has actually tested. The minimum viable disaster-recovery story is: a backup of the Post Office Agent database, a backup of the GWIA configuration, a backup of the Web Access server configuration, a backup of eDirectory, and a documented restore procedure with measured recovery times. The single most valuable habit is restoring a sample mailbox — different from restoring from last night's incremental — at least twice a year. Until you have done a real restore, every quoted recovery time is a guess.

Identity and the long-term problem

The single biggest operational risk on long-running GroupWise estates is almost always the identity store. People left, retired, or moved on, and eDirectory trees grown organically over fifteen years become difficult to administer and risky to change. If your GroupWise authenticates against a tree no-one feels confident touching, that is the place to start the lifecycle review. Modernising the identity layer — whether that means cleaning eDirectory, federating with Entra ID through a third-party SSO bridge, or both — gives you options later. Identity strain is the thing that turns "we are keeping GroupWise" into "we have to migrate urgently" without warning.

When to admit it is time to plan the move

Three signals tell you that the on-premise decision has aged out, even if the original reason for it still holds. The first is that the upgrade cadence has slipped — if you are more than one release behind tracked LTS, the cost of catching up is itself material and growing. The second is that the people who know the platform internally are no longer available and the only vendor left who can help is on a multi-week lead time. The third is that the rest of the business has moved to SaaS tooling that assumes modern authentication and GroupWise is the thing that prevents those tools being used. None of those signals is a surprise; all of them are the right time to start a deliberate migration conversation rather than a forced one.

We help SMEs across Hertfordshire, Bedfordshire and London build and run sensible lifecycle plans for legacy platforms — including the GroupWise estates that are still serving a real business purpose — and we help the same businesses prepare and execute Microsoft 365 migrations when the time comes. If you would like an independent review of where your GroupWise estate sits on that lifecycle, get in touch for a short, practical conversation.