|Manuals

Connect a Managed VM

Info

This article uses Oracle Cloud Infrastructure (OCI) as the example provider. The same Managed VM workflow applies to all supported VM-based providers — AWS (EC2), Microsoft Azure, Google Cloud Platform, IONOS Cloud, VMware (ESXi and Horizon), Microsoft Hyper-V, Proxmox VE, Oracle KVM (oVirt / OLVM), and Verge.IO. Provider-specific differences (credential fields, shape and instance type names, network parameters) are noted where they apply.

Kubernetes models follow a different flow — to run an isolated browser on a cluster, see Track C — Deploy Remote Browser Isolation. For a side-by-side mapping of provider concepts, see Provider Concepts Map.

What You’ll Build

By the end of this track, an existing OCI Compute instance will be registered in Thinfinity® Cloud Manager, exposed to an end user through an Access Profile, and reachable via the Thinfinity® Workspace dashboard.

Prerequisites

In addition to the common prerequisites:

  • A running OCI Compute instance with a public IP address assigned.
  • The instance has RDP (port 3389) or a supported remote display protocol enabled and reachable from the internet.
Info

This track uses Public IP as the connection mode. The OCI instance must be reachable on its public IP from the Thinfinity Workspace Gateway. If your environment does not allow public IP access, use Agent ID connection mode instead — see Provisioning and Pooling Options.

1

Open Cloud Manager

Log in to Thinfinity Workspace as an administrator, click the profile icon, and then click Cloud Manager in the right sidebar.

Workspace sidebar with the Cloud Manager entry highlighted

Cloud Manager opens.

Cloud Manager full UI screenshot

2

Add OCI Credentials

Cloud Manager needs OCI API Key credentials to communicate with your Oracle Cloud account. If you have already saved a valid OCI credential set in Cloud Manager (for example, from a previous Quick Start track or from earlier configuration work), skip to Step 3.

Otherwise, register your credentials now:

  1. From the top right of the screen, select Credentials.
  2. Click + New from the top right of the screen to open the credential form.
  3. Select Oracle Cloud as the provider.
Cloud Manager OCI Credentials panel showing available fields
  1. Leave Use Instance Principal off — this Quick Start uses API Key authentication, which works in every deployment topology. Instance Principal is an alternative for Thinfinity Workspace servers that run on an OCI Compute instance — see Oracle Cloud Credentials → Option B.
  2. Fill in the following fields.
Field Value
Tenancy ID Your OCI tenancy OCID (ocid1.tenancy.oc1..aaaa...).
User ID The OCID of the IAM user Cloud Manager will authenticate as.
Private Key (.PEM file) Upload the .pem private key file generated when you created the API Key in the OCI Console.
Fingerprint The MD5 fingerprint of the API Signing Key (format: xx:xx:xx:xx:...).
Region The OCI region where your Compute instance is located (e.g., us-ashburn-1).
  1. Click Save. Cloud Manager validates the credentials immediately and adds the entry to the Credentials list with a Valid status badge. If the badge instead shows Invalid, the most common causes are a mismatched fingerprint or the wrong private key file — see the linked guide below for the full error reference.
Info

For the full guide on generating these credentials in the OCI Console — including tenancy and user OCID lookup, API Key generation, and troubleshooting an Invalid credential status — see Oracle Cloud Credentials.

3

Register the Existing VM

With credentials in place, you can now bring your existing OCI Compute instance under Cloud Manager management.

In the left navigation panel, expand the Managed VMs section and click the + Add button next to the section header. The Managed VM Configuration Wizard opens.

Provider selection step

Select the provider where your VM is hosted. For our example, choose Oracle Cloud and click Next.

Cloud services providers list

Authentication step

Existing option is selected by default, choose the OCI credentials set you created in Step 2 then click Next.

Search parameters step

  1. In the Compartment Path field enter the name of the compartment where the VM lives.
  2. In the Instance pattern field, enter the complete name or part of the instance name to filter the results. Leave it blank to list all instances available in the selected compartment.
  3. Click Next.

Access step

Leave the default Connection Mode as Public IP and click Next.

Access step with Connection Mode set to Public IP

Power options step

Enable On Demand to allow Cloud Manager to start the VM automatically when a user requests a session then click Next.

Name step

Enter a descriptive Name for this connection (for example, OCI-Finance-VM) and click Finish.

Connection added to the Managed VMs tab

4

Select the Instance to Manage

The wizard has created the provider connection. Now you have to select the specific OCI instance you want to bring under management.

  1. In the Managed VMs tab, select the connection you just created.
  2. Click Manage Instances at the top right of Instances tab.
  3. In the Instances Manager window, check the OCI Compute instance you want to manage.
  4. Click Save.
Instances Manager window — a single OCI instance checked, Save button visible

The instance appears in the Instances tab with its current status.

Instances tab — the registered OCI instance with an Active or Inactive status indicator

Info

This Quick Start registers a single VM, but Cloud Manager lets a single connection manage multiple VMs from the same provider account. To bring more VMs under management later, return to Manage Instances for this connection and check the additional VMs you want to include.

5

Create an Access Profile

An Access Profile makes the instance visible and launchable in the Thinfinity® Workspace portal for end users.

  1. From the Instances tab, select the instance then from the options available to the right for it, click New Profile to launch the Access Profile wizard.
  2. In the first step of the wizard select the type of Access Profile you want to create for your instance. For our example, choose RDC then click Next.
Access Profile wizard step1
  1. In Set up the Connection step:
    • Confirm the name of the selected instance is displayed in the Available Instances field.
    • Set Stop after disconnect to 5 (minutes) to keep the VM running briefly after the user disconnects. This grace period prevents the VM from powering down immediately when the user closes their session, which is useful if they need to reconnect quickly. Tune the value to your workload — shorter delays (1–2 minutes) minimize idle compute cost; longer delays (10–15 minutes) keep the VM ready for users who reconnect frequently. Click Next when done.
Access Profile wizard step 2 — setting up the connection
  1. In Authentication Options leave the default option, Ask for new credentials (the user will enter their Windows or Linux credentials at session start), and click Next.
  2. In Permissions, add the user or group that should have access to this profile then click Next.
  3. Enter a Name for the profile (for example, OCI Finance Desktop), and then click Next. A confirmation message is displayed, click Done to leave the wizard.

You will be presented with the Public Profiles tab where all Access Profiles created in this installation are available.

  1. Check that the new Access Profile appears in the list then make sure to click Apply. The profile is not active and users will not see it in the portal until you click Apply.

Access Profiles list — OCI Finance Desktop profile listed, Apply button highlighted

6

Test the Connection

  1. Open the Thinfinity Workspace portal in a new browser tab (or in a different browser as the target end user).
  2. Log in with the credentials of the user you granted access to in Step 5.
  3. Locate the OCI Finance Desktop tile on the portal home screen.
  4. Click the tile and enter the VM credentials when prompted.

The remote session opens in the browser. Track A is complete.

Thinfinity Workspace dashboard — OCI VDI — General tile and the active RDP session inside the browser

What’s Next