Are these the only two errors you received? I encountered similar errors during beta testing when I implemented R2 in an existing forest - but a lot more than just 2. :) I created a secondary forest and validated that it did not recur. Note that I also had SFU installed in the original forest and the new secondary forest.
I was able to clean up the schema in the existing forest exhibiting the errors but it was a fairly painful process of what seemed to be a goose chase. The tasks included disabling objects attributes in the schema and renaming them amongst other things. Fortunately I have not heard of this happening in production...yet. So can these errors be ignored? If I remember correctly ADPrep is actually failing and therefore NO you cannot ignore these errors since ADPREP will nto occur until they are resolved. Regards, Aric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thommes, Michael M. Sent: Wednesday, February 15, 2006 5:22 PM To: [email protected] Subject: [ActiveDir] issue with R2 upgrade; SFU confusion? Hi, We did a adprep /forestprep from the W2K3/SP1 R2 Disk 2 CD today on our testbed FSMO DC. It gave the following errors (only a portion shown below) because, I am guessing, that we had already installed SFU 3.5 on this forest some time ago. Should I assume these errors can be ignored? Has anybody else experienced this? Thanks as always! Mike Thommes ==================================================================== "attributeId" attribute value for objects defined in Windows 2000 schema and ext ended schema do not match. A previous schema extension has defined the attribute value as "1.2.840.113556.1 .4.7000.187.70" for object "CN=uidNumber,CN=Schema,CN=Configuration,DC=anl,DC=go v" differently than the schema extension needed for Windows 2003 server . [Status/Consequence] Adprep cannot extend your existing schema [User Action] Contact the vendor of the application that previously extended the schema to res olve the inconsistency. Then run adprep again. ======================================================================== ===== "attributeId" attribute value for objects defined in Windows 2000 schema and ext ended schema do not match. A previous schema extension has defined the attribute value as "1.2.840.113556.1 .4.7000.187.71" for object "CN=gidNumber,CN=Schema,CN=Configuration,DC=anl,DC=go v" differently than the schema extension needed for Windows 2003 server . [Status/Consequence] Adprep cannot extend your existing schema [User Action] Contact the vendor of the application that previously extended the schema to res olve the inconsistency. Then run adprep again. List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
