Please Specify a Valid Jukebox Parameter and Try Again

Standalone Executables

A popular option for organizations that accept an existing endpoint management solution like LANDesk Management Suite ®, Microsoft System Center, or Novell ZENworks is to deploy containerized applications as standalone executables. These executables are built on the SVM architecture and work just like a container.

Deploying applications within containers is convenient for running different versions of applications like Internet Explorer eight and eleven side-past-side on the same system.

To produce an executable output, fix the Projection Type to ISV Awarding in Turbo Studio. Executables can be deployed directly to the users device or to a network share and do non accept any dependency requirements.

An enterprise license for Turbo Studio is required to enable executable outputs. Contact our sales team for more data.

Command Line Options

Standalone executables accept many command line options to modify settings at runtime. The post-obit is a list of available options. Note that these are case sensitive and must be specified earlier any command line options to the application itself.

• /XEnv=VariableName=Value specifies additional surroundings variables. Multiple /XEnv arguments can add additional surroundings variables.
• /XLayerPath=c:\path\to\image.svm adds the given SVM into the virtual environment. Multiple /XLayerPath arguments can add together additional virtual layers. Refer to 'Specify Additional SVMs for a Container' for more than information.
• /XSandboxPath=SandboxPath specifies the path for the application sandbox.
• /XShellEx=Command specifies a vanquish execute command to launch from within the virtual application environment. This selection overrides any startup files specified in the virtual application configuration. Only one /XShellEx argument tin can be specified.
• /XShellExVerb=CommandVerb specifies the verb to use in conjunction with the /XShellEx control. The default verb is OPEN.
• /XLogPath=LogPath specifies the destination path for generated log files (only applies to executables running in diagnostic-mode). This path can include a custom file name pattern (ex. /XLogPath=c:\logs\mylog*.log). The output directory must exist for the logs to exist written.
• /XSpawnVmExceptions=ProcessExceptions specifies a semi-colon delimited list of processes to add to the child process exception list.
• /XRegRoot=c:\path\to\RegistryCacheRoot specifies an override to the runtime-registry-cache portion of the sandbox.
• /XEnable=Setting and /XDisable=Setting enables or disables specific process configuration options. These options include: ChildProcAsUser DeleteSandbox DEPCompat Diagnostics DRMCompat ExeOptimization IndicateElevated IndicateVirtualization IsolateWindowClasses NotifyProcStarts ReadOnly ReadShare ShutdownProctree SpawnComServers SpawnVM SuppressCollisionCheck

Meet VM Settings for details on the available settings.

• /XCollisionCheck=FALSE disables detection of multiple apps attempting to utilise the same sandbox at the aforementioned time. This should only exist used to support legacy behavior.

Deploying Patch Layers

When you take updates or patches that must be deployed, Turbo Studio tin be used to specify additional paradigm layers (SVMs) to load dynamically at runtime. Turbo Studio provides ii mechanisms to reach this. Both methods support path tokens (ie. @APPDIR@) and must specify the full path to the epitome dependencies.

Using Studio

One mechanism is to specify the SVM dependencies in Turbo Studio.

The patch dependency editor tin can exist accessed past going to the Layers console and then clicking the Patches... button.

The SVM Search Pattern field specifies the consummate path to where patch paradigm layers may be located. This can exist a path straight to a specific SVM file or can be a wildcard design to dynamically notice SVM files to load. An example of using a wildcard in the search field is @APPDIR@\patches\*.svm. This search blueprint will load whatever .SVM file found in the "patches" directory where the virtual executable is located. Care must be taken to avert loading arbitrary .SVM files which happen to reside in the same location.

Multiple search design paths may be specified by seperating with a semi-colon. SVM files specified first in the list will take precedence over SVM files specified after in the list. If multiple SVMs friction match a search pattern through the utilise of the "*" wildcard, the SVM files are applied in opposite-alphabetical priority (ex: items in patch_002.svm would take higher priority than items in patch_001.svm).

The Required SVM Name list specifies which of the SVM files specified in the search blueprint are required to execute the container. Wildcard characters are not valid for this and a specific path must be used. If the file is non institute during application launch, an error will be reported and the launch volition be aborted.

Using Command Line

Another machinery is past using the /XLayerPath= command line pick. This parameter takes a path to additional SVMs to load. This can be useful for dynamically creating container environments depending on other user settings. These runtime settings broaden whatsoever which are congenital into the SVM.

An instance of a specified SVM path using total path:

          # wait for 'patches.svm' in the same directory every bit 'virtual-app.exe' > virtual-app.exe /XLayerPath=@APPDIR@\patches.svm  # look for 'patches.svm' in a specific location on the local auto > virtual-app.exe /XLayerPath=c:\path\to\patches.svm  # look for 'patches.svm' on a unc share > virtual-app.exe /XLayerPath=\\server\dir\patches.svm                  

An case of specifying SVMs from multiple locations:

          > virtual-app.exe /XLayerPath=@APPDIR@\patches.svm /XLayerPath=@APPDIR@\officepatches.svm                  

An example using a path with wildcard:

          > virtual-app.exe /XLayerPath=c:\path\to\patches\*.svm                  

This performs a wildcard friction match finding any files that match the pattern, such as 'c:\path\to\patches\patch_001.svm'.

Note: SVMs that are discovered by wildcard are applied in reverse-alphabetical priority. For case, items in 'patch_002.svm' have higher priority than items in 'patch_001.svm'.

Startup File Triggers

A container packet can define several startup files. These tin all exist activated on launch or they can be configured to but exist launched given a specified trigger. This is useful for suite applications (similar Microsoft Office) where almost of the container parcel is shared.

In Turbo Studio, the startup file triggers are managed in the 'Startup Files' dialog.

In this example, an application packet is divers with three startup files; discussion, excel, and access. Any startup files that don't have a specific trigger or have Auto Start enabled will be launched by default. Whatever startup file that has a trigger (just not 'auto start') will non exist launched unless the trigger is specified. Multiple startup files tin can have the same trigger to enable grouped launching.

To launch a startup file by its trigger, specify its trigger every bit the showtime parameter to the container .exe:

          # to launch word > virtual-app.exe WORD  # to launch access > virtual-app.exe Admission  # to launch excel > virtual-app.exe EXCEL  # to launch excel as the default > virtual-app.exe                  

To create an like shooting fish in a barrel-to-access shortcut for a trigger, right-click on your packaged executable and select Create shortcut. Then, right-click on the newly created shortcut and suspend the trigger to the Target field. Alter the shortcut proper name and icon to differentiate the awarding entry point that will be launched when the user runs the shortcut.

davistherited.blogspot.com

Source: https://app.turbo.net/docs/studio/working-with-turbo-studio/standalone-executables

Share this post