vSphere client remembers sessions

Similar Questions

• vSphere Client Console Session zooms online

  Hi all

  I have a strange here, I hope that someone can help you.  I installed vCenter 6.0 and added my 6.0 hosts.  When I connected the web client of vSphere and open a console in one of my servers Windows 2012 (others worked well) the console session seemed to open up over and over again within himself until I got a ultra zoom in the console session the I can't navigate around where do much of anything with.  Even the prompt to hit ctrl-alt-del and the login screen are ultra zoom.  I tried to use ctrl-mousewheel to zoom out, but who have no real effect, it comes to the smaller icons.  I am able to use the tab and search for open some programs, and I know that they are open because when I alt - tab I can see them and cycle through them, but when I'm on the desktop, I see is a blue field, I can not interact with and a giant cursor.  This behavior is present when I use the client Citrix go and help that is installed on the server, but it's good to a remote desktop session.  I can RDP into the session zoomed and see everything that is open and properly interact with it.  I tried to restart the guest and the host without success.  I am at a loss.  Help!

  I have attached a few screenshots to show what I'm against.

  Nick

  Hello

  I guess that this behavior of the console view of the virtual machine via the c# client is fine?

  What browser do you use on your and have you tried another? It seems strange that this only happens on 2012 R2 servers!

• vSphere client using the name Netbios on ESXi host does not connect using the credentials of a Windows session

  I have 3 ESXi 5.5 hosts, all connected to a single server vCenter, where we try to authenticate directly to the host by using the windows logon credentials. I have installation of the Administrators group of ESX and filled with the admin accounts that I want to be able to authenticate to the host. The Netbios name of the domain is tstdomain (for example) where the domain name is tstdomain.com. If I connect directly to a host and check the checkbox 'Use Windows Session Credentials', the vSphere client will default by using the Netbios name of tstdomain\adminusername and the connection will fail indicating that the username and/or password is incorrect. If I enter the domain name of tstdomain.com\adminusername, I am able to connect to the host without error.

  Does anyone know how get past that this matter have the vSphere client uses the domain name or to use the Netbios name and connect with the credentials to active directory? I looked by editing the file/etc/hosts and checked that the SPN of the host is correct in active directory with the command hostname setspn - l, with no luck on one. I also tried to change the field of research for the Netbios name of tstdomain rather than the tstdomain.com domain name, also did not work.

  Thanks in advance for your suggestions on how to correct the problem.

  Seems that this issue was due to a slow network and the connection timeout when you try to talk to the domain controller. I am able to connect with windows creds now, but the connection is very slow. I increased the default period of 30 to 60 seconds to help work around the problem.

• vSphere Client: bad user name or password

  Hello

  I'm new on the vSphere server and it seems that I made my first big mistake.

  I installed a 6 of VMware ESXi server and I am not able to connect to the admin with the vSphere Client account more.

  If I use the same credentials to log in via ssh or PowerCLI, I can connect and everything works. But when I use the vSphere client it says that the user name or password is incorrect.

  I tried to add a new user in the shell but when I try to connect with this user via the vSphere Client, I get the message that the account does not have permission to open a session.

  I also tried to use "pam_tally2 - user = root - reset" to reset the counter of failed connections, but it always says 0 failures and doesn't change anything for me.

  Change the admin password (in the shell via passwd) doesn't help either.

  Is it possible to grant permissions for connection the Client vSphere for users outside of the shell or the PowerCLI?

  Or is it possible to "wake-up" or "unlock" my admin account?

  Thanks in advance,

  DerpDerpson

  list of permissions of the system esxcli [root@VMS2:~]

  Main is the group role role Description

  ----------  --------  --------  --------------------------------------------

  false dcui rights to full Admin Access

  root of false full Admin access rights

  VI-admin00 Admin access rights full false

  vpxuser access rights Admin full false

  Nagios ReadOnly false details of the objects, but not to make changes

  VI-user00 ReadOnly false details of the objects, but not to make changes

  set of permissions of system esxcli - r = Admin-i = nagios

  
  

  list of permissions of the system esxcli [root@VMS2:~]

  Main is the group role role Description

  ----------  --------  --------  --------------------------------------------

  false dcui rights to full Admin Access

  Admin full false Nagios access rights

  root of false full Admin access rights

  VI-admin00 Admin access rights full false

  vpxuser access rights Admin full false

  VI-user00 ReadOnly false details of the objects, but not to make changes

  It's an example of how to grant rights of ssh.

  You can try with your test user?

  Brgds

• vCenter 5.5 sso works with web client but not for vsphere client

  Hello

  Just upgraded my vcenter from 5.0 to 5.5. In 5.0, I could connect to the vSphere client, using my creds of windows session, but now I can't and have to use the local account that is a member of the Administrators group local machine or [email protected]. However, it works very well with the web client.

  The Source of the identity seems to be correctly set. Have searched for a solution for four days. I'm at my wits end... :-(

  You may need to assign permission to your vCenter, refer to step #6: Back To Basics: vCenter post-configuration 5.5 installation (Web Client). VMware SMB - VMware Articles blog

• Impossible to connect to vCenter Server 5.5 using the vSphere Client

  Hello

  
  

  I'm trying to configure VMware Lab home using the link below and I have reached a stage where I need to connect to vCenter Server using the vSphere client.

  
  http://boerlowie.WordPress.com/2011/12/13/building-the-ultimate-vSphere-lab-part-9-ESXi/

  
  

  I installed the package of 5.5 full vCenter server using the simple installation option and it includes vCenter server, single sign - on, Webclient vSphere, vCenter server and vCenter Server inventory service. All the the latter is installed on a virtual machine that is running Windows server 2008 R2 guest OS.

  
  

  Whenever I try to open a session on the vCenter Server uses the vSphere client, one of the following error is displayed.

  
  

  1. you do not have the permissions to connect to the server 'vCenter server IP address.

  2. cannot complete the connection incorrect username or password-, this error is visible when I do not specify domain\username domain user name and simply enter the user name.

  
  

  For the details of the error, please see the screenshots - vSphere_client_1, vSphere_client_2 and vSphere_client_3.

  
  

  As suggested in the link below, I tried to create an SPN and then set the SPN (Principal of Service name) and the UPN (User Principal name) in the Active Directory identity Source using the web of vSphere client (please see screenshot vSphere_Webclient_2)

  
  

  http://vinfrastructure.it/2014/01/issue-in-logging-into-vCenter-server-using-Windows-ad-credentials/

  
  

  To fix the permission error, I tried to add the domain user to the Administrators group on the server vCenter (see screenshot vSphere_Webclient_1).

  
  

  However, none of the above-mentioned resolution has worked.

  
  

  So can someone please help? I am stuck because of this problem and badly need help to move forward.

  
  

  Thank you

  AJMAL
  

  Able to connect to the vSphere Client do you use the [email protected] account?

  Have you already set up permissions on the server vCenter object?

  André

• I can't create the local group on vSphere Client 5.5

  Hello, Hello all!

  I'have the vSphere Client 5.5 and I cannot create a local group on the tab "local users and groups. When I create a group shows me an error and I can not create it. This is the error that I have:

  Call "HostLocalAccountManager.CreateGroup" of object "ha-localacctmgr" on ESXi 'IP' failed.

  I am connected to the root.

  I saw in other forums that it is impossible to create groups due to the last version is only possible in the Web Client that comes integrated with vCenter.

  In the old versions is possible, but when I open a session in vSphere Client 5.0 for example, I have to update version and I can't use the 5.0 version.

  How can you help me?

  Thanks and greetings

  PD: Sorry for my bad English

  Hi Danisb3,

  It seems that local users is now the recommended around work (see link above), but as you said if you have vCenter you can add groups

  ESXi 5.1 and later versions does not support local groups. However, Active Directory groups are supported - is it possible to connect to AD?

• vSphere Client Version

  I thought we were supposed to be able to host managed low level with a newer version of vSphere, but this is not the behavior I see.

  We have a server vCenter 4.0 4.0 guests and autonomous one 5.0 host.
  I got vSphere Client installed on my machine and connected to the host 5.0 4.0. I was prompted to install vSphere 5.0. When I tried to connect to one of our 4.0 hosts, I was prompted to install vSphere 4.0 and could not open a session up to what I did. Now, I need to install vSphere Client 5.0 until I can connect to the most recent host again.
  What Miss me?
  Thank you.

  that's what it looks like in the folder programs with multiple installed versions.

  

  André

• VSpher client connection?

  Hello

  To make clear that I am a novice.

  I installed, ESX5.1 (bare metal), [VCenter Server, VSphere Client and client VSphere Web]-> Windows 2008R2.

  It is the second facility from scratch.

  In my first attempt, when all them above were installed, when I tried to log in using VSphere client, I could use the AD ID and I think what he connecterd me to ESXi through VCenter.

  In my second installation, I can connect via Vcenter using the Web client, using my username AD (ID of the administrator group). Everything works fine, I created data center and added ESXi.

  However when I click on VSphere Client, it does not accept my AD account and it only accepts the ID of the root for ESXi

  I don't know if this is what is supposed to happen?

  So the questions:

  1. in order to access ESXis using VSphere Client through VCentre, what should I do? I mentioned, that if I try to open a session using the client it does not accept AD ID

  2. How can I use webclient and no client (via VCenter)

  < added some information: I renamed localhost in ESX01 ESX and he joined the field in the context of troubleshooting and client NTP is configured on ESXi, not Windows 2008R2, but Jet lag is less than 30 seconds if not less >

  As I said I am new, however I am giving the foregoing experience of logical explanations.

  Thanks in advance.

  Welcome to the communities...

  I don't know if I understand your questions, I tried with my awakening in response to your questions

  1. in order to access ESXis using VSphere Client through VCentre, what should I do? I mentioned, that if I try to open a session using the client it does not accept AD ID

  You try to access your ESXi host or vCenter server by using AD ID?

  However when I click on VSphere Client, it does not accept my AD account and it only accepts the ID of the root for ESXi

  Have you checked that you access your vCenter and no ESXi host using vSphere Client?

  vCenter is a management software that allows to manage ESXi host. WebClient is only available to manage vCenter server and NO ESXi host

• OVF import directly to ESXi without going through the bottleneck of Vsphere client

  I'm currently installing the OVF VMA to ESXi 4.1. ESXi is installed in a data center. VSphere client is installed on my computer at home.

  I chose the URL to install from the ESXi thought it would download directly, but no, it seems that the VSphere client wants to download and then upload to the data center via my broadband connection bottleneck domestic. I'm looking now to 233 minutes to make all this happen.

  I'm still on a learning curve steep then there may be something obvious that I missed, but is it possible that I can bypass the internet connection is slow my home computer (I only have 1.3Mbps uplink speed) and deploy the OVF directly in the data center?

  There are command line tools that I can run on, say, a VM Linux running VSphere CLI to do the same thing? I couldn't find anything in PDF files, I watched so far.

  Thank you...

  Welcome to the community,

  you do not have access to the vCenter Server? In this case, you can open a vCenter Server RDP session and run the top vSphere Client to download and import the vMA.

  André

• VSphere Client limit "the virtual machine console.

  Hello

  I have done several searches and could not find anything relevant so I thought I'd post the question.

  I have ESXi 4.0 running with the installation of 3 virtual machines. I connect to the ESXi 4.0 via Client.exe vSphere hypervisor in windows.  I have a couple of people using the same account. For this reason, we have noticed that, if one of us is connected to a virtual machine, the other person can open the console of the virtual machine also and mess with what they do.  He warns that many people are watching the same virtual machine with the bar at the top of the screen indicating there are now 2 sessions of active console.

  My question is: is there a way to limit the client to only allow a connection active console both to a virtual machine?  That way if someone is already logged in / virtual console and a view, no one else can.

  I understand that I can create several vSphere client accounts with restrictions on the permission to have each account only have access to a specific virtual machine, but I would like to avoid that if possible. Everyone should have access to each virtual machine... but not at the same time...

  Perhaps there is a configuration file (or the customer's option) to limit connections of the console to one (I guess that there is a limit somewhere?).  I found there is a "VpxClient.exe.config", but it doesn't look like this kind of information can be changed here?  If this is something that is encoded in the software I will drop it, but I thought I don't know if I asked

  Thanks for your time to answer this question,

  Dan

  by default, it is set as 25, but that can be changed.  However, it is on a customer by customer basis, so as far as I know, there is no comprehensive way to do this.

  In your client - mounting - settings of the client

• Version 3.0 on 5.5 vCenter using vSphere client

  New vCenter 5.5 (build 2646482) most recent of the VMware Web site.

  vSphere client 5.5 (of course)

  Brilliant new V3.0 of OMIVV

  Installation device and registered in vCenter without error.

  Seems to work in the VMware web client (I'm still exploring). I can manually add servers iDRAC.

  Since the heavy Win32 client, I don't get the Wizard but I get an empty bar in the middle of the screen with "Error #2048" down at the bottom.

  My client is Win7 x 64 with IE10 default browser.

  Where to start?

  See you soon

  Ian

  Hello Ian,

  Try the following steps:

  1. Disconnect and connect to VMware Desktop client (thick client).
  2. Go to home > hosts and Clusters > select any host Dell > click the tab "OpenManage Intégration" and wait for it to load
  3. Now, click on Home > Dell Management Center, it should work now.

  Let me know how it goes.

  Thank you

  Vikram KV

• To access the vFoglight of in vSphere Client

  In regard to the video of the week "Accessing vFoglight go in vSphere Client" where the files that are mentioned in the video can be downloaded from?

  vfoglightplugin.XML and vsi.car

  A blogpost that contains the files can be found here: http://en.community.dell.com/techcenter/virtualization/infrastructure/b/storage-blog/archive/2012/03/06/integrating-vsphere-client-with-vfoglight

  Post edited by: Mattias Sundling

• Table of vSphere not visible from vsphere client

  I am new to vmware, so apologoes in advance for the newbie questions.

  
  It is a new HP ML350 server with 4 x 900 GB drives configured as a single raid 5 ldev. When I connect win7 via vmware vsphere client to add a data store, there is nothing to choose. Have I missed a step or something?

  OK, problem solved. To solve another problem, Support HP had me use the switch on the motherboard to reset the configuration. After the reboot, I got a data store!

• the root account not working for vSphere Client 5.5, for SSH works fine

  Hey.

  I got this:

  I can connect to vCenter 5.5 by SSH and the root user and password works fine

  I can connect to vCenter 5.5 by vSphere Client and use domain user and everything works fine

  I cant't connection 5.5 by user of vSphere vCenter Client and use of root and the password. I have information on

  "Cannot complete the connection because username or password incorect.

  IM shure I use the right password for root.

  A suggestion?

  

  Ok. Thank you community vExpert and Lukasz of my team, we found easy reason perhaps, but not at the first glance for me

  We had the installer by default "Source of identity" for Active Directory then when I used only root for connection I got the error with wrong password.

  In this possible case is just to connect to vcenter using root@localos credintials.

  

  But in addition we sam of similar mistakes inside the SSO connects:

  Location of the vCenter Single Sign-On log files for vCenter Server 5.1 and 5.5 (2033430) | VMware KB

  /var/log/VMware/SSO/VMware-STS-idmd.log

  2016 06-21 13:57:31, ERROR 142 [IdentityManager] could not authenticate [root] main tenant [vsphere.local]

  javax.security.auth.login.LoginException: failed connection

  at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.authenticate(LdapWithAdMappingsProvider.java:327)

  at com.vmware.identity.idm.server.IdentityManager.authenticate(IdentityManager.java:2412)

  at sun.reflect.GeneratedMethodAccessor24.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at sun.rmi.server.UnicastServerRef.dispatch (unknown Source)

  to sun.rmi.transport.Transport$ 1.run (unknown Source)

  to sun.rmi.transport.Transport$ 1.run (unknown Source)

  at java.security.AccessController.doPrivileged (Native Method)

  at sun.rmi.transport.Transport.serviceCall (unknown Source)

  at sun.rmi.transport.tcp.TCPTransport.handleMessages (unknown Source)

  to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run0 (unknown Source)

  to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run (unknown Source)

  at java.util.concurrent.ThreadPoolExecutor.runWorker (unknown Source)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (unknown Source)

  at java.lang.Thread.run (unknown Source)

  Caused by: com.vmware.identity.idm.InvalidPrincipalException: could not find the main id: {name: root domain: OurAdDomain.local}

  at com.vmware.identity.idm.server.provider.BaseLdapProvider.findAccountLdapEntry(BaseLdapProvider.java:543)

  at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.getUserDN(LdapWithAdMappingsProvider.java:1715)

  at com.vmware.identity.idm.server.provider.ldap.LdapWithAdMappingsProvider.authenticate(LdapWithAdMappingsProvider.java:323)

  ... 15 more

  2016-06-21 13:57:31, 144 ERROR [IdentityManager] failed to main checkUserAccountFlags [root] for tenant [vsphere.local]

  "2016-06-21 13:57:31, 144 exception ERROR [ServerUtils] ' com.vmware.identity.idm.IDMLoginException: the connection has failed.

  com.vmware.identity.idm.IDMLoginException: failed connection

  at com.vmware.identity.idm.server.IdentityManager.authenticate(IdentityManager.java:2481)

  at sun.reflect.GeneratedMethodAccessor24.invoke (unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)

  at java.lang.reflect.Method.invoke (unknown Source)

  at sun.rmi.server.UnicastServerRef.dispatch (unknown Source)

  to sun.rmi.transport.Transport$ 1.run (unknown Source)

  to sun.rmi.transport.Transport$ 1.run (unknown Source)

  at java.security.AccessController.doPrivileged (Native Method)

  at sun.rmi.transport.Transport.serviceCall (unknown Source)

  at sun.rmi.transport.tcp.TCPTransport.handleMessages (unknown Source)

  to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run0 (unknown Source)

  to sun.rmi.transport.tcp.TCPTransport$ ConnectionHandler.run (unknown Source)

  at java.util.concurrent.ThreadPoolExecutor.runWorker (unknown Source)

  to java.util.concurrent.ThreadPoolExecutor$ Worker.run (unknown Source)

  at java.lang.Thread.run (unknown Source)

  2016-06-21 13:57:31, 144 INFO [IdentityManager] authentication failed for user [root] the tenant [vsphere.local] in milliseconds [4]

  When I used the credentials with appropriate domain name:

  root@localos we received newspapers below:

  2016-06-21 14:11:58, 971 INFO [LinuxNativeAuthDbAdapter] [root] user authentication

  2016-06-21 14:11:58, 974 INFO [IdentityManager] authentication successful for the user [root@localos] [vsphere.local] tenant in milliseconds [3]

  2016-06-21 14:11:58, 984 INFO [LinuxNativeAuthDbAdapter] to get local groups for the [root] user. Recursive? [Yes]

  When I temporary switch the source of identity - "localos" and use the root account to log logs below, we received and I connected without problem:

  2016-06-21 14:14:37, 545 INFO [LinuxNativeAuthDbAdapter] [root] user authentication

  2016-06-21 14:14:37, 549 INFO [IdentityManager] authentication successful for the user [root] the tenant [vsphere.local] in milliseconds [4]

  2016-06-21 14:14:37, 564 INFO [LinuxNativeAuthDbAdapter] to get local groups for the [root] user. Recursive? [Yes]

  Now, for me, more clearly

  Once again thank you

  Sebastian