Schema replication

[Carma Trepp]

Hi all

I have a basically question. When I make a Schema edit (on the Schema
Master), gets this replicated to the other DC`s?

I have currently Problems with the replication, and replmon says me the
Schema between the DC`s is different.

Greetings
Carma

 

[Neil Ruston]

The answer is 'yes'. Objects may be created on any DC in
the forest and they all therefore need an up to date copy
of the Schema partition.

Each DC in the forest holds a read only copy, whilst the
Schema Master role holder DC has the only the read-write
copy.

Please post additional information regarding your
replication issues.

HTH,
Neil

 

[Tim Hines, MCSA, MCSE]

Whenever you update the schema, the changes will be replicated to all domain
controllers in the forest. If there is a schema mismatch in the domain then
you should troubleshoot AD replication. You should run repadmin /showreps
on your DCs to whether or not replication is working. Repadmin will give
you a reason for replication failures. You can also continue to use replmon
to look for replication failure errors. They both provide similar
information. Post any errors in the newsgroup for additional assistance.


--
--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Carma Trepp]

Thank you for your informations guys

Hmm.. I have testet the replication with replmon --> (Search
Domaincontrollers for Replication Failtures)
The log looks very good.
---------------------------------------------------------------------
Active Directory Replication Domain Controller Replication Failure Output
Printed at 24.09.2003 17:29:36

Below are the replication failures detected on Domain Controllers for
this domain:

Domain Controller Name: CBSV0
Directory Partition: CN=Configuration,DC=cirrus,DC=ch
Replication Partner: Bern\CBSVXB
Failure Code: 8418
Failure Reason: Der Replikationsvorgang ist
fehlgeschlagen, da Schemas unter den beteiligten Servern nicht
übereinstimmten.

Domain Controller Name: CBSV0
Directory Partition: DC=cirrus,DC=ch
Replication Partner: Bern\CBSVXB
Failure Code: 8418
Failure Reason: Der Replikationsvorgang ist
fehlgeschlagen, da Schemas unter den beteiligten Servern nicht
übereinstimmten.

Domain Controller Name: CBSVXB
Directory Partition:
CN=Schema,CN=Configuration,DC=cirrus,DC=ch
Replication Partner: Bern\CBSV0
Failure Code: 8453
Failure Reason: Der Replikationszugriff wurde
verweigert.

Domain Controller Name: CBSVXB
Directory Partition: CN=Configuration,DC=cirrus,DC=ch
Replication Partner: Bern\CBSV0
Failure Code: 8418
Failure Reason: Der Replikationsvorgang ist
fehlgeschlagen, da Schemas unter den beteiligten Servern nicht
übereinstimmten.

Domain Controller Name: CBSVXB
Directory Partition: DC=cirrus,DC=ch
Replication Partner: Bern\CBSV0
Failure Code: 8418
Failure Reason: Der Replikationsvorgang ist
fehlgeschlagen, da Schemas unter den beteiligten Servern nicht
übereinstimmten.
------------------------------------------------------------------------
The line "Der Replikationsvorgang ist fehlgeschlagen, da Schemas unter
den beteiligten Servern nicht übereinstimmten" means the replication is
failed, because the schema between the DC`s is different.

dcdiag on one of the DC`s say me:
------------------------------------------------------------------------
DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Bern\CBSVXB
Starting test: Connectivity
......................... CBSVXB passed test Connectivity

Doing primary tests

Testing server: Bern\CBSVXB
Starting test: Replications
[Replications Check,CBSVXB] A recent replication attempt failed:
From CBSV0 to CBSVXB
Naming Context: CN=Schema,CN=Configuration,DC=cirrus,DC=ch
The replication generated an error (8453):
Replication access was denied.
The failure occurred at 2003-09-25 15:06.45.
The last success occurred at 2003-08-29 10:45.56.
16396 failures have occurred since the last success.
The machine account for the destination CBSVXB.
is not configured properly.
Check the userAccountControl field.
Kerberos Error.
The machine account is not present, or does not match on the.
destination, source or KDC servers.
Verify domain partition of KDC is in sync with rest of
enterprise.
The tool repadmin/syncall can be used for this purpose.
REPLICATION LATENCY WARNING
CBSVXB: This replication path was preempted by higher priority
work.
from CBSV0 to CBSVXB
Reason: The replication operation failed because of a
schema mismatc
h between the servers involved.
The last success occurred at 2003-08-29 16:29.25.
Replication of new changes along this path will be delayed.
REPLICATION LATENCY WARNING
CBSVXB: This replication path was preempted by higher priority
work.
from CBSV0 to CBSVXB
--------------------------------------------------------------------------

And repadmin /showreps displays that:
---------------------------------------------------------------------------
Bern\CBSV0
DSA Options : IS_GC
objectGuid : 19a57e43-6f5e-49a1-83ac-ed079602a27c
invocationID: 19a57e43-6f5e-49a1-83ac-ed079602a27c

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=cirrus,DC=ch
Bern\CBSVXB via RPC
objectGuid: 8de00047-facc-4e06-b533-bd6be1711240
Last attempt @ 2003-10-03 10:52.14 was successful.

CN=Configuration,DC=cirrus,DC=ch
Bern\CBSVXB via RPC
objectGuid: 8de00047-facc-4e06-b533-bd6be1711240
Last attempt @ 2003-10-03 11:09.33 failed, result 8418:
The replication operation failed because of a schema
mismatch betwee
n the servers involved.
Last success @ 2003-08-29 16:38.15.
0 consecutive failure(s).

DC=cirrus,DC=ch
Bern\CBSVXB via RPC
objectGuid: 8de00047-facc-4e06-b533-bd6be1711240
Last attempt @ 2003-10-03 11:06.24 failed, result 8418:
The replication operation failed because of a schema
mismatch betwee
n the servers involved.
Last success @ 2003-08-29 16:37.21.
0 consecutive failure(s).

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=cirrus,DC=ch
Bern\CBSVXB via RPC
objectGuid: 8de00047-facc-4e06-b533-bd6be1711240

CN=Configuration,DC=cirrus,DC=ch
Bern\CBSVXB via RPC
objectGuid: 8de00047-facc-4e06-b533-bd6be1711240

DC=cirrus,DC=ch
Bern\CBSVXB via RPC
objectGuid: 8de00047-facc-4e06-b533-bd6be1711240
---------------------------------------------------------------------------
Hmm.. but I have no resolution. We have enlarged the schema on the DC
with the schemamaster role.
And now we have many problems when we create new users (regarding also
exchange)