Novell and Linux — legacy product and service inventory
Article: https://yenra.com/novell-linux/
Prepared: September 15, 2026
Purpose: identify the complete installed product and prove a service migration.
Use test identities; keep credentials and sensitive inventories private.

IDENTITY
Historical name used by the organization:
Exact current product / release / service pack / patch level:
Base operating system and architecture:
Installed product services and client versions:
Package repository / registration evidence:
Current supplying organization / support agreement / escalation:
Relevant historical and current documentation URLs:

SERVICE DEPENDENCIES
Service owner and required tasks:
Identity / groups / rights / login scripts:
Volumes / filenames / permissions / quotas:
Print queues / applications / scheduled jobs:
Certificates / backup jobs / restore method:

CHANGE PLAN
Supported source-to-target path and documentation:
Maintained target and prerequisite versions:
Test environment and representative data:
Test normal access, expected denial and administrative access:
Test file creation, update and name/permission fidelity:
Test client login, printing and scheduled work:
Backup restore result:
Cutover, rollback and communications owner:
Unresolved issue / owner / deadline:

Fictional example: copying every file from an OES server is insufficient when
the target fails a group-rights test. Resolve the access mapping before cutover.

Primary references:
https://www.suse.com/company/history/index/
https://www.microfocus.com/documentation/open-enterprise-server/24.4/oes_readme/readme.html
https://www.microfocus.com/documentation/open-enterprise-server/24.4/inst_oes_lx/bmu0fem.html
Versioned references describe those versions, not a universal upgrade path.