How to fix Schema Update for Exchange 2013 Setup.

Daniel Brown 0

The Active Directory Schema isn't up-to-date, and this user account isn't a member of the 'Schema Admin' and/or 'Enterprise Admin' but the user is already a member of both groups.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Wandi Ding -MSFT 2,885 Reputation points Microsoft Vendor

2024-02-06T09:43:16.74+00:00

Hello, it's been a few days and I'm checking the progress on this issue. If the information provided was helpful to you, you could mark the answer to help others with the same problem :)
Wandi Ding -MSFT 2,885 Reputation points Microsoft Vendor

2024-02-23T10:15:08.15+00:00

Hi, I am kindly following up to see if you have any remaining questions or concerns for this issue. If the provided method helps you fix the issue, you could mark the answer to help people who have the same issue :)

2 answers

Wandi Ding -MSFT 2,885 Reputation points Microsoft Vendor

2024-02-01T02:30:55.81+00:00
Hello @Daniel Brown,

To fix a schema update issue with Exchange 2013 Setup, you may need to perform the following steps:

Verify group membership: Make sure the user account used to update the schema is a member of the Schema Administrators and Enterprise Administrators groups.

Update the schema by running Exchange 2013 Setup with the /PrepareSchema parameter.

After the schema update is complete, run Exchange 2013 Setup using the /PrepareAD and /PrepareAllDomains parameters

For detailed information, please refer to Prepare Active Directory and domains for Exchange Server, Active Directory Exchange Server, Exchange Server Active Directory, Exchange 2019 Active Directory | Microsoft Learn

Hope the above information is helpful to you！

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Daniel Brown 0 Reputation points

2024-02-01T06:02:37.62+00:00

HI @Wandi Ding -MSFT Thank you for your response. Please note that the user is a member of both groups. Also note that I have found another error in the exchange setup logs - The Active Directory Schema version (170003) is higher than Setup's version (15312). Appreciate your assistance with this.

Wandi Ding -MSFT 2,885 Reputation points Microsoft Vendor

2024-02-01T08:24:41.5633333+00:00

Hi @Daniel Brown, Could you kindly clarify if you see The Active Directory Schema version as 17003 in the log? If so, please note that according to schema version value 17003, the last upgrade of schema version has been done with Exchange 2019 setup, if you want upgrade again the schema version with the last Exchange cumulative update, you may have to use Exchange 2019 or higher.

Daniel Brown 0 Reputation points

2024-02-01T19:07:01.3933333+00:00

HI @Wandi Ding -MSFT Is there anyway of downgrading/removing this schema so that we can install Exchange Server 2013?

Wandi Ding -MSFT 2,885 Reputation points Microsoft Vendor

2024-02-02T10:07:11.61+00:00

Hello @Daniel Brown,

Unfortunately, it seems there is no way to downgrade the Active Directory schema version, during installation of a newer version of Exchange the schema version will be upgraded and these changes are irreversible.

In this case, it is recommended to install the same or newer version of Exchange that is compatible with the current schema version.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
TStensitzki 11 Reputation points MVP

2024-03-12T17:53:55.2533333+00:00

Do you still face this issue?

This error can occur when the Windows Server running the schema update is not in the same Active Directory site as the schema master.

Run /PrepareSchema on a server in the same AD site as the schema master to move the FSMO role to a DC in the AD site of the server executing the schema update.

-Thomas
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to fix Schema Update for Exchange 2013 Setup.

2 answers

Your answer