Earlier quoted context omitted.
This guy was literally running SETI@Home on the production billing cluster servers for a multi billion $ telco, and would not stop doing so. He didn't even work directly for the Telco, but for a consulting place (Accen...). Think of the liability factor for that, when there was a production outage on the cluster. Try proving the software (maxing out cpu, screwing up instruction cache + context switching, etc) wasn't…
Your employee’s lack of discipline and/or proper systems job control is the root issue here. Trying to associate it with seti is unfortunate.
It just seems the SETI@Home (and other BIONC) projects seemed to attract people that do that kind of thing. Haven't seen it with anything else before, though I'd kind of expect cryptocurrency miners would have been similar. ;)