The Script Monitor, first introduced in ELM Enterprise Manager version 7.5 is not as much a monitoring item as it is a distributed task scheduler for scripts.  It allows you to run any PowerShell, VB or CScript on any remote system on any schedule.  Think of the possibilities.

No pushing scripts or batch files out from a central server and hoping it makes it through firewalls and security to actually run on the remote system.  The script is executed at the local level by the ELM Agent installed on the remote system utilizing a local system account.

If you do not happen to be a scripting expert, there are plenty of examples online to get you started in automating several different tasks to make your job easier (see link at bottom).

Here are some ideas to consider:

  • Check for the existence of a file and email a copy if found

    Got any legacy systems out there perhaps that generate a report but it has to be retrieved manually?  How about a PowerShell script to take care of that for you.

  • Change firewall settings on multiple servers

    Have a new application you need to allow through, or a retired application you need to cut access for?  Use a scheduled script to make the necessary changes across multiple servers.

  • Have a dispersed environment or lots of remote employees?

    Run the Script Monitor utilizing a PowerShell script to set remote desktop configuration for servers and workstations.

  • Have a remote computer run Ping (Instead of the ELM Server)

    Test inbound connections, websites, and accessibility from outside of your normal channels.

  • Need to clear out old cache, temp or log files?

    Use a PowerShell script to delete files older than X days from a path.

You could even force user logoffs, lock a workstation or remote reboot a system if needed.  You can also design your script to create an event which ELM can pick up to notify you that the script ran successfully, or failed.  For example:

If (Test-Path -Path ‘C:\Program Files\ELM Enterprise Manager\Reports\Data Profile – Partitions – Publication\Data Profile2.pdf‘ ) {

Copy-Item -Path ‘C:\Program Files\ELM Enterprise Manager\Reports\Data Profile – Partitions – Publication\Data Profile.pdf‘ -Destination C:\reports

Write-EventLog -EventId 5052 -LogName Application -Message “File Copied” -Source ELMAgent -Category 124 -EntryType Information} Else {

Write-EventLog -EventId 5053 -LogName Application -Message “Warning File Does Not Exist” -Source ELMAgent -Category 124 -EntryType Warning }

The following event id’s and category are available for use within any custom scripts.

5051 – Ex: Informational

5052 – Ex: Warning

5053 – Ex: Error

Category: 124 (Script Monitor)

The possibilities are endless!

For more ideas on how to use ELM with scripts for system administration, check out this scripting guide from Microsoft:  https://docs.microsoft.com/en-us/powershell/scripting/samples/sample-scripts-for-administration?view=powershell-7.1

*The Script Monitor is only available in the System license of ELM Enterprise Manager.