■ Linux commands – Scripts running in vMA cannot use Linux commands in the way that they do on the ESX service console because the Linux commands are running on vMA and not on the ESX host.
■ Access to ESXi files – If you need access to folders or files on an ESXi host, you can make that host a target server and use the vifs vSphere CLI command to view, retrieve, or modify folders and files.
■ References to localhost – Scripts cannot refer to localhost.
■ If vi-fastpass is initialized, all commands that do not specify --server apply to the default target.
■ Programmatic connection – In Perl scripts or Java programs, you can call VmaTarget.login() method of VmaTargetLib and specify the host to connect to. The directory /opt/vmware/vma/samples contains examples in Perl and Java. vMA handles authentication if the server has been established as a target server. Programs can use VmaTargetLib library commands. See Using the VmaTargetLib Library.
■ No proc nodes – Some service console scripts still use VMware proc nodes, which were officially made obsolete with ESX Server 3.0 and are not available in ESX/ESXi 4.0 and later. You can extract information that was available in VMware proc nodes using the vSphere CLI commands available on vMA.
■ Target specification – You must specify the target server when you run commands or scripts.vMA Components for Use in Scripts lists the vMA components that you can use for modifying scripts that include proc nodes and Linux commands.
vifs vSphere CLI command Commands are on vMA in /usr/lib/vmware-vcli/apps