Re: Server 2003 R2 -Disk 2 Adprep problem

Thanks Danny,
Good to know anyway.
We need to implement DFS so I had to get this thru.
FYI: Got a hotfix from MS that makes the necessary schema changes.
Re. KB Article Number(s): 919938

Regards,

John.

"Danny Sanders" wrote:

I'd be interested to know if you have you installed R2 without second disk
and achieved full DC functionality?

Yes. It's a Win 2k3 SP 1 DC. It's exactly the same server as if we had
installed from a Win 2k3 CD and down loaded SP 1.

We had some Win 2k3 SP1 DCs in branch offices that were *not* installed
using the first disk of the R2 set and we wanted them to replicate data back
here. All we had to do was run setup2 from the second disk of the R2 set on
those DCs and we got the updated DFSR features.

. Distributed File System (DFS) Replication Service

. Domain controllers running Windows Server 2003 R2

. Identity Management for UNIX

. The Deployed Printers functionality of the Print Management console

We did not need these on some of the DCs so we did not use the second disk.
If you are not going to use any of the R2 features on any server on your
domain you don't need to extend the schema by using disk 2 of the R2 set or
install the second disk.

We do use the DFSR features on other server on our domain so we had to do
the schema update, but we only installed the updated features where needed.

hth
DDS

"jprstokato" <jprstokato@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6B2E0E1C-C97F-46CE-B0F9-14F5DA0E2773@xxxxxxxxxxxxxxxx
Hi Danny,

Thanks for your response, and yes,I realise I have a functional R2 server
as
such.

However, accordiing to Technet....

Some features and server roles in Windows Server 2003 R2 require
corresponding updates to the Active Directory schema. These schema
additions
are automatically installed when you use Windows Server 2003 R2
installation
media to create an Active Directory forest.
In forests that contain the Windows 2000 or Windows Server 2003 schema,
you
must use the Windows Server 2003 R2 Adprep tool to add the Windows Server
2003 R2 schema additions to Active Directory before you deploy the
following
features or server roles:

. Distributed File System (DFS) Replication Service

. Domain controllers running Windows Server 2003 R2

. Identity Management for UNIX

. The Deployed Printers functionality of the Print Management console

http://technet2.microsoft.com/WindowsServer/en/library/f9d70026-ae8b-4969-8755-1ea1edc4e38e1033.mspx?mfr=true

This denotes that you require the full installation for DCs t work. We
aslo
have Unix interoperability.
I'd be interested to know if you have you installed R2 without second disk
and achieved full DC functionality?

"Danny Sanders" wrote:

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: Schema Update.
    ... You don't need to update the schema in this scenario. ... Windows Server MVP - Directory Services ... If i do not integrate the RightFAX with AD, i would have to create equally ...
    (microsoft.public.windows.server.active_directory)
  • Re: Running Wn2000 DC alongside Win2003 DC
    ... The schema needs to be extended to accommodate ... Microsoft MVP Windows Server - Active Directory ... >> extend AD schema and then do the upgrade. ...
    (microsoft.public.win2000.active_directory)
  • Re: Server 2003 R2 -Disk 2 Adprep problem
    ... Domain controllers running Windows Server 2003 R2 ... the schema update, but we only installed the updated features where needed. ... This denotes that you require the full installation for DCs t work. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows Server 2003 R2 - DFS errors 6012, 1202 ?
    ... Please read the setup file from the R2 CD regarding the schema update of SP1 ... Microsoft MVP: Windows Server ... Is the R2 server configured as a member server of a SP1 DC? ...
    (microsoft.public.windows.server.general)
  • 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)