Re: Replaced AD Server Hardware

Spyle,

Yes, replication error might seize, either bring old dc back online and
properly demote or usentdsutil to forcefully clean metedata

"Spyle" <> wrote in message
news:...
>
> Everything went well but am having a few errors like below in the event
> viewer. They started showing up after I transferred the FSMO roles and
> shutdown the old server for testing. I have not ran DCPROMO to remove
> the old server yet.. Is it safe to assume that these errors will cease
> when I demote the old server?
>
>
> Event ID 1863, NTDS Replication
> ______________
> This is the replication status for the following directory partition on
> the local domain controller.
>
> Directory partition:
> DC=ForestDnsZones,DC=***,DC=local
>
> The local domain controller has not received replication information
> from a number of domain controllers within the configured latency
> interval.
>
> Latency Interval (Hours):
> 24
> Number of domain controllers in all sites:
> 1
> Number of domain controllers in this site:
> 1
>
> The latency interval can be modified with the following registry key.
>
> Registry Key:
> HKLM\System\CurrentControlSet\Services\NTDS\Parame ters\Replicator
> latency error interval (hours)
>
> To identify the domain controllers by name, install the support tools
> included on the installation CD and run dcdiag.exe.
> You can also use the support tool repadmin.exe to display the
> replication latencies of the domain controllers in the forest. The
> command is "repadmin /showvector /latency <partition-dn>".
>
> For more information, see Help and Support Center at
>
>
> --
> Spyle
> ------------------------------------------------------------------------
> Spyle's Profile: http://forums.techarena.in/members/94259.htm
> View this thread: http://forums.techarena.in/server-migration/1169265.htm
>
> http://forums.techarena.in
>