Schema Mismatch
 




IT Certification FAQ

 
|
Home
|
Microsoft
|
CISCO
|
CompTIA
|
Exam/Study FAQ
|
Employment FAQ
| Links  | Forums  |
Book Reviews


FAQFAQ  SearchSearch  MemberlistMemberlist  UsergroupsUsergroups  RegisterRegister  ProfileProfile  Log in to check your private messagesPrivate messages  Log inLog in

Schema Mismatch

 
Post new topic   Reply to topic    Forum Index -> microsoft.public.windows.server.active_directory
Author Message
JRM
Guest





PostPosted: Wed May 17, 2006 8:45 pm    Post subject: Schema Mismatch Reply with quote

We updated our domain from 2000 functional to 2003 functional. All DCs
except one worked just fine. Afterwards this one domain wouldn't replicate
and if you tried to force it in replmon or with repadmin it gave a 'schema
mismatch' error. Fairly easy to figure out that it didn't get the schema
update. In this case I did a dcpromo down and a dcpromo back up. I was
wondering though, for future reference, is there a way to

a) Check the schema of server A versus server B
b) Force the schema to replicate again

This is a fairly uncommon item for us as we don't make many manual changes,
but it seems that this functionality must be built in somewhere - although
I'm not able to easily find it.

Thanks in advance

Jason
Back to top
Joe Richards [MVP]
Guest





PostPosted: Thu May 18, 2006 5:11 am    Post subject: Re: Schema Mismatch Reply with quote

The schema mismatch errors should have cleared up on their own. When you first
apply a schema you actually start seeing those errors thrown on every DC until
the schema fully replicates.

As for your specific questions

A. Depends on what you are trying to compare. If every single attribute then you
need to dump the schemas and do a text comparison on them. I have a special
switch in adfind specifically to get a comparable dump called -sc sdump or -sc
sdump:csv

If you are just looking for overall schema rev versions then you can look at the
schema NC Head version number.

B. Again you don't have to, it will do it on its own. All replication on a DC
will be blocked until the schema fully replicates and is in sync with the
partner it is trying to replicate with. One of the first things done when two
DCs connect to each other to replicate is they exchange Schema NC update info so
they know they are on the same page.

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm



JRM wrote:
Quote:
We updated our domain from 2000 functional to 2003 functional. All DCs
except one worked just fine. Afterwards this one domain wouldn't replicate
and if you tried to force it in replmon or with repadmin it gave a 'schema
mismatch' error. Fairly easy to figure out that it didn't get the schema
update. In this case I did a dcpromo down and a dcpromo back up. I was
wondering though, for future reference, is there a way to

a) Check the schema of server A versus server B
b) Force the schema to replicate again

This is a fairly uncommon item for us as we don't make many manual changes,
but it seems that this functionality must be built in somewhere - although
I'm not able to easily find it.

Thanks in advance

Jason
Back to top
Display posts from previous:   
Post new topic   Reply to topic    Forum Index -> microsoft.public.windows.server.active_directory All times are GMT
Page 1 of 1

 

Copyright © 2002-2006 Web-S-Sense Pty. Ltd. All rights reserved.

Powered by phpBB
Advertising | Policies/Disclaimers | Contact us | Link to us


Featured Sites: Free Antivirus and Antispyware Info | Free PC Support | MCSE Directory