{"id":46,"title":"Domain Controller Kald\u0131rma Sorunu, Kal\u0131c\u0131 Metadata Temizli\u011fi","content":"

Domain Controller Kald\u0131rma Sorunu, Kal\u0131c\u0131 Metadata Temizli\u011fi.<\/h3> Active Directory ortamlar\u0131nda domain controller kald\u0131rma i\u015flemi bazen beklenmedik zorluklarla kar\u015f\u0131la\u015fabilir. Bu teknik rehber, diren\u00e7li DC metadata kal\u0131nt\u0131lar\u0131n\u0131n temizlenmesi i\u00e7in ileri d\u00fczey \u00e7\u00f6z\u00fcm y\u00f6ntemlerini detayland\u0131rmaktad\u0131r.<\/strong>

Problem Tan\u0131m\u0131<\/h2> Windows Server ortamlar\u0131nda eski domain controller'lar\u0131n (DC) sistemden kald\u0131r\u0131lmas\u0131 s\u0131ras\u0131nda metadata kal\u0131nt\u0131lar\u0131, replikasyon sorunlar\u0131na ve sistem karars\u0131zl\u0131\u011f\u0131na neden olabilir. Standart metadata cleanup i\u015flemleri her zaman yeterli olmayabilir ve bu durumda daha derinlemesine m\u00fcdahale gerektiren y\u00f6ntemlere ba\u015fvurmak gerekir.

Senaryo Analizi<\/h2> Bu rehberdeki \u00f6rnek senaryoda, Windows Server 2016 tabanl\u0131 PDC2016 sunucusu Windows Server 2022 ile de\u011fi\u015ftirilmi\u015f, ancak eski DC'nin metadata kal\u0131nt\u0131lar\u0131 sistemde varl\u0131\u011f\u0131n\u0131 s\u00fcrd\u00fcrmeye devam etmi\u015ftir. FSMO rolleri transfer edilmi\u015f ve replikasyon do\u011frulanm\u0131\u015f olmas\u0131na ra\u011fmen:
  • Metadata cleanup i\u015flemi tamamlanm\u0131\u015f g\u00f6r\u00fcnse de objeler hala mevcut<\/li>
  • Replikasyon s\u00fcrekli eski sunucu kal\u0131nt\u0131lar\u0131n\u0131 restore ediyor<\/li>
  • ADSI Edit ile manuel silme i\u015flemleri ba\u015far\u0131s\u0131z oluyor<\/li>
  • DNS kay\u0131tlar\u0131 s\u00fcrekli yeniden olu\u015fuyor<\/li> <\/ul>

    \u00c7\u00f6z\u00fcm Metodolojisi<\/h2>

    A\u015fama 1: LDAP Seviyesinde Do\u011frudan M\u00fcdahale<\/h3> Standart ara\u00e7lar yetersiz kald\u0131\u011f\u0131nda, ldp.exe<\/code> arac\u0131 ile LDAP seviyesinde do\u011frudan m\u00fcdahale gerekir. Ba\u011flant\u0131 Kurulum S\u00fcreci:<\/strong>
    1. LDP.exe Ba\u015flatma ve Ba\u011flant\u0131:<\/strong>
      • ldp.exe<\/code> uygulamas\u0131n\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n<\/li>
      • Connection \u2192 Connect men\u00fcs\u00fcne gidin<\/li>
      • Sunucu: Aktif \u00e7al\u0131\u015fan DC'nin FQDN adresi<\/li>
      • Port: 389 (LDAP) veya 636 (LDAPS)<\/li> <\/ul> <\/li>
      • Kimlik Do\u011frulama:<\/strong>
        • Connection \u2192 Bind se\u00e7ene\u011fini kullan\u0131n<\/li>
        • Domain Administrator yetkilerine sahip hesapla oturum a\u00e7\u0131n<\/li> <\/ul> <\/li>
        • Konfig\u00fcrasyon Container'\u0131na Eri\u015fim:<\/strong>
          • View \u2192 Tree men\u00fcs\u00fcnden Base DN olarak \u015fu path'i girin:<\/li> <\/ul> 
            CN=Configuration,DC=domain,DC=com <\/code><\/pre> <\/li> <\/ol> Nesne Lokalizasyonu ve Silme:<\/strong> A\u011fa\u00e7 yap\u0131s\u0131nda \u015fu hiyerar\u015fiyi takip edin: 
            CN=Sites \u2192 CN=Default-First-Site-Name \u2192 CN=Servers \u2192 CN=PDC2016 <\/code><\/pre> Kritik Silme S\u0131ras\u0131:<\/strong> 
               
            1. \u00d6nce CN=NTDS Settings<\/code> nesnesini silin (PDC2016 alt\u0131nda)<\/li> 
            2. Ard\u0131ndan CN=PDC2016<\/code> ana nesnesini silin<\/li> 
            3. Her silme i\u015flemi sonras\u0131 replikasyon durumunu kontrol edin<\/li> <\/ol> 
              A\u015fama 2: DNS Infrastructure Temizli\u011fi<\/h3> DNS kal\u0131nt\u0131lar\u0131 sistem performans\u0131n\u0131 d\u00fc\u015f\u00fcr\u00fcr ve gelecekteki AD i\u015flemlerinde sorun yaratabilir. DNS Management Console \u0130\u015flemleri:<\/strong> 
                 
              1. Forward Lookup Zones Temizli\u011fi:<\/strong> 
                   
                • dnsmgmt.msc<\/code> konsolunu a\u00e7\u0131n<\/li> 
                • \u0130lgili domain zone'unda PDC2016 i\u00e7in t\u00fcm A ve CNAME kay\u0131tlar\u0131n\u0131 silin<\/li> 
                • PTR kay\u0131tlar\u0131 i\u00e7in Reverse Lookup Zones'u da kontrol edin<\/li> <\/ul> <\/li> 
                • Service Location (SRV) Records Temizli\u011fi:<\/strong> 
                     
                  • _msdcs.domain.com<\/code> alt domain'inde GUID tabanl\u0131 kay\u0131tlar\u0131 silin<\/li> 
                  • _sites<\/code> alt\u0131nda Default-First-Site-Name i\u00e7indeki PDC2016 referanslar\u0131n\u0131 temizleyin<\/li> 
                  • _tcp<\/code> ve _udp<\/code> protokol kay\u0131tlar\u0131n\u0131 g\u00f6zden ge\u00e7irin<\/li> <\/ul> <\/li> <\/ol> 
                    A\u015fama 3: Replikasyon Do\u011frulama ve Senkronizasyon<\/h3> Sistem Geneli Replikasyon Tetikleme:<\/strong> 
                    repadmin \/syncall \/AdeP <\/code><\/pre> Bu komut t\u00fcm domain controller'lar aras\u0131nda tam senkronizasyon ba\u015flat\u0131r. Replikasyon Durumu Kontrol\u00fc:<\/strong> 
                    repadmin \/showrepl * <\/code><\/pre> PDC2016 referanslar\u0131n\u0131n tamamen temizlendi\u011fini do\u011frulay\u0131n. Topology Kontrolleri:<\/strong> 
                    repadmin \/kcc repadmin \/showconn <\/code><\/pre> 
                    A\u015fama 4: Sistem B\u00fct\u00fcnl\u00fc\u011f\u00fc Kontrol\u00fc<\/h3> Active Directory Database Kontrol\u00fc:<\/strong> 
                    dcdiag \/v dcdiag \/test:replications <\/code><\/pre> Forest\/Domain Functional Level Kontrol\u00fc:<\/strong> 
                    netdom query fsmo <\/code><\/pre> FSMO rollerinin do\u011fru sunucularda oldu\u011funu do\u011frulay\u0131n. 
                    Alternatif \u00c7\u00f6z\u00fcm Y\u00f6ntemleri<\/h2> 
                    Method 1: Authoritative Restore Yakla\u015f\u0131m\u0131<\/h3> Kritik durumlarda, authoritative restore i\u015flemi ile belirli objeler silinebilir: 
                    ntdsutil authoritative restore restore object \"CN=PDC2016,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=com\" <\/code><\/pre> 
                    Method 2: PowerShell AD Module Kullan\u0131m\u0131<\/h3> 
                    Get-ADObject -Filter 'Name -like \"*PDC2016*\"' -SearchBase \"CN=Configuration,DC=domain,DC=com\" -IncludeDeletedObjects Remove-ADObject -Identity \"CN=PDC2016,...\" -Confirm:$false <\/code><\/pre> 
                    \u00d6nleme Stratejileri<\/h2> 
                    Planlama A\u015famas\u0131 Kontrolleri:<\/h3> 
                       
                    • DC kald\u0131rma \u00f6ncesi t\u00fcm FSMO rollerinin ba\u015fka sunuculara transfer edilmesi<\/li> 
                    • Global Catalog rol\u00fcn\u00fcn kontrol edilmesi<\/li> 
                    • Replikasyon sa\u011fl\u0131\u011f\u0131n\u0131n do\u011frulanmas\u0131<\/li> <\/ul> 
                      Monitoring ve Alerting:<\/h3> 
                         
                      • Replikasyon hatalar\u0131n\u0131n s\u00fcrekli izlenmesi<\/li> 
                      • DNS zone health kontrollerinin otomatikle\u015ftirilmesi<\/li> 
                      • AD database consistency check'lerinin d\u00fczenli \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131<\/li> <\/ul> 
                        Troubleshooting \u0130pu\u00e7lar\u0131<\/h2> Yayg\u0131n Hatalar ve \u00c7\u00f6z\u00fcmleri:<\/strong> 
                           
                        1. \"Access Denied\" Hatalar\u0131:<\/strong> 
                             
                          • Schema Admin veya Enterprise Admin yetkilerini kontrol edin<\/li> 
                          • PDC Emulator rol\u00fcn\u00fcn eri\u015filebilir oldu\u011funu do\u011frulay\u0131n<\/li> <\/ul> <\/li> 
                          • Replikasyon S\u00fcrekli Geri Getirme:<\/strong> 
                               
                            • T\u00fcm DC'lerde ayn\u0131 i\u015flemleri ger\u00e7ekle\u015ftirin<\/li> 
                            • Bridgehead server konfig\u00fcrasyonunu kontrol edin<\/li> <\/ul> <\/li> 
                            • DNS Resolution Sorunlar\u0131:<\/strong> 
                                 
                              • Forwarders ve root hints ayarlar\u0131n\u0131 g\u00f6zden ge\u00e7irin<\/li> 
                              • Cache temizli\u011fi yap\u0131n: ipconfig \/flushdns<\/code><\/li> <\/ul> <\/li> <\/ol> 
                                Sonu\u00e7 ve \u00d6neriler<\/h2> Domain Controller metadata temizli\u011fi, Active Directory altyap\u0131s\u0131n\u0131n sa\u011fl\u0131\u011f\u0131 i\u00e7in kritik bir i\u015flemdir. Standart ara\u00e7lar\u0131n yetersiz kald\u0131\u011f\u0131 durumlarda, LDAP seviyesinde m\u00fcdahale ve kapsaml\u0131 DNS temizli\u011fi ile sorunlar \u00e7\u00f6z\u00fclebilir. Best Practices:<\/strong> 
                                   
                                • Her zaman test ortam\u0131nda deneme yap\u0131n<\/li> 
                                • De\u011fi\u015fiklikleri a\u015famal\u0131 olarak uygulay\u0131n<\/li> 
                                • T\u00fcm i\u015flemleri dok\u00fcmante edin<\/li> 
                                • Rollback plan\u0131 haz\u0131rlay\u0131n<\/li> <\/ul> Bu metodoloji, enterprise Active Directory ortamlar\u0131nda g\u00fcvenli ve etkili DC kald\u0131rma i\u015flemleri i\u00e7in referans te\u015fkil edebilir. 
                                   Bu rehber Windows Server 2016\/2019\/2022 ortamlar\u0131nda test edilmi\u015f ve do\u011frulanm\u0131\u015f y\u00f6ntemleri i\u00e7ermektedir. Production ortam\u0131nda uygulamadan \u00f6nce test edilmesi \u00f6nerilir.<\/em>","excerpt":"Domain Controller Kald\u0131rma Sorunu, Kal\u0131c\u0131 Metadata Temizli\u011fi. Active Directory ortamlar\u0131nda domain controller kald\u0131rma i\u015flemi bazen...","created_at":"2025-06-22 21:13:13","updated_at":"2026-09-07 00:40:58","category_id":8,"view_count":927,"reading_time":5,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2025-06-22 21:13:13","featured_image":"resimyok.jpg","slug":"metadata-cleanup","category_name":"Active Directory \/Azure","category_slug":"active-directory-azure","category_color":"#f59e0b"}