Based on my experience and what I have heard from clients, there are two main areas where Universal CMDB could get better. First, the way it shows results to users could be more user-friendly. Second, it can be really complex because there are so many different types of things you can track, and they are organized in a complicated way. This complexity can make it take a long time to learn how to use it effectively. Making it simpler to set up and understand would be a big improvement. I have shared some suggestions with OpenText through their platform. One thing I would like to see in the next Universal CMDB is more consistency and simplification. The results it provides are really good, especially compared to other systems, but the way it shows those results could be more user-friendly. Improving the presentation and making it easier to understand would be a great step forward.
Based on my experience with UCMDB, I've faced challenges while discovering servers (nodes). We need to define the IP list of discovery in RTSM and run jobs. Instead, over the years, if we need to add some new assets, we have to add the new IP in RTSM and run jobs again. From the agent side, we need to provide the data flow probe IP. We can do this things as one way: we install the agent at the server (node) level (define the IP of the data flow probe) and after that, our data flow probe will capture the data from the agent and send it back to the UCMDB. That way, we can remove the one step of adding the IP in RTSM. When we work in an environment, the production environment continuously changes and at that time we should have knowledge about the new server (node). However, the auto-discovery part should automatically discover the new CI (node/servers) in an environment and inform the IT person.
Based on the latest version, there were multiple changes done. It had multiple fixes. However, it's based on the customer's requirements. They have modified and created, and released the changes according to those needs. The UI could be better. The page loading is very slow. The customer wants faster loading. Before releases, it would be nice to be able to upgrade to the new release and check it out in order to see the new functionality and what they have changed.
Network Operations at a government with 10,001+ employees
Real User
Jan 28, 2021
The implementation could be simplified. It is not implemented correctly and it's most likely us and the way that we had implemented it. The issue is with integration. We have multiple different operating systems and enclaves between on-premises and the cloud services that we are trying to monitor and the integration with the different products has been difficult. It is very complex. The complexity is very high. The maturity of the organization needs to be high for this product, and that is where we are missing because we are not mature yet. It's very complex and should be for a mature organization.
Learn what your peers think about OpenText Universal Discovery and Universal CMDB. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
OpenText Universal Discovery and Universal CMDB discovers, maps, and manages your IT configurations. Increase your IT visibility and reduce your IT service disruptions with robust discovery, service dependency mapping, and proactive impact analysis.
Based on my experience and what I have heard from clients, there are two main areas where Universal CMDB could get better. First, the way it shows results to users could be more user-friendly. Second, it can be really complex because there are so many different types of things you can track, and they are organized in a complicated way. This complexity can make it take a long time to learn how to use it effectively. Making it simpler to set up and understand would be a big improvement. I have shared some suggestions with OpenText through their platform. One thing I would like to see in the next Universal CMDB is more consistency and simplification. The results it provides are really good, especially compared to other systems, but the way it shows those results could be more user-friendly. Improving the presentation and making it easier to understand would be a great step forward.
Based on my experience with UCMDB, I've faced challenges while discovering servers (nodes). We need to define the IP list of discovery in RTSM and run jobs. Instead, over the years, if we need to add some new assets, we have to add the new IP in RTSM and run jobs again. From the agent side, we need to provide the data flow probe IP. We can do this things as one way: we install the agent at the server (node) level (define the IP of the data flow probe) and after that, our data flow probe will capture the data from the agent and send it back to the UCMDB. That way, we can remove the one step of adding the IP in RTSM. When we work in an environment, the production environment continuously changes and at that time we should have knowledge about the new server (node). However, the auto-discovery part should automatically discover the new CI (node/servers) in an environment and inform the IT person.
Based on the latest version, there were multiple changes done. It had multiple fixes. However, it's based on the customer's requirements. They have modified and created, and released the changes according to those needs. The UI could be better. The page loading is very slow. The customer wants faster loading. Before releases, it would be nice to be able to upgrade to the new release and check it out in order to see the new functionality and what they have changed.
The implementation could be simplified. It is not implemented correctly and it's most likely us and the way that we had implemented it. The issue is with integration. We have multiple different operating systems and enclaves between on-premises and the cloud services that we are trying to monitor and the integration with the different products has been difficult. It is very complex. The complexity is very high. The maturity of the organization needs to be high for this product, and that is where we are missing because we are not mature yet. It's very complex and should be for a mature organization.
Mobile/iPad Apps version of the UCMDB Browser would be a step ahead, which should have features, like viewing CI information, ownership, etc.