This fix took care of the issue for a while in our environment, but it has since returned. I hoped that maybe the alarm setting somehow got set back to it's default, but when I checked, it was still in effect. I restarted the service again and even rebooted the vCenter appliance and it's still happening at both our disaster recovery and production sites.
Has anybody else implemented this fix and had the problem return later?\
