Cannot Raise Domain Functional Level Found on Spiceworks:

Hi there,

Trying promoting 2016 server from 2008r2 server after moving FSMO roles and verified the roles are in the new DC. but when I try to raise domain functional level, i get this error "The functional level could not be raised. The error is: The server is unwilling to process the request." I had to do dcpromo /force on the old dc as the dcpromo would not ran. Any thoughts would be greatly appreciated..

T SAsked:
Who is Participating?
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.

Jose Gabriel Ortega CastroEE Solution Guide/Topic Advisor and CEO Faru Bonon ITCommented:
You can raise the level, but 1st you need to demote ALL the domain controllers with less than 2016 to be able to do the raize.

You can rase the Forest functional level if you don't have ANY WINDOWS SERVER with less than 2016.

and you can raise the Domain functional level if you don't have ANY WINDOWS SERVER DOMAIN CONTROLLER in less than 2016.

2003 -> 2016 it won't work each server has its maximum domain controller than can accept
T SAuthor Commented:
I already demoted the 2008r2 dc. I ran dcpromo /force since it would not just demote with the dcpromo command. There is also an exchange server 2008 which stopped functioning. I have not touched it anything. I still show the old dc in dc our in the new dc but when I try to delete it manually it is promoting that I need to run the adds removal roles wizard first so it deletes it properly. Please advise...
I had to do dcpromo /force on the old dc as the dcpromo would not ran

You forcefully removed domain controller from AD, but your active directory did not know this fact

You need to do metadata cleanup for orphaned DC, this includes, removal of DC object from Domain controllers OU manually, cleaning up any traces from AD sites and services, NS records from DNS etc

Follow step by step process to make sure Ad is clean from old DC from GUI

if you prefer to use command line version (Ntdsutil), use below article

after that try raising functional level, it will work

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
T SAuthor Commented:
Thanks, but when I try to delete old dc in DC OU in active directory it gives an error "Windows cannot delete object LDAP://DC2.DCNAME.COM/CN=DC1,CD-Computers,DC=DCNAME,DC=com" because access denied.
T SAuthor Commented:
Fixed it. Thanks Mahesh and Jose. I went to ADDS and deleted old DC then it would let me delete the DC on DC OU. It was very helpful.
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 2008

From novice to tech pro — start learning today.