Een van de meest voorkomende e-mailservers is het Nederlandse bedrijfsleven is toch wel Microsoft Exchange. Om een Exchange server optimaal in te stellen heeft Microsoft een verzameling van de zogenaamde Best Practices in het leven geroepen. Deze zijn overal na te lezen en worden ook in trainingen gebruikt. Om het voor de beheerders een stapje makkelijker te maken hebben ze ook een handig programma ontwikkeld om een Exchange server te analyseren, door te kijken naar de huidige instellingen en de prestaties. Aan de hand van deze uitkomsten worden tips gegeven om de eventuele knelpunten op te lossen en de algemene prestaties te verbeteren. De ontwikkelaars hebben Microsoft Exchange Server Best Practices Analyzer Tool 2.6 uitgebracht met de volgende opmerking:
A few hours ago we released ExBPA v2.6 (U.S. English) and ExPTA v1.1 (U.S. English) to the microsoft.com download center. We're very excited about the new features and improvements made in each tool. The final build numbers are as follows:
ExBPAIt's going to take a few hours for all download servers to see the changes, so if you don't see the new versions, try again in a few hours. We'll let the new versions settle for a few days, then at the weekend, we'll flip the bit which will cause all older versions to prompt for upgrade.
- Application version: 2.6.7812.0
- Configuration version: 22.214.171.124
- Application version: 1.1.7812.0
- Configuration version: 126.96.36.199
Here are the major differences and improvements that we have made since ExBPA v2.5:
I want to thank everyone on this newsgroup for making these tools such a success! I also want to thank the dev team here for all their tireless work.. Jon Avner, Jack Bennetto, Kevin Chase, Nicole Allen, Weiguo Zhang, Haruya Shida and Soumya Singhi.
- Tabbed reporting interface instead of a drop-down control. Viewing reports is now much more intuitive with this cool reporting structure.
- Scan types are presented through radio buttons, so the different scan types available are much more obvious.
- Group by "Issue" option when viewing list reports. For example, if you find that multiple servers are showing the same Error, you can now easily display a list of all servers affected rather than having to manually go through the entire list of items.
- An ExBPA shell extension which allows you to right-click on an XML in Explorer (or apps like WinZip) and "View with Exchange Server Best Practices Analyzer".
- ExBPA now works through proxy servers that require authentication.
- New 'Permission Structure Check' scan type. This iterates through both the domain naming context and Exchange section of the configuration naming context and will notify you if inheritance has been blocked at any level. In addition, ExBPA will also check for inheritance blocks in the configuration naming context during a regular 'Health Check'.
- Better reporting of cluster resources and groups. In the detailed view, you will now see a great hierarchical display of:
We have also implemented dependency checks. For example, if the System attendant is not dependent on every physical disk resource in the same resource group, a warning will be displayed.
- Cluster resource groups with current owner
- Cluster resources and properties
- Dependent resources
- Antecedent resources
- Possible owners
- Very latest rule set, including all the updates made to v2.5, which include the IIS metabase / transport event sink checks. In addition, we have introduced some new rules including:
- If you look in the "Information Items" report, the very first info rule details the version of ExBPA that was used to capture and analyze the data.
- A new object processor that uses DsGetSiteName to ascertain the AD site membership of the Exchange server and all DC/GCs in the DSAccess topology.
- Certificate checking. For every SMTP domain defined, we attempt to obtain the SSL cert. If we find it, we'll check that the principal matches the host name and if the cert is close to expiry (or has already expired).
- For connectivity errors, ExBPA now displays the underlying exception (e.g. Access Denied) in the Error rule itself. You no longer need to manually go through the Run Time log to see the actual error string.
- All XML files are digitally signed to improve security and prevent tampering/spoofing. On startup, ExBPA will check that a valid signature (and Microsoft certificate) is on each XML. If the XML has been modified, a popup error will be seen and ExBPA will refuse to run.
If you have feedback or comments, feel free to use the newsgroup, or send directly to email@example.com
Exchange Server Best Practices Analyzer