Best practice for raising the function level of a Domain

All DC's at one of our sites are now 2016.  Our current Forest level is 2008.  

Should I raise the function level to 2012 R2 or all the way to 2016?
J.R. SitmanIT DirectorAsked:
Who is Participating?

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

x
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.

McKnifeCommented:
No reason not to go directly to 2016.

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
J.R. SitmanIT DirectorAuthor Commented:
just checking.

Thanks
scriven_jCommented:
I would always do it in an incremental way, so go to 2012 first and then leave it for at least 24 hours to replicate and for any problems to come to light.

You should also think about moving to DFSR if you are still using FRS:-

https://blogs.technet.microsoft.com/filecab/2014/06/25/streamlined-migration-of-frs-to-dfsr-sysvol/

So you don't NEED to, but no-one ever lost their job for being cautious!
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

J.R. SitmanIT DirectorAuthor Commented:
@scriven_j, good idea.
MaheshArchitectCommented:
I would check 1st what I am getting by raising functional levels to latest one
If at all I have any requirement which needs latest (2016) functional level, then I can weigh things and then go for latest one
If there is no requirements, I would leave functional level to current
Previously functional level raise is irreversible operation and raising it without proper planning could lead to issues
That is why Microsoft allowed to downgrade functional levels from windows 2012 AD version to save from possible issues in case
J.R. SitmanIT DirectorAuthor Commented:
Thank you for the update
Lee W, MVPTechnology and Business Process AdvisorCommented:
Just because you can doesn't mean you should.  This is not a case where you must.  But rather, UNDERSTAND what raising the levels get you and if you need that.  And what that means if you do raise the levels (for one, you can never introduce a 2012 DC for example - maybe not an issue today, but can you be really certain you won't in the future?)
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.