Create an Access Profile for Managed VMs
This article walks through creating a Thinfinity® Workspace Access Profile that connects users to a VM tracked under a Managed VMs connection in Cloud Manager. For the VDI/DaaS path, see Create an Access Profile for a VDI/DaaS Model. For an overview of how Access Profiles integrate with Cloud Manager, see Access Profiles and Cloud Manager.
Prerequisites
- The target VM has been tracked by a Managed VMs connection in Cloud Manager. See Connect to Existing VMs.
- Cloud provider credentials are configured. See Credentials.
- You have the Manage Profiles permission. See Cloud Manager Permissions.
Procedure
The Access Profile creation wizard launches directly from the Managed VMs connection in Cloud Manager, with the connection pre-selected. The wizard advances through seven steps.
Open the Wizard
In the left tree, expand Managed VMs and click the connection that contains the target VM. In the header above the Instances table, click the Create Access Profile icon. The wizard opens with the Managed VMs connection already selected.
Choose the Access Profile Type
Select the protocol the profile will use then click Next.
| Type | Connection |
|---|---|
| RDC | Remote Desktop Protocol (RDP). |
| VNC | Standard VNC. |
| Thinfinity VNC | Thinfinity’s VNC implementation. |
| Remote App | Application-only remoting rather than full desktop. |
The remaining steps describe the RDC path. The other protocols follow the same wizard structure but expose protocol-specific fields. See Access Profiles in the Thinfinity Workspace product manual for those protocols’ specifics.
Set Up the Connection
This step binds the Access Profile to the Managed VMs connection and configures session behavior.
The Managed VMs dropdown and the connection picker beside it are pre-filled from the launch context — the connection you opened the wizard from is already selected.
Configure the remaining fields as needed then click Next.
| Field | Description |
|---|---|
| Use Instance | When enabled, an Available instances dropdown appears listing the VMs currently tracked under this connection. Selecting a specific instance pins the Access Profile to that VM. When disabled, the broker selects an instance at session time. |
| Stop After Disconnect | Minutes of idle time after disconnect before the VM is automatically stopped. |
| Broker Pool | When the Thinfinity Workspace deployment uses a broker pool, the pool ID that should serve this profile. Leave empty for deployments without a broker pool. |
Authentication
Choose how user credentials are handled when the session is established then click Next.
| Option | Effect |
|---|---|
| Use the authenticated credentials | Forwards the user’s Thinfinity Workspace credentials to the VM. |
| Ask for credentials | Prompts the user for credentials at connection time. |
| Use these credentials | Uses a fixed credential pair supplied in the wizard. Selecting this reveals input fields for the username and password. |
Permissions
Grant access to the users or groups who should be able to use this Access Profile. At least one user or group is required.
To add a user or group, type the name in the search field and click Add. Repeat for each entry. Click Next.
Name the Access Profile
Enter a name for the profile and, optionally, customize the icon shown in the user’s Thinfinity Workspace home view. The name is what users see when they look for the Access Profile in Workspace. Click Next.
Confirm and Apply
The wizard confirms creation with a success message. Click Done to close the wizard.
A Settings notification appears in the bottom-right of the screen indicating one section has been modified. Click Apply to commit the changes — the Access Profile becomes live for the assigned users at this point.
What Happens at Connection Time
When a user opens this Access Profile from Thinfinity Workspace:
- Workspace looks up the linked Managed VMs connection and the target VM.
- Cloud Manager checks the VM’s current state.
- If the VM is powered off, Cloud Manager powers it on.
- Workspace establishes the session via the selected protocol.
- The user receives the desktop or application.
Troubleshooting
If users report connection errors after the Access Profile is created, see Access Profile Errors for common causes and resolutions.