I run an Exchange server with a similar employee count. I find it to be cost-effective, especially since we can get charity pricing on Exchange from Microsoft. If you have a virtualized environment, your actual hardware costs for running Exchange are much lower (or at least, are spread out across multiple servers). However, there are a lot of churches looking at using Google Apps as an alternative since it’s free for non-profits. There are certainly arguments for both. We’ve been running Exchange since long before Google Apps was an option.

You may find some useful information at the Church IT Roundtable Google Apps vs. Exchange discussion page. Another option is to use Google Apps in “dual delivery” mode so email goes both to Exchange and Google Apps; this can be used as a backup if your Exchange server is down (although depending on the setup, incoming email won’t work while Exchange is down since it’s pointed at your Exchange server), or you can have some users on Exchange and some using Google Apps. This of course requires you to license and set up/maintain Exchange as well so it’s not as much of a cost saver as it is a backup (business continuity/disaster recovery) strategy or nice setup for people who like the Gmail interface more than they like Exchange.

What are you using for email now? Once you get past the learning curve of Exchange 2010 (or 2007) or you have someone set it up for you, it really doesn’t require that much maintenance, especially if you put an antispam/antivirus filtering company (MXlogic, Postini, ExchangeDefender or Reflexion are all good examples) in front of them (note that I sell ExchangeDefender on the side and it can provide a web interface to your email when your server is down much like Google Apps can, in addition to the spam filtering–I like it a lot).

I am just having trouble seeing the benefits and how it can make some of my administration tasks easier or non-existent.

I’m the Program Manager in Exchange for the moderation feature (among others), and the author of the blog post cited.

Thanks for the heads up on the typos and confusion. As you know, PowerShell parameters tend to be verbose, and we wrestled with the best name for this one. We did have a couple of names for this before settling on BypassNestedModerationEnabled, and docs/blog post seem to reflect that churn.

I’ll make sure the original post is updated for accuracy, as well as the docs.

Thanks for the great post about this piece of moderation!

–ej

G’day!

Good to know is GeoTrust SSL certificates are compatible with Exchange server 2010. You can read more about GeoTrust SSL certificates at ClickSSL.com

GeopTrust ClikSSL Discount Coupon Code: CSGQ149