VM /ETC

Unfortunately this post is an update to my post from last week titled ESXi Update 3 enables full remote administration via RCLI. Today I have received new information from VMware about the current and future status of the Remote Command Line Interface’s (RCLI) ability to manage the free version of ESXi 3.5.

With the release of VMware ESXi 3.5 Update 3, some API calls became freely available.  As it turns out, these new APIs were opened up unintentionally.  This inadvertent change happened when VMware was resolving an API-related bug.

Only customers who downloaded the free version of ESXi have been affected.  VirtualCenter and VI (Foundation, Standard, Enterprise) customers are not affected.

My VMware contacts tell me that this bug will be fixed shortly, and the next release will lock down the RCLI again.

Remote administration and configuration of the free version of ESXi 3.5 remains possible from the VMware Virtual Infrastructure Client.

I have updated my original post with this information as well.

Related Posts

• Restore Connectivity To ESXi 4 Management Network After Adding Second NIC (4)
• VMware VCB To Be Replaced by VADP. Does That Mean vDR Is The VMware Alternative? (18)
• Use Veeam FastSCP For Easy ESXi File Management (10)
• Explaining Why ESXi Installs Require Extra Space Besides The Hypervisor (9)
• ESX/ESXi 3.5 Update 4 Released – PXE Boot ESXi Experimentally Supported (7)
• If ESXi is so small why is the download so big? (6)
• VMware ESX/ESXi 3.5 Update 3 released (8)
• Managing ESX in a COS-less World #TA2659 (2)
• Latest Update on AUG 12 BUG confirms ESX/ESXi 3.5 VM reboots still required (0)
• VMware CEO Paul Maritz blogs about the Update 2 BUG (2)