Link to home
Start Free TrialLog in
Avatar of Cliff_H
Cliff_HFlag for United States of America

asked on

Demote a DC where NTFrs is not working

Can I demote a DC even though it is not doing NTFrs replication? NTDS replication is working fine. It is giving Jrnl Wrap errors in the NTFrs event log.

Here is the situation. Our customer has 3 servers (A, B, and C) in one domain that are all Domain Controllers. They are all running Server 2003 R2 Standard. Server A is also running Exchange 2003 SP2. We installed 2 new Servers (D and E) that are also DCs and are running Server 2008 R2. We did that Schema update to 2008 Schema on Server A and it replicated successfully. We moved the FSMO roles to Server D.

This is when we noticed that Server A was not doing NTFrs replication and had been in Jrnl Wrap error for a couple of months. I know we should have fixed this before installing the new DCs. NTFrs is working fine between the other 4 servers.

The plan is to demote the 3 old servers and shut them down. On server A we plan to uninstall Exchange before demoting it.

I want to make sure that there isn't something about the NTFrs not working on Server A that is going to make a mess out of this process.

Thanks.
Cliff
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

If you're going to get rid of it, I'd probably just treat it as a failed DC.  Get all other services off it, then pull it off the network and get rid of it, performing a metadata cleanup in AD afterwards.
Well first off what steps have you taken to cure the jrnl wrap so far?
SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America 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
ASKER CERTIFIED SOLUTION
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
Avatar of Cliff_H

ASKER

Thanks for the comments.

There will not be an Exchange server when we are done. The customer is up and running on an on-line Exchange Hosting Service.

The jrnl warp error is only occuring on Server A. The Servers that are supposed to replicate with Server A are giving warning Event ID 13508 that they are not replicating with Server A about once a day.

The other 4 servers are doing NTFrs replication OK. I created small text files at each DC in the Scripts folder under the SysVol share and they all appeared at each server except Server A.

Yes, we will be more careful next time.

1. Should I do the gracefull demotion after uninstalling Exchange?
2. Uninstall Exchange then shutdown and metadata cleanup?
3. Just shutdown and metadata cleanup.

Will the metadata cleanup remove the Exchange stuff from AD?
SOLUTION
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
here is the article to cleanup metadata
http://support.microsoft.com/kb/216498
SOLUTION
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
Avatar of Cliff_H

ASKER

Thanks for all the help. The DNS tested fine. It looks like Server A was in Jrnl-Wrap because the NTFrs service had stopped for awhile. I did the registry change to D2 to force a non-authoritative restore. Replication then was working fine. Uninstalled Exchange. Demoted the 3 older servers and shut them down without too much trouble. DCDiag /v is good.

Thanks again.
Cliff