Hi, we managed to find the solution. It's a permission issue! For the horizon user we didn't user an Administrator role but a special Instant Clones role as described here: Privileges Required f...
See more...
Hi, we managed to find the solution. It's a permission issue! For the horizon user we didn't user an Administrator role but a special Instant Clones role as described here: Privileges Required for the vCenter Server User With Instant Clones (vmware.com) But it turned out that this list lacks the permission "Alarms" > "Disable or enable alarm on entity" making the horizon connection server unable to disable the memory warning alarm on the cp-parents objects. Enabling that permission and publishing a new image finally solved the problem! I was told that they will eventually fix the docs and publish a KB. Giuseppe