Next up in my mini-series detailing my initial impressions with Lion is the PIM suite: Mail, iCal, and Address Book. (Be sure to read parts I, III, and IV of the series.) I won’t say I’m a heavy email or calendar user (I’m not a manager or anything… ;-)), but I am an email admin, and a persnickety one at that. I expect my mail and calendaring applications to behave in a certain way, and when they don’t, my feathers get ruffled and I get annoyed. Continue reading for a (probably too lengthy) list of pros and cons about Lion’s PIM suite.

Institutions of higher education seem to attract quite a bit of attention in the way of email phishing attacks.  I’m  fairly sure other types of institutions get with with phishing attacks as well, but since I work for a university, that’s the pool I happen to play in and the one I know best.

Sometimes I just have to wonder.

It seems that the Microsoft Exchange Team thought that you’d always want one Exchange Server 2007 CCR node to be the active, “primary” node, and the other node would always be the passive, “secondary” node. This isn’t exactly a problem, per se, except that there may be times when you want (or need) to make the “secondary” node the active one for an extended period of time. Still, not a problem, right? Sure…except when the System Attendant goes to regenerate the offline address book(s). At that point, you’ll get a nasty warning in the Application event log, EventID 9395: “OALGen is running on the wrong CCR cluster node”.