26.1.00 enhancements and patches
Downloading and installing BMC Helix ITOM 26.1.00
| Downloading from EPD | Downloading the deployment manager |
| Fresh deployment | Deploying |
| Upgrade | Upgrading |
Updates in 26.1.00
Use updated support for the technology stack
BMC Helix ITOM on-premises supports the following technology stacks:
- Kubernetes 1.35
- OpenShift 4.20
- Nginx Ingress Controller version 1.13.7 and 1.14.3
- F5 NGINX Plus R35
- Helm 3.19, 3.20
For more information, see System requirements.
Run cluster health checks with the Health Check Tool
Use the Health Check Tool (HCT) to run cluster health checks to validate cluster readiness and current health before deploying BMC Helix IT Operations Management. This enhancement improves reliability by identifying cluster issues early and helping reduce deployment failures.
For more information, see Installing Health Check Tool.
Enable SmartGraph services for BMC Helix ITSM deployments
Configure the DYNAMIC_SERVICE_MODELING and SM_PLATFORM_FULL parameters to deploy SmartGraph services and run BMC Helix ITSM in the FULL mode. This configuration enables BMC Helix ITSM users to use the network impact analysis feature in BMC Helix Telco Extensions and reduces infrastructure cost.
For more information, see Configuration file settings.
Use Valkey for in‑memory data operations
BMC Helix ITOM 26.1.00 uses Valkey for caching, session management, and data storage. This change helps reduce licensing and security risks and provides a cost-effective in-memory data store.
For more information, see Configuration file settings, Upgrading BMC Helix IT Operations Management from version 25.3 to 26.1, and Upgrading BMC Helix IT Operations Management from version 25.4 to 26.1.
Back up critical infrastructure components
BMC Helix ITOM supports backup of OpenSearch logs and Apache Kafka data to help protect critical data during system disruptions.
For more information, see Backing up critical infrastructure components.
Generate alarm events for additional services
Import the following alarm policies to generate alarm events when metric values reach the defined thresholds. This capability enables early detection and proactive remediation of issues.
- BMC_Self_Mon_PVC_Kubernetes
- BMC_Self_Mon_PVC_Openshift
For more information, see Importing the monitoring and alarm policies.
(Available for logged-in users only) Get help faster with DocuAssistant
Use DocuAssistant, an AI-powered tool, to find answers to your questions, get procedural information, clarify concepts, and understand terms better. DocuAssistant retrieves answers from the official BMC Helix documentation. To get help, click DocuAssistant
on the documentation page and type your question.

What else changed in this release
Update | Product behavior in versions before 26.1.00 | Product behavior in version 26.1.00 |
|---|---|---|
Valkey monitoring policy
| Redis cache infrastructure is monitored using the Self‑Monitoring‑Redis policy. |
Valkey infrastructure is monitored using the Self‑Monitoring‑Valkey policy. This policy also tracks the availability and performance of microservices that depend on Valkey. For more information, see Importing the monitoring and alarm policies. |
ARServices configuration | The ARServices parameter is configured directly. | To deploy services previously controlled by the ARServices parameter, configure the SM_PLATFORM_FULL parameter. |