Re: Server 2003 R2 -Disk 2 Adprep problem

You do realize that the second disk of the R2 set is only some updated
features that only need to be installed if you want to use those features.
Without installing the second disk you have a Win 2k3 Sp1 server.

hth
DDS

"jprstokato" <jprstokato@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7EA992AC-4EED-45D4-9038-47CB21E95AA4@xxxxxxxxxxxxxxxx
Hi,

As instructed by an error message from the setup on Windows Server 2003 R2
(disk2), I attempted to run adprep from d:\cmpnents\r2\adprep, with the
following output:

=============================================================================
"attributeId" 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
"1.2.840.113556.1.4.7000.187.70" for object
"CN=uidNumber,CN=Schema,CN=Configuration,DC=....,DC=....,DC=....."
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
resolve the inconsistency. Then run adprep again.

=============================================================================
29 other attributes are similarly affected: gidNumber,gecos, loginShell,
shadowLastChange....and so on..

I have done some research and found that these changes have likley been
made by Windows Services for unix (SFU), (at some point before I joined
this
company)

R2 adprep seems to want to make changes as listed in in the SCH31.ldf (on
the R2 disk 2) e.g for this attribute:

dn: CN=UidNumber,CN=Schema,CN=Configuration,DC=X
changetype: ntdsSchemaAdd
objectClass: attributeSchema
ldapDisplayName: uidNumber
adminDisplayName: uidNumber
adminDescription: An integer uniquely identifying a user in an
administrative domain (RFC 2307)
attributeId: 1.3.6.1.1.1.1.0
attributeSyntax: 2.5.5.9
omSyntax: 2
isSingleValued: TRUE
systemOnly: FALSE
searchFlags: 1
schemaIdGuid:: j8wPhWuc4Ue2cXxlS+TVsw==
showInAdvancedViewOnly: TRUE


clearly there is a conflicting Attribute ID.

One forum article cites 'renaming CN and ldapdisplayname' for the
attributes. However the return message on attempting this is: "the
attribute
cannot be modified because it is owned by the system"

I have also tried setting the attributes to 'defunct' (another suggestion)
which does not alter the output from adprep

The second R2 disc must be successfully run, and therefore this adprep
needs
to be applied. Adprep from disk 1 prepared the forest and domain (after
applying some changes both for Exchange and Cisco Callmanager), and Server
2003 has installed up to Disk 1, and I thought we were home and dry until
I
continued with the second disk and encountered yet more schema
discrepancies.

Can you please help with a suggestion on how I might solve this problem as
it is becoming a real headache!

Thanks and regards,
John.
MCSE, CCNA




.

Relevant Pages

  • Re: Administration Tools Pack
    ... 2k3 R2 you would have to run adprep from the first CD of the R2 set to prepare the Win 2k schema for Win 2k3 and you would have to run adprep from the second disk of the R2 set to prepare the schema for the R2 features. ... Try running adprep from the second disk of the R2 set on the schema master, then try to install the tools. ...
    (microsoft.public.windows.server.setup)
  • Re: DCPROMO error message
    ... use ADPREP from the second disk to apply the R2 schema ... # Jorge de Almeida Pinto # MVP Windows Server - Directory Services ... the adprep /forestprep & adprep /domainprep on our existing domain ... "The version of the Active Directory schema of the source forest is not ...
    (microsoft.public.windows.server.active_directory)
  • Re: Server 2003 R2 -Disk 2 Adprep problem
    ... Got a hotfix from MS that makes the necessary schema changes. ... Domain controllers running Windows Server 2003 R2 ... We did not need these on some of the DCs so we did not use the second disk. ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 AD upgrade to R2...
    ... Extending the schema to a new version is common and needed practise to add newer OS DC's to a forest/domain. ... So you have NOT to run the setup2.exe from the second disk set on the existing ... And also the setup2.exe on the second disk will only install the additional tools. ...
    (microsoft.public.windows.server.setup)
  • Re: Administration Tools Pack
    ... do you just put the cd in, navigate to the adprep folder then click on ... from the second disk of the R2 set to prepare the schema for the R2 ... R2 set on the schema master, then try to install the tools. ... from the ADMIN folder of CD2. ...
    (microsoft.public.windows.server.setup)
Loading