Forum
Ortamda ADC gorevi olan serveri domainden dcpromo ile kaldirmaya calisirken asagidaki hatayi aliyorum. Sifre vs tam olarak dogru. Sebebi ne olabilir?
DC olarak 2003 server mı mevcut ortamda,replikasyon da sıkıntı var sanırım.Belirtilen yolu bulamadığından adc ortamdan kaldıramıyor.Replikasyonu kontrol edermsiniz.DC şuan hala ayaktamı peki?
Eğer dc ortamda çöktü ve yok ise çalıştıra dcpromo /forceremoval şeklinde adc'de ortamda kaldırabilirsiniz.Yalnız dc ortamda duruyor ise bu komut kullanmayınız.DC'ye zarar verir.
Ek olarak adc ortamdan silmek istiyorsanız ve adc sıkıntı varsa, http://www.cozumpark.com/blogs/windows_server/archive/2008/03/30/ula-lmyan-additionel-domain-controller-in-active-directory-den-kald-r-lmas-ntdsut_3101_l-tools-with-metadata-cleanup.aspx inceleyebilirsiniz.
Keyifli çalışmalar.
merhaba cevap yazılana kadar burdan araştırmanızı öneririm
event id vs varsa onada bakabilirsiniz
http://www.google.com/microsoft?hl=tr&q=the+target+principal+name+is+incorrect&lr =
DC (Win2003 Enterprise) ayakta ve çalışıyor. Replikasyonu sağlıklı çalışıp çalışmadığını tam olarak nasıl kontrol edebilirim zira File Serverdan bakınca herşey normalmiş gibi görünüyor. Event loglara bu uyarıdan sonra yeni bir uyarı düşmüyor. Öteden beri bir DNS problemimiz var bu neden olabilir mi? Daha önceden bir konu açmıştım subnetlerle ilgili halen çözülemedi.
http://www.cozumpark.com/forums/thread/120969.aspx
Ayrıca dcdiag sonuçlarını aşağıya kopyaladım (az önce buldum verdiğiniz arama sonuçlarından)
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine ICB21, is a DC.
* Connecting to directory service on server ICB21.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 3 DC(s). Testing 3 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\ICB21
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... ICB21 passed test Connectivity
Testing server: Default-First-Site-Name\ICB22
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... ICB22 passed test Connectivity
Testing server: Default-First-Site-Name\ICB20
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... ICB20 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\ICB21
Starting test: Replications
* Replications Check
ICB21: There are 2 replication work items in the queue.
The first job has been executing for 0:3.
* Replication Latency Check
DC=ForestDnsZones,DC=icb,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=DomainDnsZones,DC=icb,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=icb,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=icb,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=icb,DC=local
Latency information for 5 entries in the vector were ignored.
5 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
* Replication Site Latency Check
Site
CN=NTDS Site Settings,CN=Icb,CN=Sites,CN=Configuration,DC=icb,DC=local
was skipped because it never had an ISTG running in it.
......................... ICB21 passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for DC=ForestDnsZones,DC=icb,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=DomainDnsZones,DC=icb,DC=local.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Schema,CN=Configuration,DC=icb,DC=local.
* Performing upstream (of target) analysis.
Merhaba,
AD Site and services açın.Default-first-name/servers altında bulunan serverlerınızı bulun ve automatically generated sağ tuşla tıklayın replicate now diyerek replikasoynu elle tetikleyin.Daha sonra adc kaldırmayı deneyin.
Sonuc ayni hocam. replicationlar tamamlandi ancak yukaridaki sorun aynen yerinde.
Bu yöntemden uzak durmaya çalışıyordum napalım elimiz mahkum gibi görünüyor. ntdutil'i kullanırken işlemleri diğer ADCler üzerindede tekrarlamam gerekiyor mu?
Sorun varsa ve adcde kaldırma işlemi yapamıyorsanız, bu yöntemi kullanmalısınız.DC üzerinden bu işlemi yapmnız kafidir.
Keyifli çalışmalar.