I am running vRO 6.0.3, and I don't seem to have that problem.
I have a Wildcard certificate (similar use-case as yours), which I would like to use for both the VAMI (5480), the Configuration Interface (8283), the Web HTTPS (8281), the Client Communication (8286 and 8287) and acutally also for the "Server Package Signing Certificate" part of vRO.
I have got it to work with VAMI (5480), the Configuration Interface (8283) and the Web HTTPS (8281).
But when I connect using the Orchestrator Client, it sees the new Certificate. The CA (root certificate) and the CA Intermediate part of the certificate is trusted, but the actual Wildcard part is untrusted.
I am also have a hard time, figuring out how to use this Wildcard certificate for the "Server Package Signing Certificate".
So if you have gotten any of those parts working I would be happy to hear about that.
