AAD Connect Upgrade Error E_MMS_SCHEMA_CLASS_NOT_FOUND

UPDATE: This process seems to be outdated, and refresh schema should be done from AAD Connect Wizard.
See this link from MS for details.
Thank you Nuno, for pointing it out!

When upgrading AD Connect from a previous version (not DirSync or AD Sync, but an earlier version of AD Connect) I encountered this error when the upgrade process tried to configure synchronization rules:

15420906_260331594381992_1349974433037950144_n

I had actually upgraded the AD Schema from Windows Server 2012 to Windows Server 2012 R2 (because of Device Writeback) after initially installing AD Connect, but didn’t think this would impact upgrade of AD Connect. In my case it turns out the upgraded AD Schema actually caused this error message (assumption based on the fact that the upgrade succeeded after performing the steps below).

The fix? Easy:

  • Open Synchonization Service Manager on the AAD Connect Server
  • Navigate to “Connectors”
  • Select the connector named after your On-Premises Active Directory
  • Start action “Refresh Schema”

15380374_260387914376360_7943415947011071978_n

Conclusion:

If you installed AAD Connect, then upgraded your AD Schema, you might get into trouble when trying to upgrade AAD Connect.

4 Replies to “AAD Connect Upgrade Error E_MMS_SCHEMA_CLASS_NOT_FOUND”

  1. These steps are not Supported by Microsoft. Refreshing AD DS Schema have to be done through AAD Connect Wizard – Refresh directory Schema

  2. WARNING: These steps are NOT SUPPORTED by Microsoft. Refreshing AD DS Schema have to be done through AAD COnnect Wizard – Refresh directory Schema

    1. Well, this is an old post, and I hope people treat it as such. Information is provided as is. I will update the post to reflect this, if I can find official information from MS.

Leave a Reply to Nuno Alex Cancel reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.