Well, if IBM's PC image is anything like it was in the early 2000's probably > 50% of their PC issues are self inflicted by the IT people who built the image. From buggy unsigned drivers, to crapware for security/etc, I stabilized my machine by uninstalling a bunch of things that should never have been in the standard image. If you compare the PC vs MAC images at the last couple companies I worked at, you will find t…
> Well, if IBM's PC image is anything like it was in the early 2000's probably > 50% of their PC issues are self inflicted by the IT people who built the image. I'd argue that most issues people have with Windows PC fall in the category of 'self inflicted', but the point is, is that this is much harder to do on a Mac (apparently). I never heard someone building an image for a mac for example.
This happens where I work. Amongst other things it:
1) Set the hostname of the machine. 2) At one point, changed the timezone to one of the US offices (I work in Europe). 3) Prohibited upgrades to newer versions of OS X until they were approved by the IT staff. 4) Forced reboots for installation of security updates (happened to everyone in the office at the same time, with a few minutes warning and no option to cancel).
and some other annoyances. I needed at one stage to reinstall OS X (my fault, as opposed to something wrong with OS X), and this got rid of the issue.
I was informed by a colleague that if you reinstalled OS X while connected to the corporate network, that it would install OS X from the company's IT servers instead of Apple's ones, thus pulling down the corporate image. I can't 100% verify that claim, but it sounds true what I have seen when people reformatted in the office.