Community

Idea:
The implementation of a script library where techs could create their own pre made scripts and use them on support machines in real time.

Use case:
- Remote support agents can add scripts which they frequently use to the library to save time while supporting clients. This can include scripts to add printers, set default printers, clear print queues, clean up temporary files, deploy patches or remediations, set configurations, etc..

Scripts can be added to the script library by either:
1) Quick entry mode - Specifying the type of script (powershell, command prompt, bash, shell) and then entering the code into a text box area.
2) Uploading a zip file if there are multiple assets associated with the script then specifying the main script to run and type of script, similar to how an intunewin package is added to intune.

Upon running:
- The script would be downloaded to a location under RU app data, extracted, and run.
- While running it would show a terminal window on the viewer side which will make the script interactive to the support agent (easiest implementation)

Possible improvements may include the ability to:
- Schedule scripts to run on specific machines at predesignated times (one time or reoccurring)
- Specify what context to run the script in (user, admin, system, any) and have RemoteUtilities try to elevate if needed automatically.
- Specify if this is to be run as a 32bit or 64bit process and have RemoteUtilities automatically run it in the specified mode if applicable
- Specify whether the script window should be visible/hidden and have RemoteUtilities run it accordingly
- Specify if this is to be run in an interactive mode (showing terminal on viewer, or as a summary showing the status and final result/outputs of the script)
- Use parameters in the deployment, set default script parameters, and being able to edit them when deploying the script
- Specify if this script should be executed in a temporary location or persist the script + data and have RemoteUtilities clean up if needed.

Current workflow:
- Support agent must have a script written and saved on the system they are providing support from. If they switch computers they must access the script or archive from a saved location or manually move it to the other computer. The script must also include detection of user context, 32/64bit process and how to run the window or the support agent will manually have to check and perform actions to manually adjust the environment.
- Support agent must transfer the script or archive using the File Transfer tool (locate it on their system, create directory for the script, transfer)
- Support agent must switch to terminal mode, navigate to the temporary folder, execute the script checking user context first, process, etc..
- Once complete the support agent may leave the files or may need to delete the temporary files or rely on Windows to perform the cleanup.