OpenText Open Enterprise Server explained: what it is and why it still earns its place in a UK SME in 2026

OpenText Open Enterprise Server is the long-running file, print, identity and storage platform that grew out of Novell NetWare and evolved through Open Enterprise Server into its current form under OpenText. It is still in active development — the current line is the OpenText OES 24.x quarterly track sitting on top of OES 23.4 LTS — and it is still widely deployed across UK education, local government suppliers, professional services and mid-market businesses that have run their estates on it for two decades. For an SME wondering whether OES is in scope as a deliberate choice in 2026, the answer is yes.

What Open Enterprise Server actually is

At its core OES is a Linux-based services platform for SMEs and mid-market sites. It delivers file services via the NSS (Novell Storage Services) file system and NCP and CIFS protocols, shared printing through iPrint, mobile and remote file access through Filr, identity through eDirectory, and a cluster stack for high availability. It runs on SLES (SUSE Linux Enterprise Server) and is sold as a per-server or per-user subscription. The current generation explicitly supports using Active Directory as the identity source alongside — or in place of — eDirectory, which materially changes the integration story for sites that have already moved some workloads into Microsoft.

A short history

• 1980s–2000s: Novell NetWare dominates SME and education file and print. eDirectory (then NDS) becomes one of the most replicated directory trees in production anywhere.
• 2000s–2010s: Novell Open Workgroup Suite bundles GroupWise, eDirectory, iPrint and ZENworks. The Novell stack becomes the default mid-market IT environment.
• 2011: Attachmate acquires Novell. The product lines continue, including OES.
• 2014: Micro Focus acquires Attachmate. Open Enterprise Server becomes a Micro Focus product line.
• 2023: OpenText acquires Micro Focus. OES is published under OpenText branding, on a quarterly release model with explicit LTS branches.
• Today: OpenText OES 24.x is the current generation. OES 23.4 remains the LTS track. A Community Edition of recent releases is available for evaluation, home and small-business use.

Where OES still makes sense in 2026

There is a category of SME for whom OES is still the obvious answer. Schools and colleges who built their admin estates on Novell twenty years ago and have never had a reason to leave — the directory, the file shares, the print queues and the GroupWise mailbox have all worked consistently and quietly across multiple IT team handovers. Professional services firms whose case file shares, document management and identity are deeply embedded in eDirectory trees no-one wants to disturb. Manufacturing and logistics sites whose file and print services have run on OES for over a decade with negligible downtime. Government-adjacent SMEs whose customers and contracts expect on-premise file and identity by design. None of these are particularly fashionable reasons to choose a platform in 2026. They are, however, real reasons and they keep showing up in actual renewals.

Where OES shows its age

Honest list of weaknesses: the SME-facing talent pool for OES is smaller than the talent pool for Windows Server, and that talent pool skews older and retires faster than it grows. Management is overwhelmingly Linux-based and tools-fluent, which excludes a chunk of the Windows-trained SME IT population. The browser and SaaS-integration story has improved but is not as automatic as the Microsoft equivalents. The mobile experience depends on Filr being deployed well, which many sites have not done. None of these disqualifies OES. They do mean OES works best where there is a named eDirectory-fluent engineer, internal or contracted, who can keep the estate healthy.

What to do if you still run it

• Get onto a supported release. Running an OES version that is past committed support is the single biggest risk we see on long-running OES estates.
• Pick the LTS line deliberately. The 23.4 LTS branch is the right starting point for almost every SME that values stability over feature velocity.
• Document identity. If your eDirectory tree has not been actively audited in years, that is the single biggest operational risk you have.
• Make sure your backup and restore story is tested. OES estates tend to have working backups and untested restore procedures, often for years.
• Decide whether OES is a permanent choice or a deliberate transition. Either decision is fine; the worst outcome is the choice being made for you by an unplanned incident.

OpenText is committed to the Open Enterprise Server product line and the roadmap continues to ship on a quarterly cadence. For SMEs that have a genuine operational, financial or strategic reason to keep OES in production, the platform remains a sensible and supported choice. If you would like an independent review of your OES estate, get in touch for a short, practical conversation.