Follow me on Twitter...
Have a look at a my blogs on 'You Had Me At EHLO...' Protecting Exchange Data with DPM, CCR Decision Making Flowcharts, SCR Decision Making Flowcharts, On email archiving. ...and a few more here High item counts - what do you do about it?, Archive v Big Mailboxes, Getting your Exchange 2007 Project Approved, (and the follow up 7 blogs), Recovery Scenarios Part 1, Recovery Scenarios Part 2, Recovery Scenarios Part 3, How quick will DPM backup?, Synchronous or Asynchronous Replication?, Why not stretch CCR?, Backup solutions for Exchange 2007..., Do we actually need to backup Exchange?, SAN v DAS.
...and a few more here High item counts - what do you do about it?, Archive v Big Mailboxes, Getting your Exchange 2007 Project Approved, (and the follow up 7 blogs), Recovery Scenarios Part 1, Recovery Scenarios Part 2, Recovery Scenarios Part 3, How quick will DPM backup?, Synchronous or Asynchronous Replication?, Why not stretch CCR?, Backup solutions for Exchange 2007..., Do we actually need to backup Exchange?, SAN v DAS.
There are of lot of different parts to this topic. A lot of this will be covered in the Operations Section and should include the following:
There might also be potential security risks identified by ExBPA. The following are a few of many rules related to security:
I would also run MBSA for this section of the health check. Install MBSA on your workstation and run it against each Exchange Server in turn. Each time you run the tool against a computer a new scan report is created for you to review at a later data. The reports will be located in a 'SecurityScans' directory on your workstation. You should see a report similar to the following for each server: (This is just the top part from a sample MBSA report and shows one of the most obvious reasons for running MBSA - that is to determine the security update status for the server.)
When you click on the 'Result Details' the tool will display which updates you are missing.
It is also important that review all the information that MBSA is reporting on. For example in 'Administrative Vulnerabilities' the tool determines if there are any local user accounts on the computer with non-expiring passwords or that have blank or simple passwords.
Ideally in the Operations section of the health check you will have identified whether you have a good solid procedure in place to report on the security update status of your Exchange Servers and install updates as appropriate. If you don't then use MBSA manually until you do. For the purposes of this health check run MBSA against each server, list all missing updates, and other security vulnerabilities that MBSA highlights.
..'Run your own Exchange Server Health Check.... Part 4 - Server Performance' to follow soon...
PingBack from http://joshmaher.wordpress.com/2007/06/13/exchange-2007-health-checks/
Exchange auditing is a good security practice as well.
From my personal experience I can recommend a tool called change auditor for exchange.
The tool can report and alert on all critical changes to exchange environment like, for example, mailbox policies, administrative groups, distribution list changes, track user and administrator activity for user account and delivery restriction changes.
http://www.changeauditorforexchange.com