Custom Process Launcher Setup Instructions and Troubleshooting

Root > Secret Server
Secret Server has the ability to wire up a program to run when clicking the Launcher icon on a Secret. The process Launchers can be customized to work with any command-line-started application and will pass values from the Secret. In order for the process launchers to work, the client machine will need to have the program installed and typically needs the program folder in the PATH environment variable.
Creating a custom process launcher
1.  From the ADMIN menu, select Secret Templates.
2.  Click Configure Launchers, and then click +New.
3.  Select Process for the Launcher Type, and then type a name for the Launcher.
4.  For Process Name, type the process you would like to launch. For example, notepad.exe. Note that if the application is not typically in the Windows Path, you will need to either add it for all users of the Launcher or specify the entire path to the executable. For example, C:\Windows\System32\notepad.exe.
5.  If your process requires extra arguments, type them in Process Arguments. To reference a Secret field, type $ followed by the name of the relevant Secret field. For example, /A $FILENAME where filename is the name of a Secret field name on a Secret template that will be used with this Launcher.
6.  If you need the process to run as the credentials that will be on the Secret, select the Run Process As Secret Credentials check box.
7.  If you need to prompt the user for additional information that will not be in a Secret field, select the Use Additional Prompt check box, and then type a name for the variable. Then be sure to reference this variable with a $ in the Process Arguments field where it will be used.
8.  Click Save.
Adding a custom launcher to a Secret template
1.  From the ADMIN menu, select Secret Templates.
2.  Select the Secret template you want to add the Launcher to, and then click Edit.
3.  Click Configure Launcher (at the bottom of the page), and then click Add New Launcher.
4.  Select the name of your custom Launcher, and then map Secret fields to those that will be used by the Launcher. If you only see Domain, Password, and Username, map these to those same fields on the template. These will be used if you have chosen to run the Launcher as the Secret credentials.
5.  Click Save.

Default Launchers Requirements:
  • SQL Server Launcher - Requires SQL Server Management Studio installed. When installed the program will be automatically added to the PATH. (Default uses 2008)
  • Powershell Launcher - Requires Powershell installed. When installed the program will be automatically added to the PATH.
  • Sybase isql Launcher - Requires isql.exe installed. It may need to be added to the PATH if $SYSBASE has not been added.

How to add a Program Folder to the PATH?

Right click on Computer and go to Properties. In the properties window click Advanced system settings. On the Advanced Tab, click the Environment Variables button. In the System Variables section scroll to Path. Click Edit then at the very end of the Textbox, paste the full path to the folder where the program file is located but make sure not to replace any existing entries. The list is semi-colon separated. Click Ok to close  the dialogs.  It may be necessary to restart the client computer for the path to take effect.

Common Errors:
  • The process (process name) was not found 
    • The application has not been installed on the machine. If the application was installed, the program folder will need to be added to the path.
  • The stub received bad data (1783)
    • The process is set to Launch As the Credentials of the Secret but the username or domain is not correct on the Secret or the client machine cannot find the user or domain credentials specified.
  • Error(740): The requested operation requires elevation
    • When using "Run process as Secret credentials," even though the credentials have admin privileges the process cannot be run with elevated privileges from the command prompt using runas. Instead, configure the process launcher as follows (substituting your .exe for program.exe):
      • Process Name: cmd.exe
      • Process Arguments: /C start /B program.exe


Add Feedback
The problem with the bottom suggestion of using cmd.exe breaks the concept of session recording. It would be helpful to note that disabling UAC is also a solution, though not ideal.
Glen Willms (February 4 at 9:22 AM)
What about custom launchers for a Mac?
Yan Kravchenko (October 22 at 5:37 PM)

Add Feedback