Workspot Control Release 26.7 Notes

Highlights

Released in the US on August 22, 2026 at 0200 UTC and in the EU on August 25, 2026 at 0530 UTC.
See What to Expect During a Control Update Window

(Akamai) API support for creating desktops, deleting desktops, assigning users, and unassigning users.
(Akamai) Linux desktops pools (both persistent and non-persistent) are now supported on Akamai.
(Amazon Workspaces Core) Shared tenancy pools are now supported.
(Azure Linux desktop pools.) Support for the "Shutdown" power-saving mode, Time Limits Policies, and Warmup Policies.
- When a new Linux pool is created or an existing one is edited, a Time Limits policy is now required. Existing pools with no Time Limits Policy will continue to run their desktops 24/7.
(GCP) In deployments using shared VPC networks, Workspot managed gateways now reserve the public IP within the (local) service project instead of the host project.
(GCP) The use of multiple zones in the same GCP region, and a ranked list of zones in order of preference, is now supported on shared tenancy pools. Previously, it was supported only on sole tenancy pools.
(GCP) When creating or editing a desktop pool, "Use All Zones for High Availability” allows you to specify the order in which to try multiple zones.

See also Using the Workspot Control API.
(API) You can now use the API "POST /v1.0/cloudAppPools/applications/{appId}/icon" command to specify a custom application icon.
(API) The API "GET /v1.0/cloudAppPools/applications/{appId}" command now returns the command-line parameters, if any, for application server apps.

A bug that sometimes caused newly warmed up desktops in non-persistent pools to shut down prematurely has been fixed.

(Akamai) The Template Details table lists "FQDN" as "localhost" instead of a fully qualified domain name.
(Azure/Linux) Warmup Policies cannot be assigned to non-persistent pools created before the release of Control 26.7. New pools can have Warmup Policies.