In parts 1 and two of this series, I covered the basics of how to start getting Exchange specific information easily out of the WMI classes specific to Exchange using PowerShell.

Do you ever dare to leave your home with doors open? Probably not! The same goes with our company network, if you do not have a properly configured firewall. Also, if you do not give any importance for security in your messaging infrastructure, the impact will be severe too. In other words, mail server will get exposed highly to the very bad “animals” such as Trojans & Viruses.

This product review reflects my own views on this product and as such reflect my opinion. While some GFI product documentation has been consulted for the sake of clarity, none of it has been reproduced for the sake of this review.

I'm going to start off with by referring to an Exchange 2000 article called Automating Exchange 2000 Management with Windows Script Host, since it set's the scene quite nicely for WMI based management for Exchange 2000. Exchange 2000 introduced a set of new WMI classes, and Exchange 2003 introduced a few more. PoweShell is renowned as an Exchange 2007 tool, however here were going to learn to use it to manage just about anything that has a MWI provider, with Exchange 2000/3 as my focus for today.

Most folks I talk to have installed Powershell, but not done much with it. Most of these folks also run Exchange 2000 or Exchange 2003 and don't dream of managing Exchange from anything else but the GUI or VBScript. Point in case, a lot of Exchange 2003 information is available via WMI. Powershell makes WMI information rapidly accessible via the Get-WMiObject, or it's alias gwmi. Aliases are a shortened version of a command and are interchangeable. Makes for quicker typing.

Fax is not going to vanish, but we can make the Fax machines disappear from our work place. Yes, I am talking about the Fax Server. In this article, I will give you an overview about an awesome Fax Server product – GFI FAXmaker for MS Exchange/SMTP.

Un-deleting Objects in AD isn't new anymore, however the ramifications of user deletions and un-deletions aren’t always well documented or understood. This is the second Article in the Exchange Server DR planning - Realizing the importance of backing up Active Directory series.In this article, I explore what is and more importantly what is not recovered when un-deleting a Mailbox Enabled Exchange User and how this method features as part of your Exchange and Active Directory Disaster Recovery Strategy.

Recovery Storage Groups (RSG) are one of the most administrator friendly features of Exchange Server 2003 SP1. You may have used them already, and you may have had the same questions I’ve been asked. This article aims to answer those questions.

Many organizations cluster their Exchange back-end servers in an effort to provide high availability. This article will cover two methods you can use to load balance your front-end servers in an effort to maximize performance and availability.

In this article, you will learn how to control object visibility…. Sound familiar? Yes, but with a twist. My previous article focused on limiting visibility of Exchange objects within Exchange System Manager only. This time objects visibility is influenced for the sake of data entry, i.e. limiting your choices in AD Users and Computers, or any other AD integrated administration tool.