I've seen something similar but it was for a previous customer so I can't verify how much of this I remember correctly...
The hierarchy of the KM config changes between some of the versions of the KMs (I saw it with the Linux KM). This means that a config that is valid for one version (let's say 1.1.10, just as an example) does not directly map to the new version (let's say 1.2.00).
I've seen the config disappear when you manually change the version to a newer one with a different structure. It feels like the JSON structure that it's building in 11.3.03 has a problem and so it's not building the policy properly. I've also heard rumours of similar problems after updating the repository.
Can you export the original policy at commandline, go into the config and then save so that the config seems to disappear, and then export the policy again? I'm wondering if the config is still there but it's not being presented in the GUI?
1 of 1 people found this helpful
It is a hotfix for that.
DRTMN-63 Monitoring policies with two or more monitoring solutions are deleted on editing them.
You need to install the hotfix 11.3.03.000.004
2 of 2 people found this helpful
Thanks, I eventually found the download link in the following article:
I've looked back through the patches and the fix only appears in 11.3.03. I think the issue may be present in earlier versions but I can't confirm that yet.