Schema FSMO role not found
[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 https://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-17
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the domain controller that is specified as the schema FSMO (fSMORoleOwner at the Schema Naming Context). If the Exchange Server Analyzer finds that the domain controller specified in the fSMORoleOwner attribute does not exist in the forest, an error is displayed.
The fSMORoleOwner attribute at the Schema Naming Context (CN=Schema,CN=Configuration,DC=domain,DC=com) defines the domain controller that is the schema master for the forest. The schema master domain controller controls all updates and modifications to the schema. To update the schema of a forest, you must have access to the schema master. There can be only one schema master in the whole forest.
You must have a schema master defined for your Active Directory forest. Exchange 2000 Server Setup and Exchange 2000 Server Service Pack Setup will fail (even if you are not updating the schema) if a schema master domain controller is not online during setup. If the domain controller listed as the schema master is offline, it must be brought back online. This does not apply to Exchange Server 2003. Exchange Server 2003 Setup only contacts the schema master if it determines that the schema has not been extended.
To correct this error
Verify that the designated Active Directory server is physically present.
If this directory server has been decommissioned, assign the role of schema master to another domain controller.
For more information about how to assign the role of schema master to another domain controller, see the following Microsoft Knowledge Base articles:
280178, "XADM: Exchange 2000 Installation Requires Access to Schema Master" (https://go.microsoft.com/fwlink/?linkid=3052&kbid=280178)
For Microsoft Windows Server™ 2003, see 324801, "How To View and Transfer FSMO Roles in Windows Server 2003" (https://go.microsoft.com/fwlink/?LinkId=3052&kbid=324801)
For Microsoft Windows® 2000 Server, see 255690, "HOW TO: View and Transfer FSMO Roles in the Graphical User Interface" (https://go.microsoft.com/fwlink/?LinkId=3052&kbid=255690)