Wir verwenden Cookies, um unsere Dienste zu verbessern. Lesen Sie mehr darüber, wie wir Cookies verwenden und wie Sie diese ablehnen können.
It happens often:
Yet the audit report is shocking.
And it leaves you wondering, why?
Here's what you can do to prevent that.
Is your entire IT covered by the tool?
What about:
Pro tips:
If you only have inventory of virtual machines but no related data from hosts and clusters, the data is useless for compliance calculations.
Pro tips:
Tools are rarely capable of automatic discovery of virtualised infrastructure.
Out-of-the-box software catalogue may not “know” that you acquired your licences in bundles. Ifso, compliance calculations will be incorrect.
IBM software may be the most frequent but not the only example.
Pro tips:
Ifyour license says “per user” but the tool reports software per device, how can you calculate compliance?
Pro tips:
It’s not unusual to have duplicates or incorrect data in the tool. The reasons may be:
-Multiple data sources, -Multiple discovery methods, -Quality of data from third party tools -Manually maintained CMDBs
Pro tips:
Sometimes the tool just doesn’t know how to calculate compliance position (ELP).
Even worse,it may simply be incorrect.
Oracle customers are the most frequent victims of tools’ shortcomings. But it may happen to any other vendor’s software.
Please contact us to discuss how we can help you achieve the best commercial outcome.