windows server 2003 won't demote

we have replaced a windows 2003 SBS server with a standard windows 2012r2 , the windows 2012 appeared to promote ok
But when we run the dcpromo on the windows 2003 server, it wont demote has it says it cant see another DC on the domain also when we disconnect the 2003 server workstations can either.
the active directory shows the 2012 server is the PDC etc and we have shared the SYSVOL on the 2012 server has it appeared not to be shared.

Alan DuckAsked: 2015-07-20

Who is Participating?

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

Experts Exchange Solution brought to you by

Enjoy your complimentary solution view.

Get this solution by purchasing an Individual license! Start your 7-day free trial.

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.

LVL 22

Wayne88Commented: 2015-07-20

You have to force demote it. Please follow this steps:

https://support.microsoft.com/en-us/kb/332199

https://support.microsoft.com/en-us/kb/555846

LVL 22

Wayne88Commented: 2015-07-20

Forcefully demote a Windows Server 2003 domain controller:

http://blogs.technet.com/b/asiasupp/archive/2006/09/06/454327.aspx

LVL 37

it_saigeDeveloperCommented: 2015-07-20

Before you rush in and force a demotion, I would verify that you have a healthy domain and that replication is functioning properly.

This error may indicate a failure with the promotion on your 2012 server which means that it is not truly a domain controller yet. The failure may stem from a corrupted FRS database on the 2003 server or improper DNS. Personally I am leaning towards a corrupted FRS database since you mention that you created the SYSVOL share.

Look in the event logs for any FRS and/or DNS related failures. It also wouldn't hurt to run a DCDIAG.

-saige-

LVL 7

NinjaStyle82Systems AdministratorCommented: 2015-07-20

I agree with Saige, i would definitely not force demote right away. Make sure everything is operating normally, it should gracefully demote.

Alan DuckAuthor Commented: 2015-07-22

I will check the logs and DCDIAG before forcing a demote , will do that today.

Alan DuckAuthor Commented: 2015-07-22

I have run a DCDIAG it errors with Error 1355 A Global Catalogue Server cannot be located
Also The Server holding the PDC Role is Down
The new 2012 server holds both these roles.
The File Replication Service gives an error 13508

LVL 22

Wayne88Commented: 2015-07-22

There are just too many errors to solve and you already promoted a server replacement. I would force demote it.

LVL 7

NinjaStyle82Systems AdministratorCommented: 2015-07-22

I would force demote it.

I wouldn't, looks like you might need to check on your fsmo roles...

maybe verify time on each of the DCs, maybe do a "w32tm /resync"

force demoting it is going to leave mess behind you will need to clean up, not to mention that there a clear problem with your domain currently.

Also, what is your forest and domain functional levels?

Alan DuckAuthor Commented: 2015-07-29

Due to the complicated nature of the fault and the work load we got Microsoft Technical support to solve this problem.
I haven't has yet seen a email break down how it has been cured but the problem seems solved.
I will update with the solution used when I get the 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