Product documentation
Citrix SecurSpaces™
View PDF

Install on a local VM

September 24, 2026
Contributed by: 
C

This page installs Citrix SecurSpaces™ on an Ubuntu VM or host that you have prepared. You run the installer on a separate machine, the installer host. It generates a deployment script that you run on the target host.

To prepare a VM first, see Prepare a XenServer VM or Prepare a Hyper-V VM.

Prerequisites

  • A target host that meets the 1-Click VM requirements, with no Docker, Kubernetes or K3s installed.
  • An installer host with Docker, outbound HTTPS access to Docker Hub, and 20 GB of free disk space.
  • An administrator email address.
  • A machine capacity. See Sizing.

Check the target host

  1. On the target host, run:

    cat /etc/os-release
grep -o 'avx[^ ]*' /proc/cpuinfo | head -1
free -h
df -h /
hostname -I
<!--NeedCopy-->
  2. Check that:
    • The operating system is Ubuntu 22.04 or 24.04.
    • The AVX command returns output. If it does not, use a different host.
    • The memory and disk match your machine capacity.
  3. Note the IP address that client devices will use.

Run the installer

  1. On the installer host, create a private directory and run the installer in it:

    mkdir -p ~/sds-local-deployment
cd ~/sds-local-deployment
docker run -it --rm -v ${PWD}:/strong-network/shared strongnetwork/strong_installer:<version>
<!--NeedCopy-->

    Replace <version> with the release to deploy, for example 2026.9.1. On Windows, see Run later steps from Windows.

    SecurSpaces installer container

  2. If the installer offers a newer version, select No to stay on the version you chose.

The sds-cli prompt opens. It accepts SecurSpaces CLI subcommands only. See SDS CLI.

SecurSpaces CLI subcommands

Generate the deployment script

  1. At the sds-cli prompt, enter this command on one line:

    deploy-demo --deployment-location=local
<!--NeedCopy-->

    deploy-demo command

  2. Complete the prompts:

    Prompt Enter
    Administrator email The address you sign in with
    Administrator password A strong password, or leave empty to generate one
    Machine capacity The capacity that matches the target host. The default is Medium.
    Region 1 US, 2 EU or 3 Asia

    Local deployment wizard prompts

  3. Under Generated Local Deployment Script, copy the script from #!/bin/bash up to, but not including, the separator line.
  4. Save it on the installer host as deploy.sh, in UTF-8 without BOM and with LF line endings.
  5. Note the assigned URL, for example <name>.try.sds.citrix.com, and the administrator credentials.

Caution:

The script and the installer output contain secrets. Store them privately.

Leave the installer open for the next step.

Associate the IP address with DNS

Important:

Complete this step within 1 hour of generating the script. You can run the script at the same time.

  1. When the installer asks whether to proceed with the DNS and IP association, enter y.

  2. Enter the target host’s IP address. DNS and IP association

  3. From a client device, check that the assigned hostname resolves to that address:

    nslookup <name>.try.sds.citrix.com
<!--NeedCopy-->

If client devices cannot resolve the hostname, add a record to their DNS server, or add this line to the hosts file on each client device:

<host-ip>  <name>.try.sds.citrix.com
<!--NeedCopy-->

Hosts file entry

Run the deployment script

  1. Copy deploy.sh to the target host, and connect to it:

    scp deploy.sh <user>@<host-ip>:~/deploy.sh
ssh <user>@<host-ip>
<!--NeedCopy-->

  2. On the target host, restrict the file’s permissions and run it:

    chmod 600 ~/deploy.sh
sudo sh -c 'umask 077; exec bash ~/deploy.sh'
<!--NeedCopy-->

    Deployment script running

  3. When the script finishes, check the cluster:

    sudo kubectl get nodes
sudo kubectl get pods -A
<!--NeedCopy-->

    Wait until the node is Ready and every pod shows all its containers ready in the READY column.

Wait for initialization

A background job applies the evaluation license and creates sample data after the script finishes.

  1. Find the job and follow its log:

    sudo kubectl get jobs
sudo kubectl logs job/<job-name>
<!--NeedCopy-->

  2. Wait for One Click VM Demo Data Successfully Initialized. in the log.

Caution:

Until initialization finishes, the setup wizard can show a License step with Community selected. Do not select Community. Wait, then reload the page.

Troubleshooting

Issue Resolution
The installer container does not start Make sure Docker is running and can reach Docker Hub.
unknown command at the sds-cli prompt Enter the subcommand on one line, without sds-cli, a path or line-continuation characters.
The script fails immediately Make sure deploy.sh contains only the script, starts with #!/bin/bash, and uses LF line endings without BOM.
The script fails later The target host is not clean. Restore a clean snapshot or reinstall Ubuntu, then run the script again.
The platform URL does not resolve Check the DNS record or hosts file. If more than 1 hour has passed, run the installer again to generate a new script.

Next step

Continue with Validate the deployment.

Install on a local VM
September 24, 2026
Contributed by: 
C
September 24, 2026
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.