Today Microsoft released version 8.03.0056 of the Microsoft Exchange Server Profile Analyzer (EPA). You can use EPA to collect (statistical) information from Exchange mailbox stores or an Exchange organization. For instance, you can collection information on user activity and profile statistics for sets of subsets of the mailbox population, which can be used as input when dimensioning (upgraded) Exchange infrastructure using the Exchange Mailbox Role Calculator (being more specific than the default Light, Average, Heavy and Very Heavy user profiles). The analysis of mailbox servers or organization can also provide input for processes like capacity planning.
Usage of EPA is straightforward, check out this older article on how to use EPA here.
You can download the 32-bit version here or the 64-bit version here.
Today Microsoft released the (take a deep breath) Microsoft Forefront Protection 2010 for Exchange Server Best Practices Analyzer (v11.0), or FPE 2010 BPA for short. The FPE 2010 BPA examines servers running ForeFront Protection 2010 for Exchange Server and checks the system configuration as well as the product configuration. Any settings or combination of settings that do not conform to FPE 2010 best practices are reported, enabling administrators to easily identify and address possible issues.
I assume everbody knows how these BPAs work, but in case you don’t proceed as follows:
- Download the FPE 2010 BPA from this location;
- Install the ForeFront Server Protection Best Practices Analyzer (FPBPA) on a server containing ForeFront Security 2010 for Exchange Server;
- Use the default settings and have FPBPA retrieve updates from the internet when required;
- Start FPBPA. It will check for online updates;
- Click Select options for a new scan;
- Enter a scan label, i.e. Initial FPBPA Scan, and click Start Scanning. FPBPA will now scan your ForeFront environment;
- When Scanning Completed click View a report of this Best Practices scan.
As you can see from the first issue, I still need to install the RTM 🙂 The second issue is about a non-configured critical error notification, i.e. it has no no e-mail recipient specified. The other two issues are about possible misconfiguration of the number of scan processes (as FPE 2010 BPA states, the recommended setting is twice the number of CPUs here).