ActiveXperts Network Monitor ships with a powerful set of pre-defined checks. Each individual check has a static number of configuration items. To monitor other items, or to combine monitoring items, you can make use of custom PowerShell checks.
Most of the built-in checks have a PowerShell equivalent, implemented as a PowerShell (.ps1) script file. Out-of-the-box, each PowerShell script monitors the same items as the built-in check. Feel free to modify the script.
To add a new PowerShell-based File Exists monitoring check, do the following:
- On the 'Monitor menu', open 'New Monitoring Check (Script)' and choose 'New PowerShell Check'. The 'PowerShell Check' dialog box appears;
- In the 'Script File' selection box, select 'File-CheckFileExists.ps1';
- In the 'Script Parameters'group box enter the required parameters. You can also load a working sample first by clicking on the 'Click here to load a sample' link.
To customize the above monitoring check, click on the 'Edit button' next to the 'Script File' selection box. Notepad will be launched. You can now make changes to the PowerShell script.

File-CheckFileExists.ps1 script source code
################################################################################# # ActiveXperts Network Monitor PowerShell script, (c) ActiveXperts Software B.V. # For more information about ActiveXperts Network Monitor, visit the ActiveXperts # Network Monitor web site at https://www.activexperts.com ################################################################################# # Script # FileExists.ps1 # Description: # Checks if the specified file exists # Parameters: # 1) strComputer (string) - Hostname or IP address of the computer you want to monitor # 2) strFileName - Path to the file to check # 3) strAltCredentials (string, optional) - Alternate credentials # Usage: # .\FileExists.ps1 '<computer>' '<file>' '<alt-credentials> | <>' # Sample: # .\FileExists.ps1 'localhost' 'C:\boot.ini' ################################################################################# # Parameters param ( [string]$strComputer, [string]$strFileName, [string]$strAltCredentials ) cls # Check paramters input if( [string]$strComputer -eq "" -or [string]$strFileName -eq "" ) { echo "UNCERTAIN: Invalid number of parameters - Usage: .\FileExists.ps1 <computer> <file> [alt-credentials]" exit } # Create object if( [string]$strAltCredentials -eq "" ) { $objPath = Get-WmiObject -ComputerName $strComputer -Class Win32_OperatingSystem $exists = Test-Path $strFileName } else { $objNmCredentials = new-object -comobject ActiveXperts.NMServerCredentials $strLogin = $objNmCredentials.GetLogin( $strAltCredentials ) $strPassword = $objNmCredentials.GetPassword( $strAltCredentials ) $strPasswordSecure =ConvertTo-SecureString -string $strPassword -AsPlainText -Force $objCredentials = new-object -typename System.Management.Automation.PSCredential $strLogin, $strPasswordSecure $objPath = Get-WmiObject -ComputerName $strComputer -Class Win32_OperatingSystem -Credential $objCredentials //<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< $exists = Test-Path $strFileName -Credential $objPath } ################################################################################# # THE SCRIPT ITSELF ################################################################################# if( $objPath -eq $null ) { $res = "UNCERTAIN: Unable to connect. Please make sure that PowerShell and WMI are both installed on the monitered system. Also check your credentials" echo $res exit } # Checks for the file existance if(!($exists)) { $res = "ERROR: File " + $strFileName + " does not exist DATA: 0" echo $res } else { $res = "SUCCESS: File " + $strFileName + " exists DATA: 1" echo $res }