Also note you could use the schema documentation tool found
here: http://msdn.microsoft.com/library/default.asp?url="">
if you feel that you may have a schema extension referring to this attribute as
well. Simply look at the containedIn field for UID. Thanks, -Steve From: Steve Linehan Unless something else has extended the schema you should be able
to look at the definition in MSDN and find the classes it is used in: http://msdn.microsoft.com/library/default.asp?url="">
in your case you only care about the 2003 classes since that is the version of
the schema that you are running. Remember to put these back once you are
finished and of course as always test your procedure in a test environment to
ensure success in production. Thanks, -Steve From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of WATSON, BEN Hello
all, I am at the point
where I now have a smooth running Windows 2003 forest and domain with the one
exception of the UID attribute which I bypassed thanks to the hidden ADPREP switch
Steve informed me of. So I am now
attempting to go back and defunct this UID attribute so I can repair it.
Unfortunately, I am unable to do so at this point. When attempting to defunct
the object through Active Directory Schema, I receive an error stating it
cannot be done because, "this schema object may be in use as part of the
definition of another schema object". When attempting to set the
isDefunct attribute within UID to TRUE via ADSIEDIT, I receive a more
informative error,"Schema deletion failed: attribute is used in
may-contain." How can I find out
which attributes have UID as part of the may-contain attribute so I can defunct
this attribute? If you might have any further advice for me I would
greatly appreciate it. I've been doing my
best to study the schema over the past few days thanks to Joe's Active
Directory book, however I'll readily admit that advanced searching and
filtering are still beyond my grasp at this point. Thanks, ~Ben From:
[EMAIL PROTECTED] on behalf of Steve Linehan Ben, a. Open ldp on
the Schema FSMO (make sure you have Checked the option "The Schema may be modified
on this Domain Controller" using the Schema Manager Snap-in). This should allow the roomNumber attribute in the base Windows
Server 2003 Schema to be imported. You would of course need to update the
third party application to point to the renamed attribute or import the data in
the OldRoomNumber attribute to the new RoomNumber attribute and hope that none
of the values were multivalued and that the application was not referring to it
by OID. Next you need to address the syntax of the UID attribute.
We are expecting the syntax to be String (Unicode) 2.5.5.12 not String
(Printable) 2.5.5.5. This problem is tougher as there is not a supported
way to change the syntax of an attribute and renaming it will not work since
the OID is the one we are expecting, yes there are ways it can be done but it
would leave you in an unsupportable state. To fix this issue I would
recommend running ADPREP /forestprep /nosyntaxcheck, yes this is a hidden
switch and should only be used in cases where one cannot make changes to the
conflicting attribute to make it compliant with the base schema also note you
must be using ADPREP from SP1 or a QFE that was used to distribute adprep from SP1
to use this switch. You can then upgrade to Windows Server 2003 and after
this is successful then take the forest to Windows Server 2003 Forest
Functional Level which will allow you to defunct this attribute and fix it to
match the expected definition. Note in both cases you may break the third
party application that defined these values that are in conflict. I would
suggest testing to ensure that the third party application works after making
the above changes or that steps are taken to mitigate the loss of functionality
in the third party application. I would also suggest opening a case with
Microsoft Support if further assistance or issues arise and fully testing
before doing any of this in production. Thanks, -Steve From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of WATSON, BEN To try and answer everyone’s question all at once… At this point, we don’t have Exchange running in our test
environment, we do have copies of the servers there, but have not re-added them
to the domain to bring them up. I don’t think that having the actual
Exchange servers online should really matter at this point since all that
FORESTPREP is attempting to do is extend the schema which already contain the
extensions that Exchange 2003 had made previously. Mark, yes, I am absolutely sure SFU had not been installed or more
importantly, ever extended the schema. Just to be sure, I contacted
Microsoft this morning and requested the hotfix for it and when I ran it, it
could not find the schema extensions SFU would have made. Could you elaborate a little more on what you mean by running
Schema Admins empty? At this point, I have my account added to the Schema
Admins so I can (hopefully) perform the FORESTPREP. ~Ben From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Mark Parris Ben,
Mark From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of WATSON, BEN Hello Mathieu, Yes, we run a fairly simple domain setup. Single domain,
single forest. We are running in Windows 2000 native mode for domain and
forest. Exchange 2003 is also in native mode. And nice catch on SMS, I deployed it myself and should’ve
remembered to mention that. We do have SMS 2003 in our environment with
the schema extended of course. ~Ben From: Mathieu CHATEAU
[mailto:[EMAIL PROTECTED] Hello
BEN, are you
in Windows 2000 native mode ? the forest too ? exchange native mode ? Do you
have SMS ? it extends the schema as well. Cheers, Mathieu
CHATEAU Thursday,
July 6, 2006, 7:43:21 PM, you wrote:
-- Best regards, Mathieu
mailto:[EMAIL PROTECTED] |
- RE: [ActiveDir] Forestprep Failure WATSON, BEN
- RE: [ActiveDir] Forestprep Failure Steve Linehan
- RE: [ActiveDir] Forestprep Failure Steve Linehan
- RE: [ActiveDir] Forestprep Failure WATSON, BEN
- Re: [ActiveDir] Forestprep Failure Matheesha Weerasinghe
- RE: [ActiveDir] Forestprep Failure WATSON, BEN
- RE: [ActiveDir] Forestprep Failure WATSON, BEN
- RE: [ActiveDir] Forestprep Failure WATSON, BEN