Install the OS and applications required for deployment.
For manual OS installation, installation by remote console is recommended after starting the MB (Management Blade) or iRMC (Remote Management Controller) screen.
Additionally, apply any required patches and other necessary settings.
Make sure that the source server operates properly after those steps.
Check whether the DHCP client is enabled on the managed server to collect the cloning image from.
Cloning images with the same name can be saved up until the maximum number of image versions.
When collecting a new cloning image when the maximum number of image versions has already been reached, select the cloning image to delete.
The maximum number of image versions is three by default.
For details of how to change the maximum number of image versions, refer to "6.4 Changing the Maximum Number of Cloning Image Versions (Physical Servers)" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When the target of operation is a PRIMEQUEST server, confirm that the boot option settings on the target server and the boot option set in BIOS are configured for Legacy boot.
When the settings of one of the servers are UEFI, configure the settings after changing to Legacy boot.
For details on changing the boot options, refer to "7.1.10 Changing Boot Options" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
[Windows]
Enable NetBIOS over TCP/IP
A volume license is required. In addition, the volume license information must be entered during the installation of Resource Orchestrator agent.
For details, refer to "2.2.1.2 Collecting and Checking Required Information" and "2.2.2 Installation [Windows] [Hyper-V]".
If no volume license is entered during the agent installation, or if this information is changed after installation, edit the following license configuration file on the source server. Note that the structure and location of this file depend on the version of Windows that is being used.
For Windows Server 2003
Installation_folder\Agent\scw\SeparateSetting\sysprep\sysprep.inf
Edit the following line to enter a valid product ID.
ProductID=Windows product key (*1) |
*1: 5-digit values separated by hyphens
Example
ProductID=11111-22222-33333-44444-55555 |
Note
If there is a mistake in the product ID value or format, an error occurs when the collected cloning image is deployed. Make sure to enter a valid product ID when editing the definition file.
For Windows Server 2008 or Later
Installation_folder\Agent\scw\SeparateSetting\ipadj\activation.dat
Specify the parameters in the format "parameter=value" in each line of the [ActivationInfo] section of the definition file.
Refer to the following table for details on each parameter.
Method | Parameter | Value |
|---|---|---|
KMS | .cmd.remotescript.1.params.kmscheck (Mandatory) | KMS host search type. Select one of the following:
|
.cmd.remotescript.1.params.kmsname | Host name (FQDN), computer name or IP address of the KMS host. | |
.cmd.remotescript.1.params.kmsport | KMS host port number. If omitted, "1688" will be set. | |
MAK | .cmd.remotescript.1.params.makkey (Mandatory) | MAK key. |
Common | .cmd.remotescript.1.params.ieproxy | Host name (FQDN) and the port number of the proxy server. The host name and port number are separated by a colon (":"). |
.cmd.remotescript.1.params.password | Administrator password. An existing password setting will be displayed as an encrypted character string. | |
encrypted | The encryption status of the Administrator password. |
Example
With KMS (Automatic Search)
[ActivationInfo] |
With KMS (Manual Settings)
[ActivationInfo] |
With MAK
[ActivationInfo] |
If the Administrator password has been changed, execute the following command. The password specified in the .cmd.remotescript.1.params.password parameter of the definition file is changed to the encrypted string, and the line "encrypted=yes" is added to indicate that the password is encrypted.
For details, refer to "5.8 rcxadm deployctl" in the "Reference Guide (Command/XML) CE".
>"Installation_folder\Agent\bin\rcxadm" deployctl passwd -encrypt <RETURN> |
With MAK (Already Encrypted Password)
[ActivationInfo] |
[Windows]
For physical L-Servers, specify the NIC number defined for the rack mount or tower servers decided in "9.1.1 Admin LAN Network Design" and "9.1.3 Physical Network Design for the Public LAN and iSCSI LAN" in the "Design Guide CE" as the subscript.
Example
If the NIC number of the leftmost NIC on the back of a rack mount server is defined as "1", specify "Local area connection 1" here.
[Linux]
For physical L-Servers, specify the number with 1 subtracted from the NIC number defined for the rack mount or tower servers decided in "9.1.1 Admin LAN Network Design" and "9.1.3 Physical Network Design for the Public LAN and iSCSI LAN" in the "Design Guide CE" as the subscript.
Example
If the NIC number of the leftmost NIC on the back of a rack mount server is defined as "1", specify "eth0" here.
Information
The following are examples of the methods for aligning the subscript of a network interface name and NIC number of the NIC at back of the rack mount server.
For details, refer to the OS manual.
Red Hat Enterprise Linux
Configure the MAC address of the NIC at the back of the rack mount server for HWADDR in the following file: /etc/sysconfig/network-scripts/ifcfg-ethX
SLES
Use udev.
