the client can only open one instance (vCenter/ESX) at a time. You can open multiple instances of the VIC, but then it may become an administration headache. It may be time to start to look at vCenter.
Hope this addressed your question.
Check out this link http://itknowledgeexchange.techtarget.com/virtualization-pro/configuring-single-sign-on-to-log-into-virtualcenter/ that will let you set up SSO and have the option you are looking for
VMware Communities User Moderator
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: http://www.thevirtualblackhole.com/
*Virtualization is a journey, not a project.*
I have the Vcenter, but in the project I'm working on, the customer wants to have also two ESXi servers outside the Infrastructure. I know is annoing to connect everytime to a different host, but unfortunately it is so
the link steve provided will work for single sign on the vCenter, but not for ESX. The only downfall with the single sign on is that if you need to go to an ESX host, you'll have to remove the parameters before launching the client.
I think, you will have to launch multiple clients to get to the ESX side.
Thank you very much ! The -s option is the solution.
I have mRemote connection manager, where I can configure the lauch of external applications (in this case VI client). I create one <VpxClient.exe -s> entry for every ESXi server.
I have tried just now, and it is work: VpxClient.exe -s <hostname> without
Are you sure about that? I was almost positive that it will connect to whatever it points too
I know it works for passthrough to vCenter, but I don't understand how it would work for passthrough to ESX. I'll test and see what I can come up with. Unless you know the exact syntax.
I'm not automatically connect into the host, but the client automatically fill the ip address/hostname field. I must to enter login/password, but I'm satisfied by this