◦ 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, first 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.
• ESX server -- Server on which VMware vSphere ESXi (or VMware ESX Server) 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.
• Whether OS initialization processing is completed is determined by whether the information set in the
OS can be acquired. The time required for determining completion of initialization depends on the
value specified for the OS information acquisition repeat interval (vmware.checkOSInitCountInterval
property), as well as the specification of the OS information acquisition repeat count
(vmware.checkOSInitCount property). If the specified value is too small, a timeout might occur even
during OS initialization. Adjust the value for the performance of the virtualization environment being
used. Initially, specify the settings so that the OS information acquisition repeat interval is at least a
few hours.
• Do not specify for the IP addresses to set with values that are not valid as IP addresses in the virtual
server's OS, such as management and application IP addresses. For example, network addresses,
broadcast addresses, and special addresses such as 0.0.0.0 and 255.255.255.255 cannot be
specified. If an invalid address is entered, the virtual server deployment processing results in an error.
For a management IP address, specify an IP address that can be used to communicate with the local
server. Be aware that even though the correct address is specified, deployment might fail.
• While the virtual server is being deployed, do not use any other service to modify it. Doing so may
cause deployment of the virtual server to fail. Also, do not modify the virtual server directly from a
vCenter server.
• When you are deploying Linux OS, specify a root password for the template OS in the
Linux.adminPassword property (using the permitted characters.)
Additional service templates
263
