remFREE provides two related script concepts:
Script Hub
and:
Script Library
They serve different purposes.
Script Hub
The Script Hub is a catalog of remFREE-provided script templates.
It can contain useful administrative tools for tasks such as:
- diagnostics
- inventory helpers
- software management
- maintenance
- endpoint administration
A template in the Script Hub is not automatically executed against a device.
It is a starting point.
Script Library
The Script Library contains the scripts available to the tenant for use.
An administrator can take an appropriate Script Hub template and add it to the organization's Script Library.
The library then becomes the tenant's working collection of scripts.
Why separate the Hub from the Library?
This separation gives administrators control over what becomes part of their operational toolbox.
Conceptually:
Script Hub
|
| choose
v
Tenant Script Library
|
| execute
v
Managed Device
A large central catalog does not automatically become a large set of tenant actions.
Running a script
When an administrator runs a supported script against a managed endpoint, remFREE creates a job.
The agent receives the work, executes the script using the appropriate endpoint environment, and returns output and status information.
Platform and shell matter
A script intended for PowerShell is not the same thing as a Bash script.
Script metadata can describe properties such as:
- operating system
- shell
- category
- risk
- keywords
- execution timeout
Administrators should choose scripts appropriate for the target endpoint.
Script output
Script output is useful for both operations and troubleshooting.
Where supported, remFREE can also interpret specially structured output for higher-level features.
For example, structured script results can contribute evidence to supported workflows.
Scripts are privileged
Scripts can make significant changes to managed systems.
Before running a script:
- understand what it does
- verify the target operating system
- confirm the intended devices
- review its risk
- consider whether the change is reversible
Scripts versus core remFREE features
Not every capability should be implemented as a script forever.
remFREE can use scripts to extend the platform, but important product capabilities may eventually become native agent or server features.
For example, core compliance is intended to behave as a first-class remFREE capability rather than requiring every customer to manually install compliance scripts.
Auditability
Script execution should leave operational evidence.
Administrators should be able to determine which script ran, which endpoint received it, and whether execution succeeded.
Powerful automation is most useful when it remains understandable.