After an upgrade of vCenter and ESXi from 5.1 U1 to 5.5 U1, when using the 'traditional' 5.5 C# vCenter Client, my existing pre-upgrade Storage Profiles now show as "Noncompliant" for the "vm home" component of a VM, with the reason of "Capability Mismatch" given. However, Hard disks continue to show "Complaint" as normal and expected.
Recreating and reassigning the Storage Profiles for datastores and VM's fails to resolve the issue. Restarting the Profile Driven Storage Service has also failed to have an impact.
Storage Profiles all show as Compliant when using the Web Client, and all seems to function perfectly fine when using that interface.
Is it possible that there is a compatibility issue when using the C# Client as opposed to the Web Client when managing Storage Profiles?
Edit: I have also implemented VMware KB: Profile Driven Storage service fails to start after upgrading to vCenter Server 5.5 though it has had no effect on the Storage Profiles issue in the C# Client. Elsewhere there is the suggestion that the Inventory Service should also be run in the same authentication context as the vCenter Server Service, which I may try.
Message was edited by: EnterpriseTeam