The Active Directory schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.
I am busy installing Exchange 2016 in a test environment and received the below error when running Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareSchema when trying to extend the domain schema.
“The Active Directory schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.”
Thing is, my account is part of the Schema Admins and Enterprise Admins group.
I then found the solution from this post (thanks Andy!)
In short, open the group membership tab on your account in Active Directory Users and Computers and then check which group is set to default, then click on Schema Admins and click on Set Primary Group to make it the primary group.
Logoff and log back in to the server and run:
Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareSchema
Remember to make the original group membership the primary again after you updated the schema.
7 Comments
Phil
Thanks for your post 🙂
I was getting this error attemping to install Exch 2019 CU14 on to a new domain. I wonder why this step isn’t mentioned in Microsoft’s documentation?
https://learn.microsoft.com/en-us/exchange/plan-and-deploy/prepare-ad-and-domains?view=exchserver-2019#step-2-prepare-active-directory
Michael Khordi - Moodi
Hello,
Just wanted to say this article is fantastic I have been battling with exchange 2019 and soon as I applied this primary group to my admin account logged out and back in to the server it instantly let me install.
You sir are a legend and I am now bookmarking this site.
Andi Kovaci
Thank you it works for me!
Daniel
I tried this option but did not resolve my issue. Any other suggestions.
Exchange Times .Net
Hi Daniel
I’ve been out of that space for a few years now, unfortunately I do not have any additional ideas to help you.
Hope you got it sorted?
Andy
Glad it helped! Took a couple of attempts to work this one out and didn’t see any other references to this at the time.
It’s almost as obscure as installing SSRS on a SQL server that complains about the licence key being invalid when it actually means reboot required before I can install. (spoiler alert for my next blog post)
Exchange Times .Net
You were a life saver there 🙂
Glad I found your blog as I will be checking it regularly too