I am also seeing this issue. VSC is causing the domain account of the logged in user in the VMware Web Client to become locked out. This is a pretty big problem. Any one have a clue on what's causing this?
I am working on a similar issue internally and here is what I know that might help:
Symptom: Account used to login to vCenter web GUI is locked out in AD when VSC is used.
- Veryfy that SMVI/VSC services are using local system account to run (VSC was should be email@example.com with vCenter) - Stop SMVI/VSC services - Set SVMI/VSC services to run as an AD service account - Restart SMVI/VSC services - Re-register VSC plugin with vCenter server with credentials for an AD account. - If issue continues, open a case with NetApp Support and provide full AD event logs showing logins leading up to account being locked to from VSC)
I'm also having this problem. I installed the production release of vsc 5.0 earlier this week. My AD account is being locked immediately when I access the Backup Jobs section. I have full administrator privilegies in vsphere/vsc as well. I've tried the mentioned possible solution in this post, which didn't help. Any other ideas?
Same issue. Any user who launches the vSphere web client and logs in using their AD account soon has their account locked. I have a ticket open with NetApp, but here's what I'm seeing in smvi.log that looks to be the culprit (%Program Files%\NetApp\Virtual Storage Console\log). AD user omitted but in bold. AD lockout times match up with log entry times.
I am having the same issue as described in the OP.
I tried Jeff King's solution from above with no luck. Disabling the SMVI service did allow us to continue working within vCenter without getting locked out, but prevents making any changes to backups or performing any restores.
I had the same issue after upgrading the VSC from version 4.2.1 to 5.0. My issue was gone after I set the default credential for the storage systems again. You can find this setting in the webclient when clicking on the NetApp-Icon -> Configuration -> Set default credentials
After setting the correct credentials for your storage systems please run the a discovery task afterwards. (Storage Systems -> Update all)
There was a similar issue in earlier releases. Your AD-Account was locked once you entered invalid credentials for the storage systems.