Exchange object in Lost and Found container

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at]  

Topic Last Modified: 2006-12-01

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine whether any objects exist in the LostAndFoundConfig container under the Configuration container. If the Exchange Server Analyzer finds that objects exist in the LostAndFoundConfig container, an error is displayed together with the object and the object class from which the object derives.

The LostAndFoundConfig container holds objects that cannot be reconciled by Active Directory. Make sure that you delete any objects that are in the LostAndFoundConfig container, because Exchange will try to use these objects. For example, when Exchange queries Active Directory by object class (that is, Servers), all objects—regardless of whether they might be in the LostAndFoundConfig container—are returned as valid objects. The result is that Exchange may try to connect to the Server that is under the LostAndFoundConfig container instead of the real object. This could lead to unpredictable behavior by Exchange and even server failure. The presence of these objects may also prevent objects of the same class from being created.

To resolve this issue, you must remove the entries in the LostAndFoundConfig container from Active Directory by using Active Directory Service Interfaces (ADSI) Edit.


If you incorrectly modify the attributes of Active Directory objects when you use ADSI Edit, the LDP (ldp.exe) tool, or another Lightweight Directory Access Protocol (LDAP) version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003 or Exchange Server 2007, or both. Modify Active Directory object attributes at your own risk.


ADSI Edit is a tool that is provided with the Windows 2000 Server and Windows Server 2003 Support tools.

To correct this error

  1. Open the ADSI Edit MMC snap-in.

  2. On the Action menu, click Connect to.

  3. In the Connection Settings dialog box, in the Name field, enter a name for the ADSI connection. Under Connection Point, select Select a well known Naming Context, and then select Configuration in the drop-down menu. Click OK.

  4. In the left pane, double-click the Configuration object, and then double-click LostAndFoundConfig.

  5. In the right pane, delete all objects and containers. Right-click the object or container, click Delete, and then click Yes.

  6. Exit ADSI Edit.