Workspace Extensions

Workspace Extensions are applications that are installed locally, but integrate into Centralized (Server Based) Computing Workspace Control environments. This makes it possible to manage and control the access to local applications as well as Terminal Server applications from one central point: the Workspace Control Console.
Workspace Extensions use Ivanti VDX.

If you configure an application to run as a Workspace Extension, it will be displayed in the Workspace Control menu like any other application. The only difference is that you need to specify the local path on the client for the application.

Where to find Workspace Extensions



Workspace Extensions

Composition > Applications, on the Properties > General tab of an application


To run an executable on a local workstation as a Workspace Extension in a Centralized Computing session (for example a CAD program), complete the following steps:

  • Install the VDX Client plugin on the client.
  • Create an application with the Workspace Control Console. Select the option Run as Workspace Extension.
  • Test the configuration by starting the Application.
  • Check Usage Tracking to see whether the application usage is logged.

You may also associate the application with a Zone:

  • Open the Application's properties in the Workspace Control Console.
  • Add a Zone at the Access Control > Locations and Devices tab.
  • Select a previously created Zone or create one.

This restricts the Workspace Extension to a specific Zone. This can be useful, for example, if the application is not locally installed on all workstations. As an alternative, assign the application to a specific Workspace Container.

Integrate File Types with Workspace Extensions

File Types seamlessly integrate with Workspace Extensions.

If you configure a File Type and select Also register this command as Workspace Extension, the File Type will also be registered on the client using the Workspace Extender (provided that your environment uses the Workspace Extender).

  • If the user runs an application configured to run as Workspace Extension and accesses a file that is associated with an application that is located on a Terminal Server, Workspace Control will automatically open this application. For example, if you have configured Microsoft Outlook to run on a Terminal Server and associate it with the "mailto" special file type, Workspace Control will automatically open Microsoft Outlook in the Terminal Server session if the user opens a mail link in Internet Explorer that runs locally.
  • If you have configured a File Type for a Workspace Extension and the user double-clicks this file type in the Terminal Server session, Workspace Control will automatically start the associated Workspace Extension and open the selected file (or resource). For example, if you have associated the file type "http" with the Workspace Extension Internet Explorer and the user double-clicks an Internet URL from any application in the Terminal Server session, Workspace Control will start the Internet Explorer which was configured to run as Workspace Extension.

In both cases, the files (or resources) must be available on the Terminal Server AND the local client. For example, if the user double-clicks a PDF file on a network share that has been mapped with drive letter "T:" and you have associated this file type with an application configured to run as Workspace Extension on the client, the same drive letter "T:" must be accessible on the client.

You can view the location of both file and application in the File Types node of the Workspace Analysis window of a specific user, which can be accessed through the node Diagnostics > Workspace Analysis. In this way, it is always clear how the redirection of File Types takes place between VDX and Workspace Control.