Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Kiwi Syslog Server > Kiwi Sys - Knowledgebase Articles > Kiwi Syslog Server Run Script task

Kiwi Syslog Server Run Script task

Updated March 5, 2018


The Run Script task allows you to run a Kiwi Syslog Server Run-Script.


All Kiwi Syslog versions


Any Run Script task can be scheduled to occur over any interval or at any date and time desired, during application/service start-up or shutdown.

Whether a Run Script task is scheduled or not, it consists of the following two parts:

  • Run Script Options
  • Run Script Notification

Run Script options

  • Script file name
    The script file is a standard text file that contains the script commands. The file name can have any extension, but .txt is used by default for ease of editing with Notepad.

  • Script description
    This field can contain any descriptive text you like. Its purpose is to briefly describe the function of the script.
  • Script language
    Windows Script provides two script engines, Visual Basic® Scripting Edition and Microsoft JScript®.
    VBScript - A variation of Visual Basic or VBA (Visual Basic for Applications) used in MS Word and Excel. This language is easy to learn and has a rich feature set. See the Microsoft website for more information on VBScript.
    JScript - A variation of JavaScript and ECMAScript used in Microsoft's Internet Explorer for web-client scripting. See the Microsoft website for more information on JScript.
    Both languages offer similar functionality and speed, so the choice on which to use is up to personal preference. However, we have found through our tests that if your script is performing mainly string manipulation then JScript appears to be faster in most cases.


It is also possible to add additional scripting languages such as Perl or Python. To do this, you will need to install the Active Scripting engines for any new languages that you want to script in. See the PerlScript website or the Python website for more information. To download and for further information on ActiveScriptRuby, check out the Ruby website.

Field Read/Write permissions

For reasons of security and speed, access to the message/scripting variables can be restricted. Each time a script is run, the message fields are copied to the script variables and back again upon completion of the script. Because the copying takes time and uses CPU cycles, limiting the read/write access to only the variables you want to use will improve the speed of the program.

  • When you enable read access for a group of fields, their values will be copied into the script variables and will readable from within the script.

  • When you enable write access for a group of fields, their values will be copied from the script variables and will replace the equivalent program fields.

The fields are divided into groups based on the likelihood of usage within a script. 

More details on each of the fields can be found here.

Run Script Notification

  • E-mail format
    The Run Script report can be generated and sent in either HTML or plain-text format.
    Send Run Script Notification Report by e-mail:
    If selected, an e-mail containing the Run Script report will be sent to the e-mail address specified in the "Recipient(s)" field.

  • Recipient(s)
    Comma or semi-colon delimited list of e-mail addresses, which are to receive copies of the Run Script report.

  • Send Run Script Notification Report to disk
    If selected, a file containing the Run Script report will be sent to disk using the file name and path specified.

 Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified