I run an exchange server in my office. I tried to get it up and running on my own, using a sybex Exchange 2000 MCSE book. I got close, very close to setting it up correctly. I could get the web access to send and receive just fine. All users could receive just fine, and could send to domains outside of our own ok, but we couldn't send anything internally to our own domain. I dinked around with that thing for about 48 hours and still couldn't finger out what was wrong with it.
I conceded and called in an exchange consultant to help me out. We wiped out the 2k install, restalled 2k server, set up active directory, and reinstalled exchange. In about 3 hours I had a fully functional exchange server.
It's great. I'd have a mutiny on my hands if I went back to using pop mail accounts now. I've got my users using the calendar, scheduling, and tasks collaborations on a daily basis. I've been told that it's one of the best things they've ever used - the calendar feature in particular.
I've got trend micro scan mail antivirus scanner on there scanning all incoming and out going messages for viruses. It checks for updates every 2 hours and I have been virtually virus free since implementing it.
I also took the risk and implemented outlook web access. It's been invaluable for my traveling users. They can log on from remote locations and have access to all of their folders and the company calendar to update their office hours on the fly. Very cool stuff.
As far as babysitting it. Don't really have to do anything short of jockeying tapes and checking the virus logs every now and then. It's been pretty stable. *knocks on desk*.
Well, well, well worth the investment.