Filter
Top Products
If the same server names are detected on the same network, a network duplication error will occur.
Some programs may experience problems when started with a different hostname. If such programs have been installed, configure
their services not to start automatically. This has to be configured before collecting the cloning image.
Some programs may experience problems when the same server name exists. If such programs have been installed, configure their
services not to start automatically. This has to be configured before collecting cloning images.
- When using the network parameter auto-configuration function, check the operation before performing collection.
For details, refer to "17.6.1 Operation Checks and Preparations".
- 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 how to change boot options, refer to "9.1.10 Changing Boot Options".
- When using local disks as system disks, and iSCSI storage as data disks, refer to the advisory notes described in "Table 8.1 Supported
Storage Device Configurations" in "8.1.1 Storage Configuration" in the "Design Guide VE".
[Windows]
- Enable NetBIOS over TCP/IP
- A volume license is required for cloning, and must be entered during the installation of Resource Orchestrator Agent.
Refer to "2.2.1.2 Collecting and Checking Required Information" and "2.2.2 Installation [Windows] [Hyper-V]" in the "Setup Guide
VE" for details.
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
(*)
* Note: 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
Installation_folder
\Agent\scw\SeparateSetting\ipadj\activation.dat
In the [ActivationInfo] section, set the following parameters using a "parameter=value" syntax.
Refer to the following table for details on each parameter.
Table 17.2 Structure of the Definition File
Format Parameter Value
KMS
.cmd.remotescript.
1.params.kmscheck
(Mandatory)
KMS host search type.
Select one of the following:
- AUTO
- 125 -