The Turbo for PC February 2019 Update now allows Active Directory Federation Services (ADFS) based authentication for both local (Run on My PC) and cloud-based execution, even on PCs that are not joined to an Active Directory domain.
This release also introduces support for the ADFS2 protocol in addition to the currently supported ADFS3 protocol.
Previously, Active Directory-based authentication for local execution was available only on PCs connected to the AD domain.
The Turbo for PC February 2019 Update is available for download immediately. Turbo for PC will automatically update unless otherwise specified by the administrator.
Turbo Hub Server is an on-premise version of the Turbo.net Hub designed for enterprise environments.
This major update to Turbo Hub Server includes support for the new on-premises Turbo Application Server and Turbo Portal Server 19.
The Turbo Hub Server 19 update is available for download at turbo.net/server.
Turbo Hub Server 19 is available for download at turbo.net/server/download.
The upgrade to Turbo Hub Server 19 is free to all licensed users of Turbo Hub Server on active maintenance. If eligible, a new license key is available from the Account Settings page of your Turbo.net account.
We hope you enjoy Turbo Server 19!
The latest version of Turbo for PC includes a completely rearchitected browser integration model that supports all modern web browsers. This release retires the previous browser plugin-based API and replaces it with a new turbo:// protocol handler.
This update also includes full support for authentication using Active Directory Federation Services (AD FS) and on-premises Turbo Application Servers.
Turbo for PC will automatically update unless otherwise specified by the administrator.
Administrators can define trusted workspaces for all users in %PROGRAMDATA%\Turbo\Containers\trusted-sources.json.
Combined client toggle settings under turbo config --enable|--disable=[option] command.
Administrators can set default or override settings for the client configuration using turbo config --as-inherit|--as-override command.
Added ability to disable merge isolation using turbo config --disable=mergeisolation command.
Added --working-dir|-w=[path] flag to turbo commit for setting the working directory of an image.
Added the Java component to the Turbo for PC installer to support systems that are not connected to the Internet.
Turbo for PC fails to launch application on the local PC when a cloud container session is not synchronized to the local system.
Turbo for PC now respects network rules specified in application settings.
The login dialog may fail to detect when an on-premises workspace is using an SSO authentication method.
Certain applications may crash on application exit due to a race condition.
Applications may fail to start with an "Object reference not set to an instance of an object" error.
A new application version is downloaded even when upgrade check is disabled on application startup.
Running the clean and base images with incompatible isolation should display a warning message.
The turbo config --image-path=allusers command may fail with invalid container storage path error.
The turbo-plugin.exe --app-server command to provision application servers should detect incompatible OS versions.
The latest version of Turbo VM is now available in the Turbo Hub.
Added support for the latest Windows build, Windows 10 Insider Preview 18305.
Added a new IsolateDrive ability to hide specified drives from virtualized applications.
Added a new IsolateDDE flag to isolate DDE messages coming from outside the container.
Added a new ExtendedAppLockerCompatibility flag that disables AppLocker DLL rules that are incompatible with virtualization.
Fixed a compatibility bug in WriteCopy registry isolation when running native installation of Office 365 under VM.
Fixed a compatibility bug that prevented some Autodesk applications from being able to load specific DLLs.
Fixed a compatibility bug with the SPACE GASS application.
Fixed a rare crash during application startup when SentinelOne security software is present.
Fixed a condition that could cause process hang during startup in rare conditions.
Improved shutdown processing during ExitProcess calls. This ensures that data is correctly flushed to files if managed by buffered C streams and the C library was linked statically to the application.
Allow running the 64-bit version of PowerShell. Previously attempting to start a 64-bit PowerShell instance resulted in start of the 32-bit version.
Image upgrades with layered session state preservation are now performed by default during turbo run.
Isolation mode override flag --isolate=[full|write-copy|merge] is now available for portable application outputs.
Support for additional Security Support Providers (SSPs), enabling authentication via Kerberos, NLA, and more.
The Turbo for PC installer now uses HTTPS to download components.
The Turbo for Mac client has been updated with improved support for copy-and-paste between native and virtualized environments, support for the Windows hidden files flag, and improved diagnostic logging.
The Turbo for Android and Turbo for Chromebook clients now support Single Sign-On.
The working directory may now be specified in the image configuration. The clean image has been updated to maintain backwards compatibility with the new behavior.
Images are not extracted in the local repository folder when using portable applications.
Subsequent executions of a portable executions may crash under some circumstances.
The installer UI may not disappear until the associated portable application is closed.
The turbo rm command fails when an improperly named container folder exists.
The turbo installi command may check the local user repository for images even when the --all-users flag is specified.
The turbo installi command may not create a valid application shortcut when startup file arguments are specified.
Turbo for PC ignores the Allow access to local user folders setting when using on-premise Hub Server.
Improved support for Azure AD and ADFS authentication in Turbo for Mac.
Users will be automatically updated to the latest version of Turbo Client and VM.
Turbo VM honors the SYSTEM attribute for virtualized files.
Turbo Client installation can fail if the installer is not executed from the correct folder.
The turbo pull command is not listed in turbo help.