hello,

2 weeks ago,I had a crash of AD so I rebuild a new PDC.

The new PDC replicate good informations on offsite DCs,
only one offsite DC stay on the old unreachable PDC.

so on this offsite DC, DCDIAG indicate the OLD PDC.

How can I force the new PDC ?

Thank's

RE: offsite DC don't find new PDC by ZiadKChafi

ZiadKChafi
Fri Mar 28 07:32:01 PDT 2008

Try to run replmon to check if the server is replicating correctly, you can
also check the server's NTDS Settings in AD Sites and Services to se if it
has proper connections to other DCs in order to receive updates on the
configuration and domain partitions.

Let me know...
--
Ziad K. Chafi
MCT, MCTS, MCDBA, MCSE: S, MCDST
CompTIA A+, CompTIA N+,


"lucbft" wrote:

> hello,
>
> 2 weeks ago,I had a crash of AD so I rebuild a new PDC.
>
> The new PDC replicate good informations on offsite DCs,
> only one offsite DC stay on the old unreachable PDC.
>
> so on this offsite DC, DCDIAG indicate the OLD PDC.
>
> How can I force the new PDC ?
>
> Thank's
>
>
>

Re: offsite DC don't find new PDC by Paul

Paul
Mon Mar 31 05:59:26 PDT 2008

When you lost the old dc did you run a cleanup of your metadata?

http://support.microsoft.com/?id=216498


Run diagnostics against your Active Directory domain.

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be output
in notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.

Description and download for dnslint
http://support.microsoft.com/kb/321045


--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"lucbft" <luc.bonenfant@laposte.net> wrote in message
news:etvvUsNkIHA.5584@TK2MSFTNGP02.phx.gbl...
> hello,
>
> 2 weeks ago,I had a crash of AD so I rebuild a new PDC.
>
> The new PDC replicate good informations on offsite DCs,
> only one offsite DC stay on the old unreachable PDC.
>
> so on this offsite DC, DCDIAG indicate the OLD PDC.
>
> How can I force the new PDC ?
>
> Thank's
>



Re: offsite DC don't find new PDC by luc

luc
Wed Apr 02 08:09:14 PDT 2008

thank s to your answer

It s seems to be a big mistake on my PDC so I will contatc a AD expert for
assitance on site.


"Paul Bergson [MVP-DS]" <pbergson@allete_nospam.com> a écrit dans le message
de news: ekh9N8ykIHA.5160@TK2MSFTNGP05.phx.gbl...
> When you lost the old dc did you run a cleanup of your metadata?
>
> http://support.microsoft.com/?id=216498
>
>
> Run diagnostics against your Active Directory domain.
>
> If you don't have the support tools installed, install them from your
> server install disk.
> d:\support\tools\setup.exe
>
> Run dcdiag, netdiag and repadmin in verbose mode.
> -> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
> -> netdiag.exe /v > c:\netdiag.log (On each dc)
> -> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
> -> dnslint /ad /s "ip address of your dc"
>
> **Note: Using the /E switch in dcdiag will run diagnostics against ALL
> dc's in the forest. If you have significant numbers of DC's this test
> could generate significant detail and take a long time. You also want to
> take into account slow links to dc's will also add to the testing time.
>
> If you download a gui script I wrote it should be simple to set and run
> (DCDiag and NetDiag). It also has the option to run individual tests
> without having to learn all the switch options. The details will be
> output in notepad text files that pop up automagically.
>
> The script is located on my website at
> http://www.pbbergs.com/windows/downloads.htm
>
> Just select both dcdiag and netdiag make sure verbose is set. (Leave the
> default settings for dcdiag as set when selected)
>
> When complete search for fail, error and warning messages.
>
> Description and download for dnslint
> http://support.microsoft.com/kb/321045
>
>
> --
> Paul Bergson
> MVP - Directory Services
> MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "lucbft" <luc.bonenfant@laposte.net> wrote in message
> news:etvvUsNkIHA.5584@TK2MSFTNGP02.phx.gbl...
>> hello,
>>
>> 2 weeks ago,I had a crash of AD so I rebuild a new PDC.
>>
>> The new PDC replicate good informations on offsite DCs,
>> only one offsite DC stay on the old unreachable PDC.
>>
>> so on this offsite DC, DCDIAG indicate the OLD PDC.
>>
>> How can I force the new PDC ?
>>
>> Thank's
>>
>
>