Link to home
Start Free TrialLog in
Avatar of Alan Duck
Alan DuckFlag for United Kingdom of Great Britain and Northern Ireland

asked on

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.
Avatar of Wayne88
Wayne88
Flag of Canada image

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
Forcefully demote a Windows Server 2003 domain controller:

http://blogs.technet.com/b/asiasupp/archive/2006/09/06/454327.aspx
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-
I agree with Saige, i would definitely not force demote right away. Make sure everything is operating normally, it should gracefully demote.
Avatar of Alan Duck

ASKER

I will check the logs and DCDIAG before forcing a demote , will do that today.
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
There are just too many errors to solve and you already promoted a server replacement.  I would force demote it.
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?
ASKER CERTIFIED SOLUTION
Avatar of Alan Duck
Alan Duck
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
We used Microsoft support to solve this problem