Removing Corrupt Server Side Rules

I followed this procedure to remove corrupted server side rules that were preventing "Out of Office" automated replies from sending to internal recipients:

1. Find mdbvu32.exe in the \support\utils\i386 directory on the base Exchange 2000 cd.
2. Run mdbvu32.exe.
3. Click OK to clear the first window that pops up.
4. Make sure that your profile is selected in the Choose Profile window and click OK.
5. Click on the MDB menu option.
6. Click on the OpenMessageStore option.
7. Make sure that "Mailbox- [user's full name]" is selected and click on Open.
8. Click on the MDB menu option again.
9. Click Open Root Folder.
10. In the Child Folders box - double click on "Top of Information Store".
11. In the next Child Folders box - double click on "Inbox".
12. Look in the Associated Messages in Fld box. All of your rules are in this box.
13. Once you find the rule that you want to delete then close the properties for that rule.
14. On the MAPI_FOLDER page make sure that the rule that you want to delete is still highlighted.
15. In the "Operations available (select operation, then push Call Function button)" text box, push the drop down button to reveal the list of functions.
16. Scroll down the list of functions until you see "lpFld -> deleteMessages() (ON SELECTED MSGS)" and then click on it to select it.
17. Next press the Call Function button. This will delete the rule that you selected.
18. Press the Close button to exit the MAPI_FOLDER window.
19. Press Close again to exit the next window.
20. Press Close again to exit the last window.
21. Click on the MDB menu option.
22. Click Store Logoff. Then click OK and OK again.
23. Click Session and then click on Exit.

The 12 Commandments of Exchange Deployments

Brien Posey has written another good article over at SearchExchange.com, this one is covering The 12 Commandments of Exchange Deployments

"Rolling out an Exchange Server deployment can be a complicated task. Need some help? I have put together my list of 12 commandments to follow when you find yourself heading an Exchange 2000 or 2003 deployment"

Q Article 284204

If you're having a problem trying to track down an error code for an NDR, do a quick Google search for Q article 284204. This Microsoft technical article lists a number of codes, their possible cause, and troubleshooting options.

Quest Software - Quest MessageStats

Quest has just released the latest update to their Microsoft Exchange reporting product. Last fall I evaluated a number of these products and found the Quest application to be the most feature rich. More info can be found at:

http://wm.quest.com/products/messagestats/

Microsoft Lookout v1.2

An addin to Outlook to quickly search all of your e-mail, contacts, calendar, and filesystem.

Overview
Lookout is lightning-fast search for your e-mail, files, and desktop integrated with Microsoft Outlook™. Built on top of a powerful search engine, Lookout is the only personal search engine that can search all of your e-mail from directly within Outlook - in seconds...

You can use Lookout to search:
* E-mail messages
* Contacts, calendar, notes, tasks, etc.
* Data from exchange, POP, IMAP, PST files, Public Folders
* Files on your computer or other computers

Just enter your search and press enter. Results are instant. Lookout will find your search terms hiding nearly anywhere in your Outlook mailbox - subjects, bodies, phone numbers, addresses, etc.

System Requirements
* Supported Operating Systems: Windows 2000, Windows Server 2003, Windows XP

* Microsoft Outlook 2000, Outlook XP, or Outlook 2003 must be installed on your computer.

* Microsoft .NET Framework 1.1

Click this link for additional information and to download the addin:

http://www.microsoft.com/downloads/details.aspx?FamilyID=09b835ee-16e5-4961-91b8-2200ba31ea37&displaylang=en

Priv.edb File Size Tracking Through Perl

I've updated the Disk Space Utilization Perl script to add a column which displays file size information for your Exchange private information store. This is nice to use to compare with the disk free space on the server to determine if you're going to have a potential issue if you need to do offline Exchange maintenance. Here is the main subroutine I've added:

# Figuring out the file size for the priv1.edb file
$filename="\\\\@Drivearray[0]\\@Drivearray[2]\\Program Files\\Exchansrvr\\MDBDATA\\priv1.edb";
$edb=0;
$edb=(stat($filename))[7];
$edb1=$edb / 1023741824;
$edb1=sprintf("%5.2f/n", "$edb1");

The full script with the modifications for the edb addition can be downloaded at:

http://webpages.charter.net/mhenderson1/Blogs/PerlDriveSpace.pl

Current constraints in the subroutine limit the tracking of only one .edb file per Exchange server. I may change this in the future if we move to a multiple store standard.

Microsoft Exchange Server Best Practices Analyzer Tool

Here is the link to the recently released Microsoft Exchange Best Practices Analyzer tool. It's a good test to see how your currently installed configuration is performing compared to what Microsoft recommends...

http://www.microsoft.com/exchange/downloads/2003/ExBPA/default.asp