Upgrading UNIX/Linux agents in System Center Operations Manager (SCOM) is typically a smooth and simple process. Most environments can perform the upgrade directly from the Administration pane by selecting the agent and executing the upgrade task. However, when Apache is installed on the target Linux server, the upgrade may unexpectedly fail due to additional components introduced during the agent installation.

In this post, we break down why this happens and how you can resolve the issue quickly.
Why Apache Causes Upgrade Problems in Linux
During installation or upgrade of the SCX Agent, SCOM performs a check to determine whether additional monitored components exist—such as Apache or MySQL. When Apache is detected, SCOM automatically installs an additional package:
✔ Apache CIM Provider (apache-cimprov)

This provider enables SCOM to collect monitoring metrics from the Apache service. It is tightly linked to the OMI server package, which the SCX Agent relies on.
This dependency design means:
- The Apache CIM provider must be removed before uninstalling the SCX Agent & OMI Server.
- The dependency can block automated upgrades initiated from the SCOM console.
- Attempts to upgrade may result in a failure message such as:
“Operation is not valid due to the current state of the object.”
Root Cause: Linux Apache CIM Provider Blocking the Upgrade
Through testing, the problematic package was identified as:
apache-cimprov-1.0.1-13.universal.1.x86_64
This package, along with its dependency chain, prevents SCOM from completing the upgrade successfully.
How to Fix the Issue
Fortunately, the solution is simple:
🔧 Remove the Apache CIM Provider
Run the following command on the affected Linux server:
rpm -e apache-cimprov-1.0.1-13.x86_64
Once the package is removed, re-run the agent upgrade from the SCOM console—the upgrade will complete successfully and reinstall this provider while installing the new agent version.

Final Recommendation
If your SCOM agent upgrade fails on a Linux server with Apache installed, first check for the Apache CIM Provider package. Removing it resolves the issue instantly and avoids unnecessary troubleshooting.
This subtle but impactful behavior is important for SCOM administrators managing diverse Linux workloads. Identifying the package early can save time and streamline agent lifecycle management.