Re: Trouble Extending Schema

From: Micah (M_at_m.com)
Date: 05/02/04 

Date: Sun, 2 May 2004 12:09:55 -0500

As far as manually extending so far all I have done is add the "system
management" container to the System folder using ADSI edit
That stopped the 4909 errors in SMS but now those have been replaced with
4913 errors. The SMS Server account has full control of the new system
management folder and all child objects as well as the legacy user account
just for the hell of it

I've tried running the extend schema application from each of the domain
controllers and each return the same error. I am running it using an
account that is in the schema admin group and have verified that the allow
changes box is checked, it's still a 2000 domain.

Righ now we only have a single domain

"Jason Nelson" <anonymous@discussions.microsoft.com> wrote in message
news:0C0691ED-DC67-4DFD-8E52-41DE92EEE375@microsoft.com...
> Micah,
> It looks like you are following the right path to getting this done.
Could you be more specific on how you are "manually" extending the AD
schema? A few things to consider are whether this is a Windows 2003 AD or a
Windows 2000 AD. If this is a 2000 AD schema, you need to manually modify
the schema to allow for updates whereas in a 2003 AD by default it is set to
allow for schema changes out of the box. Ensure the account you are using
is a member of the Schema Group, as this will give you permission when
manually setting up the SMS System Container. In addition, do you have just
one domain or do you have a Root and a Production domain?
>
> However, from the included log it looks like SMS does not have sufficient
permissions.
>
> Lastly, the account you created for legacy computers. Was this account
specified in the schema? I say this, as you only need to have the SMS
computer account specified. Legacy clients do not touch the AD schema in
any way. The only account that needs permission is the one SMS site server
computer account or a group if you have multiple SMS sites that are set it
up.
>
> Cheers,
> jason nelson

Relevant Pages

  • Re: SMS-Site-001 could not be created, error code = 5 in hman.log
    ... there are 'No Ranged IP boundaries are currently published for this ... container and delegated control to the computer account of my SMS ... Verified in the extadsch.log that the schema extension was ... I ran SMS Trace to view the hman.log and saw that it has not yet ...
    (microsoft.public.sms.admin)
  • Re: SMS-Site-001 could not be created, error code = 5 in hman.log
    ... container and delegated control to the computer account of my SMS ... Verified in the extadsch.log that the schema extension was ... I ran SMS Trace to view the hman.log and saw that it has not yet ...
    (microsoft.public.sms.admin)
  • RE: Automatic Site Code Discovery was unsuccessful
    ... Windows Server 2003 and Windows 2000 ... or a combination of both) that is the code for the SMS site to ... "If you have extended the Active Directory schema, ... i just insatlled the SMS 2003 without extending the ...
    (microsoft.public.sms.admin)
  • RE: Automatic Site Code Discovery was unsuccessful
    ... Straight from the SMS FAQ: ... "If you have extended the Active Directory schema, ... Install Windows 2003 Server Ent. ... i just insatlled the SMS 2003 without extending the ...
    (microsoft.public.sms.admin)
  • Re: Merged environments with different Active Directory Versions
    ... > extending the schema for SMS. ... >>> My company recently was acquired by another company which didn't use SMS. ... I haven't yet extended the AD schema. ... Ad or change management :-). ...
    (microsoft.public.sms.setup)