Re: Replication problems

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"Guy Kerr" <GuyKerr@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:637F124E-1D98-4B18-9728-2FFF4B45B3A5@xxxxxxxxxxxxxxxx
I have a similar situation. I have a Windows 2000 Server that was simply
shutdown a few months ago which held Schema Master and Operations Master
roles. The Windows 2003 server which is the other DC is still working
correctly but is showing repeated 2042 errors under the Directory Service
Events.

This is an issue but not a hard one to fix. Nearly trivial in fact, if a
little bit tedious.

I think your instructions are EXACTLY what I need to do but I want to
confirm the order.

NOTE: the old DC will be completely retired since it is old and
problematic.

1). Demote old DC

What old DC? You have one 2003, and another that was "shutdown" so
what is the OLD DC?

You cannot DCPromo a (now) missing DC.

2). Seize roles on Windows Server 2003 server from the now demoted old
DC.

You can do that now IF no other DC has these roles -- if one of the current
DCs has these roles then you should TRANSFER the roles (and NOT Seize).

Use NTDSUtil -> Roles -> (Transfer or Seize)

Used following instructions to seize roles
http://support.microsoft.com/default.aspx/kb/324801
3). dcpromo /forceremoval on the old DC.

You cannot do that if it is shutdown, but must instead use

NTDSUtil metadata cleanup

Google for this (quoted) phrase if you have ANY missing DCs.

4). Shutdown old DC.

If the old DC is still online you should just transfer any roles it has
and do an ordinary DCPromo (without forceremoval)

Forceremoval is only for a still working DC that cannot be brought back
online (with the other DCs) but which must remain as a Server.

Can someone respond to either confirm these are the correct steps or
correct
me if I'm missing something?


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

Thanks in advance.

"Jorge Silva" wrote:

Hi Joao
Sounds like your DC failed to replicate whithin the Tombstonelifetime
period, generally the best option is to demote (perform metadata cleanup)
the LESS updated DC seize any fsmo roles helded by that DC and then using
the dcpromo /forceremoval switch take the AD off that DC and then add it
again the Domain as normal process. In future pay a litle more attention
to
the replication process ny monitring that operation(s).
also ahave a look at:
http://technet2.microsoft.com/windowsserver/en/library/34c15446-b47f-4d51-8e4a-c14527060f901033.mspx?mfr=true


--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Joao Luis Rita" <JoaoLuisRita@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:86EE3538-F588-4F5B-A868-9D4CA07DF4DE@xxxxxxxxxxxxxxxx
Hello all

I need some ideas for the following problems.

We have 2 main Windows 2003 servers, PDC1 and PDC2 (service pack 1). A
few
days ago, the 2 servers apparently stopped replicating each other. Some
users
couldn't log in, others received messages stating their PC account didn't
exist. I checked the users/computers listings on the servers and some
PCs
are
in PDC2 while not being in PDC1. I checked the event viewer: the
"directory
service" log is full of replication errors. All the errors fall in 3
events
IDs-1864, 2042, 2092. I've checked Technet, and all seem to point to
firewall
problems. However we have no firewall between these servers.

I've been forced to shutdown PDC2 to stop all these errors.
Unfortunately,
the person that usually handles these problems is on vacation, and
after
2mn
on the phone he said he may have to format/reinstall PDC2, when he
returns.

Anyone has any ideas about this? I'd like to avoid the whole
format/reinstall.

Any way we can maybe force a replication, using PDC1 as base (it seems
to
have the most updated listings)?




.

Relevant Pages

  • RE: AD transition to Windows 2008
    ... Domain controllers are redundant since AD is multi master replication model. ... So you will build first servers, you will DCpromo in to your existing ...
    (microsoft.public.windows.server.active_directory)
  • Re: how to correct the problem of AD
    ... imaging to backup DCs (or any servers in my opinion). ... which means that the replication partner already thinks it ... You need to do a DCPROMO /FORCEREMOVAL, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... Ethernet adapter PUBLIC: ... regarding EX-DC3 replication look interesting...anyway, ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... regarding EX-DC3 replication look interesting...anyway, ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
    ... DC's should NOT be multihomed, this creates lot's of problems, especially with replication. ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
    (microsoft.public.windows.server.active_directory)