Provisioning a Device on a Legacy SecureCloud Agent Parent topic

This feature allows users of SecureCloud to provision new devices on legacy versions of the SecureCloud Agent.
Important
Important
This feature also functions for previously encrypted device recognition, but when moving or cloning to a legacy device, confirm that both images have already registered with SecureCloud and that both devices are encrypted. If the device has not been encrypted, SecureCloud will format the device and encrypt it, erasing all data.

Procedure

  1. Receive the self-provision tool from SecureCloud technical support and place it in the SecureCloud folder.
    • On Linux, the default path is /var/lib/SecureCloud
    • On Microsoft Windows, the default path is C:\Program Files (x86)\Trend Micro\SecureCloud
  2. Stop the agent service.
    • On Linux, do the following:
      1. Type cd /var/lib/securecloud/
      2. Type the command service scagentd stop
      prov_leg_linux_scagent_stop.jpg
    • On Microsoft Windows, do the following to stop the device and then navigate to the appropriate directory in a command shell:
      1. Click Start and type run to open the Run window, then type services.msc
      2. Select Trend Micro SecureCloud Agent Service and click the stop button.
        prov_leg_windows_scagent_stop.jpg
      3. Click Start and type cmd to open a command shell, then type cd C:\Program Files (x86)\Trend Micro\SecureCloud\Agent\
  3. Execute the appropriate selfprov.py script in the command shell.
    • On Amazon Web Services, type python selfprov.py --device <volume_id> --mountpoint <mount_point> --cspcredential access_id=<access_id>,secret_key=<secret_key> --passphrase <passphrase>
      An example script is as follows:
      prov_leg_selfprov_aws.png
    • On other instances, type python selfprov.py --device <volume_id> --mountpoint <mount_point> --passphrase <passphrase>
      An example script is as follows:
      prov_leg_selfprov_other.png
    When the process is finished, the following message displays:
    prov_leg_selfprov_result.jpg
  4. Start the SecureCloud Agent service.
    You can find the instance on the Active Keys screen of the Web Console.
    legacy_key_active.png