Monitor Windows Mount points for Exchange Servers

Document ID : KB000103990
Last Modified Date : 02/07/2018
Show Technical Document Details
Issue:
The "cdm" probe and "dirscan" probe do not monitor Exchange Mount Points.  
They cannot see them.  These drives do not have Mount Points and do not have Drive letters.
For example:
UIM and Windows Mount Points
Environment:
UIM 8.5.1 
logmon 3.,92
Cause:
The "cdm" and "dirscan" probes cannot see these mount points.
The "Logmon" probe can be used to launch a PowerShell script to check the free space.
Resolution:
1- Create a Powershell script in the robot directory of the Exchange Server(s):
    under "C:\Progra~2\Nimsoft\" called "MountPoint.ps1"

2- Add these contents:
$servers = (Get-Content "C:\Progra~2\Nimsoft\servers.txt")
# Check each server
foreach ($server in $servers)
{
     # First check if the server is up
    if ((Test-Connection -quiet $server) -eq $true) {
         # Get all the volumes on the server with out a drive letter
        $volumes = Get-WmiObject -computer $server win32_volume | Where-object {$_.DriveLetter -eq $null}
         # Check each volume found
        foreach ($volume in $volumes) {
             # Skip the System Reserved volume. It will always be low
            if ($volume.Label -ne "System Reserved") {
                 # Do some math to convert bytes into GB, rounded and 2 decimal places
                if (([math]::round(($volume.FreeSpace / 1073741824),2)) -le $lowSpace) {
                     # write output including low disk space setting, server fqdn and volume name
                    Write-Output "Low disk space warning (below $($lowSpace)GB) - $($server) - $($volume.Label)"
                    }
                }
            }
        }
3- Create a "servers.txt" file in the same folder.
    This should contain a list of FQDN of Exchange servers for the servers you want to monitor.
     For example: 
        server1-exchange.company.com
        server2-exchange.company.com
        server3-exchange.company.com
        server4-exchange.company.com

4- Run the script to make sure it works
User-added image
4- Download and deploy the logmon probe to this robot.

5- This example is using the Infrastructure Manager client, it is fine to also use the web adminconsole.
     Create a new profile.
    General Tab:
User-added image
6- Add a Watcher Rule
User-added image
7- This should product alarms similar to the following:
User-added image
Additional Information:
Please note that the Powershell script will run with the same account that the "Nimsoft Robot Watcher Service" is running as on that robot.