Hi ,
Welcome to the Support Portal. How can we help?
Follow

Launching local apps (registry)

Table of Contents

 

Introduction

In this article we will explain how you can launch local applications with some Windows Registry edits. We make use of the URI handlers within the OS. For the Workspace 365 App Launcher, we make use of the same protocol. But as admin it's much easier to create and deploy these instructions to launch local applications including parameters. 

We recommend using the Local App Launcher to launch local apps from your Workspace.
27-09-2019 15:35 CEST - Since the latest version of Google Chrome (77.0.3865.90), you will get a pop-up notification every time you want to launch a local app. This is due to changes made in Google Chrome. This is not related to Workspace 365. We are in contact with Google Chrome to find a workaround and/or solution.

 

Configuration

Protocol

The protocol has to be created in a .txt file. Open a new .txt file using Notepad. Copy the content of the example, paste it into the .txt file and save the file.

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

 

 

 

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 the step below.

Back to top


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
[HKEY_CLASSES_ROOT\Notepadapp]
@="URL:Notepadapp"
"EditFlags"=dword:00000002
"FriendlyTypeName"="Notepadapp"
"URL Protocol"=""
[HKEY_CLASSES_ROOT\Notepadapp\shell]
@="open"
[HKEY_CLASSES_ROOT\Notepadapp\shell\open]
[HKEY_CLASSES_ROOT\Notepadapp\shell\open\command]
@="\"C:\\Program Files (x86)\\Notepad++\\notepad++.exe\""

 

Or e.g. "Windows Lock"

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\ws-lock]
@="URL:ws-lock"
"EditFlags"=dword:00000002
"FriendlyTypeName"="ws-lock"
"URL Protocol"=""

[HKEY_CLASSES_ROOT\ws-lock\shell]
@="open"

[HKEY_CLASSES_ROOT\ws-lock\shell\open]
[HKEY_CLASSES_ROOT\ws-lock\shell\open\command]
@="C:\\Windows\\System32\\rundll32.exe user32.dll,LockWorkStation"

 

Or e.g. "Internet Explorer with specific page"

Windows Registry Editor Version 5.00

  [HKEY_CLASSES_ROOT\workspace365]
  @="URL:workspace365"
  "EditFlags"=dword:00000002
  "FriendlyTypeName"="workspace365"
  "URL Protocol"=""

  [HKEY_CLASSES_ROOT\workspace365\shell]
  @="open"

  [HKEY_CLASSES_ROOT\workspace365\shell\open]
  [HKEY_CLASSES_ROOT\workspace365\shell\open\command]
  @="\"C:\\Program Files\\internet explorer\\iexplore.exe\" www.workspace365.net"

 

Or e.g. "Start RDP with mstsc"

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\rdp]
@="URL:Remote Desktop Protocol <URL:Remote%20Desktop%20Protocol> "
"EditFlags"=dword:00000002
"URL Protocol"=""
[HKEY_CLASSES_ROOT\rdp\shell]

[HKEY_CLASSES_ROOT\rdp\shell\open]

[HKEY_CLASSES_ROOT\rdp\shell\open\command]
@="cmd /V:ON /c setlocal && set url=%1 && set url=!url:rdp:=! && set url=!url:,= ! && start mstsc !url!"

Back to top

 

Activate the app

  • Go to the App store (or click on "+ Add tiles").
  • Click Create tile to create a Shortcut.

create_shortcut2.png

  • You need to fill in the following information in the tile to connect to a server via gateway and hostname. For example:
rdp:/v:broker.remoteapp.local,/g:demogateway.workspace365.me
  • Or fill in the pad to your Rdp file to connect. For example:
rdp:c:/temp/rdpfile.rdp

create_shortvut_path.png

Spaces in the path are not allowed.
  • App permissions, such as who has access can be managed from the App store.
  • When all the information has been filled in correctly, you can add the shortcut to your Workspace, either to a Personal or Shared group. 

add_to_workspace.PNG

Back to top

 

Edit app

Select the “Shortcut” app, Fill in the app name of your choice and select an icon for the tile. Fill in the following at the Webpage field.

NOTE: change "Applicationname" to the name you have given the application.
In our case, it should be "Notepadapp:open".

Applicationname:open

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.

Back to top

Launching local Office applications on MAC

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:
https://docs.microsoft.com/en-us/office/client-developer/office-uri-schemes

Example scheme:
ms-Word:ofe|u|file:///filelocationname)

Back to top