I've constructed a script for my office which needs to be run by every office computer. It works very well for everyone, but one, my manager (of course). The issue (without getting too technical) is that he has deep seeded corruption in his computer. This interferes with how my script runs, and breaks it. (If you want to read more, look here)
The problem isn't that his computer is broken, the problem is that he refuses to accept that it is. I can understand why he's hesitant to call our IT department; our computers are very tightly controlled which is frustrating for those of us who actually know what we're doing. He's worried that if he calls IT, he'll be put back in the "baby pen".
Now, (thanks to the help of Super User) I think I can fix his machine without calling IT, but he won't let me "because it isn't broken".
My question to you, how do I convince him to let me fix the problem (or at the very least diagnose it better).
Some Extra Info:
- We're engineers and a fairly literate in higher level computer use (though neither of us are computer engineers.
- He must be able to run the script on his computer.
- The script cannot be changed to avoid the issue (and even if it could, it would be a huge hassle).
In Response to Roger's Comment
The purpose of the script is to track and record "conditions adverse to quality" (essentially whenever someone breaks procedure. We are required to have a program in place to do this by federal law. The previous system was terrible, and my boss approached me asking if I could update it, my script is that update.
I'm attempting to fix his computer (perform an IT function) to avoid the risk of calling IT and having them revoke his admin privileges. So yes, I'm absolutely going beyond my core responsibilities.