Re: SMS Site Component Manager
- From: "Jeff Gilbert [MSFT]" <jeff.gilbert@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 18 Nov 2006 10:08:54 -0800
Giving full control to the System container allows the site server's
computer account (advanced security) the ability to create the needed System
Management container. The easiest thing to do at this point I would try (in
this order):
1. Ensure that the SMS 2003 SP2 schema extensions have been applied (not
still at SP1 extensions or something).
2. Assuming you are in advanced security at this point--ensure that the
computer account for the primary site server has Full Control to the System
Management container and all of it its child objects (note that there is no
's' on the end of System for this). If I have assumed incorrectly and you
are in standard security, then check that the service account has these
permissions.
3. If all of the above are correct, delete the existing information
published to the System Management container and allow the site to republish
the site information.
Hope this helps,
Jeff Gilbert, MCSE
Technical Writer | Windows & Enterprise Management Division
Microsoft Corporation
This posting is provided "AS IS" with no warranties and confers no rights.
"Goddard" <Goddard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A7DF5BE8-FF99-4067-A378-30781858B2AF@xxxxxxxxxxxxxxxx
"apereira" wrote:
Hello,
I am new to SMS and have setup a windows 2003 server, with SQL 2005
server,
and SMS 2003 SP2.
I have an error that keeps coming up as follows in the System status
section. Is it the site component manager.The error I see is as follows
Systems Management Server cannot update the already existing object
"cn=SMS-SLP-MTL-MTL-SMS" in Active Directory.
Possible cause: This site's SMS Service account or the site server's
machine
account may not have full control rights for the "System Management"
container in Active Directory
Solution: Give the site's SMS Service account full control rights to the
"System Management" container, and all child objects in Active Directory.
Possible cause: The Active Directory object "cn=SMS-SLP-MTL-MTL-SMS" has
been moved to a location outside of the "System Management" container, or
has
been lost.
Solution: Delete the object from its current location, and let SMS create
a
new object.
Possible cause: The Active Directory schema has not been extended with
the
correct SMS Active Directory classes and attributes.
Solution: Turn off Active Directory publishing for each site in the
forest,
until the schema can be extended. The schema can be extended with the
tool
"extadsch.exe" from the SMS CD.
I am new to this and a little confused as to where and look. I have
looked
at the local account that it might use which is "SMSServer_MTL". I have
added
admin rights to this account. Still I get this error.
Any help in the right direction would be appreciated.
This are all trial versions as well.
Thank you
I had the same error. Look for KB830022. In my case the error was resolved
by giving the SMS machine name full access to the system folder and child
objects in AD.
.
- Prev by Date: Re: Proper Discovery
- Next by Date: Re: SMS Reports missed
- Previous by thread: Re: SMS Site Component Manager
- Next by thread: Failed to get a SQL Server connection
- Index(es):
Relevant Pages
|
