Software Update protocol: 3 parts surgery, 8 parts voodoo

My usual routine -- somewhat complicated, I know -- goes like this. First, I see some mention somewhere that an update was just released moments ago. I run Software Update. Then, I tell it to update. Then, if it makes me reboot, I do. This rather involved procedure has worked flawlessly for me since 10.0.4.

I'm the point person for my organization--I install the upgrades as soon as they're available, which I've been doing since Mac OS X 10.0.4. I agree with having a current backup just incase and running repair permissions after installs, particularly if several updates are being installed at once. Probably the most important issue for successful updates is not installing applications that make low-level changes to the operating system. -- Al

At my office (all Macs, well over 400 machines) everyone does their own updates. There are generally a few issues, easily resolved by archive/install and a new update. People stagger updates so everyone doesn't update at once. 10.2.8 rev 1 was a different matter

Yes. Jesus, this is all massssively overwrought. Rebooting? Logging out? Killing extensions? Font caches? Sod all that. The only useful advice either of them have is to wait a day, and that's only because Apple are mokes. 1. Wait a day or two. 2. Open Software Update 3. Click update. 4. Carry on as usual. 5. If *forced*, reboot. I've taken this here mac from 9.1 to 10.3.7 that way, upgrading all the time even on new major releases. Hell, my iTunes burning pane still shows the name of a USB CD Burner I used under OS 9. It's supposed to be that way: this isn't Windows. They'll be talking about editing the registry next, these guys.