Every OpenText release arrives with detailed release notes written for specialists. The people who own the platform, approve the budget or depend on it every day usually need something shorter: what has changed, does it matter to us, and what should we do about it? This guide answers those questions for Content Server 26.2, part of OpenText Content Management 26.2, which OpenText announced in June 2026.
If you already know you are upgrading, our first-hand account of upgrading our own lab from Content Server 24.3 to 26.2 covers the practical detail.
What 26.2 is
Content Server is the repository at the heart of OpenText Content Management: where documents, records, business workspaces and their permissions live. 26.2 is the latest release at the time of writing. OpenText describes it as introducing the first agentic capabilities in Content Aviator, along with practical improvements that help customers modernise, administer and use the platform.
For most estates the headline is not a single feature. It is that 26.2 is a current release, at a time when older versions such as 21.4 have left Current Maintenance.
Content Aviator can now act, not only answer
Content Aviator is OpenText's AI content assistant. Until now it has mostly helped people find, summarise and draft. In 26.2, OpenText says users can ask it to complete common tasks that previously needed manual navigation, menu clicks or specialist system knowledge. These include:
- generating a completed document from the right template, from a natural language request
- moving, copying, renaming and deleting objects
- reading and updating categories and attributes, including populating attributes based on content
- using workspace relationships to find related information
- records actions, such as placing a document on hold
For teams that spend their day on exactly these tasks, that is a real step forward. It also means an assistant with rights to change content, so give its permissions, logging and ownership the same care you would give a new colleague. Our page on preparing for Content Management 26.2 covers this.
A first step towards OpenText Private Cloud
26.2 introduces what OpenText calls its first steps towards a better technical foundation for migrating from on premises to OpenText Private Cloud. OpenText says the tooling gives earlier insight into readiness, dependencies and migration scope, and that the migration experience will expand in future releases. If Private Cloud is on your roadmap, it is worth knowing about now, even if a move is some way off.
More for business administrators
Several changes help the people who run the business side of the platform:
- a Business Administrator home page with preconfigured widgets and status metrics
- access for Business Administrators to WebReports administration pages and Usage Privilege administration
- Records Management Metadata Bulk Update Rules in Smart View, for large volumes of managed items
- read audit logging, so you can record when users acknowledge that they have reviewed a document
These matter because the business administration layer is often where work queues up. Moving routine tasks to the people who understand the business process can take pressure off a small platform team, as long as it is clear who owns what.
Everyday improvements for users
Users can reach key workspace actions, including Content Aviator, Favorites and Properties, from the workspace header. Roles and participants can be created and managed from the Permissions side panel and Permissions Explorer. Users can also rename documents before uploading, start a delete workflow from a document's Properties page, and see when a document is outdated or approaching expiration.
What this means if you are on an older version
If you are on 24.x or earlier, 26.2 is the obvious target to evaluate. If you are still on 21.4, the question is more pressing, because Content Server 21.4 left Current Maintenance on 1 October 2026. Either way, the decision should rest on evidence about your own estate, not on the feature list alone.
Before you upgrade: four lessons from our lab
When we upgraded our own lab to 26.2, four lessons stood out. They are covered in full in our Content Server 26.2 upgrade lessons:
1. The database upgrade is one way. Once it has run, the previous version cannot use the database, so rollback means a restore. Prove the restore before you start.
2. Check your licence before and after. Include any add-ons that carry their own licence keys.
3. Add-ons need their own upgrade. Check every add-on against its vendor's compatibility matrix for 26.2.
4. Upgrade OTDS first, to at least the Content Server version.
In practice, an upgrade is three upgrades: the platform, the add-ons and the database, planned as one change. The 15 OpenText estate health checks are a good way to confirm the basics an upgrade relies on, such as a tested restore and documented customisations.
Want a second opinion on 26.2?
If you are weighing up 26.2 and would like a second view on your versions, add-ons or rollback plan, talk to Nuca. Book a free 45-minute continuity check call: you describe the estate and the upgrade plan, and we tell you what deserves a closer look. If your estate is ready, we say so.
Sources
- OpenText Blogs, What's new in OpenText Content Management (24 June 2026), Content Management 26.2 features: blogs.opentext.com
- OpenText Blogs, What's new in OpenText Content Aviator (20 July 2026), Content Aviator 26.2: blogs.opentext.com
- OpenText Blogs, Modernize your content foundation for the agentic AI era (13 May 2026), Content Cloud 26.2 migration tooling: blogs.opentext.com
- Nuca Systems, Content Server 26.2 upgrade lessons (13 October 2026), first-hand lab findings: nucasystems.com
- AnswerModules, Module Suite 4.0.0 release notes (compatibility matrix): developer.answermodules.com
Frequently asked questions
Related reading