Input values for procedure


I’m wondering if it is possible to create a procedure that prompts for values when it is run?

My scenario is: We have an application that needs a configuration to be generated for each user on each device. Aside from the unique user ID and passcode, the configuration file is standard across all devices.

Is it possible to create a procedure so that when the procedure is run it prompts the user running the procedure to enter the user ID and passcode for that device, then uses them to create the complete configuration file on the device?

I think I have a feature request open for a procedure with a linked Form so we can make our own sort of dynamic procedures.

Hi @hamish

Yes, it is already possible. We can help you on that. Please request with details on scripts section.

You just need to run it with “user” option to show the prompt to enduser.


Thanks @Ilker, but I might not have been clear with the user. I want this prompt to be for the ITSM user, not the end user, so we don’t have to send them the details and reduce the risk of them messing it up.


Not sure if you are talking about the staff or the person who sits in front of the enrolled computer. If it is staff, it is on the roadmap.


I was referring to MSP staff. Thanks for the update, any idea how far down the roadmap it is?

This feature would be a complete game changer and match the abilities of most other RMM tools.

Hi @hamish

Do you want to generate a prompt which needs credentials to be entered for each users who has communication with ITSM ? If they accessed or clicked “YES” by entering credentials it should run otherwise if they click “NO” it should come out of it , is it so ?

Hi @Aravind_pandi

Basically we want to generate a configuration file for an end user. For example:

The end user logs on to PC and notifies the MSP they are online, no further action is required from the end user.

The MSP user then locates the device in ITSM and triggers the procedure to create a configuration file, when they trigger the procedure they’re prompted to enter the relevant fields for the configuration file.

​​​​​​​The end user should never see or interact with any of this.


Now I got it. Correct me if I am wrong,

  • For each and every end user, credentials will be unique.
  • Prompt should generate for MSP User not for end user.
  • After accessing that prompt by entering all credentials, configuration file should create which you have.
If I am good so far, Could you please tell me what are the fields should prompt contains which will be filled out by MSP user?


All these scenarios could be possible only if the MSP user system has installed Comodo client communication and has communication with ITSM. If so, we should run this Script for all end users by having an MSP user system as Default for each machine that the MSP user system will be prompted. After entering credentials that script will run further to the appropriate end user system. Is that Ok ?

Hi @Aravind_pandi

What you’ve described is exactly what we’re after. In this case we would be inputting an extension number and password (we’re provisioning a VoIP extension) but I can imagine others might find it useful to be able to modify the input fields to suit their scenarios.

All devices have the Comodo Client Communication software installed. Ideally the script would be initiated on a per device basis as needed, as we’re just going to be adding the extension for a new user or re-issuing the configuration if it’s failed for an existing user.

Hi @hamish

Thanks for your information. As you said running the Script on a per device basis is the better idea. So, configuration file will be having the datas which we entered via prompt and that file should be in the end user system right ?

Progressing the Script for your request, hope will do great things will update you once it has completed.

Thank you.

Hi @Aravind_pandi

That is correct. We run the procedure, enter the extension number and password which then get added to the appropriate lines of the configuration file and the configuration files is created in the right folder on the end users computer. For the next end user these would be different so there’s no need to remember them.

Thanks for looking at this, we look forward to being able to use it.

I’d like to see it (personally) so that when you as the admin schedule a script to run and you need to have a variable entered into the script … a box pops up on your screen (the admin’s screen) prompting for that information to be entered, and once entered, the script then runs with that variable entered in it … This would be useful in any number of scenarios - from the provisioning VOIP extensions mentioned above, to using the Wake on LAN script, to setting static IPs on an endpoint, to renaming endpoints, etc - the list goes on and on …

Really this is a functionality change in the way scripting currently works … Kaseya and several other RMMs have a way to do this and have for quite some time, so it should be almost a no brainer to include this functionality eventually in the must have department to eventually get done …

Hi everyone,

Thank you for the amazing feedback on this. Ability to pass parameters to a procedure by admin before running on endpoints is already on the roadmap. We will communicate the planned timeline soon. Looking for an update from the team based on your interest to this.


Hi @hamish

Kindly please refer the attached json files (Head_system and End_system ) for your request :

Head_system :
End_system :

Let me explain you clearly about the logic, Based on your request we need a communicator between two Systems

  1. Head System where prompt will be generate and values will be given
  2. End System, which is End user.


  • Run "End_System.json" as System user and "Head_System.json" as Logged in user.
  • Here Communicator used is "NETWORK SHARE" so please provide the network share details as follow : Filepath= r'\\Win-biktodgscbo\e' #Provide the network share file path share_user= "administrator" # Provide the user name for the shared system share_pass= "**********" # Provide the password for the shared system
Steps to follow:
  • Run "End_System.json" file first in required End system, it will send Machine details to Network share and hold the script for 5 minutes to further process.
  • within a min Run "Head_System.json" file to the system where you wanted to generate a prompt and there you can give Extension Number and Password, which will make configuration file and send that file to Network share.
  • After 5 minutes hold "End_System.json" automatically download the configuration file to end user from Network share.
Kindly share your feedback.

Thank you.

20171215-Head_system.json (8.34 KB)

20171215-End_system.json (4.75 KB)

Hello @hamish

Have you tested the above-provided scripts? Could you please share your feedback.

Thanks in advance.