I have a Warning status for SMS_HIERARCHY_MANAGER, and a Critical status for SMS_SITE_COMPONENT_MANAGER. The message is: "Systems Management Server cannot create the object "SMS-Site-ITB" in Active Directory." - For the Hierarchy_Manager Systems Management Server cannot create the object "cn=SMS-SLP-ITB-DFGSCCM1" in Active Directory. - For Component_Manager Systems Management Server cannot create the object "cn=SMS-MP-ITB-DFGSCCM1" in Active Directory. - For Component_Manager I've verified that the Site compute account has Full Control on the needed spots in AD, including the Apply to this and all child objects. Any other ideas on what could be going on? I did finally get the clients communicating with Config Mgr, and they all say Yes under Client in the Collection.

Did you create the "System Management" container under the System container? Did you use ADSIEdit to do this? Did you grant permissions to te "System Management" container using a security group or the actual computer account of the site server?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I'm in line with Jason. The error occurs because the site server cannot write data to the System Management container. You need to assign the computer account Full control to all objects and child objects on the System Management container. If the site server has been added to a group then remember that a restart is required to pick up that change. How to Configure security for the container - http://technet.microsoft.com/en-us/library/bb633169.aspxKent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

Hi, Have you extended the schema for ConfigMgr? You could run extadsch.exe again to see what's in extadsch.log.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Sorry for the delay in response, I was out Thursday and Friday of last week. Yes, I did create the "System Management" container under the System container. I believe I used ADSIEdit... it was a while ago now. Yes, I granted Full permissions to the container to the actual computer account. (It shows up as a user, though... DFGSCCM1$) Does this look right? It's weird, when I first installed, I had similar issues, that pointed to this permissions stuff, then I "fixed" it, and the component status was fine. Then, I had issues getting the agent installed on my test clients. I got that issue fixed, and now we're back to the component status problem.

Have you added the computer account of the siteserver to a group and used that group to grant permissions? If so: have you rebooted the server?

Could you check the hman.log and sitecomp.log for more details on the errors?"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm

Here's what is listed in between all the Wait for site control changes for maximum 3600 seconds... " Site ITB in Sites table: Site status = 1, Detailed status = 1 SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Processing site control file: Site ITB File C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\hman.box\19P41F94.CT2 SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Update the Sites table: Site=ITB Parent= SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Unable to decode MBEx passwordAttempt to release mutex not owned by caller. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Starting processing MP Certificates. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Signed MP Cert 308201E030820149A00302010202102950DE80B8591F844525C48B5B84B5DF300D06092A864886F70D010105050030213111300F060355040313084446475343434D31310C300A06035504031303534D533020170D3130303732323137323834345A180F32313130303632393137323834345A30213111300F060355040313084446475343434D31310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D00308189028181009F105BC2F0C361F5C3354A024DEC57C18F2E968B8D90B4333026F568B61C394C11360A566F270F0AC68D0A07655D5584201096E29AA5007F616A3F30C0379CD42721C0184D333D1461F70C10946DEB40459736891965B72A9B33A85869F548BC4EE78245C42D6D746EDD5A9E45CBADE69F3428BD65A4D27E8B89065F5449D5BB0203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D0101050500038181007AF413E0348834921B030AD8A434FAF95A0416C8332F3D7D6FC9C408E7DC561BC1ED63A281A066223CFB52A42F3F553735F1EBBFFE7CA6BC395AA002E1734EA05C03980514740520D5586FFAFF3CDF6C2A6446E0EBC017E9AF0E185951CDA07D27DB57003568CCA50DBC9633FC34F2376D7A5A90AB47E318D7EC41613736199E, into sig: AF8801D2F1AE9D92DA3318CFD85CC36CB963032B4A908972F681CF3C0839AC51F448167D9BFC69BDF808264A2900DD8CE941F2E535670D3CF90BA101012CFF3692917C8E179744A1FD48F60AA05C738E11FF8E6A3B096119DC3699B77FCFC0A3B8BFE99042834050AB3A875D2C3224EAA9CA96ECE1AD01042E229AC2D872BB69 SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Site system currently in use: ITB DFGSCCM1 SMS Component Server SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Site system currently in use: ITB DFGSCCM1 SMS Distribution Point SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Site system currently in use: ITB DFGSCCM1 SMS Management Point SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Site system currently in use: ITB DFGSCCM1 SMS Server Locator Point SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Site system currently in use: ITB DFGSCCM1 SMS Site Server SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Site system currently in use: ITB DFGSCCM1 SMS Site System SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Site system currently in use: ITB DFGSCCM1 SMS SQL Server SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Checking SQL Cluster configuration. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) This site is not using clustered SQL. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Server Info of site ITB has not changed. HMAN will not update the DPInfo table in the database. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Distribution Points of site ITB have not changed.HMAN will not update the DistributionPoints table in the database. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Site System <DFGSCCM1> is the Default Management Point.for site <ITB> SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) ClientDataCleanUpOnSecurityModeChange: No change detected in SSL_State. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Health state references are published in the same Active Directory forest where site server is located. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Check if the security mode of the site has changed. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) WCM Configuration of site ITB has not changed. HMAN will not update the WSUSServerLocations table in the database. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Update Site Boundaries in Active Directory SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Active Directory DS Root:DC=geo,DC=dfg,DC=ca,DC=gov SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Searching for the System Management Container. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) System Management container exists. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Searching for SMS-Site-ITB Site Object. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) SMS-Site-ITB doesn't exist, creating it. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) SMS-Site-ITB could not be created, error code = 8202. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) STATMSG: ID=4913 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=DFGSCCM1 SITE=ITB PID=2240 TID=3112 GMTDATE=Tue Aug 31 07:00:10.713 2010 ISTR0="SMS-Site-ITB" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) No Ranged IP boundaries are currently published for this site. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Searching for SMS-ITB-184098941-184098943 Ranged Roaming Boundary Object. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) SMS-ITB-184098941-184098943 doesn't exist, creating it. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) SMS-ITB-184098941-184098943 could not be created, error code = 8202. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) There is no parent site, no need to forward any site control images. SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) Created site control notification for site ITB SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=DFGSCCM1 SITE=ITB PID=2240 TID=3112 GMTDATE=Tue Aug 31 07:00:10.720 2010 ISTR0="C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\hman.box\19P41F94.CT2" ISTR1="ITB Primary Site" ISTR2="ITB" ISTR3="50" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_HIERARCHY_MANAGER 8/31/2010 12:00:10 AM 3112 (0x0C28) " Sorry for the messiness, I copied directly from Trace32. Here's the repeating section for sitecomp.log SLP Configuration for DFGSCCM1 is correct. SMS_SITE_COMPONENT_MANAGER 8/31/2010 8:44:25 AM 2452 (0x0994) Installing Security settings on site system ... SMS_SITE_COMPONENT_MANAGER 8/31/2010 8:44:25 AM 2452 (0x0994) Security settings are up to date for DFGSCCM1. SMS_SITE_COMPONENT_MANAGER 8/31/2010 8:44:25 AM 2452 (0x0994) Publishing DFGSCCM1 as an SLP into Active Directory. SMS_SITE_COMPONENT_MANAGER 8/31/2010 8:44:25 AM 2452 (0x0994) SLP Class SMS-SLP-ITB-DFGSCCM1 doesn't exists. Creating SMS_SITE_COMPONENT_MANAGER 8/31/2010 8:44:25 AM 2452 (0x0994) SMS-SLP-ITB-DFGSCCM1 could not be created, Win32 error = 8202. SMS_SITE_COMPONENT_MANAGER 8/31/2010 8:44:25 AM 2452 (0x0994) STATMSG: ID=4913 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=DFGSCCM1 SITE=ITB PID=2432 TID=2452 GMTDATE=Tue Aug 31 15:44:25.945 2010 ISTR0="cn=SMS-SLP-ITB-DFGSCCM1" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 8/31/2010 8:44:25 AM 2452 (0x0994) The bolded line I guess is the error line. Any ideas from these logs?

No, I didn't extend the schema.

That's your problem as marked in the log by error 8202. 8202 means The specified directory service attribute or value does not exist. Run Extadsch.exe from the smssetup cd, and the issue should be resolved. Assuming you assigned permissions correctly."Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm

Not going to extend the schema at the moment. Haven't had it extended the whole time, and didn't have these errors until the clients actually had the agent installed. What will these errors prevent me from doing?

I'm also encountering the same issue. This is from the sitecomp.log: SLP Configuration for SDSCCM01 is correct. SMS_SITE_COMPONENT_MANAGER Installing Security settings on site system ... SMS_SITE_COMPONENT_MANAGER Security settings are up to date for SDSCCM01. SMS_SITE_COMPONENT_MANAGER Publishing SDSCCM01 as an SLP into Active Directory. SMS_SITE_COMPONENT_MANAGER SLP Class SMS-SLP-APL-SDSCCM01 doesn't exists. Creating SMS_SITE_COMPONENT_MANAGER SMS-SLP-APL-SDSCCM01 could not be created, Win32 error = 8202. SMS_SITE_COMPONENT_MANAGER (0x0804) STATMSG: ID=4913 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SDSCCM01 SITE=APL PID=1292 TID=2052 GMTDATE=Thu Sep 09 18:23:45.467 2010 ISTR0="cn=SMS-SLP-APL-SDSCCM01" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER Site System <SDSCCM01> is the Default Management Point. HTTP=80 HTTPS=443. SMS_SITE_COMPONENT_MANAGER I've tried multiple ways to fix this. I created the System Management container through ADSIedit, granted full control to this and child objects to my server (sdsccm01). Then I granted the read permission to Everyone. That didn't work, so I deleted the container, granted full control to the system container and let SCCM create the folder itself. It did manage to create the System Management container, but it still won't populate it. I also don't have the schema extended, as it's not a possibility at this time. I've made sure that the management point and server locator point roles are installed, and I've verified the "Publish this site in AD DS" and "Publish the default management point in DNS" are ticked. This is a brand new SCCM install. This is the only server in the environment. It's been installed on a fresh 2008 R2 VM. I've read through every article I can find, and they all tell me that it's a permissions issue. I've checked and rechecked the permissions and it still won't work.

I also don't have the schema extended, as it's not a possibility at this time ... and I've verified the "Publish this site in AD DS" It's NOT a permission issue. It's because you did not extend the schema. See Kim's reply above.