Adding Cloned Machines to the Inventory

Before you begin

For machines with encrypted boot volumes, administrators must power off the machines before cloning. For machines with encrypted data volumes, administrators must stop the SecureCloud Agent before cloning.

When a machine is cloned, the original and cloned devices have the same encryption key. After cloning, administrators must update the inventory using the Configuration Tool. If administrators do not update the inventory using the following procedure, the Key Management Server will prevent the cloned devices from using the encryption key at the same time as the original devices.

Procedure

If you have not done so already, change the host name of the clone.
Stop the SecureCloud Agent service:
- On Linux, type /etc/init.d/scagentd stop
- On Microsoft Windows, stop the SecureCloud Agent in the Services panel:
Navigate to the appropriate directory:
- On Linux, enter cd /var/lib/securecloud/
- On Microsoft Windows, click Start and type cmd to open a command shell, then enter cd C:\Program Files (x86)\Trend Micro\SecureCloud\Agent\
Start the Configuration Tool:
- On Linux, type ./scconfig.sh
- On Windows, type sc_config.exe
The Configuration Tool command line interface appears:

Run the clone script:

On Linux, type scconfig.sh --clone-this -x <passphrase>
On Windows, type scconfig.exe --clone-this -x <passphrase>

Tip

Administrators can specify the clone name and assign a policy to the clone using the following parameters:

--clone-image-name <image name>
--policy-name <policy name>

If the name is not specified, the clone is identified by its machine name in the inventory. Similarly, if the policy is not specified, the Default Policy is automatically assigned to the clone.

The clone is added to the inventory.

Start the SecureCloud Agent service:
- On Linux, type /etc/init.d/scagentd start.
- On Microsoft Windows, start the SecureCloud Agent in the Services panel:

$('#title').html($('meta[name=description]').attr('content'));