Schema Extension to 2003 R2

While trying to extend the schema to R2 in preparation for DFS R2 there are several similar entries after running adprep /forestprep.  All 2000 DC's are sp4, all 2003 DC's are sp1 - the only previous extensions that I know of were the addition of a 2003 DC, and BioLogin (fingerprint readers).

c:\@Data\ADPREP>adprep /forestprep

ADPREP WARNING:

Before running adprep, all Windows 2000 domain controllers in the forest should
be upgraded to Windows 2000 Service Pack 1 (SP1) with QFE 265089, or to Windows
2000 SP2 (or later).

QFE 265089 (included in Windows 2000 SP2 and later) is required to prevent poten
tial domain controller corruption.

For more information about preparing your forest and domain see KB article Q3311
61 at http://support.microsoft.com.

[User Action]
If ALL your existing Windows 2000 domain controllers meet this requirement, type
 C and then press ENTER to continue. Otherwise, type any other key and press ENT
ER to quit.


c\

=============================================================================
"lDAPDisplayName" attribute value for objects defined in Windows 2000 schema and
 extended schema do not match.


A previous schema extension has defined the attribute value as "DUP-uid-e378b4a9
-c6fe-48cb-af5f-735cc90202d2" for object "CN=uid,CN=Schema,CN=Configuration,DC=b
ankersbank,DC=corp" differently than the schema extension needed for Windows 200
3 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.70" for object "CN=uidNumber,CN=Schema,CN=Configuration,DC=bankersba
nk,DC=corp" 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.


There are several more of these I can post upon request - also the dcdiag and netdiags look good.  Any help is most appreciated.