Top-Themen

AppleEntwicklungHardwareInternetLinuxMicrosoftMultimediaNetzwerkeOff TopicSicherheitSonstige SystemeVirtualisierungWeiterbildungZusammenarbeit

Aktuelle Themen

Administrator.de FeedbackApache ServerAppleAssemblerAudioAusbildungAuslandBackupBasicBatch & ShellBenchmarksBibliotheken & ToolkitsBlogsCloud-DiensteClusterCMSCPU, RAM, MainboardsCSSC und C++DatenbankenDatenschutzDebianDigitiales FernsehenDNSDrucker und ScannerDSL, VDSLE-BooksE-BusinessE-MailEntwicklungErkennung und -AbwehrExchange ServerFestplatten, SSD, RaidFirewallFlatratesGoogle AndroidGrafikGrafikkarten & MonitoreGroupwareHardwareHosting & HousingHTMLHumor (lol)Hyper-VIconsIDE & EditorenInformationsdiensteInstallationInstant MessagingInternetInternet DomäneniOSISDN & AnaloganschlüsseiTunesJavaJavaScriptKiXtartKVMLAN, WAN, WirelessLinuxLinux DesktopLinux NetzwerkLinux ToolsLinux UserverwaltungLizenzierungMac OS XMicrosoftMicrosoft OfficeMikroTik RouterOSMonitoringMultimediaMultimedia & ZubehörNetzwerkeNetzwerkgrundlagenNetzwerkmanagementNetzwerkprotokolleNotebook & ZubehörNovell NetwareOff TopicOpenOffice, LibreOfficeOutlook & MailPapierkorbPascal und DelphiPeripheriegerätePerlPHPPythonRechtliche FragenRedHat, CentOS, FedoraRouter & RoutingSambaSAN, NAS, DASSchriftartenSchulung & TrainingSEOServerServer-HardwareSicherheitSicherheits-ToolsSicherheitsgrundlagenSolarisSonstige SystemeSoziale NetzwerkeSpeicherkartenStudentenjobs & PraktikumSuche ProjektpartnerSuseSwitche und HubsTipps & TricksTK-Netze & GeräteUbuntuUMTS, EDGE & GPRSUtilitiesVB for ApplicationsVerschlüsselung & ZertifikateVideo & StreamingViren und TrojanerVirtualisierungVisual StudioVmwareVoice over IPWebbrowserWebentwicklungWeiterbildungWindows 7Windows 8Windows 10Windows InstallationWindows MobileWindows NetzwerkWindows ServerWindows SystemdateienWindows ToolsWindows UpdateWindows UserverwaltungWindows VistaWindows XPXenserverXMLZusammenarbeit

AD Replikationsproblem

Frage Microsoft

Mitglied: benscha

benscha (Level 1) - Jetzt verbinden

06.10.2009 um 15:26 Uhr, 5707 Aufrufe, 4 Kommentare

Seit ein paar Tagen werden 2 meiner DC's nicht mer repliziert! Die DC's befinden sich an 2 Standorten (Standort-M und Standort-Z)! Ich google nun schon seit 2 Tagen bringe jedoch keine Replikation hin!! ( habe schon diverese durchgetestet leider alles ohne Erfolg!

Standort-M: 3 DC's (PCM-SRV04, PCM_SRV01 und neu hinzugefügt PCM-SRV02 wird erfolgreich mit PCM-SRV04 repliziert)
Standort-Z: 1 DC (PCZ-SRV01)

DCDIAG von PCM-SRV04 am Standort-M


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Standort-M\PCM-SRV04
Starting test: Connectivity
......................... PCM-SRV04 passed test Connectivity

Doing primary tests

Testing server: Standort-M\PCM-SRV04
Starting test: Replications
......................... PCM-SRV04 passed test Replications
Starting test: NCSecDesc
......................... PCM-SRV04 passed test NCSecDesc
Starting test: NetLogons
......................... PCM-SRV04 passed test NetLogons
Starting test: Advertising
......................... PCM-SRV04 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... PCM-SRV04 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... PCM-SRV04 passed test RidManager
Starting test: MachineAccount
......................... PCM-SRV04 passed test MachineAccount
Starting test: Services
......................... PCM-SRV04 passed test Services
Starting test: ObjectsReplicated
......................... PCM-SRV04 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... PCM-SRV04 passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x8000046E
Time Generated: 10/06/2009 15:03:40
(Event String could not be retrieved)
......................... PCM-SRV04 failed test kccevent
Starting test: systemlog
......................... PCM-SRV04 passed test systemlog

Running enterprise tests on : pcolo.local
Starting test: Intersite
......................... pcolo.local passed test Intersite
Starting test: FsmoCheck
......................... pcolo.local passed test FsmoCheck






DCDIAG PCM_SRV01 Standort-M


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Standort-M\PCM_SRV01
Starting test: Connectivity
......................... PCM_SRV01 passed test Connectivity

Doing primary tests

Testing server: Standort-M\PCM_SRV01
Starting test: Replications
......................... PCM_SRV01 passed test Replications
Starting test: NCSecDesc
......................... PCM_SRV01 passed test NCSecDesc
Starting test: NetLogons
......................... PCM_SRV01 passed test NetLogons
Starting test: Advertising
......................... PCM_SRV01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... PCM_SRV01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... PCM_SRV01 passed test RidManager
Starting test: MachineAccount
......................... PCM_SRV01 passed test MachineAccount
Starting test: Services
......................... PCM_SRV01 passed test Services
Starting test: ObjectsReplicated
......................... PCM_SRV01 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... PCM_SRV01 passed test frssysvol
Starting test: kccevent
An Error Event occured. EventID: 0xC0000583
Time Generated: 10/06/2009 14:55:47
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000583
Time Generated: 10/06/2009 15:00:48
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000583
Time Generated: 10/06/2009 15:05:49
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000583
Time Generated: 10/06/2009 15:07:01
(Event String could not be retrieved)
......................... PCM_SRV01 failed test kccevent
Starting test: systemlog
......................... PCM_SRV01 passed test systemlog

Running enterprise tests on : pcolo.local
Starting test: Intersite
......................... pcolo.local passed test Intersite
Starting test: FsmoCheck
......................... pcolo.local passed test FsmoCheck



DCDIAG PCZ-SRV01 Standort-Z


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Standort-Z\PCZ-SRV01
Starting test: Connectivity
......................... PCZ-SRV01 passed test Connectivity

Doing primary tests

Testing server: Standort-Z\PCZ-SRV01
Starting test: Replications
[Replications Check,PCZ-SRV01] A recent replication attempt failed:
From PCM_SRV01 to PCZ-SRV01
Naming Context: CN=Schema,CN=Configuration,DC=pcolo,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2009-10-05 10:59.48.
The last success occurred at 2009-09-19 09:55.35.
261 failures have occurred since the last success.
[Replications Check,PCZ-SRV01] A recent replication attempt failed:
From PCM-SRV04 to PCZ-SRV01
Naming Context: CN=Schema,CN=Configuration,DC=pcolo,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2009-10-05 11:07.30.
The last success occurred at 2009-09-16 09:25.36.
3658 failures have occurred since the last success.
[Replications Check,PCZ-SRV01] A recent replication attempt failed:
From PCM_SRV01 to PCZ-SRV01
Naming Context: CN=Configuration,DC=pcolo,DC=local
The replication generated an error (8524):
Win32 Error 8524
The failure occurred at 2009-10-05 09:52.29.
The last success occurred at 2009-09-19 09:55.35.
260 failures have occurred since the last success.
The guid-based DNS name 269b76ba-3b23-41a6-840a-b058d15cf73e._msdcs.pcolo.local
is not registered on one or more DNS servers.
[Replications Check,PCZ-SRV01] A recent replication attempt failed:
From PCM-SRV04 to PCZ-SRV01
Naming Context: CN=Configuration,DC=pcolo,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2009-10-05 11:07.30.
The last success occurred at 2009-09-16 09:25.36.
3658 failures have occurred since the last success.
[Replications Check,PCZ-SRV01] A recent replication attempt failed:
From PCM-SRV04 to PCZ-SRV01
Naming Context: DC=pcolo,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2009-10-05 11:07.30.
The last success occurred at 2009-09-16 09:25.36.
3658 failures have occurred since the last success.
[Replications Check,PCZ-SRV01] A recent replication attempt failed:
From PCM_SRV01 to PCZ-SRV01
Naming Context: DC=pcolo,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2009-10-05 11:08.00.
The last success occurred at 2009-09-19 09:55.34.
262 failures have occurred since the last success.
......................... PCZ-SRV01 passed test Replications
Starting test: NCSecDesc
......................... PCZ-SRV01 passed test NCSecDesc
Starting test: NetLogons
......................... PCZ-SRV01 passed test NetLogons
Starting test: Advertising
......................... PCZ-SRV01 passed test Advertising
Starting test: KnowsOfRoleHolders
[PCM-SRV04] DsBind() failed with error -2146893022,
Win32 Error -2146893022.
Warning: PCM-SRV04 is the Schema Owner, but is not responding to DS RPC Bind.
[PCM-SRV04] LDAP bind failed with error 31,
Win32 Error 31.
Warning: PCM-SRV04 is the Schema Owner, but is not responding to LDAP Bind.
Warning: PCM-SRV04 is the Domain Owner, but is not responding to DS RPC Bind.
Warning: PCM-SRV04 is the Domain Owner, but is not responding to LDAP Bind.
[PCM_SRV01] DsBind() failed with error -2146893022,
Win32 Error -2146893022.
Warning: PCM_SRV01 is the PDC Owner, but is not responding to DS RPC Bind.
[PCM_SRV01] LDAP bind failed with error 31,
Win32 Error 31.
Warning: PCM_SRV01 is the PDC Owner, but is not responding to LDAP Bind.
Warning: PCM-SRV04 is the Rid Owner, but is not responding to DS RPC Bind.
Warning: PCM-SRV04 is the Rid Owner, but is not responding to LDAP Bind.
Warning: PCM-SRV04 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: PCM-SRV04 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... PCZ-SRV01 failed test KnowsOfRoleHolders
Starting test: RidManager
[PCZ-SRV01] DsBindWithCred() failed with error -2146893022. Win32 Error -2146893022
......................... PCZ-SRV01 failed test RidManager
Starting test: MachineAccount
......................... PCZ-SRV01 passed test MachineAccount
Starting test: Services
......................... PCZ-SRV01 passed test Services
Starting test: ObjectsReplicated
......................... PCZ-SRV01 passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... PCZ-SRV01 passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x8000061E
Time Generated: 10/05/2009 11:12:30
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000051F
Time Generated: 10/05/2009 11:12:30
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x8000061E
Time Generated: 10/05/2009 11:12:30
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000051F
Time Generated: 10/05/2009 11:12:30
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 10/05/2009 11:12:30
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 10/05/2009 11:12:30
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800004F1
Time Generated: 10/05/2009 11:12:30
(Event String could not be retrieved)
......................... PCZ-SRV01 failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000C8A
Time Generated: 10/05/2009 10:32:58
(Event String could not be retrieved)
......................... PCZ-SRV01 failed test systemlog

Running enterprise tests on : pcolo.local
Starting test: Intersite
......................... pcolo.local passed test Intersite
Starting test: FsmoCheck
Error: The server returned by DsGetDcName() did not match DsListRoles() for the PDC
......................... pcolo.local passed test FsmoCheck



Leider liegt ein entfernen aus der Domain nicht drin, da auf den DC's(PCM_SRV01 und PCZ-SRV01) von meinem Vorgänger Exchange installiert wurde!!!


REPLMON meldet zwischen PCM_SRV01 und PCZ-SRV01

Active Directory Replication Monitor
Printed on 06.10.2009 15:24:54
This report was generated on data from the server: PCM_SRV01

*
PCM_SRV01 Data
*

This server currently has writable copies of the following directory partitions:
CN=Schema,CN=Configuration,DC=pcolo,DC=local
CN=Configuration,DC=pcolo,DC=local
DC=pcolo,DC=local

Because this server is a Global Catalog (GC) server, it also has copies
of the following directory partitions:
Current NTDS Connection Objects
Standort-Z\PCZ-SRV01
Connection Name : 56ade0ac-efd1-41ba-b455-f8d809a3cdd4
Administrator Generated?: AUTO
Reasons for this connection:
Directory Partition (DC=pcolo,DC=local)

Directory Partition (CN=Configuration,DC=pcolo,DC=local)

Standort-M\PCM-SRV04
Connection Name : b160bccb-fcdb-4374-8f83-d38d19fb70e5
Administrator Generated?: AUTO
Reasons for this connection:
Directory Partition (DC=pcolo,DC=local)
Replicated because the replication partner is a ring neighbor.

Directory Partition (CN=Configuration,DC=pcolo,DC=local)
Replicated because the replication partner is a ring neighbor.

Directory Partition (CN=Schema,CN=Configuration,DC=pcolo,DC=local)
Replicated because the replication partner is a ring neighbor.


Current Direct Replication Partner Status
Directory Partition: CN=Schema,CN=Configuration,DC=pcolo,DC=local

Partner Name: Standort-Z\PCZ-SRV01
Partner GUID: D87D5917-DAA9-44F7-826C-C3D480F699E3
Last Attempted Replication: 10/6/2009 2:27:04 PM (local)
Last Successful Replication: 10/6/2009 2:27:04 PM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags: DRS_WRIT_REP,DRS_PER_SYNC,DRS_USE_COMPRESSION,DRS_NEVER_NOTIFY
USN of Last Property Updated: 3282240
USN of Last Object Updated: 3282240
Transport: Inter-Site RPC

Partner Name: Standort-M\PCM-SRV04
Partner GUID: 33CAD9F0-1CDA-45BE-9479-7B6BC8384FF8
Last Attempted Replication: 10/6/2009 3:01:59 PM (local)
Last Successful Replication: 10/6/2009 3:01:59 PM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 85079288
USN of Last Object Updated: 85079288
Transport: Intra-Site RPC

Directory Partition: CN=Configuration,DC=pcolo,DC=local

Partner Name: Standort-Z\PCZ-SRV01
Partner GUID: D87D5917-DAA9-44F7-826C-C3D480F699E3
Last Attempted Replication: 10/6/2009 2:27:34 PM (local)
Last Successful Replication: 10/6/2009 2:27:34 PM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags: DRS_WRIT_REP,DRS_PER_SYNC,DRS_USE_COMPRESSION,DRS_NEVER_NOTIFY
USN of Last Property Updated: 3282250
USN of Last Object Updated: 3282250
Transport: Inter-Site RPC

Partner Name: Standort-M\PCM-SRV04
Partner GUID: 33CAD9F0-1CDA-45BE-9479-7B6BC8384FF8
Last Attempted Replication: 10/6/2009 3:24:07 PM (local)
Last Successful Replication: 10/6/2009 3:24:07 PM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 85079288
USN of Last Object Updated: 85079288
Transport: Intra-Site RPC

Directory Partition: DC=pcolo,DC=local

Partner Name: Standort-Z\PCZ-SRV01
Partner GUID: D87D5917-DAA9-44F7-826C-C3D480F699E3
Last Attempted Replication: 10/6/2009 2:27:47 PM (local)
Last Successful Replication: 10/6/2009 2:27:47 PM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags: DRS_WRIT_REP,DRS_PER_SYNC,DRS_USE_COMPRESSION,DRS_NEVER_NOTIFY
USN of Last Property Updated: 3282256
USN of Last Object Updated: 3282256
Transport: Inter-Site RPC

Partner Name: Standort-M\PCM-SRV04
Partner GUID: 33CAD9F0-1CDA-45BE-9479-7B6BC8384FF8
Last Attempted Replication: 10/6/2009 3:23:07 PM (local)
Last Successful Replication: 10/6/2009 3:23:07 PM (local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed successfully.
Synchronization Flags: DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
USN of Last Property Updated: 85079288
USN of Last Object Updated: 85079288
Transport: Intra-Site RPC

Current Transitive Replication Partner Status
Directory Partition: CN=Schema,CN=Configuration,DC=pcolo,DC=local

Partner Name: Standort-M\PCM-SRV04
Partner GUID: 33CAD9F0-1CDA-45BE-9479-7B6BC8384FF8
USN: 85079288

Partner Name: Standort-M\PCM-SRV02
Partner GUID: B113732A-C1F7-43E6-A552-8FF6EE643175
USN: 15517

Partner Name: Standort-M\PCM_SRV01
Partner GUID: D6865F1F-E3DD-4692-BCBF-B281785A820C
USN: 6180355

Partner Name: Standort-Z\PCZ-SRV01
Partner GUID: D87D5917-DAA9-44F7-826C-C3D480F699E3
USN: 3282308

Partner Name: DELETED SERVER #1
Partner GUID: E33998E4-1A1B-402F-AC48-FBC86D5505A1
USN: 401423

Directory Partition: CN=Configuration,DC=pcolo,DC=local

Partner Name: Standort-M\PCM-SRV04
Partner GUID: 33CAD9F0-1CDA-45BE-9479-7B6BC8384FF8
USN: 85079288

Partner Name: Standort-M\PCM-SRV02
Partner GUID: B113732A-C1F7-43E6-A552-8FF6EE643175
USN: 15549

Partner Name: Standort-M\PCM_SRV01
Partner GUID: D6865F1F-E3DD-4692-BCBF-B281785A820C
USN: 6180355

Partner Name: Standort-Z\PCZ-SRV01
Partner GUID: D87D5917-DAA9-44F7-826C-C3D480F699E3
USN: 3282321

Partner Name:
DELETED SERVER #1
Partner GUID: E33998E4-1A1B-402F-AC48-FBC86D5505A1
USN: 401423

Directory Partition: DC=pcolo,DC=local

Partner Name: Standort-M\PCM-SRV04
Partner GUID: 33CAD9F0-1CDA-45BE-9479-7B6BC8384FF8
USN: 85079288

Partner Name: Standort-M\PCM-SRV02
Partner GUID: B113732A-C1F7-43E6-A552-8FF6EE643175
USN: 15549

Partner Name: Standort-M\PCM_SRV01
Partner GUID: D6865F1F-E3DD-4692-BCBF-B281785A820C
USN: 6180355

Partner Name: Standort-Z\PCZ-SRV01
Partner GUID: D87D5917-DAA9-44F7-826C-C3D480F699E3
USN: 3282321

Partner Name: DELETED SERVER #1
Partner GUID: E33998E4-1A1B-402F-AC48-FBC86D5505A1
USN: 401423

Current Group Policy Object Status
Auführen gesperrte Dateien
Group Policy Object GUID: {0A0C1DDE-062B-4303-8454-6B40CE4064C2}
Group Policy Object Version in the DS: 393222
Group Policy Object Version in SYSVOL: 393222

Default Domain Policy
Group Policy Object GUID: {31B2F340-016D-11D2-945F-00C04FB984F9}
Group Policy Object Version in the DS: 1507342
Group Policy Object Version in SYSVOL: 1507342

Office
Group Policy Object GUID: {33558006-8C6D-44B4-8C9B-410CCD4FD85A}
Group Policy Object Version in the DS: 786432
Group Policy Object Version in SYSVOL: 786432

perönliche Menüs
Group Policy Object GUID: {3695371A-BC7C-423C-99A5-3905EB385714}
Group Policy Object Version in the DS: 65536
Group Policy Object Version in SYSVOL: 65536

SUS-Config
Group Policy Object GUID: {58DE9933-A1BE-4D11-B203-498E3B1C441E}
Group Policy Object Version in the DS: 65544
Group Policy Object Version in SYSVOL: 65544

persönliche Menu
Group Policy Object GUID: {5992FBAD-0DAD-4BBC-8797-BFC023FD601A}
Group Policy Object Version in the DS: 262153
Group Policy Object Version in SYSVOL: 262153

Neues Gruppenrichtlinienobjekt
Group Policy Object GUID: {5ED723E0-044C-4D70-AB4E-B21B5BFFAD5F}
Group Policy Object Version in the DS: 0
Group Policy Object Version in SYSVOL: 0

Default Domain Controllers Policy
Group Policy Object GUID: {6AC1786C-016F-11D2-945F-00C04fB984F9}
Group Policy Object Version in the DS: 30
Group Policy Object Version in SYSVOL: 30

Office
Group Policy Object GUID: {6D16118B-6D09-43A8-A5A8-4AEA7E3E7C5E}
Group Policy Object Version in the DS: 720896
Group Policy Object Version in SYSVOL: 720896

Office_pcm-srv03
Group Policy Object GUID: {87BF1C6F-A42C-4539-A5A4-FAF9054D6EC1}
Group Policy Object Version in the DS: 131073
Group Policy Object Version in SYSVOL: 131073

Tastatur Layout
Group Policy Object GUID: {A36481D6-CC71-4822-B832-7A1163514375}
Group Policy Object Version in the DS: 0
Group Policy Object Version in SYSVOL: 0

Hotbar.exe
Group Policy Object GUID: {A3B1F29D-A67A-4730-958D-F22022E83124}
Group Policy Object Version in the DS: 8
Group Policy Object Version in SYSVOL: 8

TastaturLayout
Group Policy Object GUID: {A544B74A-7878-43F4-876E-8F702FB7CEA9}
Group Policy Object Version in the DS: 0
Group Policy Object Version in SYSVOL: 0

lokale Admin Rechte
Group Policy Object GUID: {C9968405-DAD4-40D5-9DF1-8A8526498116}
Group Policy Object Version in the DS: 2
Group Policy Object Version in SYSVOL: 2

Metaframe Einstellungen
Group Policy Object GUID: {D057EE3D-EF0D-4EF4-87FC-627521101321}
Group Policy Object Version in the DS: 131072
Group Policy Object Version in SYSVOL: 131072

PST
Group Policy Object GUID: {D91585D3-28A2-4390-978D-7FF025FFD372}
Group Policy Object Version in the DS: 0
Group Policy Object Version in SYSVOL: 0

SUS-Config
Group Policy Object GUID: {E63C09AD-9B6B-4386-B113-C450EE2B3BBC}
Group Policy Object Version in the DS: 131088
Group Policy Object Version in SYSVOL: 131088


The server PCM_SRV01 knows about the following FSMO roles:
Schema FSMO: Standort-M\PCM-SRV04
Domain Naming FSMO: Standort-M\PCM-SRV04
Infrastructure FSMO: Standort-M\PCM-SRV04
Primary Domain Controller FSMO: Standort-M\PCM_SRV01
RID Pool FSMO: Standort-M\PCM-SRV04

Performance Statistics at Time of Report
Configuration (Registry)
NOTE: an empty value indicates that Windows 2000 will use the internal default
NOTE: all empty values may indicate insufficient permission to retrieve this information from the domain controller
DSA
---

Days per Database Phantom Scan:
Initialize MAPI interface:
Enforce LIST_OBJECTS rights:
DSA Heuristics:
Max Threads (ExDS+NSP+DRA): 15
DSA Database file: C:\WINNT\NTDS\ntds.dit
DSA Working Directory: C:\WINNT\NTDS
Critical Object Installation:
DS Drive Mappings:
DSA Previous Restore Count:

REPLICATION
-----------

Replicator notify pause after modify (secs): 300
Replicator notify pause between DSAs (secs): 30
Replicator intra site packet size (objects):
Replicator intra site packet size (bytes):
Replicator inter site packet size (objects):
Replicator inter site packet size (bytes):
Replicator maximum concurrent read threads:
Replicator operation backlog limit:
Replicator thread op priority threshold:
Replicator intra site RPC handle lifetime (secs):
Replicator inter site RPC handle lifetime (secs):
Replicator RPC handle expiry check interval (secs):

LDAP
----

Max objects in LDAP Search (Admin Limit):
Max concurrent LDAP connections allowed:
Max time allowed for an LDAP Search:
Max concurrent LDAP searches allowed:
Max concurrent threads per LDAP connection allowed:
Minimum idle seconds before potential \ timeout of LDAP connection (non-authenticated client):
Minimum idle seconds before potential \ timeout of LDAP connection (authenticated client):

Database
--------

Database backup path: C:\WINNT\NTDS\dsadata.bak
Database backup interval (hours):
Database log files path: C:\WINNT\NTDS
Database logging/recovery: ON
Hierarchy Table Recalculation interval (minutes): 720
Database restored from backup:
Pending object ownership conversions:
EDB max buffers:
EDB max log buffers:
EDB log buffer flush threshold:
EDB buffer flush start:
EDB buffer flush stop:
EDB max ver pages (increment over the minimum:
Circular Logging:
Server Functionality:
TCP/IP Port:
Restore from disk backup:
Performance Counter Version: 10

KCC
---

Repl topology update delay (secs):
Repl topology update period (secs):
KCC site generator fail-over (minutes):
KCC site generator renewal interval (minutes):
KCC site generator renewal interval (minutes):
CriticalLinkFailuresAllowed:
MaxFailureTimeForCriticalLink (sec):
NonCriticalLinkFailuresAllowed:
MaxFailureTimeForNonCriticalLink (sec):
IntersiteFailuresAllowed:
MaxFailureTimeForIntersiteLink (sec):
KCC connection failures:
IntersiteFailuresAllowed:
IntersiteFailuresAllowed:

*
Enterprise Data
***

Globally Unique Identifiers (GUIDs) for each domain controller in the enterprise
NOTE: the absence of a GUID means that the server has been demoted.
Site Name: Standort-M
---------------------------------------
Site Options :
Site Topology Generator: CN=NTDS Settings,CN=PCM_SRV01,CN=Servers,CN=Standort-M,CN=Sites,CN=Configuration,DC=pcolo,DC=local
Site Topology Renewal :
Site Topology Failover :

PCM_SRV01
Server GUID (used for DNS) : 269B76BA-3B23-41A6-840A-B058D15CF73E
Replication Database GUID (used to identify partner in replication): D6865F1F-E3DD-4692-BCBF-B281785A820C
DSA Options : NTDSDSA_OPT_IS_GC
DSA Computer Path : CN=PCM_SRV01,OU=Domain Controllers,DC=pcolo,DC=local
DSA Schema Location : CN=Schema,CN=Configuration,DC=pcolo,DC=local
DSA Mail Address : _IsmService@269b76ba-3b23-41a6-840a-b058d15cf73e._msdcs.pcolo.local
DSA DNS Host Name : pcm_srv01.pcolo.local
DSA BridgeHead Transports :
SMTP
IP

PCM-SRV04
Server GUID (used for DNS) : 33CAD9F0-1CDA-45BE-9479-7B6BC8384FF8
Replication Database GUID (used to identify partner in replication): 33CAD9F0-1CDA-45BE-9479-7B6BC8384FF8
DSA Options :
DSA Computer Path : CN=PCM-SRV04,OU=Domain Controllers,DC=pcolo,DC=local
DSA Schema Location : CN=Schema,CN=Configuration,DC=pcolo,DC=local
DSA Mail Address :
DSA DNS Host Name : pcm-srv04.pcolo.local
DSA BridgeHead Transports :


Site Name: Standort-Z
---------------------------------------
Site Options :
Site Topology Generator: CN=NTDS Settings,CN=PCZ-SRV01,CN=Servers,CN=Standort-Z,CN=Sites,CN=Configuration,DC=pcolo,DC=local
Site Topology Renewal :
Site Topology Failover :

INTREXXSRV
Server GUID (used for DNS) :
Replication Database GUID (used to identify partner in replication):
DSA Options :
DSA Computer Path : CN=INTREXXSRV,OU=Rechner PCZ,OU=Standort-Z,DC=pcolo,DC=local
DSA Schema Location :
DSA Mail Address :
DSA DNS Host Name : intrexxsrv.pcolo.local
DSA BridgeHead Transports :

PCZ-SRV01
Server GUID (used for DNS) : 62C97FA8-029D-4A3B-AD6E-CCB531AC6930
Replication Database GUID (used to identify partner in replication): D87D5917-DAA9-44F7-826C-C3D480F699E3
DSA Options : NTDSDSA_OPT_IS_GC
DSA Computer Path : CN=PCZ-SRV01,OU=Domain Controllers,DC=pcolo,DC=local
DSA Schema Location : CN=Schema,CN=Configuration,DC=pcolo,DC=local
DSA Mail Address : _IsmService@62c97fa8-029d-4a3b-ad6e-ccb531ac6930._msdcs.pcolo.local
DSA DNS Host Name : pcz-srv01.pcolo.local
DSA BridgeHead Transports :



Site Links and Site Link Bridges
Site Links
----------

DEFAULTIPSITELINK
Link Type: : IP
Distinguished Name : CN=DEFAULTIPSITELINK,CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=pcolo,DC=local
Replication Interval : 180
Cost : 100
Options :
Site List :
Standort-Z
Standort-M

Site Link Bridges
------------------

Active Directory Replication Monitor determined that no Site Link Bridges are present in the Directory.
Inter-Site Transports
---------------------

IP
Options :
DLL Name : ismip.dll
Address Type: dNSHostName

SMTP
Options : NTDSTRANSPORT_OPT_IGNORE_SCHEDULES
DLL Name : ismsmtp.dll
Address Type: mailAddress

Subnets
-------
192.168.1.0/24
Associated Site : CN=Standort-M,CN=Sites,CN=Configuration,DC=pcolo,DC=local

192.168.2.0/24
Associated Site : CN=Standort-Z,CN=Sites,CN=Configuration,DC=pcolo,DC=local

Active Directory Configuration Data
-----------------------------------
Stay of Execution for Servers: 0
SPN Mappings : host=alerter,appmgmt,cisvc,clipsrv,browser,dhcp,dnscache,replicator,eventlog,eventsystem,policyagent,oakley,dmserver,dns,mcsvc,fax,msiserver,ias,messenger,netlogon,netman,netdde,netddedsm,nmagent,plugplay,protectedstorage,rasman,rpclocator,rpc,rpcss,remoteaccess,rsvp,samss,scardsvr,scesrv,seclogon,scm,dcom,cifs,spooler,snmp,schedule,tapisrv,trksvr,trkwks,ups,time,wins,www,http,w3svc,iisadmin




hab ich noch irgendwelche Chancen??? Bin für sämtliche Hilfe überaus dankbar!
Mitglied: 2hard4you
06.10.2009 um 21:14 Uhr
Moin,

haste ne Kiste, worauf Du die Exchange verschieben kannst?

Mein Idee wäre folgende...

die ESXe mit allen Mailboxen / Routinggroups etc. dort wegnehmen

FSMO - Rollen (Wo?) checken

dann ein depromo machen

Eventlog checken ggf, sogar die zwei Server aus dem AD werfen, ggf. neu aufbauen

und dann sie *frisch* wieder reinnehmen....

iss ein WE Arbeit, aber auch ein Weg

Gruß

24
Bitte warten ..
Mitglied: benscha
06.10.2009 um 21:30 Uhr
Hi 24

Danke für deinen Tipp! Leider hab ich keine weitere Exchanges wohin ich die Postfächer moven kann!! ( Auch ist ein Versuch gescheitert ein PF vom einen auf den anderen Exch zu bewegen! /

mir ist aber noch folgendes aufgefallen!

auf pcm_srv01 ist der Container Domain Controllers leer wenn ich dsa.msc aufrufe!! Zudem finde ich jetzt im eventlog, ca. alle 5min., folgenden Fehler:

Ein SPN (Service Principal Name) mit gegenseitiger Authentifizierung für den Server 60e5d2f1-fac7-43fd-ba95-d0357007a4e1._msdcs.pcolo.local konnte nicht erstellt werden. Der Aufruf wurde verweigert. Fehler:
Das DSA-Objekt wurde nicht gefunden.

habe schon probiert die GUID aufzulösen leider auch ohne Erfolg!


Danke für jeden Tipp...
Bitte warten ..
Mitglied: benscha
06.10.2009 um 21:44 Uhr
Das gibt mir repadmin aus:

repadmin /showreps
Standort-M\PCM_SRV01
DSA Options : IS_GC
objectGuid : 269b76ba-3b23-41a6-840a-b058d15cf73e
invocationID: d6865f1f-e3dd-4692-bcbf-b281785a820c

INBOUND NEIGHBORS

CN=Schema,CN=Configuration,DC=pcolo,DC=local
Standort-Z\PCZ-SRV01 via RPC
objectGuid: 62c97fa8-029d-4a3b-ad6e-ccb531ac6930
Last attempt @ 2009-10-06 20:05.16 was successful.
Standort-M\PCM-SRV04 via RPC
objectGuid: 33cad9f0-1cda-45be-9479-7b6bc8384ff8
Last attempt @ 2009-10-06 20:50.05 was successful.

CN=Configuration,DC=pcolo,DC=local
Standort-Z\PCZ-SRV01 via RPC
objectGuid: 62c97fa8-029d-4a3b-ad6e-ccb531ac6930
Last attempt @ 2009-10-06 20:05.16 was successful.
Standort-M\PCM-SRV04 via RPC
objectGuid: 33cad9f0-1cda-45be-9479-7b6bc8384ff8
Last attempt @ 2009-10-06 21:32.12 was successful.

DC=pcolo,DC=local
Standort-Z\PCZ-SRV01 via RPC
objectGuid: 62c97fa8-029d-4a3b-ad6e-ccb531ac6930
Last attempt @ 2009-10-06 20:05.16 was successful.
Standort-M\PCM-SRV04 via RPC
objectGuid: 33cad9f0-1cda-45be-9479-7b6bc8384ff8
Last attempt @ 2009-10-06 21:32.42 was successful.

OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS

CN=Schema,CN=Configuration,DC=pcolo,DC=local
Standort-M\PCM-SRV04 via RPC
objectGuid: 33cad9f0-1cda-45be-9479-7b6bc8384ff8
Standort-Z\PCZ-SRV01 via RPC
objectGuid: 62c97fa8-029d-4a3b-ad6e-ccb531ac6930
(null) via RPC
objectGuid: 60e5d2f1-fac7-43fd-ba95-d0357007a4e1

CN=Configuration,DC=pcolo,DC=local
Standort-M\PCM-SRV04 via RPC
objectGuid: 33cad9f0-1cda-45be-9479-7b6bc8384ff8
(null) via RPC
objectGuid: 60e5d2f1-fac7-43fd-ba95-d0357007a4e1

DC=pcolo,DC=local
Standort-M\PCM-SRV04 via RPC
objectGuid: 33cad9f0-1cda-45be-9479-7b6bc8384ff8
(null) via RPC
objectGuid: 60e5d2f1-fac7-43fd-ba95-d0357007a4e1
Bitte warten ..
Mitglied: 2hard4you
06.10.2009 um 22:16 Uhr
Moin,

hast Du ein aktuelles Backup, inkl. Systemstate?

und sehr wichtig wäre, hast Du Blech, wo Du mal was hochziehen kannst?

Gruß

24
Bitte warten ..
Neuester Wissensbeitrag
Humor (lol)

Linkliste für Adventskalender

(3)

Information von nikoatit zum Thema Humor (lol) ...

Ähnliche Inhalte
Windows Server
AD Replikation zwischen untergeordneten Domäne zwingend? (1)

Frage von Gien-app zum Thema Windows Server ...

Windows Server
AD DC Failover zeitintensiv und DHCP repliziert nicht (2)

Frage von JiggyLee zum Thema Windows Server ...

Windows Userverwaltung
AD Gruppe der Domänen-Admins überwachen (5)

Frage von ThorstenRay zum Thema Windows Userverwaltung ...

Microsoft
AD Problem und VPN (4)

Frage von Yannosch zum Thema Microsoft ...

Heiß diskutierte Inhalte
Exchange Server
gelöst Exchange 2010 Berechtigungen wiederherstellen (20)

Frage von semperf1delis zum Thema Exchange Server ...

Windows Server
DHCP Server switchen (20)

Frage von M.Marz zum Thema Windows Server ...

Hardware
gelöst Negative Erfahrungen LAN-Karten (19)

Frage von MegaGiga zum Thema Hardware ...

Exchange Server
DNS Einstellung - zwei feste IPs für Mailserver (15)

Frage von ivan0s zum Thema Exchange Server ...