This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
In a hosting environment where Microsoft Exchange Server 2003 computers are configured as offline address list servers, you may find that CPU usage by the Microsoft Exchange System Attendant service (Mad.exe) on each of the servers increases to 50 percent. You experience these symptoms even after you restart each server.
For example, you may experience these symptoms in a hosting environment where you have 10,000 offline address lists and 10 Exchange Server 2003 computers that are configured as offline address list servers.
This problem occurs in hosting environments where Exchange Server 2003 computers are configured as dedicated offline address list servers. This problem occurs in this type of hosting environment when the update schedule for offline address lists is set to Never run. The Microsoft Exchange System Attendant service uses an OABScan task to scan offline address lists that are generated on the server. This task is scheduled to run every 13 minutes and may increase CPU usage in the Microsoft Exchange System Attendant service to 50 percent. In a hosting environment that has this configuration, the OABScan task is not required.
Service pack information
To resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest updates and service packs for Exchange Server 2003
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. Component: Exchange System Attendant
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Date Time Version Size File name ------------------------------------------------------ 20-Dec-2003 04:35 6.5.6980.58 8,765,440 Mad.exe
Note Because of file dependencies, this hotfix requires Exchange Server 2003.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Exchange Server 2003 Service Pack 1.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
After you apply the hotfix that is described in this article, you must edit the registry to activate the hotfix and to turn off the OABScan task.