What is Local App Launcher?

With Workspace 365 Local App Launcher, you launch local Windows applications from Workspace. Users no longer need to switch between different environments.

Local App Launcher works with a configuration file (Instructions.xml). This file links Workspace apps to applications on the user's device. You also add parameters to applications.

This article is for technical administrators who manage Workspace 365.

What You Need

Local App Launcher consists of two files:

• Workspace 365 App Launcher.msi – the installation file

• Instructions.xml – the configuration file

Requirements:

• Windows operating system on each client device

• The .msi file processes commands from Workspace to the device

• Instructions.xml contains the configuration for applications

Instructions.xml already contains three pre-configured applications:

• Google Chrome

• Calculator

• Teams (with two versions)

Two instructions are available for Teams. Use option 1 in most situations. Try option 2 only if option 1 does not work.

💡 TIP: Download pages are available only to partners and direct customers. Contact your Workspace 365 vendor if you do not have access.

Installation

Step 1. Download Local App Launcer

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.msi.
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

💡 TIP: You can silently install the .msi file. Use Intune or another deployment tool to roll out the file to all client devices.

Configuring Instructions.xml

Step 2: Open and Edit Instructions.xml

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 Path

Enter the target for the application. This is the path to the local application that Workspace launches.

Make sure the path exists on each client device. Local App Launcher launches the application only if the path is available.

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.

Common path formats:

1. .exe name only:

target="SnippingTool.exe"

2. With full path:

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

3. Sysnative (for 32-bit applications that need 64-bit System32):

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

4. %ProgramW6432% (for 64-bit Program Files folder):

target="%ProgramW6432%\TeamViewer\TeamViewer.exe"

5. Universal Windows Platform (UWP) apps:

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

💡 TIP: Test the target path using the Windows Run command (Win+R). Use the same path in Instructions.xml when the command works.

Step 5: Configure the Working Directory (Optional)

Use workingdirectory when the application must start from a specific folder. This option is available from version 1.2 of Local App Launcher onwards.

Example:

Step 6: Add Parameters (Optional)

Use args when the local application needs parameters.

Example:

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

This launches Windows Explorer in this folder:

C:\Workspace 365 Support

Warning: Use XML-encoded arguments. Use " for quotation marks, not straight quotation marks.

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 using 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 roll out the .msi and Instructions.xml to all target clients.

Troubleshooting

Problem: The local application does not launch from Workspace.

Cause: Local App Launcher cannot complete the launch action.

Steps to resolve:

1. Check that the target path exists on the client device. Use Windows Run (Win+R) to test the path.

2. Make sure the instruction id is exactly the same in Workspace and in Instructions.xml.

3. Check the XML file for typos in the id, target, or args.

4. Make sure the .msi file is correctly installed in C:\Program Files (x86)\Workspace 365 App Launcher.

5. Check that Instructions.xml is in the same folder as the installed .msi file.

Limitations

• Local App Launcher works only on Windows devices.

• The target path must exist on each target client.

• Local App Launcher supports only XML-encoded arguments.

• Download pages are available only to partners and direct customers.

Glossary

Args: Parameters that Local App Launcher passes to the local application.

GUID: Globally Unique Identifier. A unique value you can use as an instruction id.

Instruction id: The id that links the Workspace app to the instruction in Instructions.xml.

Instructions.xml: The XML file containing the instructions for local applications.

Local App Launcher: A component with which you launch local Windows applications from Workspace.

MSI: A Windows installation file with which you install Local App Launcher on a client.

Sysnative: A Windows alias with which 32-bit applications access the 64-bit System32 folder.

Target (target path): The local path to the application that Workspace launches.

UWP app: Universal Windows Platform app. An application from the Microsoft Store.

Workingdirectory (working folder): The folder in which the application starts.

XML: Extensible Markup Language. A computer file format for storing information.

Launching local apps with the App Launcher