Product manual

Manual Writing your own monitoring functions |167
» Function name – Specify the function that GFI Network Server Monitor service will be
calling from the specified script file.
» VB Function Parameters – Double click on the line where the additional parameter values
required by this function are to be specified.
Parameters will be passed to the function according to their position in the list,
starting from 1.
Screenshot 161 - Add Parameters dialog
» Specify the parameter value and description. Parameter values can be extracted from
system variables (e.g. %USERNAME%) upon execution of the function or directly specified
as a string (e.g. “JasonM”)
Enclose string parameter values within quotes (e.g. “CPU0”).
You can make changes to the selected script by clicking on the „Edit script …‟ button.
14.4 WMI (Windows Management Instrumentation)
If you plan to write monitor functions based on WMI (Windows Management Instrumentation), be
sure you have WMI installed on the GFI Network Server Monitor server and on the target
computer/server that you want to monitor.
WMI is by default included as part of the Windows 2000/2003 operating system only. For NT4
systems download the file (for free) from the Microsoft website;
GFI has collected more than a hundred WMI samples. You can use these samples as a base for
new monitor functions that you write yourself. You can find them on the GFI website.
14.5 ADSI (Active Directory Service Interfaces)
GFI Network Server Monitor can check several Directory Services including Active Directory, and
NTDS (NT4 SAM database) directory services.
You can program GFI Network Server Monitor to check user accounts (locked out, disabled, etc.),
computer accounts, groups, group membership, organizational units, and so on.
If you plan to write monitor functions based on ADSI (Active Directory Service Interfaces), be
sure you have ADSI installed on the GFI Network Server Monitor server and on the server that you
want to monitor. ADSI allows you to access Windows 2000/2003 Active Directory, but also NT4
User information from the SAM database, and other User Databases. ADSI is part of the Windows