◦ Virtual servers must have a unique name.
◦ Server names are case-sensitive in VMware, but not in the vSphere PowerCLI instance run from
this plug-in.
• Conditions related to the virtual server:
◦ The virtual server must be running.
◦ If the virtual server OS is a Windows-based OS, Windows PowerShell 2.0 or later must be installed.
◦ VMwareTools must be installed on the virtual server.
Usage guidelines
• If a file with the same name exists in the location specified by the path to the script file on the guest
OS (vmware.scriptFileOnGuest property) or the path to the output file for the script
(vmware.scriptOutputFilePath property), the existing file is overwritten. If any of the folders specified
by the file path do not exist, that folder is created and the file is transmitted. Delete the created folder if
it is no longer necessary.
• If a folder with the same name exists in the location specified by the path to the script file on the guest
OS (vmware.scriptFileOnGuest property), the target script file is transmitted and stored in the existing
folder without any change to the file name. If this occurs, the script fails and the service ends
abnormally.
• If an error occurs during file transmission, the file that is being transmitted to the virtual server is not
deleted automatically. Delete this file if it is not necessary.
• Do not run interactive scripts that require user entry, or scripts that display a UI and do not end
automatically.
• Do not run this service template on the same virtual server simultaneously.
• The script specified as the script file on the VMware vCenter control server (vmware.scriptFileOnHost
property) is transferred to the guest OS in binary format. Create the script in advance on the guest OS
by using executable line break codes and character codes.
Service Definition Properties
The following table lists the properties shown in the
Service Definition
window.
NOTE:
Consider the following precautions when setting properties:
• You can specify the following script files for the script file path on the guest OS
(vmware.scriptFileOnGuest property): Windows batch file (extension
.bat
), Windows PowerShell
script (extension
.ps1
), and shell script (extension
.sh
).
• When you specify multiple arguments for the script argument (vmware.scriptParameter property), you
can separate arguments by using a single-byte comma (,) or single-byte hyphen (-).
272
Additional service templates