You should use 'root' account when logging into VAMI.
AFAIK there wouldn't be any impact on VSS, vMotion, port groups. Might impact vDS.
hi thaks you to spending time on my question.
after loging with root user it said validate sso and want sso user.
what about vm that moved after backup and hardware locks on host servers?
i stoped HA,DRS and there were no VDS because i changed my servers and update them.could i install a new VCSA and disassociate host from failed VCSA and add then to new VCSA?
Yes deploying new vCSA is better option in my opinion.
You just have to add the hosts to new VCSA.
Please mark my comment as the Correct Answer if this solution resolved your problem
there were no place to disassociate host from failed vcsa on esxi 6.7 u3 web ui?
1. Deploy new vCSA
2. Create new Data-center and cluster if need be.
3. Right-click and add the ESXi hosts to the new vCSA.
didn't need to disconnect hosts from previous VCSA or maintenance mode?if need it just has disconnect from vcenter in menu?
do you advise VCHA that seems to be far from production environment?it not it?
thank you dear vijay i goto work and check it. i hope it works. i do reply the result.
thank you vijay i deploy nes VCSA just one more question.
is there a way to add host with power on vm to new vcsa?
or suspend vm to add them to cluster?are they keep current state if they suspend?
You don't have to suspend or power-off VM's.
Just add the hosts to new vcsa
If you don't add your ESXi host in a cluster with EVC-enabled feature, no need to worry about VM's operation. You can simply add the Host without any concern for your VMs power state.Please mark my comment as the Correct Answer if this solution resolved your problem