Launching Local applicationsFollow
Local apps are only accessible via Workspace on the device which they are installed to. In order to enable local applications from the Workspace, please follow these steps:
Create .reg file
First, a protocol must be created in the Windows registry for the local application. In this case, Notepad will be the example application we want to add and launch using the Workspace. See the example below:
Windows Registry Editor Version 5.00
@="\"C:\\Program Files (x86)\\Notepad++\\notepad++.exe\""
The protocol has to be created in a .txt file. Open a new .txt file using Notepad. Copy the content of the example above, paste it into the .txt file and save the file.
Note: In case of preventing any registry conflicts, we advise you to use a unique application name at the “HKEY_CLASSES_ROOT\ “positions in the protocol as we also did in the example above (not “notepad”, but “notepadapp” for example).
The app name specified in “@=URL: notepad” and "FriendlyTypeName"="Notepad" can be the app name of your choice and does not have to be unique.
The path of the .exe file in the protocol should match the exact path of that .exe file on your local disk (see the last line in the example above). Locate your .exe file and make sure the path is correctly stated in the protocol.
The .txt file must now be changed to a .reg file. Please rename the file to a .reg file and save this. Open the registry editor on your PC (regedit.exe) and import the created .reg file in the Registry:
Add new apps to the Workspace
Now login to Workspace 365 with your credentials and click “Add new apps”.
Select the “Shortcut” app and click “Add to workspace”. The selected app is added to the overview. Select the “Shortcut” app, Click “Edit app” in edit mode. Fill in the app name of your choice and select an icon for the tile. Fill in the following at the Webpage field
Unique name used behind [HKEY_CLASSES_ROOT\ in the protocol. Click “Done”. The local application will now be opened by clicking the created “Shortcut” app.
Launching local Office applications on MAC works a bit differently then launching it on Windows.
The best way to launch an Office application locally is by using Office URI Schemes.
Here is full documentation on how to use Office URI Schemes:
ms-Word:ofe|u|file:///(Bestands locatie van de template)