[Çözüldü] Eski DC halen sistemde silememe problemi...

Sistemdeki DC yi yeni bir servere tasidim dogal olarak serverin isminide degistirdim. Su an eski DC yi de goruyor. Profile ve Offline Sync yaparken olmayan eski DC ye ulasmaya caliyor boyle olunca login suresi uzadi. Eski kayitlari silmek icin internetten arattim birseyler yaptim NTDIS uzerinde. Fakat eskik olmus sanirim. Su anda asagidaki hatayi aliyorum AD Event viewer dan.

Asagida da Yine FSMO rolleri ile alakali bir hata var. Su an nasil yapacagimi bilemiyorum. DC yi yeniden mi yapilandirmaliyim bu benim sistemi tamamen etkiler mi?

Tesekkurler...

 Bu hata gibi sirasi ile

Directory partition:
DC=DomainDnsZones,DC=xxxxxx,DC=com 

Directory partition:
CN=Schema,CN=Configuration,DC=xxxxx,DC=com

Directory partition:
CN=Configuration,DC=xxxxx,DC=com 

Directory partition:
DC=xxxxxx,DC=com
 

Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Date:          4/15/2011 4:25:38 AM
Event ID:      2089
Task Category: Backup
Level:         Warning
Keywords:      Classic
User:          ANONYMOUS LOGON
Computer:      xxxxx.xxxxxx.com
Description:
This directory partition has not been backed up since at least the following number of days.
 
Directory partition:
DC=ForestDnsZones,DC=yscpcs,DC=com
 
'Backup latency interval' (days):
90
 
It is recommended that you take a backup as often as possible to recover from accidental loss of data. However if you haven't taken a backup since at least the 'backup latency interval' number of days, this message will be logged every day until a backup is taken. You can take a backup of any replica that holds this partition.
 
By default the 'Backup latency interval' is set to half the 'Tombstone Lifetime Interval'. If you want to change the default 'Backup latency interval', you could do so by adding the following registry key.
 
'Backup latency interval' (days) registry key:
System\CurrentControlSet\Services\NTDS\Parameters\Backup Latency Threshold (days)

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS Replication" />
    <EventID Qualifiers="32768">2089</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>14</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-15T08:25:38.932Z" />
    <EventRecordID>4818</EventRecordID>
    <Correlation />
    <Execution ProcessID="584" ThreadID="796" />
    <Channel>Directory Service</Channel>
    <Computer>xxxxxxx.xxxxx.com</Computer>
    <Security UserID="S-1-5-7" />
  </System>
  <EventData>
    <Data>DC=ForestDnsZones,DC=xxxxx,DC=com</Data>
    <Data>90</Data>
    <Data>System\CurrentControlSet\Services\NTDS\Parameters</Data>
    <Data>Backup Latency Threshold (days)</Data>
  </EventData>
</Event>

 Ikinci hata:

Ownership of the following FSMO role is set to a server which is deleted or does not exist.
 
Operations which require contacting a FSMO operation master will fail until this condition is corrected.
 
FSMO Role: CN=RID Manager$,CN=System,DC=xxxxxx,DC=com
FSMO Server DN: CN=NTDS Settings\0ADEL:b1a47d7c-fe94-490a-a5e6-521c1926ac17,CN=MAINSERVER\0ADEL:7659400f-773d-4273-a6d5-15df8664d051,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=xxxxx,DC=com
 
User Action:
 
1. Determine which server should hold the role in question.
2. Configuration view may be out of date. If the server in question has been promoted recently, verify that the Configuration partition has replicated from the new server recently.  If the server in question has been demoted recently and the role transferred, verify that this server has replicated the partition (containing the latest role ownership) lately.
3. Determine whether the role is set properly on the FSMO role holder server. If the role is not set, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.
4. Verify that replication of the FSMO partition between the FSMO role holder server and this server is occurring successfully.
 
The following operations may be impacted:
Schema: You will no longer be able to modify the schema for this forest.
Domain Naming: You will no longer be able to add or remove domains from this forest.
PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.