The product is stable if you have equipment maintenance.

I rate the solution’s stability a nine out of ten.

OpenText Content Manager is a market leader in the category and is very stable. 

OpenText Content Manager is an RDBMS system having certain power-related limitations.

Stability-wise, I rate the solution a six out of ten.

We have not experienced any stability issues.

I rate the tool’s stability a nine out of ten. It is quite stable.

Actually, we have not seen the product working yet, to be quite honest. We have seen a demo, but we have challenges getting it working with the metadata we have. In the demo, I think we have been using it for year. Since then we have been struggling to get it implemented.

Our organisation uses VDIs instead of hard drives. Our experience has been that conducting simple tasks such as sorting by columns results in latency in the system, to the point of stalling it, despite having minimum people using the software.

The stability is reasonable. Although, like any software, it has areas to improve. It seams sensitive to configuration changes. Misconfiguration causes problems very quickly.

The database configuration would need to be redeployed to servers after a restart, even though everything looked OK and reported as OK. Clients could not resolve the data-source until the configuration was redeployed.

We have not really had any stability issues.

Considering the complexity/range of functionality, and the sheer amount of content it can handle, the stability of the product is impressive. The database side is excellent. The document store is reliable, as well as the workgroup and event services. Most user problems occur because of network connectivity issues or issues with client applications such as Word or Outlook and are not related to Content Manager directly. Outlook integration and, in versions 7 and before, content index searching has been a little flaky (it may have improved since they changed to IDOL searching). Other than that, I’ve seen the HPE developers continually improving the product and resolving any issues that arise (most of which are not significant).

Microsoft Office disabling the HPE Records Manager integration is an issue.

We had stability issues primarily with performance, where title searches slowed down compared to previous versions. TRIM was stable with DCI itself, although it had its own bottlenecks.

In the case of conversion of Adlib software polling MS Exchange and writing to an HNAS drive, it managed to bring down both servers. It's paramount to adequately plan capacity and preventive maintenance.

The product is very stable.

In order to maintain stability, some monitoring from ICT staff is required to catch any anomalies before they become issues.

It is hard to get technical support when you try to integrate HPE RM with other products. For example, when implementing a third-party load balancer, the response time was impacted significantly. It is a gray area between technical support and/or consulting, HPE did not provide much support.

Generally speaking, HPE’s support for the product has been weak since the acquisition from TOWER Software. There is a large gap between 1st-level support and the often-required 3rd-tier support. Escalation is often onerous and HPE seems to be focused on closing tickets rather than solving issues. More technical issues that need to go beyond support to the development group are extremely difficult to move forward.

The solution is stable and is being used by bigger companies the world over. 

I did not encounter any issues with stability.

We had regular and different experiences related to user profiles and control over client product.