VSphere Client activation

Similar Questions

• Users of Active Directory cannot connect to vCenter 5 device via vSphere Client

  I'm unable to use credentials to access AD unit vCenter 5 via the vSphere client. I get an error message that I can log in because of 'incorrect user or password name' I am able to connect with this AD username and password for my vCenter 4.1, and environment to my RDP hosts by using the credentials of the AD, if AD works very well. And the password that I entered is correct.

  I could connect with AD credentials two weeks ago. Two weeks ago I stopped being able to connect with the credentials of the AD. I dropped back to the use of the local access through the vSphere client root user login. It seems that two weeks ago, my Oracle user passwords has expired. I fixed that by connecting to the EM console and responding to the command prompt to change the passwords. I've "changed" them to return the same password. Then, I subsequently put the limit password_life_time unlimited in the default profile. I tested since the vCSA admin interface the database settings. The settings saved and restarted the service VPXD.

  I have a 5.0.0 - 455964 vCenter device connected to an Oracle database. I activated the AD authentication in vCenter web admin GUI. I restarted vCenter Server Appliance after you have enabled this feature. I have validated that the time on the device of vCenter and the Active Directory zone are less than one second on the other. DNS forward and reverse unit number of AD and self-esteem are good. DNS is hosted on the AD controller, so I have connectivity between vCenter and AD. I run the query domainjoin-cli command and output is correct. I checked from the vSphere that my AD user customer and the ad group each received the Administrator role for the vCenter in the permissions screen object.

  Any ideas where to look next?

  Paul

  Hello

  (1) log the vCenter Server Appliance as root.

  2) reset the number of connection attempts that have failed for the domain user assigned with the command:

  / sbin/pam_tally - reset user user@domain--

  (3) to determine the status of each user, run the following script:

  to CONNECT to ' / opt/same/bin/lw-enum-users | grep name | AWK {' print $2' '}'
  do
  DOMAIN = $(écho $LOGIN | cut-d ' \'-f1)
  USER = $(écho $LOGIN | cut-d ' \'-f2)
  / sbin/pam_tally - user $USER@$DOMAIN
  fact

• 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

• 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.

• 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é

• VMware Vsphere Client "Error unexpected envio" no puedo connect

  Hola a todos,

  I have an al servidor me conecto through VMware Vsphere Client. Hoy al try connect me salta este error:

  vSphere client could not connect to xx.xx.xx.xx a unknown connection error has occurred. (The client may not send a request to the server. (Se ha terminado la conexión: erreur inesperado de envío))

  If hago UN ping an IP the well esta responde y las maquinas office alojadas in el servidor estan well running. Intento connect desde a Windows 8 y otras veces conectado has no sin problemas, pero ahora no puedo. ¿Algun Consejo? MUCHAS gracias.

  Hola,

  El activated HE SSH, he accedido via consoled y ejecutado he:

  services.sh reboot

  Y el problema is ha solved. Este comando're valido para VMWare ESXi 4.x

  A greeting

• 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?

• Cannot save orchestrator in vsphere client of web (v5.5)

  Hello

  We have difficulties registration orchestrator to use in the web client.  Control https://**server-ip**/mob shows that it is registered as an extension and that heart rate were received recently.  However, even after a reboot of the vcenter server services and services of orchestrator, logging out and back in the vsphere client, try to save it manually in the web client, etc is not always appearing.

  When you try to save it manually, what format should be used?  We tried several methods

  1. https://FQDN:8281

  2 https://FQDN:8281 / api

  3. COMPLETE DOMAIN NAME

  4 FQDN:8281

  5. INTELLECTUAL PROPERTY

  6 https://IP

  7 https://IP:8281

  8 https://IP:8281 / api

  All of these methods give a negative result.

  Also, even if SINGLE sign-on is configured, and perform a connection test using configuration orchestrator web page succeeds, we are unable to log into the customer orchestrator!  It indicates that the user is not allowed, even if it's the same user specified in the orchestrator as administrator of the active directory configuration.  Just in case this might help, we use MS SQL Server Enterprise 2012 for the two vcenter orchestrator and.  In order to ensure that orchestrator db was fully complient, we duplicated the DB original vcenter then creates a user in the connection to the db vco and populated SQL tables.  The reported configuration wizard success.  (Note we also tried it with a fresh database and let orcestrator populate tables - which was also successful, but we still had the same problems with integration and customer sign; so to maximize compatibility, in case the db does not have the necessary objects, we have reproduced the vcenter db... the reason for this wsa as orchestrator can use the vcenter server db if installed in "easy" mode)

  We have searched communities and found many people with the same problem, but none of the cases that we found was actually marked "resolved."

  Could someone help us please with it?  Although version 5.5. impressive regarding the progress made and new features, etc., it has been an absolute nightmare of application.  I hope that VMware is working on fixes of bugs because if we had it to do over again, we would stay with version 5.1 for awhile.

  Thanks in advance for your help.  If anyone has had problems with the installation of version 5.5 (fees or upgrade), we can help... just ask me.  At our facility, we had about 6 or 7 different issues to which we have documented resolutions (most are easy to solve, but in a production environment, no downtime is not good!

  Sincerely.

  Post edited by: sietec2 - changed the ports that have attempted to 8081 8281, typo.

  Solved!  After the suggestions from you, I had a hunch and checked the file 'vco.properties'... then noticed something strange.  Here is the content of the file

  INSTALLER_UI = SILENT

  USER_INSTALL_DIR = C: / $Program Files$ / $$ / $VMware Infrastructure$ / $Orchestrator$ / $

  CHOSEN_INSTALL_SET = CS

  VC_Database_User_Name =

  VC_LogOn_User_Name = administrator

  JDBC_URL = jdbc:vdb:vcdb

  VC_web_Service_Http_Port = 8080

  VC_web_Service_Https_Port = 8443

  VC_Http_Port = 80

  VC_Https_Port = 443

  Upgrade_or_Fresh_install_Flag = fresh

  SSL_Certificate_location = C:\ProgramData\VMware\VMware VirtualCenter\SSL\

  Customer_information = Windows user #.

  [email protected]

  SSO_URL =https://Our.domain.com:7444 / sso-adminserver/sdk

  [email protected]

  LS_URL =https://our.domain.com:7444/lookupservice/sdk

  IS_URL =https://our.domain.com:10443 /

  [email protected]

  SSO_DISABLED = 0

  Notice the line "BOLD", VC_LogOn_User_Name, went to the administrator.  Change that to administrator@{ourdomain.com} and restarting the server orchestrator, then logging on and in the web interface of vcenter server resolved the problem and the server of the vco appeared!

  So if anyone has the issue where it won't register in the web client, check the server.properties file in {orchestrator_install_root} and make sure the log the user name is correct for your environment!

  Thanks to those who helped!

• An internal error has occurred in the vSphere Client. Details: Index was outside the bounds of the array.

  Hello world

  I have a number of active hosts VMWare ESXi 5 I manage, but since yesterday I encounter the above error.

  On a new server, I installed ESXi 5 successfully and I can connect to my Client vSphere host. However, as soon as I try to create a new virtual machine, the error message appears. (See attached screenshot)

  Later, I tried to connect to my existing 5 ESXi hosts and has experienced the same error when you try to perform the same operation.

  Any advice on how to fix this? I tried to reinstall the client on my machine without success. However, I can perform the same operations with success since another spare machine I have on the network.

  vSphere Client: Version 5.1.0 Build 786111

  (I'm trying to download the new version as we speak)

  Well, there are two things you could do to further isolate:

  1. on your account, try a clean boot and check http://support.microsoft.com/kb/929135

  2. try to recreate your user profile and check the difficulty of a user profile is corrupted

  Concerning

  one

• PowerCLI equivalent to vSphere client "Detach" memory card?

  I'm trying to find the PowerCLI equirvelent to disconnect an adapter of the ESX host storage device. Preferably using the LUN ID.

  For reference, in the vSphere client GUI I have run the command by selecting a host configuration tab, then select adapters and storage in detail looking at the peripheral view, I can right click on a device and have the ability to "unpin".

  I've been watching the cmdlets Get-ScsiLun and Set-ScsiLun.

  I have also been watching the ScsiLunPath together and wonder if Active the parameter false, that's what I'm looking for?

  I am also looking to hard drive Set and remove hard drive but these commands seem to be relevant to VM and hosts no.

  Any help or hints would be appreciated.

  This new feature in the vSphere client 5 is not taken in charge by a cmdlet PowerCLI AFAIK.

  But you can get the same result by using the DetachScsiLun method.

  2 following functions (I added a function to fix as well) will allow you to detach and attach the lun.

  I chose to spend the LUN target via its canonicalname, but you can easily adapt the functiosn to use another LUN property.

  function Detach-Disk{
      param(
          [VMware.VimAutomation.ViCore.Impl.V1.Inventory.VMHostImpl]$VMHost,
          [string]$CanonicalName    )
  
      $storSys = Get-View $VMHost.Extensiondata.ConfigManager.StorageSystem
      $lunUuid = (Get-ScsiLun -VmHost $VMHost | where {$_.CanonicalName -eq $CanonicalName}).ExtensionData.Uuid
  
      $storSys.DetachScsiLun($lunUuid)
  }
  
  function Attach-Disk{
      param(
          [VMware.VimAutomation.ViCore.Impl.V1.Inventory.VMHostImpl]$VMHost,
          [string]$CanonicalName    )
  
      $storSys = Get-View $VMHost.Extensiondata.ConfigManager.StorageSystem
      $lunUuid = (Get-ScsiLun -VmHost $VMHost | where {$_.CanonicalName -eq $CanonicalName}).ExtensionData.Uuid
  
      $storSys.AttachScsiLun($lunUuid)
  }
  

  You can call the function like this

  $esx = Get-VMHost MyEsx $name = "The-canonical-name-of-the-target-LUN"
  
  Detach-Disk -VMHost $esx -CanonicalName $name
  

• VSphere Client errors after upgrade to 4.1

  Since I upgraded our infrastructure to 4.1 4.0, the Vsphere Client throws an error anytime it is left open for an extended time.

  If I open the client and let it sit for a few hours or overnight, I will go back to him and ther will be a popup of error with the following details.

  An internal error has occurred in the vSphere Client.

  Details: No enopugh storage is available to process this command.

  Contact VMware support if necessary.

  Once this bug has produced the error dialog box may not be rejected if you click Close, it just POPs upward.  The customer is inaccessible after this point, as the error dialog box is selected and that you can not touch the main window.  You must kill the client of Taskmgr.   Then it will restart and will work perfectly for a certain period.  Occasionally, almost hitting the error dialog will return to the client, but most of the tabs is not working and clicking on almost anything causing the error.  It is not a show-stopper, but it is a time wasting, irritating bug.  I've never seen the bug pop up while I was working on the customer, so I don't know what triggers it.

  The client runs on Windows 7 64 bit, but I have confirmed same behavior under the Server 2008 32-bit client.  I have not seen the error yet when the client is on Server 2003 32-bit, but I can't be left open long enough so that the error present.  Attached are the log files that the dialog box 'Error report to VMware' wants to send.  The customer is attaching to a server VCenter 2008 64 bit, not the ESXi hosts.  The smallest attached data store has more than 40 GB of free space.

  I have not supported active then the ratio to VMware dialogue suggested I post here.  It doesn't seem to be a community specifically for the customer and this started only after the upgrade, so I posted it in this community.

  Thank you
  Joe

  I think I followed the status tab of the hardware. If I use the hardware status tab and let it sit there for a while, memory begins to be chewed.

  I opened a SR w / Vmware, and they confirmed. Their words:

  "After a webex and looking through our internal KBs, I was led to a bug and the KB and the bug that both speak to the material status page causing a memory leak to do with CIMs and JAVA.  It looks like no to this question will be resolved in a future version, but it does not say clearly what version they will address in.  4.0U1's should be out soon.  I think of 30-90 days.  Workaround at this time is to not let the vSphere Client open for long periods of time. »

• 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

• SRM plugin has me re - authenticate each time after I have logged in vSphere client?

  After I authenticate the client vSphere and then proceed to the section of Site recovery, I wonder to be re - authenticate the vCenter recovery.

  Is it possible to store my credentials, so I sign in twice now when I need for activities of MRS?  Once for vsphere client, and then back to recovery vcenter as SRM is plugged.

  Thank you.

  This is a normal activity and there is not yet a cache for the other site identification method, would be awesome to have device assuming that the remote site is located in the area of trust or A.D. even.

  Tim Oudin

• How to correctly record the ESXi 4.0 and vSphere Client for free?

  Hello everyone.

  Can someone help me with registration

  of free VMware ESXi 4.0? I am totally confused with the process I

  certainly do not understand.

  My goal is to install and use ESXi

  4.0 and manage via vSphere client with free licenses free of charge for

  more than 60 dayes. Is it possible?

  Installation of its products

  gone without problems, but failed to save. I found a few

  suggestion on other threads, but nothing helped. Give me a hand please,

  I will be grateful.

  I'll write what I did:

  1. I went to the http://www.vmware.com/products/esxi/ site.

  2. I read that I can get the free license for VMware ESXi 4 and VMware vSphere Client.

  3. Decided to download this software, registered and was redirected to
     the site where I could download iso 4 ESXi and vSphere Client .exe

  4. Installation and basic configuration of ESXi on the bare metal and vSphere Client Windows XP without problems.

  5. I am able to create virtual machines and use it - it's OK, but vSphere Client know that I have to the 60-day trial.

  6. Meanwhile I received the email with "Activate your VMware ESXi license".

  7. I have
     Click on the link in the e-mail and was redirected to the same
     the site, where I can download the software, but on the top of the web page I can
     find information and a 'ESXI licenses""this license key is valid.
     "for VMware ESXi 3.5 Update 2 and later versions. So I guess it's also valid
     for ESXI 4.0. I'm I right?

  8. I would like to record my ESXi 4 software installed and the vSphere Client. Of
     I chose the vSphere Client Menu: help - & gt; VMware on the web - & gt;
     Sign up for now. The site ask me "series/license number Activation".
     Code"so I typed the license key. Iassume that this license key should not be placed here, because the web site of replay that: "Code of Activation of series/license number has already been registered. So how do?

  As I wrote, I'm confused. How to correctly record the ESXi 4.0 and vSphere Client? What I did wrong and how to fix?

  To register the serial number in your ESX4i host

  Home-> inventory-> higher level (your ESXi host)

  Tab Configuration

  Left side - features licensed

  Edit-> Assign new key for this host-> Enter Key

  Paste your key

  Confirm all

  Your ESXi server is now fully licensed

  Note: you no longer have the basic features and all the enterprise features that came with a trial license are no longer valid

  Maish

  Architect of virtualization & Systems Administrator

  http://technodrone.blogspot.com

• 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