Setting the Default Launcher via Registry

The sslauncher: URL protocol can be handled by either Delinea Connection Manager or the Secret Server Protocol Handler. You can control which one is used by default by editing the command subkey for the sslauncher protocol in the Windows registry.

If the Secret Server Protocol Handler is not installed, only Connection Manager will be available to handle the protocol.

Registry Key Scope

The key can be set per-user or for all users. If both are set, the per-user (HKCU) value takes precedence over the all-users (HKLM) value.

Scope Registry key
Current user HKEY_CURRENT_USER\Software\Classes\sslauncher\shell\open\command
All users HKEY_LOCAL_MACHINE\SOFTWARE\Classes\sslauncher\shell\open\command

Selecting the Launcher

Set the (Default) value of the command subkey to the path of the launcher executable, followed by "%1".

Use Delinea Connection Manager

Set the (Default) value to the path to Delinea.ConnectionManager.Win.ProtocolHandler.exe. For example:

Copy 
"C:\Program Files\Delinea\Delinea Connection Manager\Delinea.ConnectionManager.Win.ProtocolHandler.exe" "%1"

Use the Secret Server Protocol Handler

Set the (Default) value to the path to RDPWin.Bootstrapper.exe. For example:

Copy 
"C:\Program Files\Thycotic Software Ltd\Secret Server Protocol Handler\RDPWin.Bootstrapper.exe" "%1"

Notes

  • Only the command subkey value needs to change to switch launchers.

  • The parent sslauncher key's (Default) value (URL:Secret Server Launcher Protocol) and its empty URL Protocol value are standard boilerplate that register the URL-protocol scheme. These are the same regardless of which launcher is active and do not need to be modified.

  • Installation paths may vary depending on the environment (for example, custom install directories or Program Files (x86) on some systems). Confirm the actual executable location on the target machine before applying.