Component |
Agent for x360Recover Direct-to-Cloud (D2C) |
Release Date: |
February 2021 |
The Direct-to-Cloud agent can be silently deployed through RMM or other tools.
The latest agent installer has been packaged as a standard Windows Installer .MSI package.
Download the installer file
You can download the Direct-to-Cloud installer package from the Clients page located on the vault.
The standard Direct-to-Cloud installer leverages a specially-named file that embeds a token value associated with the client being targeted. The installer file name (containing the identity token) is the only differentiating factor that separates this installation from a normal appliance agent install. The special filename format (with token) determines which client this agent will register under. This file name should not be changed or the token identity will be lost.
Note: This token contained within the downloaded file is valid for 14 days. After 14 days, new installations using this installer will no longer be able to register with the vault. A new file can be downloaded (whenever needed) to generate a new token for this client.
Example installer file name:
| agentSetup-dataprotection-acme123-1150ba6723.msi |
Configure custom properties
In order to perform an automated installation, custom properties must be set when calling the Windows Installer in order to configure the agent settings.
To perform a silent installation of the x360Recover agent, use MSIEXEC as follows:
| msiexec /i <installer file name> /quiet <additional optional parameters> |
Additional optional parameters include:
- BACKUP_VOLUMES=<Drv>,<Drv>...
- PASSWORD=<agent password/passphrase>
Note: The SERVER parameter is not used.
EXAMPLE: [Brackets] indicate optional commands
msiexec /i <installer file name> /quiet [BACKUP_VOLUMES=<DRV>,<DRV>…] [PASSWORD=<agent password/password>] |
Looks like:
msiexec /i agentSetup-dataprotection-acme123-1150ba6723.msi /quiet BACKUP_VOLUMES=C,D,E PASSWORD=password123 |
- See x360Recover Best Practices for guidelines, and recommendations when deploying agents.
Deploy via RMM
When deploying via RMM tools, we recommend using the TOKENID command-line parameter.
Rather than downloading the dedicated client-specific agent installer, use the standard agent installer (agentInstaller.msi) with the TOKENID parameter. This will allow you to use a single installer binary for any customer.
|
NOTE: Where do I get the agentinstaller.msi file? 1. The easiest way is to rename the installer file (such as the example cited earlier) agentInstaller-dataprotection-acme123-1150ba6723.msi to agentInstaller.msi 2. Alternatively, you can also go to the vault URL at https://rb-edandt1.rb.slc.efscloud.net/ and click the Download agent button in the bottom left corner:  If the vault has Lockdown Mode enabled, you will see this:  |
After you get the current TOKENID for the customer, you'll specify it on the command-line in your RMM deployment script.
The RMM tool should execute something like this on the managed system:
msiexec /i agentSetup.msi /quiet TOKENID=6484c41f970d49ac8156b9c967e7a295 |
You may also include other command-line options (such as PASSWORD) to set the agent password/ passphrase, etc.
In a future release, a planned feature will make managing Token ID’s within the UI more user-friendly.
SUPPORT | 720-204-4500 | 800-352-0248
- To learn more about any of our Axcient products, sign up for free one-on-one training.
- Please contact your Partner Success Manager or Support if you have specific technical questions.
- Subscribe to the Axcient Status page for a list of status updates and scheduled maintenance.
628 | 1259