This script comes from the Hyper-V MP.
But when I took a deeper look at it, this Alert occurred only on the Hyper-V cluster nodes which did not host any VM at that moment. The other Hyper-V cluster nodes, hosting multiple VMs, did not experience this issue. Somehow this script flunks when it runs on ‘empty’ Hyper-V cluster nodes.
So this particular Alert can be safely ignored. Hopefully the future edition of the Hyper-V MP will contain a script which is a bit ‘smarter’.
1 comment:
Spot on! We had a similar problem in a Management pack and it was invoking Left on an empty string! Thank you.
Post a Comment