What happens to applications when moving schema extension from 2012R2 to 2016?

When a company is moving from Windows 2012 R2 to Windows 2016, are there any known issues that may occur with this upgrade, talking specifically to our applications? Before we begin this upgrade, we want to make sure we know and understand any known issues that we might expect to our applications.

By applications I mean sharepoints, windows 7 desktops, office and lync 2013, etc.

I appreciate your assistance.
PiedraCellDepot 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:
Regarding the subject line, upgrading doesn't remove schema changes. Schema changes to Active Directory are permanent.

As to the question in the post, each application will be different and you need to check with ach manufacturer. We can't possibly knoweery appl7cation in your environment nor how you configured them.
PiedraCellDepot EngineerAuthor Commented:
Thank you for your response Cliff. While reading through the internet, I’m guessing that any application issues that may be encountered would be it applies to any of the following reasons. Would you agree?

If a vendor does any of the following when building their application, unexpected problems may result when the Active Directory schema is extended:
1.      The application checks for the Active Directory schema version and has a dependency of some kind on the schema version.
2.      The application requires the administrator to manually specify the root object identifier (OID) during setup and configuration of the product.
3.      The application includes its own extensions to the Active Directory schema but these extensions may have implemented improperly or might conflict with or even block future schema changes from Microsoft. Examples of improper implementation of schema changes can include such things as duplicate IODs, duplicate schema-id GUIDs, wrong syntax for attributes, missing must-contain attributes, missing may-contain attributes, and so on.

If the above statements are true, this would apply mainly to 3rd party applications and not to Microsoft applications (Lync, Office, Exchange, etc)?
Cliff GaliherCommented:
That is only a partial list. It's kinda like asking"shat can go wrong with a car engine?"  The answer is a lot.  Exchange 2010 didn't support a 2812 R2 schema or domain functional level for months after release l, for example, and required an exchange update to add support. And Exchange is an MS program.

So I stand my first answer. You can't assume compatibility just because Microsoft made something. Look up each and every program and version for supportability.

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
PiedraCellDepot EngineerAuthor Commented:
Understood. Thank you very much for your replies, you've helped me a lot.
Have a great day!
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 OS

From novice to tech pro — start learning today.