Upcoming Change in Maintenance Information Collection Technique

Upcoming Change in Maintenance Information Collection Technique

As you are aware, our organization has always strived to enhance our maintenance processes to ensure the smooth functioning of our equipment and facilities. In line with our continuous improvement efforts, we have evaluated our current maintenance information collection technique and identified an opportunity to streamline and optimize the process.

Currently, DiIT is getting the preventive maintenance data using FTP or SFTP. The same for deploying the support environment and the new CAO server updates. 


Option 1:
Install the probe service on each CAO server.
Option 2 (preferred):
Using a dedicated system (Windows OS) to install the probe service.

Monitoring Solution

System Requirements for the Remote Probe

βœ… Operating System

  • Windows Server 2025, 2022, 2019, 2016; Windows 11/10

  • ❌ Not supported: Windows Server Core or Minimal Server Interface

βœ… Hardware

  • CPU: Dual-core or better

  • RAM: 2 GB minimum (add 1 GB per 1,000 sensors)

  • Disk: ~200 KB/day per sensor (temporary data only)

βœ… Software

  • .NET Framework: 4.7.2 or later (4.8 recommended)

🌐 2. Network & Firewall Requirements

πŸ”’ External Communication (Probe ↔ Core Server)

  • Destination: monitoring.diit.de

  • Port: 23560/TCP (outbound/inbound)

πŸ”„ Internal Monitoring (Probe β†’ Target Servers)

Protocol

Port(s)

Purpose

WMI (DCOM)

TCP 135 + dynamic ports (TCP 49152–65535 by default)

WMI queries

MySQL

TCP 3306

MySQL sensor queries

ICMP

N/A

Ping sensors (allow ICMP Echo Request/Reply)

SNMP (optional)

UDP 161, 162

SNMP sensors and traps

RPC

TCP 135 + dynamic ports

Required for some Windows sensors

HTTP/ HTTPS

TCP 80, 443

Web Service requests

 

 

 

πŸ” 3. Sensor-Specific Requirements

πŸ“Š WMI Monitoring

  • Requires a user account with administrative privileges

  • Needs DCOM and WMI namespace access (root\cimv2)

  • Firewall must allow:

    • TCP 135

    • Dynamic RPC ports (default: 49152–65535)

    • WMI-In rule enabled

πŸ›’οΈ MySQL Monitoring

  • Requires:

    • Port 3306 open between the probe and target (CAO servers)

πŸ‘€ 4. User Account for WMI

Permissions

  • Local or domain admin rights

  • DCOM and WMI namespace access

Password Policy

  • Prevent password expiration or change:

    • βœ… Password never expires

    • βœ… (Optional) User cannot change password


Data collection (approx. 5MB of data per day)

  • MySQL status

  • MySQL Replication status

  • CPU, Memory, hard disk status

  • CAO web application (status and http error messages)

  • Monitoring of CAO database backups

  • Monitoring of CAO-Services

  • Monitoring of CAO web applications


How the PRTG Remote Probe connects to the Core Server and the local servers



    • Related Articles

    • CAO Support Lifetime

      The world is spinning. Fast. But in your investment-driven industry, it partly turns a little slower. We know this, and it means that we have to make compromises to meet your demands for state-of-the-art software products and investment protection. ...
    • Resolving Incorrect CAO Instruction Manual Version After CAO Update

      Problem If you recently updated the CAO version of a CAO server, and the IM version isn’t displayed correctly in the top section, it’s likely because your web browser is caching outdated information. Solution The most effective and common fix is to ...
    • How to fix "api-ms-win-crt-runtime -l1-1-0.dll is missing" Error

      Causes Corrupted installation for Visual C++ Missing Windows updates Solutions Firstly check your window and your Window should be Updated. If Windows is updated and everything looks fine, try re-installing the particular program that is reverting ...
    • .NET Runtime Installation

      Effective with the release of CAO version 7.0, the application has transitioned from using the .NET 6.0 Framework to the .NET 8.0 Framework. The CAO 7.0 installation package does not include the required runtimes for .NET Framework 4.8 and .NET 8.0. ...
    • The version of this file is not compatible with the version of Windows your are running.

      Causes Missing Windows updates / patches Solutions Firstly check your window and your Window should be Updated. Verify the .NET information using the command (CLI) "dotnet --info" the .Net information. If you encounter an error, the CAO applications ...