Configure Bootstrap Node for Omnissa Access Installation

The Bootstrap node acts as the deployment controller. Run all deployment commands from this Bootstrap node. Perform the tasks that follow.

Create the Working Directory

Procedure:

• Run the following commands to create the working directory.

  The placeholder <cluster_name> stands for a directory name you choose, for example access-cluster. You create this directory with the mkdir command below, and you reuse the same name in commands and file paths throughout the rest of this guide. This is different from cp-cluster, which you will see later as the fixed name of the Control Plane cluster itself, for example in profile.yml and cp-cluster.ini. You do not create or choose that name:

  ssh configuser@<bootstrap-ip>
  sudo su
  mkdir -p /opt/wss/<cluster_name>/assets
  cd /opt/wss/<cluster_name>
  

  The folder structure must be as follows:

  • /opt/wss/<cluster_name>
  • /opt/wss/<cluster_name>/assets

  The asset bundle must always be placed inside the assets folder.

Download and Copy the Asset Bundle to the Bootstrap VM

Procedure:

1. Download the Asset bundle xxxxxx.zip from the shared location and copy it to the Bootstrap vm using any of the FTP tools or the linux utility (scp):

   # Copy the asset to the following location:
   /opt/wss/<cluster_name>/assets/xxxxxx.zip
   

2. Unzip the bundle. This can take approximately 5 minutes to complete.

   # Navigate to assets directory to unzip
   cd /opt/wss/<cluster_name>/assets
   unzip xxxxxx.zip
   
   # OUTPUT
   Archive: xxxxxx.zip
       inflating: control-plane-manifest.json
       creating: cli-distribution/
       creating: cli-distribution/linux/
       inflating: cli-distribution/linux/wso
       inflating: control-plane-images.tar.gz
       inflating: offline-hydrater.tar.gz
   

Install WSO CLI

Procedure:

• Follow the inline instructions below to install the WSO CLI (Workspace ONE Command-Line Interface) and to verify the installation:

  # Add WSO CLI to PATH
  cp cli-distribution/linux/wso /usr/bin/
  
  ## Verify WSO CLI is installed successfully
  wso version
  
  # OUTPUT
  Workspace ONE CLI 
  Platform: linux/amd64 
  Version: 26.07.0.0-2026.07.13-528-eb05a4e  
  Build time: Mon Jul 13 10:26:53 UTC 2026
  CP  Image Version: 0.5.0-2026.07.10-829-05c0b8a 
  CPS Image Version: 0.1.2-2026.07.13.0-e4b30287895ad3339b27adf97e2273a082a4a033
  

Configure Assets

Procedure:

1. Read and Accept the EULA. For example:

       # After you run the following command, read the EULA and enter Y to accept or N to decline when prompted.
       wso eula
   
       # OUTPUT
      <timestamp> Review the eula at https://www.omnissa.com/general-terms/
       Do you agree to these terms ? [y/n]: y
       <timestamp> EULA accepted
   

2. Load images. For example:

   wso configure /opt/wss/<cluster_name>/assets/
   
   # OUTPUT
   <timestamp> Version control is enabled but no current version details file found. First time configure skipping version check.
   <timestamp> Copying files to cli home directory /opt/wss/.wso-cli
   <timestamp> Loading Workspace ONE components
   

   Note: It is recommended that you run all WSO commands from the /opt/wss/<cluster_name>/ directory. If you run commands from a different directory, you might receive the following error:

   The cluster work directory does not seem to be initialized. Please run init command on the directory.

3. Verify images. For example:

   docker images
   
   # OUTPUT
   REPOSITORY                                                            TAG                                                           IMAGE ID       CREATED       SIZE
   docker-local-xxxxxx-builds/control-plane                              0.5.0-2026.01.23-446-ee28f9f                                  013df7d6281d   10 days ago   1.69GB
   docker-local-ws1access/access-onprem/control-plane-services   0.1.2-2026.01.22.0-117d3c12b269ddfc25aef69eec8bafbe5fd73bb6   7ea2678a6f81   10 days ago   511MB