2026.3 HF1 Release Notes

Veeam 13 Automatic Service Discovery

Summary: N-central now detects and automatically onboards Veeam Backup & Replication 13 installations.

Issue: Previously, devices running Veeam 13 were not recognized by the service template discovery process, preventing Veeam monitoring services from being deployed automatically. Partners had to manually configure monitoring after installing Veeam 13.

Fix: The N-central Agent has been updated to recognize Veeam 13 and automatically deploy the appropriate Veeam monitoring service templates, restoring the expected onboarding experience.

Updated Built-in Veeam Monitoring Services for Veeam 13

Summary: Updated the following built-in Veeam monitoring services to support Veeam Backup & Replication 13:

• Veeam Failed Jobs 

• Veeam Job Monitor 

• Veeam Sure Job Monitor 

Issue: Veeam 13 requires PowerShell 7 (pwsh) for its PowerShell modules. The existing monitoring services used Windows PowerShell, preventing them from collecting monitoring data correctly in Veeam 13 environments.

Fix: The Automation Manager policies have been updated to execute using PowerShell 7, ensuring the built-in monitoring services function correctly with Veeam 13 while remaining compatible with earlier supported Veeam versions.

AMP Monitoring: Resolved Invalid Script Format Errors

Summary: Resolved an issue that could cause custom Automation Manager Policy (AMP) monitoring services to report a 201: Invalid Script Format error, even when the underlying scripts were valid.

Issue: In certain environments, an invalid Automation Manager token registry state could cause AMP to incorrectly interpret valid monitoring scripts as invalid, resulting in monitoring failures across affected devices.

Fix: This update corrects the Automation Manager token registry handling to prevent invalid registry states from impacting script execution. AMP monitoring services now process valid scripts correctly, eliminating these erroneous validation failures.