Good practice to extend Svr 2016 AD schema to gain Exchange attributes (to access with ADSIedit) when no on-prem Exchange servers will be added?

Within the website you are told that "It is possible to extend the active directory schema to contain the required Exchange attributes without purchasing or installing Microsoft Exchange server."

According to the article you can then use the ADSIedit.msc command to change the attributes for certain users (such as whether or not that user will appear within the Outlook Global Address List (GAL).

These attributes weren't visible before the Active Directory schema was extended but then become available after the AD schema is extended by running the following command from the Exchange server installation media: “setup.exe /prepareschema /iacceptexchangeserverlicenseterms”.

I'm just wondering if there will be any issues with extending the Server 2016 Active Directory schema simply to gain these extended Exchange attributes when no on- premesis Exchange servers will ever be added to the environment (which is running Office 365 and is using Azure AD sync).

Please advise.
IT GuyNetwork EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
No problems at this time.
Schema alteration if done correctly, it will not create any problems no matter you install applications and use new schema attributes or not
You simply need to take care of schema alteration prerequisites given by MS Docs
Todd NelsonSystems EngineerCommented:
Make sure that all of your DCs and FFL/DFL are Windows 2008 R2 or newer.

Extending the schema and preparing AD will work to permit changing attributes, nevertheless, the only supported method to change these attributes when directory synchronization is enabled is with an Exchange server installed.

I'm curious why there is such an aversion to using Exchange as a management console.  It's not like Exchange has to be configured like a production server when it's hosts mailboxes and manages access and mail flow.
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

timgreen7077Exchange EngineerCommented:
You can safely update the schema using the Exchange 2016 media. Just download Exchange 2016 and run the below commands on a server that's a member of the same domain.

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms

This will not be an install of exchange.

see below link for more info:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The excuses given by management
If it is just exchange managemt console all you need, then why don't there is simple mmc console with just ad object managemt with reference to smtp attributes, why you need entire server with exchange server roles along with so many prerequisites with at least 4 cores / 8gb memory?
According to management it should get installed as small console app on desktop without needing server components
We know that this is not possible today, but at some point ms will / may come with simple smtp app which will eliminate need for complete exchange server install
Todd NelsonSystems EngineerCommented:

Microsoft is planning such a tool that is anticipated soon after Exchange 2019 is released later this year.
Who told you you need 4 cores and 8 GB RAM for a management console?  That's for a production server with mailboxes.  However, installing Exchange purely for management works just fine with 1 core and 2-4 GB RAM and very little storage.
Storage is not concern here
When we install 2012 and above OS servers in lab , there also we provide minimum 4 gb and 2 cores to just work with server under normal / no load condition
Whenever you build 2012 R2 and above servers that is also with all exchange role, it always eatup at least 80% memory minimum and with 1 core it most of the time spikes the utilization
Hence I always prefer 8gb / 4 core for empty exchange server
Todd NelsonSystems EngineerCommented:
Hence I always prefer 8gb / 4 core for empty exchange server

I think it's perfectly fine that we agree to disagree for an Exchange server utilized for management only.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.