Remove Active Directory from 2003 Server R2 after migrating to 2012 R2 Essentials

I replaced an old Windows 2003 R2 server with 2012 R2 Essentials as per this article
FSMO roles successfully transferred, and all users happily accessing their files on the new server.
The only thing left is to remove AD from the old server.
dcpromo fails with the following error:

The operation failed because: Managing the network session with failed
"The network path was not found. If this computer is connected to the network via a Remote Access Service (RAS) connection, ensure that File and Printer Sharing for Microsoft Networks is enabled for that connection."

Another symptom is that the 2003 R2 server can't access the shares on the 2012 R2 server.
This is to be expected, since 2003 is not supported anymore.

What would be the best way remove the old server from AD?
1. Temporarily downgrade security on the 2012 serve to allow connection from 2003
    (enable SMB1 etc.) Not sure if this would still work at all.
2. Use one of the AD cleanup methods to remove the old server from AD
    Which method would be best? Can this be done using PowerShell?
George KeslerAsked:
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.

IvanSystem EngineerCommented:

when ever I had problems of this kinde, if I couldn't resolve it in some normal amount of time, I usually did /force on dcpromo, and then clean metadata.

If you do have opportunity to enable SMB1, you could try and see if that works. It will allow file share access, since Windows 2003 uses SMB1 and Windows 2012 uses SMB3... but I don't know will that solve your dcpromo problem.

I had issues demoting a couple of 2003 DCs when I migrated to 2012. Since these servers where going to be decommissioned I just shut them down, untracked them, never to be turned on again and just ran the Metadata clean up following the instructions foun in the link below.

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
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 2003

From novice to tech pro — start learning today.