VIServer - connect to an ESXi host

Similar Questions

• A procedure for restart underlying SAN connected to 5 ESXi hosts?

  Hello

  We get the warning of the underlying SAN connected to ESXi 5 hosts.  Consultant suggests restarting the SAN and the FC Switch.

  We would like to know is there, any measure must be made on the hosts ESXi connected to the San to restart will not affect the ESXi host and VM?  Such as: Stop all VMs,... etc.

  Your opinion is requested.

  Thank you

  I would say, put the army in maintenance mode and perform a restart of the SAN and CF.

  Once the window over, make sure that the host does not see the paths of the dead and exit the host from maintenance mode.

• Backup VDR when connected directly to ESXi host (no vCenter)?

  I have a single host of vShpere ESXi with camera VDR configured and running. I don't have a vCenter. I have the plugin installed into my vSphere client and I am able to set it up.  I have created a backup task and provided it works, however I get the following message in th events and journal

  "Connected to the ESX Server, automatic backups will not be executed."

  VDR works when connected directly to a host no vCenter ESXi 4? If so, what is my next step in this problem?

  VDR works when connected directly to an ESXi 4 host with vCenter not?

  N °

  If so, what is my next step in this problem?

  Buy vCenter

• Unable to connect to update ESXi host to vCenter

  So I have a client who does the following:

  Added several hosts, vCenter, went to install the updates using the Update Manager.  Host selected and selected re-mediation.  Server through the remediation proposals and restarted.  After server comes back online after the first reboot, it is impossible to connect to vCenter.

  Updated version: 5.5U3b ESXi

  Any help would be greatly appreciated.

  Sean.

  Hello

  I assume that your customer has forgotten to update the vCenter server before it has updated the hosts.

  You must have at least version 5.5 U3b on the vCenter to manage the hosts of these version.

  See interop matrix:

  https://www.VMware.com/resources/compatibility/SIM/interop_matrix.php

  Tim

• Unidad USB connect a remote ESXi host para copy ahi una VM

  Hola Comunidad!

  Host of I have an ESXi 4.1 con several VM running pero Necesito UN liberar espacio y tengo una VM 1.5 to Quebec City are no utilizo pero no quiero eliminarla sin mas.

  Como el host are remote y the VM are huge, no puedo descargarla por internet y he pensado en un disco para copiarla pero ahi 2 TB USB conectarla no se if the host the reconocera that comandos debo emplear or el sistema archivos than debe tener said disco.

  If pudieran help me, would be very grateful.

  A cordial saludo,

  Alvaro.

  You must connect el of esta donde el en USB host ESXi VM for the con sistema archivo NTFS y luego desde vSphere Client editas VM y mallards a USB controller y luego peripheral USB.

  Editor captured.

  A greeting.

• Connection usb to esxi host and copy vmdk

  Hello

  I'm trying to migrate a vSphere cluster to another machines.  There is no network connectivity between the 2, so I intend to copy the files vmdk and vmx more via USB directly connected to the host for thoroughput max.  Anyone tried this?  I looked in the documentation and online, and I see that the only supported file systems FAT32 and ext3.  For a 40 GB virtual computer, can I use an ext3 formatted USB key, copy locally and then USB attach themselves to a host on the new cluster and copy?  Anyone see any problems with this?  We are doing this process via a USB port connected to a position of the user and SCPing between the host and the USB port on the network.  I think that cutting the transfer network will speed up the process, currently a 40-50 GB VM takes about 3 hours

  Hello

  I understand that you can read in what she argued, however...

  If there is a KB article while this does not mean that it is supported, it simply means that it is possible and you might be able to use it if the need is high enough. For example, in case of problems you can risk some stability/performance and fix the most urgent problem at hand, as a critical VM that was on a LUN which disappeared earlier that day there so that you only restore backup on a USB drive.

  Also note the supplement "additional note" at the bottom of the KB that you are facing

  Quote (my highlighting):

  More information

  The USB key must be a minimum of 4 GB in size. This procedure is not recommended for basic file transfers.

  This procedure includes steps on disabling the intercom USB host function. Then earlier in the article that they use the same feature to connect the USB drive to the guest.

  If this isn't everything, they use the DCUI for mode of tech support that their link in an article KB1017910 to using the console is already a bit dodgy on a production host. About using the console for day-to-day operations is a no No

  Another quote, this time from this KB article, underscores once again with me.

  Tech Support Mode

  Tech Support Mode (TSM) provides a command line interface that can be used by the Administrator to troubleshoot and correct abnormal conditionson hosts VMware ESXi. TSM is accessible in two ways:

  • Connecting directly to the ESXi Server console.
  • Remote SSH connection.

  Further down in this article, it is pointed out again that it is for support only, I would say is something different as 'supported environment.

  It does not mean that you can not and never use should the DCUI, but be careful.

  Back on the focus to what you're trying to do.

  If your USB drive is broken, you now have a hypervisor that attempts to mount it to the level of the hypervisor, which, in itself, can cause downtime at the level of the hypervisor risks of release for ALL your guests. USB transfer at least maintains these problems located in the virtual machine, it is attached to.

  Besides that... the only system files that you can mount is VFAT, so you can't even put files there that are larger than 2 GB (or 4 GB) in size.

  File systems ext2/ext3/ext4 that none of those who are supported, VFAT only for your external USB drive.

  Yes there are ways around the VFAT file size limit too, but you're just jumping through the next pole, and if something's not going then your users is satisfied by the retoric "but backups are faster".

  --

  Wil

• Change the name of the logfile refelect esxi host name

  Hello

  I'm changing the name of the log file to reflect the name of each host name in listed in a file text How would I have done that?

  Thank you

  CODE

  --------

  ##Load VimAutomation PSSnapin...
  If ((Get - PSSnapin - name VMware.VimAutomation.Core - ErrorAction SilentlyContinue) - eq $null)
  {Add-PSsnapin VMware.VimAutomation.Core - ErrorAction SilentlyContinue}
  
  ##Set server Mode...
  SetPowerCLIConfiguration - Multiple DefaultVIServerMode - confirm: $false

  #Get # hosts.txt file ESXi host list...
  $varHost = get-Content "S:\Get-Logs\hosts.txt".

  The cluster name #Enter...
  $Cluster = Read-Host "enter the cluster name.

  
  ##Path to clear the logs...
  $FilePath = "S:\Get-Logs\Logs\" + $Cluster + "\".

  Cluster ##Create folder...
  If ((New-Item - path $FilePath ItemType - directory - ErrorAction SilentlyContinue) - eq $null)
  {- New - path $FilePath ItemType - directory - ErrorAction SilentlyContinue}

  
  Password ##Root
  #Convert to ensure the chain...
  $varGetPassword = Read-Host "enter the ESX Root Password" - AsSecureString
  $ESXRootPassword = [Runtime.InteropServices.Marshal]: PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR($varGetPassword)))
  
  ESXi hosts ##Connect
  Write-Host "" connection to the ESXi host: ', $varHost ' "»
  SE connect-VIserver $varHost - user 'root' - password $ESXRootPassword - WarningAction SilentlyContinue
  
  ##Do something useful here...
  ##------------------------------------------------------------------------------
  {foreach ($ESX to $varHost)
  
  Get - Log - VMHost (Get-VMHost-name $ESX) - Bundle - DestinationPath $FilePath
  }
  ##------------------------------------------------------------------------------

  
  
  ##Disconnect Esxi host
  Write-Host "" disconnect from ESXi host: ', $varHost ' "»
  Disconnect-VIServer $varHost - confirm: $false
  
  The script ##End

  End CODE

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

  The cmdlet Get - Log do not create the destination folder if it does not exist, so you will need to test for this condition.

  AFAIK, you don't need to connect to each ESXi individually when you are connected to the vCenter.

  Since the discharge of generated log file name is rather cryptic, I rename the file normally and add a timestamp.

  You could do something like that

  $clusterName = "mycluster.

  $FilePath = 'S:\Get-Logs\Logs\$($clusterName) ".

  If (!) ((Test-Path-path $FilePath)))

  {

  Novelty - ItemType Directory - Path $FilePath

  }

  $varHost = get-Cluster-name $cluserName | Get-VMHost

  {foreach ($ESX to $varHost)

  $destPath = "$($FilePath)-$($ESX.). Name.Split('.') [0])"

  If (!) ((Test-Path-path $destPath)))

  {

  Novelty - ItemType Directory - Path $destPath

  }

  $logName = get - Log - VMHost $ESX - Bundle - DestinationPath $destPath

  If ($LogName)

  {

  Rename-Item - Path $logName - NewName "$($destPath)-$($ESX.). Name.Split('.') [0])-$((Get-Date).) ToString('yyyy-MM-dd-hh-mm')).

  }

  }

• Strange script error when you connect directly to a host and stopping

  Don't know why I get this error so thought I would ask everyone.  PowerCLI 5.5

  I am writing a script that stop a whole environment, hosts and vCenter.

  Everything works fine until I viserver - connect directly to the host running vCetner.

  (1) connect the correct vCenter

  (2) brings together all ESXi hosts

  (3) brings together the host that is running vCenter

  (4) includes all virtual machines and their current status

  (5) start stop VMs or stop VMs if VMWare tools is running

  (6) wait until all but the vCenter VM is running

  7) penetrates into all hosts, but the host to vCenter in Maintenance Mode

  (8) disconnects the vCenter (order of disconnection-VIServer)

  (9) connects directly to the host that is running vCenter (Connect-VIServer), enter correct details.

  Here's where I start to have problems.

  (10) issues a command Shutdown-VMGuest

  (11) waits until the VM is turned off

  (12) sets this host in Maintenance Mode (Set-VMHost-Mode of State of Maintenance-confirm: $false)

  (13) stop the virtual machine host. (Stop-VMHost-confirm: $false)

  If I unplug the vCenter I get an error if I stay connected to vCenter it works very well, it's a problem I want to turn off the vCenter and just need to talk directly to the host.

  } {Code

  SE connect-VIServer $Global: vCenterHost.VMHost | Out-Null

  Stop-VMGuest - VM $Global: vCenter - confirm: $false - WhatIf

  #Wait for vCenter be put off.

  While (Get - VM $Global: vCenter | where {$_.}) ({PowerState - don't 'Receiving'}) {}

  Game-VMHost - VMHost $Global: vCenterHost.VMHost - Maintenance of State-confirm: $false - WhatIf

  Stop-VMHost - VMHost $Global: vCenterHost.VMHost - confirm: $false - WhatIf

  } / {Of code

  Error:

  Game-VMHost: 01/01/2014 22:27:22 Set-VMHost the connection to the server

  "User domain\username @(vCenter): 443 is required by the current operation." The

  connection does not exist, perhaps because he has been actively closed or delayed

  outside.

  \Vmware-scripts\Park-shutdown-startup-test.ps1:125 char: 2

  + Set-VMHost - VMHost $Global: vCenterHost.VMHost - maintenance State

  -Confirm: $fals...

  +    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  ~~~~~~

  + CategoryInfo: InvalidArgument: (/ VIServer =(user/vCenter): 4)

  43 /: string) [Set-VMHost], ViServerConnectionException

  + FullyQualifiedErrorId: Sdk_InvalidConnectionId, VMware.VimAutomation.ViC

  ore.Cmdlets.Commands.SetVMHost

  Stop-VMHost: 01/01/2014 22:27:22 stop-VMHost the connection to the server

  "User domain\username @(vCenter): 443 is required by the current operation." The

  connection does not exist, perhaps because he has been actively closed or delayed

  outside.

  \Vmware-scripts\Park-shutdown-startup-test.ps1:126 char: 2

  + Stop-VMHost - VMHost $Global: vCenterHost.VMHost - confirm: $false - WhatIf

  +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: InvalidArgument: (/ VIServer =(user/vCenter): 4)

  43 /: string) [Stop-VMHost], ViServerConnectionException

  + FullyQualifiedErrorId: Sdk_InvalidConnectionId, VMware.VimAutomation.ViC

  ore.Cmdlets.Commands.StopVMHost

  / Error

  I built this script a bit when the functions but have tried this outside being a function call and just do not know what is happening and why it gives me this error.

  I know that my $Global: variables are correct because it calls the correct information and like I said works without a problem, when I'm always connected to the vCenter I stop.

  Yes I know I '-Whatif "in orders, I'm testing right at that moment.

  Thanks for any help or ideas.   I tell myself that if all else fails I will post just the necessary data in a file and they have this script calls another script and gather the necessary content but would rather not do.

  The problem is probably due to the fact that you have recovered the contents of the variable $Global: vCenterHost.VMHost, while you were connected to the vCenter.

  In being VMHost , the ID property contains information about the connection to access the corresponding object of vSphere.

  To resolve this issue, 'Get' the VMHost object again when you are connected directly to the ESXi server.

• 8.3 OMSA @ ESXi 6.0 U2 @ R515-> cannot log into the website OMSA to ESXi HOST.--

  Hello guys.

  I've updated my ESXi of U3 5.0 to 6.0 U2 and I lost my OMSA. I can not connect from the web page.

  For the update of the host, I used this ISO file:
  . VMware-VMvisor-Installer-6.0.0.update02-3620759.x86_64-Dell_Customized-A00.iso

  After that, I installed OM-SrvAdmin-Dell-Web-WINX64-8.3.0-1908_A00. EXE to a VM W2012S to this host. I can open the web site to connect, but when I try to connect to my ESXi HOST, I received this message: failed to connect... connection error.

  When I saw that I began to check a few things, I ran: 'list of vib software esxcli' and I saw:
  Name Version Date seller installation acceptance level
  ----------------------------- ----------------------------------- ------ ---------------- ------------
  ...
  OpenManage 8.3.0.ESXi600-0000 Dell PartnerSupported 2016-07-29
  Reference Dell-configuration-vib 6.0 - 2A 00 Dell PartnerSupported 2016-07-29
  iSM 2.3.0.ESXi600 - 0000 Dell PartnerSupported 2016-07-29
  ...

  Another very strange for me, is that I can't see any reading of the sensors to Interface web server: HOST /... / or Vsphere Client.
  But I can read a large number of web page Idrac and ESXi SSH data using ' esxcli ipmi sdr list material.
  Node-sensor Description-reading raw reading of raw Timestamp/comment base calculated entity Instance
  ----------- --------------------------------- --------------- ---------------- ----------- ----------- ------------------- ---
  0.1 1 Temp 3.1 processor 38 degrees C 166 2016-08 - 01 T 14: 18:32
  0.2 2 Temp 3.2 processor 34 degrees C 162 2016-08 - 01 T 14: 18:32
  0.5 power 1 10.1 Temp 40 degrees C 168 2016-08 - 01 T 14: 18:32
  0.6 power 2 Temp 10.2 37 degrees C 165 2016-08 - 01 T 14: 18:32
  0.7 power Supply 2 Temp ambient 10.2 26 degrees C 154 2016-08 - 01 T 14: 18:32
  0.8 power Supply 2 Temp ambient 10.2 28 degrees C 156 2016-08 - 01 T 14: 18:32
  0.12 system Board 1 BIO Temp 7.1 44 degrees C 172 2016 - 08-01 T 14: 18:32
  0.14 front Panel Board 1 Temp ambient 12.1 16 degrees C 144 2016-08 - 01 T 14: 18:32
  0.13 system Board 1 Temp Planar 7.1 28 degrees C 156 2016-08 - 01 T 14: 18:32
  0.10 memory Module 1 Temp 8.1 24 degrees C 152 2016-08 - 01 T 14: 18:32
  0.11 memory Module 2 Temp 8.2 36 degrees C 164 2016-08 - 01 T 14: 18:32
  System of 0.48 to edge 1 FAN MOD 1A RPM 7.1 2760 RPM 23 2016-08 - 01 T 14: 18:32
  System to 0.49 to edge 1 FAN 1 b MOD RPM 7.1 0 RPM 0-2016 - 08-01 T 14: 18:32
  System of 0.50 to edge 1 FAN 2 a MOD RPM 7.1 2760 RPM 23 2016-08 - 01 T 14: 18:32
  System of 0.51 to edge 1 FAN 2 b MOD RPM 7.1 0 RPM 0-2016 - 08-01 T 14: 18:32
  System of 0.52 to edge 1 FAN MOD 3A RPM 7.1 2760 RPM 23 2016-08 - 01 T 14: 18:32
  System of 0.53 to edge 1 FAN 3 b MOD RPM 7.1 0 RPM 0-2016 - 08-01 T 14: 18:32
  System of 0.54 to edge 1 FAN MOD 4A RPM 7.1 2760 RPM 23 2016-08 - 01 T 14: 18:32
  System of 0.55 to edge 1 FAN MOD 4 b RPM 7.1 0 RPM 0-2016 - 08-01 T 14: 18:32
  System of 0.56 to edge 1 FAN MOD 5A RPM 7.1 2760 RPM 23 2016-08 - 01 T 14: 18:32
  System of 0.57 to edge 1 FAN MOD 5 b RPM 7.1 0 RPM 0-2016 - 08-01 T 14: 18:32
  Power supply 0.148 1 1 current 10.1 0.6 amps 15 2016-08 - 01 T 14: 18:32
  Power 0,149 2 current 10.2 2 0.48 amps 12 2016-08 - 01 T 14: 18:32
  0.150 1 power supply 1 10.1 206 Volts 103 2016-08 - 01 T 14: 18:32
  0.151 power 2 2 10.2 206 Volts 103 2016-08 - 01 T 14: 18:32
  System of 0,152 onboard System 7.1 220 Watts 22 2016-08 - 01 T 14-1 level: 18:32

  The details of the server are:
  BIOS 2.3.0
  IDRAC 2.85 (Build 04)
  Lifecycle controller 1.7.5.4

  Any kind of help to connect to the host ESXi OMSA is welcome!

  This is the correct service.

• How to remove ESXi host of Distributed Switch

  3 Cluster DRS - 1 x physical, 2 nested nodes in a LAB environment

  I need to downgrade a 6.0 U2 ESXi host and replace it (from ESXi nested in Physics). I am trying to remove the host from a distributed switch, but it seems that I can't do that until I remove it from the Distributed Switch. I can't remove the VMkernel group management ports that prevents me to remove the host from the Distributed Switch. Any suggestions? I guess that I need that migrate to a Standard switch first?

  I am connected to the ESXi host through vSphere Client, migrated the group management to a Standard switch ports, then I was able to clear the host of the distributed switch. I could then remove the host from the Cluster.

• Update Server VC and 5.5 ESXi hosts to update 3 b (Build 3248547)

  I'm in vCenter Server 5.5 and 5.5 ESXi hosts.  Both are updated 3A, patched to version 201510001, which is the build 3116895.  I plan the upgrade of update 3 b (Build 3248547) and I'm a little confused on the question of SSLv3.

  I wonder if this point below ESXi55 U3b & VC 55U3b Known Issues applies to my config:

  ESXi does not automatically added to the inventory of the vCenter servers
  If you install an earlier version of vCenter Server and vSphere Update Manager for ESXi 5.5 updated 3B, then after the task of sanitation, ESXi does not automatically added to the VC inventory. Remediation process never gets done and ESXi State of connection in the VC inventory is presented as disconnected. Solution: When you restart ESXi after reorganization process is started, enable SSLv3 on ESXi (which is disabled by default). This will ensure that ESXi is added to the VC inventory automatically in minutes and sanitation as completed.

  If I'm reading things correctly, upgrade to vCenter Server to 3 b first and then upgrade the ESXi hosts, will avoid lost communication problems.  Can anyone confirm?

  It should be good if you update vCenter first.

  The problem is that pre - U3b vCenter 5.5 forces an SSLv3 connection when connecting to an ESXi host on port 443 (not the reverse). It does this, even if the host ESXi and vCenter SSL/TLS libraries actually support TLS 1.0 + since at least vSphere 4.0.

  So when you update one host to 5.5 U3b, the oldest vCenter again will try to force a connection SSLv3 that will fail, since SSLv3 has been disabled to the host. If you're updating vCenter, first of all, it will initiate a good TLS 1.0 + connection to more similar and updated hosts.

  Here is an explanation of the (pre - U3b) vCenter SSLv3 handshake behavior:

  Re: vCenter and host communication SSL v3

• ESXi host running 6 VCSA disconnected from the vCenter

  Hi guys,.

  I have a weird problem with my vCenter build 6. Single cluster of ESXi hosts. Running VCSA 6.0 and 6.0 ESXI. Making a storage of the vCenter vMotion initially got stuck at 77% and the ESXi host running the disconnected from vCenter vCenter. But I can connect directly to the ESXi host with vsphere client and see the vCenter VM works perfectly well. If I try to manually connect host ESXi and vCenter, I get the error "Failed to contact the host specified") both are in the same subnet and VLAN. I can migrate to other virtual machines without problem. I even restarted the host and yet I am not able to connect to vCenter. The host connects to vCenter if I reboot vCenter, but after a few minutes, disconnects again (even if no task does run on this topic.) I have no HA or DRS enabled at this point that I build this new environment and only presented a single LUN as a store of test data to the cluster.

  Any ideas?

  OK, I think I fixed that or have at least a work around. So the underlying question was hiding ID mode/CPU EVC. I'm under the cluster to a level of EVC to reduce until I have migrate workloads from old environment and I think that this created a problem for the unit vCenter. To resolve this problem, I turned off the unit, directly connected to the ESXi host that had the camera running, edited the virtual machine and reset the masking of CPUID. Also, I've hidden the flag NX/XD of the guest. It's temporary (I hope) as once I increase the EVC to the Haswell, I will expose the NX/XD comments and test. For the moment, it is of the workaround I did. It may be of some use to someone.

• How to get the material status of ESXi host of external surveillance system?

  Hello!

  I've got hardware ESXi host information (for example, CPU, disk, etc.)

  that I want back outside a vCenter/ESXi for an external monitoring system.

  I really really slighty possible via Powershell saw...

  Thanks for your help!

  Hello

  the link that I commented, explian how to monitor the status of the ESXi hardware by using the cmdlets for powershell CIM 3.0.

  Not the virtual machines

  This, will you?

  Check this code from the link, you should notice that connects to an esxi host, not virtual machines:

  import-moduleCimCmdlets

  2	$ipaddress="10.20.177.15"

  3	$HostUsername="root"

  4	$CIOpt= New-CimSessionOption-SkipCACheck -SkipCNCheck -SkipRevocationCheck -EncodingUtf8-UseSsl

  5	$Session= New-CimSession-Authentication Basic -Credential $HostUsername -ComputerName $Ipaddress -port 443-SessionOption$CIOpt

  6	Get-CimInstance-CimSession$Session-ClassNameCIM_Fan

  Best regards

  Pablo

• Change the password for root to an ESXi host

  Hello

  I need help to get a script VCO that change password for root to an ESXi host.

  In PowerCLI is the Set-VMHostAccount cmdlet. I searched in VCO API... I have not found or something similar.

  I found the object of VcHostAccountSpec but seems it only works with "Host Profiles" and my licenses are Standard and Enterprise.

  http://www.VMware.com/support/Orchestrator/doc/vco_vsphere51_api/HTML/VcHostAccountSpec.html

  Any idea?

  Thanks, Roberto

  Another option would be to connect to the ESXi host with vCO plugin SSH and run the command "passwd" remotely. Haven't tried, but in theory, it should work.

  @Tim - we try to keep the compatibility of the existing whenever possible plug-ins vCO so PowerShell module should work with the latest vCO relies.

• 5.0 ESXi hosts all say "not responding" after a while

  Hi all

  First of all, yes I know this is a repetition of something that is posed before but I tried all the resolutions that I can find - nothing has worked so far.  In the vSphere client, all hosts currently have a status of "not responding". For reference, however, here is what I have tried/checked so far:

  -vCenter and ESXi are all in evaluation mode.

  -I do not use the brand HP ESXi ISO (as referenced by http://communities.vmware.com/message/1852500 more numerous other positions of the community).  Material * is * HP hardware, though.

  -Change of the security policy of vCenter Server (as referenced by http://communities.vmware.com/thread/271809).

  -Go through all checks VMware published listed in http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003409.

  -Network connectivity verified using PING, nslookup and telnet on port 902.  All ESXi hosts respond on port 902.

  -AD DNS monitoring verifies that all say "Pass".

  -There is no firewall on the network (it has physically isolated from everything, including the internet... obviously I am writing this post on another network).

  -Direct connection to the ESXi hosts works very well - this only happens when connecting through vCenter (so running virtual machines are available and usable without any problem... There is no HA).

  -/etc/VMware/VMware.LIC has a license of '0' key (confirms the status of the evaluation, I think).

  -/etc/vmware/vmware.lic mode is the following... - rw - T.

  -All hosts are on the same version of ESXi.

  -There is only 1 Server vCenter.

  A strange thing is that some items, including VMware ones, say to run 'rpm' and 'service' in a variety of different ways.  'Rpm' or 'service' are valid commands on my ESXi servers.  This seems odd, unless ESXi 5.0 withdrew these commands to the shell.

  Can anyone suggest anything else that might be the cause?

  Thank you!

  If VC is virtual and the problem that happens on the same ESXi what they are and all on the same subnet, I am almost sure that something on your windows it blocks. Check the steps in KB http://kb.vmware.com/kb/1029919 to try to discover what is happening.