Yesterday we released a major new update to the ExBPA Config XML - this is version 184.108.40.206. We wanted to give you some information on the enhancements made between this and the previous version that we published (220.127.116.11).
#1 - Detection of servers that exhibit kernel memory problems because of hot-add memory pre-allocation. This is one of the most important reasons why you'll want to update to this new version. If you have come across Exchange servers hitting paged pool issues, then you most definitely want to run this new version against the server. There are a number of servers on the market that have hot-add memory enabled by default (this includes various server models from HP, Dell and Unisys). This causes Windows 2003 to pre-allocate kernel resources 'just in case' that memory is added after initial boot. The net effect is a much lower ceiling for max paged pool (in many cases, you'll see an 80 MB loss), which can result in system instability on scale-up Exchange servers. ExBPA will identify servers that have this problem and tell you how to resolve it. The good news is that in the vast majority of cases, the resolution is to add a single reg key and reboot. The associated web article that provides more information on this subject is http://www.microsoft.com/technet/prodtechnol/exchange/Analyzer/2b0d4c6e-92b7-410b-876b-367c4043b1c7.mspx. In addition, we've reconditioned many of our kernel memory rules to provide enhanced detection of resource shortage scenarios.
#2 - Enhanced support for Exchange 2003 SP2. Including, a) organization-wide PF replication stop b) flat restriction best practices c) detection of OAB Version 4 d) detection of max database size reg key e) IMF custom response implementation f) check supported configuration boundaries when running under Virtual Server g) Advise on the upgrade of Exchange 2003 SP2 for servers and ADC servers h) MTA disable support i) Verifies that the server is running the final build and not the CTP version that was released on the web.
#3 - HP storage enhancements. Detects whether the very latest version of SecurePath is running. Also advises on the installation of the free-of-charge EVAPerf tool (adds more storage perfmon counters) if the SAN is an EVA.
#4 - Updated firmware checks. Enhanced support for checking out-of-date BIOS' on HP and Dell servers.
#5 - Checks for a plethora of manual registry overrides. Includes a) MaxClientRequestBuffer b) RPC Ports c) MinUserDc d) Lookup Sid Cache Expire e) Lookup Sid Cache Limit
#6 - Exchange server naming consistency checks. Verifies that the FQDN in ncacn_ip_tcp is the same as the resolved name in DNS. Also checks to see if the server name has been manually adjusted in the registry. The tool warns if the DHCP Client service is not running (causes dynamic DNS update failures). Finally, support has been added for pure Exchange 2000 IM installations where the networkAddress property is not populated.
#7 - Warn if GCs aren't responding on port 3268. Good for older Windows 2000 GCs that require a reboot after promotion and other GCs that are 'deaf'.
#8 - Front end services. Checks to see if the RUS and/or OAB generation is configured to run on a front-end server.
#9 - System folder replica check. Identifies system folders (e.g. OAB, Schedule+ Free/Busy) that have a single replica and could be a single point of failure in an organization containing multiple servers with Public Folder stores.
#10 - MTA routing check. Verifies that X.400 addresses in recipient policies are formatted correctly. For example, an address that doesn't have a trailing semi-colon can cause routing failures.
#11 - Storage quota checks. Warns if storage quotas aren't in place. Also warns if receive limit and send/receive limit are within 20% of each other.
#12 - RUS/Domain associations. Warns if a domain has been DomainPrep'd, but an associated RUS does not exist.
#13 - ACL upgrade failures. Warns if excessive ACL upgrade failures are occurring.
#14 - Front-end/Back-end version comparison. Warns if the wmtemplates.dll file is newer on back-end servers. This is a good indication that a back-end server has received an OWA hotfix that hasn't been applied to a front-end.
#15 - Alockout detection. Detects servers that have Account Lookout Management tools installed.
#16 - Exchmem.dll hell. Checks to see if exchmem.dll is hanging around in the \windows\system32 folder. Throws an error if it's older than the version in \exchsrvr\bin.
#17 - VMWare rule. Revised supportability wording.
#18 - Transaction log generation. Implemented an Error threshold (1,020,000) so it's more obvious if the server is reaching a critical point and is in danger of running out of log numbers (the warning fires at 950,000).
#19 - Journaling recipient configuration. Verifies a number of different aspects, ensuring that the journaling recipient a) has not been deleted b) is hidden in the GAL c) is not on the same server as the MDB being journaled d) is properly mail or mailbox-enabled e) is not a disabled account (and msExchMasterAccountSid is not set).
#20 - AD Sites and subnets. Collects more information on site and site link configuration.
#21 - McAfee GroupShield updates. Verifies that the very latest patches for GroupShield 6.0 are installed.
#22 - Connectivity test update. Increased max allowable time from 1 minute to 5 minutes per server. This will prevent premature timeouts on slow connections.
We'd like to thank everyone out there that has made a suggestion to enhance the functionality provided by ExBPA. We've still got many checks waiting to be added, but I hope the improvements made in this release help you troubleshoot those 'needle in a hay stack' problems.
As always, to get ExBPA, go to www.exbpa.com !
- The Microsoft Exchange Operational Support Tools Team