Introduction

You can start local Windows applications from Workspace with the Workspace 365 App Launcher.

The App Launcher uses an instruction file to connect a Workspace app to a local application on the user’s device. You can also add parameters to the local application.

This article is for technical administrators and people who manage a Workspace 365 ecosystem.

Requirements

The Workspace 365 App Launcher consists of two files:

Workspace 365 App Launcher.msi
Instructions.xml

You need a Windows operating system on each target client.

The Workspace 365 App Launcher.msi file handles the commands that Workspace sends to the local device.

The Instructions.xml file contains the configuration for the local applications and optional parameters.

The instruction file includes three preconfigured applications:

Google Chrome
Calculator
Teams

For Teams, the file includes two instructions for the new Teams. Use option 1 in most situations. Use option 2 when option 1 does not work.

The download pages are only available for partners and direct customers. Contact your Workspace 365 supplier if you cannot access the download page.

Instructions

Step 1. Download and deploy the Workspace 365 App Launcher

Go to the download page through the support widget on the partner portal.
- Please contact your Workspace 365 supplier to provide the files if you cannot access the download page. Our download pages are only accessible to partners.
Download the App Launcher.
Deploy Workspace 365 App Launcher.msi to the target clients.
Deploy Instructions.xml to the Workspace 365 App Launcher folder.

Use this installation path:

C:\Program Files (x86)\Workspace 365 App Launcher

You can install the .msi silently. Use Intune or another application deployment tool.

Step 2. Edit the instruction file

Open Instructions.xml in a text editor, such as Notepad.

Each instruction can use these parameters:

Parameter	Required	Description
`id`	Yes	Connects the Workspace app to the instruction in the XML file.
`target`	Yes	Defines the local application path.
`workingdirectory`	No	Defines the folder where the application starts.
`args`	No	Adds parameters to the local application.

Pay attention to capital letters and punctuation when you edit the XML file.

Instruction file example

<?xml version="1.0" encoding="utf-8" ?>
<Instructions>
  <!-- Explorer -->
  <Instruction id="D0369AB1-EDBB-40DE-B74F-62EE43798C8A" target="%windir%\Explorer.exe" />

  <!-- Snipping Tool -->
  <Instruction id="j8faf5fa-d271-414c-8723-1cedd5881c27" target="SnippingTool.exe" />
  <Instruction id="d8faf5gb-g300-425c-9724-3ccd5981d198" target="C:\Windows\Sysnative\SnippingTool.exe" />

  <!-- Calculator -->
  <Instruction id="G1370AB1-ADJJ-41DC-G75G-73EE43808C9B" target="%windir%\system32\calc.exe" />

  <!-- Chrome -->
  <Instruction id="3ACA9EE8-4204-4B14-98A4-C79D8E7E7E4B" target="Chrome.exe" args="-incognito" />

  <!-- Spotify -->
  <Instruction id="6C09F2CB-099C-457A-BE09-81CEEC529716" target="%AppData%\Spotify\Spotify.exe" />

  <!-- TeamViewer -->
  <Instruction id="GC14C38E-1796-4104-BF32-1E0464574C6A" target="%ProgramW6432%\TeamViewer\TeamViewer.exe" />

  <!-- PowerShell -->
  <Instruction id="4A7F2CAC-2F72-4577-8A3C-F2DD06A39010" target="%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe" />
  <Instruction id="25FDD6A5-175B-4ED2-B3BB-BB76EC768650" target="%windir%\system32\WindowsPowerShell\v1.0\PowerShell_ISE.exe" />
  <Instruction id="5ad45702-c1b1-4eea-a0f4-9d035247ff2f" target="Test\powershell.lnk" workingdirectory="%userprofile%" />
  <Instruction id="351f1c63-75a1-45d0-8a31-d0133d778216" target="powershell_ise.exe" workingdirectory="C:\Windows\System32\WindowsPowerShell\v1.0" />

  <!-- Loom -->
  <Instruction id="1178D2B6-012E-4E76-A25B-B6B97243AE34" target="%LOCALAPPDATA%\Programs\Loom\Loom.exe" />
</Instructions>

Step 3. Configure the instruction ID

Fill in the id for the application.

The instruction ID is the value that links the Workspace app to the instruction in Instructions.xml.

You can use a custom globally unique identifier (GUID). You can generate a GUID yourself via this this generator

Step 4. Configure the target

Fill in the target for the application.

The target is the local path to the application that Workspace starts.

Use an application path that exists on each target client. The App Launcher can only start the application when the path exists on the client.

The App Launcher process runs as an x86 process. When you use a system variable such as %ProgramFiles%, Windows points to the Program Files (x86) folder.

Use %ProgramW6432% when the application does not start with the configured path and the application is installed in the 64-bit Program Files folder.

You can often use the same path that works in the Windows Run command.

Sometimes you only need the .exe file:

target="SnippingTool.exe"

Use Sysnative when a 32-bit application or script must access the 64-bit System32 folder:

target="C:\Windows\Sysnative\SnippingTool.exe"

Use this format for Universal Windows Platform (UWP) apps:

target="shell:appsFolder\Microsoft.MSPaint_8wekyb3d8bbwe!Microsoft.MSPaint"

Step 5. Configure the working directory

Use workingdirectory when the application must start from a specific folder.

The working directory is the folder where the application starts.

This option is available from version 1.2 of the Local App Launcher.

Example:

<Instruction id="75f51d21-11b2-4cdc-83a7-b5c911f5d69a" target="D:\Deleteme\ShowCurrentFolder.bat" workingdirectory="%userprofile%"/>

Step 6. Configure arguments

Use args when the local application needs parameters.

Example:

args="/root,&quot;C:\Workspace 365 Support&quot;"

This starts Windows Explorer in this folder:

C:\Workspace 365 Support

Use XML encoded arguments. For example, use this value:

&quot;C:\Workspace 365 Support&quot;

Do not use this value:

"C:\Workspace 365 Support"

Step 7. Add the local app to Workspace

Go to the App store.
Select Manage apps.
Image content: the App store with Manage apps selected and Add new app visible.
Select Add new app.
Add the Local app.
Select Add
Image content: the Add new app screen with the Local app tile.
Fill in the app name.
Fill in the instruction ID.
The instruction ID must match the ID in Instructions.xml.
Image content: the Local app settings screen with the App name and Instruction id fields.

You can also configure these optional settings:
- App color
- Icon
- Access to the app
Select Save.
You can now add the app to Workspace from the App store.

Best practices

Use the same local application path on each target client.
Test the target path with the Windows Run command. Use the same path in Instructions.xml when the command works.
Use %ProgramW6432% when the application does not start with the configured path and the application is installed in the 64-bit Program Files folder.
Use XML encoded arguments when the path contains spaces.
Use a deployment tool, such as Intune, to deploy the .msi and Instructions.xml to all target clients.

Limitations

The Workspace 365 App Launcher works on Windows devices.

The target path must exist on each target client.

The App Launcher only supports XML encoded arguments.

The download pages are only available for partners and direct customers.

Troubleshoot

Problems with the Local App Launcher

What do you see?
The local application does not start from Workspace.
What does it mean?
The App Launcher cannot complete the launch action.
What should you do?
Open the dedicated article Troubleshooting the Local App Launcher.
Hyperlink text: Troubleshooting the Local App Launcher
URL: https://support.workspace365.net/en/articles/175632-troubleshooting-the-local-app-launcher

Glossary

Workspace 365 App Launcher: A component that starts local Windows applications from Workspace.
MSI: A Windows installer file that installs the Workspace 365 App Launcher on a client.
Instructions.xml: The XML file that contains the instructions for local applications.
Instruction ID: The ID that links the Workspace app to the instruction in Instructions.xml.
GUID: A unique value that you can use as an instruction ID.
Target: The local path to the application that Workspace starts.
Working directory: The folder where the application starts.
Args: Parameters that the App Launcher sends to the local application.
Sysnative: A Windows alias that lets 32-bit applications access the 64-bit System32 folder.
UWP app: A Universal Windows Platform app, such as a Microsoft Store app.