Remote Setup and Deployment

Note: Setting up the Automation Remote virtual appliance requires advanced understanding of how to create and manage resources in VMware. If you encounter issues within the vSphere client, contact an administrator in your organization or VMware support.

To configure a new Automation Remote virtual appliance, you must first create the Remote in your Automation tenant. You can then download the appliance and deploy it using VMware vSphere. After you deploy the Remote from VMware, configure targets to use the Remote.

Automation Remote supports the following target types:

The maximum number of Remotes you're allowed to create is 20.

Perform the following steps to create a new Remote on your Automation tenant:

  1. Choose Automate > Advanced in the navigation menu.

  2. Click the Remotes tab, and click the New Remote button on the right.

    New Remote

  3. Enter a meaningful Display Name and optional Description.

  4. In the Remote Details section, click the DHCP or Static IP radio button to set your DNS type.

    If you are using a Static IP, provide the following information:

    • IP address in CIDR notation (for example: 192.168.1.100/24)
    • List of DNS servers (for example: 192.168.1.1,192.168.1.2)
    • Default gateway (for example: 192.168.1.1)

    Remote Details

  5. If a proxy is required for the Remote to access the internet, click the Requires Proxy toggle and enter the Proxy Address (only SOCKS5 proxies are supported).

    6. Proxy Details

  6. If you want to override the default subnets and provide private subnets to start the Remote, click the Show advanced options toggle and enter the Remote Cluster Subnet and Remote Service Subnet that you want to use instead of the defaults.

    7. Note: In some cases, the default subnets may sometimes collide with your existing network. In such a scenario, you may need to override the default values with whatever subnet you have available. However, any changes you make to the default subnets are permanent and cannot be reversed without installing a new appliance.

    Advanced Options

  7. Click Submit.

    The new Remote will be displayed in the list with a status of Not Connected.

Configuration information is unique to each Remote. After you create a Remote in Automation, download its virtual machine configuration file.

  1. On the Remotes page, hover the mouse over the new Remote you just created and click the ellipsis (…) in the Actions column to open the drop-down menu.

    Actions

  2. Choose Connect from the Actions drop-down menu.

  3. In the Connect Remote dialog box, click Generate Package.

    Generate Package

    A remotePackage.zip file with the Remote configuration will be downloaded to your system.

After you create a Remote in Automation and download its configuration file, use VMware vSphere to deploy the virtual appliance OVA and apply the configuration.

  1. On the Remotes page, click the Download Appliance button to download the newest version of the Remote appliance to your computer.

    New Remote

  2. To verify that the OVA is complete and not corrupted, compare its file hash against the following:

    File Name OVA Name SHA256 Hash

    xdr-automation-remote-2.4.ova

    xdr-automation-remote-6.26.0-34-20240906T1835-f173eb5

    12ad60ca30dc74acaee80683c4e248bfff0de44cdab6db76833c5b02f8672804

    xdr-automation-remote-2.2.ova

    xdr-automation-remote-6.25.0-33-20240823T1754-f173eb5

    a30246f1aa78ee18aadbf09df7942d88f55e0270ef34deb3bab0d627f096f00e
    xdr-automation-remote-2.1.ova xdr-automation-remote-6.2.0-25-20230821T2007-d895de0 b635cb4a9c6c9101c8e902c16f00c2b44f13cd2e147ff4195967dbeeb1535f16
    xdr-automation-remote-2.0.ova xdr-automation-remote-6.0.0-23-20230720T1756-d895de0 dda58bc0fbbbfee50caaf27f5b319d74d9b261447db9a096f25047b7bc595ecc

  3. In your VMware vSphere client, right click on the folder you want to deploy the Remote in, and select Deploy OVF Template.

  4. Click the Local file radio button, and click Choose Files. Navigate to the Remote OVA you downloaded, and select it.

    Local File Option

  5. Click Next.

  6. Give the virtual appliance a unique name, confirm the location for the virtual machine, and click Next.

    Select Name and Folder

  7. Click the compute resource where the virtual appliance will be deployed, and click Next.

    Select Compute Resource

  8. Review the details of the deployment, and click Next.

  9. In the list of datastores, choose the datastore you want to use for the virtual appliance, and click Next.

    Note: We recommend a minimum of 30 GB of available disk space for an Automation Remote.

    Select Datastore

  10. For each Source Network, click the Destination Network drop-down, choose the network where you want to deploy the virtual appliance, and click Next.

    Select Network

  11. On the Customize Template screen, provide the following information:

    • Unique ID and hostname for the virtual appliance.

      Name Virtual Appliance

    • (Optional) SSH public key for SSH access to the appliance (see Generate an SSH Key Pair).

    • Set Encoded user-data to the contents of remoteconfig.txt (from the remotePackage.zip configuration file.

    • Set a Default User’s Password for access to the virtual appliance console (username: ubuntu).

      Specify Password

  12. Click Next.

  13. Review all of the virtual appliance details, and click Finish.

  14. After the virtual appliance deployment completes, click Power On to start the appliance.

    When the appliance is online, the Status of the Remote should change from Not Connected to Connected on the Remotes page.

    Note: A newly deployed Remote may take up to 10 minutes to show as connected.

After deploying your Automation Remote, you can configure the virtual appliance to use custom NTP servers using these steps:

Note: If you are unsure of the settings to use, contact your network administrator.

  1. Sign in to your virtual appliance using one of the following methods:

    • Open a console to the VM in vSphere and sign in with your password.
    • SSH to the VM using the key pair you created during setup.

  2. Open the /etc/chrony/chrony.conf file and change the NTP servers to your preferred servers.

  3. Save and close the file.

  4. Run the following command to restart the NTP service and verify that the time is correct:

    systemctl restart chronyd ; watch chronyc tracking

If you want to use SSH to access your Remote virtual appliance, you must generate a key pair for authentication. You can use any key pair that is valid for a standard Ubuntu authorized_hosts file (for example, RSA or ED25519).

Use the following examples to generate a default RSA key pair.

Linux/macOS

  1. Open a terminal and execute the following command:

    ssh-keygen -t rsa -b 4096 -f /path/to/output/keypair` (for a 4096-bit RSA key)

  2. If you want to use a passphrase, enter the passphrase and confirm it. If not, press Enter twice.

    A public and private key will be generated at the path you provided:

    • keypair will contain the private key
    • keypair.pub will contain the public key

Windows

Use the PuTTygen utility to generate a keypair:

  1. Download PuTTygen. Use the file puttygen.exe located under Alternative binary files.
  2. Run puttygen.exe.
  3. To use a passphrase for your key pair, enter it in the Key passphrase and Confirm passphrase fields.
  4. Select the type of key and key length at the bottom of the window (we recommend a minimum 2048-bit RSA key).
  5. Click Generate.
  6. Use the Save public key and Save private key buttons to export the keys.

Configure your on-premises targets to use the Automation Remote virtual appliance.

  1. Choose Automate > Targets in the navigation menu.

  2. Select the target you want to add a remote to (or create a new target).

  3. Under the Remotes section, click the Remote Keys drop-down list, and choose the Remote you want to use with this target.

    Select Remote

  4. Click Submit.