I can use vmware-cmd to list VMs installed on my ESXi 4.1 host but not to start or stop VM's. Is this an intentionally crippled feature of the free ESXi 4.1 version? Will I have same issue if I upgrade to ESXI 5 ?
Thanks in advance for any tips or direction,
Thanks for the fast concise reply.
>For the free editions, the API is limited to read-only access. Same for all versions (except for a few builds where VMware forgot to ristrict the API)
Just to confirm, start and stop are considered write operations and are restricted?
I fear it may be time to find out if our small company can afford ESX or look for alternatives.