Skip to main content

Frame Platform 24-05-19

Frame Console 4.10.0​

Added:

  • Support for customers to register their own IBM Cloud account.
  • USB Redirection now generally available.
  • Ability to increase the size of persistent desktop disks beyond 512 GB.
  • Ability for customers to restrict access to the Azure storage container and/or skip Azure cloud account validation when registering their own Azure cloud accounts.
  • Ability for administrators to check the status of an ongoing replication process for specific backups and disable the ablity to replicate if the task is in progress.
  • Updated the branding of the invitation email.

Removed:

  • “Require Login with Domain User Account” slider removed from Settings > Domain Settings.

Fixed:

  • Issue where Settings > Deployment Group options for Server 9.X Frame Accounts were not labeled correctly.
  • Issue where Frame would attempt to backup user volumes of terminated Frame Accounts.
  • Issue where the Dashboard > Volumes page did not use the additional horizontal space of higher resolution displays.
  • Issue in the GUI where the Backup Settings Time Zone dropdown values were misaligned, and the label on the Scheduled Backup Interval slider was clipped.
  • Issue with the replication of backups from the primary Azure region to the secondary Azure region.
  • Issue where FRP7-based sessions may fail to start if multiple browser tabs were open.
  • Issue where Settings > Disaster Recovery page validations were performed before the field values were changed.
  • Additional reliability fixes.

Frame Gateway 11.10.0​

Added:

  • Support for suspension of persistent desktop VMs when idle timeout is reached (requires Frame Server 9.1).
  • Option for customers to restrict access to the Azure storage container and/or skip Azure cloud account validation when registering their own Azure cloud accounts.
  • Option for customers to define custom tags in the Cloud Account for Frame-provisioned public cloud resources.

Removed:

  • The UNSUPPORTED_LOGOFF notification message, as this message is generated when the user logs out of Windows or powers off the desktop VM using standard Windows functions instead of closing the session from the Frame Terminal.
  • The logic that restricts each Azure resource group to 800 VMs, disks, or snapshots.

Fixed:

  • Issue where an unnecessary persistent desktop VM was created when a persistent desktop backup was restored.
  • Issue where replication needed to be stopped if an administrator disabled Frame Disaster Recovery (DR).
  • [Azure] Issue where Azure snapshot resource groups were not created using the standard naming convention when registering an Azure cloud account.
  • [Azure] Issue where Azure storage accounts and VNET resource groups did not follow the standard naming convention.
  • Reliability fixes.