The nas has the "preprocessor" function that allows you to manipulate the content of alarms before they are stored. That is the place to put code to fix the message on the fly.
Otherwise the suggestion would be to create a package (need IM for that - neither MSC or admin consiole can do that still) with a cfx file that looks like:
<messages> overwrite
<WrongState> edit
text = This is the new message for Service in wrong state - $profile_name (Expected: $expected_state, found: $state)
</WrongState>
</messages>
and then deploy that to the 100 systems. This file will only change the text of the message WrongState if it exists.
What we do when a changed message is desired is to put the preprocessing script in place which effectively changes everything in an instant, then go and update the individual probes with the package method (there's also a call back to the controller to set a single field value) and then when all are updated, remove the preprocessing code.
Original Message:
Sent: 04-28-2020 03:28 AM
From: Murat Gokoz
Subject: Changing alarm message
Hi ;
I am new to Dx Infrastructure manager, I wanted to change alarm messages on ntservices probe, There are 100 servers that I need to change messages is there any way to do it without changing alarm messages in each probe? I configured alarms from Admin console. Which way is the best practice to create windows service alarms msc or admin console?
Regards