Skip to main content

Frontend 2.17.10

· 7 min read
Tera Insights Team
Tera Insights Team
tiCrypt Team

Frontend 2.17.10 is, above all, a repair release for the Management console. In 2.17.9, selecting a VM in Management > Running VMs produced an empty actions menu, so actions administrators rely on there, such as Power, View logs and Set project, were unavailable. Viewing a VM's users could also show a blank screen or an error. This release fixes both.

Alongside the repairs, bulk VM shutdown is back, every authorized user on a running VM now shows a copyable user ID, and eleven more fixes cover virtual machines, Vault storage, and layout across the interface.

What is in this release​

CountSummary
New3Bulk VM shutdown, a user ID for every authorized user, a quieter task button
Fix13Two Management console fixes, four virtual machine fixes, two Vault fixes, five layout fixes
One fix needs backend 3.14.1

Emptying the trash updates your Vault storage total immediately only on backend 3.14.1 or later. Every other change in this release is in the front end alone.

New​

Bulk VM shutdown​

A running VM is an instance started from a VM configuration. It holds CPU and memory on its host until it is shut down, so clearing machines at the end of a lab session or a teaching term is routine work. Without a bulk action, twenty VMs meant twenty separate shutdowns.

Bulk shutdown is back in Management > Running VMs. For example, to shut down every VM left from a finished lab session:

  1. Go to Management and open Running VMs under Virtual Machines.
  2. Select the VMs to shut down.
  3. Click Open Full Menu (⋮) in the top right panel and choose Power.
  4. In the pop-up, click Normal Shutdown.

Both procedures are documented in full: Shut Down Running VM(s) from Management and Hard Shut Down Running VM(s) from Management.

Which VMs this applies to

Every action in Management > Running VMs operates on VMs you own, co-own, or have been explicitly added to. The Admin and Super-admin roles do not change this. See Which VMs these actions apply to.

A user ID for every authorized user​

A user ID is the unique identifier tiCrypt assigns to each account. Some administrative tasks need it rather than a name: a per-user audit report, for instance, is scoped by user ID.

Viewing a running VM's users from Management previously showed the ID only for owners and managers, so finding any other member's ID meant looking the account up elsewhere. Every authorized user now shows their user ID beneath their name, with a copy button that puts it on the clipboard.

For example, to run a per-user audit report on a member of a shared VM, open the VM's users from Management > Running VMs, copy that member's ID, and paste it into the report. See View Users of a Running VM from Management.

A quieter task button​

Tasks record the background operations the interface runs, such as connecting to a VM over RDP. The Show tasks button carried a red count badge that kept drawing attention to tasks you had already seen.

The button now sits next to the Notifications bell, without the red count. Your tasks open from it as before.

Fixes​

Management console​

  • Admin actions are back for selected VMs. In 2.17.9, selecting a VM in Management > Running VMs produced an empty menu. The actions your permissions allow appear again, such as Power, View logs, JSON Export, Set project and Bulk email.
  • Viewing a VM's users opens its user list. From Management, the panel now lists the VM's authorized users instead of showing a blank screen or the Cannot display VM information error.

Virtual machines​

  • Shutting down or restarting a VM no longer reports VM not found or no longer accessible. The message was misleading and no longer appears. See Restart a Virtual Machine and Shut Down a Virtual Machine.
  • Saving a VM configuration with the option to boot the VM closes the window and starts the VM. Previously, when the boot option was your only change, the window stayed open and showed No changes made.
  • The RDP success task dismisses itself. After you connect to a VM over Remote Desktop, the task counts down and clears on its own. It previously stuck at Dismissing in 9s... until closed by hand.
  • Refreshing Drives & ADs keeps the section open. In the VM file explorer, Refresh on the Drives & ADs section reloads drives and access directories without collapsing the section.

Vault​

  • Emptying the trash updates your storage total immediately. The Vault had kept counting the deleted files, so a user who emptied the trash to get under quota still appeared to be over it. This needs backend 3.14.1 or later; with older backends, the total refreshes once the deletion finishes. See Permanently Empty Trash.
  • Clicking anywhere on the My Computer header expands and collapses it. In the Vault file explorer, the row previously highlighted but did not open. My Computer is the Vault's view of your local drives, provided by the Connect Application.

Layout​

  • Table scrollbars are no longer partly hidden behind the floating toolbar above the table.
  • The Terms of Service editor controls are no longer cut off. In System Settings > Terms of Service, the Edit, View and Split buttons now carry text labels and sit on their own toolbar row.
  • The Track Drive Backup radio buttons are no longer clipped. In System Settings > Track Drive Backup, the Yes and No options had been cut off at the left edge.
  • The More actions (⋮) button is right-aligned with the other action buttons in detail panels that have many actions.
  • Long folder names in the file explorer path are no longer cut off early. In the VM file explorer, the header now reads Root when you browse with admin or root access (previously File Explorer (as Admin/Root)), and the Attach/mount drives button lines up with the edges of the sidebar.

Upgrading​

The front end ships as a .szip build. In the Connect Application:

  • Automatically. Connect runs the latest front-end version by default, and versions update globally unless a user has chosen a specific one. Connect checks for new versions at the Update URL set in System Settings. See Specify a Front-End URL for Automatic Updates.
  • By hand. Upload the .szip file, or paste its link, in Connect's Manage versions dialog. See Add a Front-End Version.

There is no configuration change and no migration.

Questions about a specific deployment: contact our team.