If you use Powershell Monitoring Community Management Pack like me, maybe you had this issue:
It happened to me recently, creating a task, and I struggled a while to find the culprit, but in the end, here is it:
It’s the variable called $database. For some strange reason, maybe connected to the content of the destination MP, SCOM does not like the name. Once I renamed this variable as $DB everything went fine.
Well, another mistery resolved !
You are welcome :)
Commentaires