For anyone following this post, it looks like Dell have finally released VASA provider support for subordinate vCenter Server VMCA's in v5.1.0.0.5.394. #hallelujah New Features: Support for subordinate VMware Certificate Authority (VMCA) Summary of benefits: Unity now supports subordinate certificate authority configuration.The VMCA is the default certificate authority that is used to secure communications between vCenter Server and a VASA Provider. With Unity releases before 5.1, the VASA provider (VP) only supports self-signed certificates from the VMCA. Only VASA 2.0 and VASA 3.0 configurations in which the VP can be registered are supported.  Dell EMC Release Notes for the Dell EMC Unity Family for Release Version: 5.1.0.0.5.394 (Dell Support Login Required)  
Hi, I know this has been discussed on here before, as it has been an issue for over 3 years now, but please can someone from the Unity product marketing or engineering team advise if there is any real plan for it to ever get fixed; and if so what priority has it been assigned & when are we likely to get the fix (months/years)? [IMAGE] "Failed: Unable to register VASA vendor provider on the VMware vCenter. Please review the event logs on the VMware hypervisor side. (Error Code:0x5c00013)" I would love to use VVols, but I cannot register the VASA provider as my vCenter Servers are using subordinate CA certs to my Enterprise PKI CA's. This is not a 'unicorn' configuration and no other array vendor I work with has this problem. The official workaround ([URL] is laughable. Reconfiguring vCenter Servers back to using Self-Signed certificates is not an option. If you could also advise the internal 'Issue ID' this has been assigned, it would make trawling the release notes easier. Cheers, M
Unable to register VASA provider with vCenter Server when VMCA is 
subordinate/intermediate to enterprise CA