◦ Resource pool name.
◦ vApp name.
• Conditions for the template used for deployment:
◦ VMware Tools are installed.
◦ The running of remote commands is allowed by the settings (administrative share for Windows-
based OS and SSH for Linux OS is enabled.)
◦ NICs are configured (up to two).
◦ The reception of and response to pings is allowed.
◦ For a Windows-based OS, the administrator password is left blank.
◦ For a Windows-based OS, run sysprep. To run sysprep, the maximum number of Windows-based
OS initializations (three times) must not be reached.
◦ When you convert a virtual server to a template, ensure that the virtual server is stopped.
• Condition of the virtual server:
◦ There is no duplication of the virtual server name under the management of an identical vCenter.
• The authentication information of the virtual server to deploy is registered to the agentless connection
destination definition in the "Management" tab in advance.
Server requirements
To use this service template, the following servers are required:
• vCenter server -- This is a server on which VMware vCenter Server is installed.
• vCenter control server -- This is a server on which VMware vSphere PowerCLI is installed.
• Virtual server -- This is a virtual server managed by the vCenter server and VMware vSphere ESX.
Usage guidelines
• The specified port group must be able to communicate with the local server. If there are multiple NICs
for the virtual server, set one of the NICs to a port group that can communicate with the local server.
• For the IP address (for management) do not specify a value that is not a valid IP address in the virtual
server's OS. For example, network addresses, broadcast addresses, and special addresses such as
0.0.0.0 and 255.255.255.255 cannot be specified.
Script execution through the vCenter server: Service details
The following is an overview of the processing:
1.
Run the PowerCLI commandlet
Copy-VMGuestFile
on the target server to transmit the specified
script from the target server to the guest OS on the virtual server.
2.
Run the PowerCLI commandlet
Invoke-VMScript
on the target server to run the script transmitted
in (1). Then, run the scripts on the virtual server by using the following codes.
270
Script execution through the vCenter server: Service details
