You can also run browsers on your local desktop when using a compatible Windows device. Turbo.net automatically synchronizes containers between desktops and the cloud so your applications are available anywhere.
Local or Cloud
Turbo.net will automatically select the best execution option (Local or Cloud) based on your device type. To manually select an execution mode, click on the arrow on the Run button to expand run options and select the preferred execution mode.
The Turbo.net Browser Sandbox now provides all versions of major browsers including Internet Explorer, Chrome, Firefox.
Chrome and Firefox images are automatically updated as new updates are released. Every legacy version is available for execution on demand.
Browsers can be configured with any combination of plugins and runtimes, including Java, .NET, Flash, and Silverlight.
Browser Sandbox also includes nightly Chrome Canary and Firefox Nightly builds and Firefox Mobile. Containerized browsers are a easy and safe way to test and develop against non-production builds of Chrome and Firefox.
A set of popular browsers are available free to use for evaluation purposes.
Turbo.net Pro subscribers can use the new cloud functionality at no additional charge for session lengths up to 10 minutes. (Additional cloud session time available separately.)
The Turbo.net Pro subscription is just $9.95 per month and includes the ability to create customized browsers and applications, run containerized servers, use Turbo Studio, and much more.
Turbo Studio is an easy-to-use graphical editing tool for creating and editing Turbo container environments.
The latest version of Turbo Studio includes direct integration with the Turbo.net Hub, an installer based wizard alternative to snapshots, the ability to create portable container (single EXE) outputs, new subscription-based licensing, as well as support for the latest Windows operating systems.
This update includes the following new features and improvements:
New! Studio 17 directly integrates with the Turbo.net Hub. Templates and import wizards are automatically updated with continuously updated Hub content.
New! New Portable Applications (.exe) output mode generates portable containers with Turbo Client embedded, all in a single EXE.
New! Create applications by installing the application (MSI or EXE) into a container console. This alternative to the snapshot process does not require a clean operating system and does not dirty up the host filesystem or registry.
New! Support added for Windows 10 “Redstone 2” pre-release versions.
Studio available in MSI format and scriptable legacy XStudio command-line tool.
Ability to configure the Minimum OS Requirement for images.
Internal Turbo VM version has been updated to 11.8.1060.
This update includes fixes for the following issues:
Projects containing dependencies on the Turbo.hub Hub fail to build.
Containerized ProgIds are not fully isolated.
Renaming a folder incorrectly fails with a message that the resource is used by another process.
Failure to deinitialize and flush streams may cause missing file writes in specific scenarios.
Virtualized applications can crash if started from multiple paths.
Product version is not set correctly when the metadata field is set to inherit from the startup file.
Trailing spaces are trimmed incorrectly for file paths with arguments.
The command-line XStudio.exe tool does not recognize some encodings for the license file.
An error may occur pushing a XAPPL configuration with a service to the local repository or the Turbo.net Hub.
Many user interface fixes and improvements.
The component version numbers for this release are:
Any Turbo.net user with a Pro subscription can use Turbo Studio 17 by signing in with their account. Studio may be used in a limited fashion by Free users for evaluation purposes.
The ISV upgrade to Turbo Studio 17 is available for free to all licensed users of previous versions of Studio on active maintenance. For commercial users of previous versions, a new license key is available from the account management page of your Turbo.net account.
Need to subscribe an entire XenApp farm to a set of containerized applications?
Turbo.net now provides tools to automatically push Turbo channels to XenApp servers, including making necessary updates to the XenApp configuration. Turbo.net’s Citrix tools support XenApp 6.5 and forward.
Step-by-step instructions for the xa7-subscribe and xa6-subscribe tools have been added to the Turbo Citrix tour:
By default Turbo containers will run in the security context of the user executing the turbo command. But what if we need to run as a different user?
In this example, let’s run SQL Server Management Studio as a different domain user than the currently logged in user. In our scenario we have the Turbo Sandbox Manager installed in the local profile, which is the default behavior.
Our first attempt is to just use the runas command to execute the command turbo run ssms2012:
> runas /user:user@domain "turbo run ssms2012"
Enter the password for user@domain:
Attempting to start turbo run ssms2012 as user "user@doamin" ...
RUNAS ERROR: Unable to run - turbo run ssms2012
5: Access is denied.
Unfortunately with the Turbo Sandbox Manager installed in my local profile I cannot use runas to run SSMS in the user context I want since it does not have access to that user’s profile!
One workaround then is to install Turbo for all users via MSI and then use runas:
> runas /user:user@domain "turbo run ssms2012"
This works well — except we may not want to reinstall the plugin, or may not want to install it for all users.
We can solve this by using runas with the /netonly flag:
> runas /netonly /user:user@domain "turbo run ssms2012"
The /netonly flag forces the application to use the runas account for remote resources and the logged in account for local resources.