Re: system container in SMS 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Luke Packard [MSFT] (lukep_at_online.microsoft.com)
Date: 09/01/04


Date: Wed, 1 Sep 2004 08:48:36 -0700

The log excerpts you sent don't have anything about publishing. Check to
see that AD publishing is enabled in the advanced tab of the site properties
page. When publishing SMS object in AD the hman.log should have entries
like this:

Searching for the System Management Container. 9/1/2004 8:36:04 AM
System Management container exists. 9/1/2004 8:36:04 AM
   Searching for SMS-Site-M14 Site Object. 9/1/2004 8:36:04 AM
   SMS-Site-M14 doesn't exist, creating it. 9/1/2004 8:36:04 AM
SMS-Site-M14 successfully created. 9/1/2004 8:36:04 AM

and the sitecomp.log should have entries like this:

    Publishing LPM14 as a Management Point into Active Directory. 9/1/2004
8:35:58 AM
STATMSG: ID=4911 SEV=I LEV=M SOURCE="SMS Server"
COMP="SMS_SITE_COMPONENT_MANAGER" SYS=LPM14 SITE=M14 PID=2360 TID=2992
GMTDATE=Wed Sep 01 15:35:59.020 2004 ISTR0="cn=SMS-MP-M14-LPM14" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 9/1/2004 8:35:59 AM
    SMS-MP-M14-LPM14 successfully created. 9/1/2004 8:35:59 AM
     Granted LPM14$ security permissions in AD. 9/1/2004 8:36:00 AM
    SLP Configuration for LPM14 is correct. 9/1/2004 8:36:00 AM
    Publishing LPM14 as an SLP into Active Directory. 9/1/2004 8:36:00 AM
    SLP Class SMS-SLP-M14-LPM14 doesn't exists. Creating 9/1/2004 8:36:00
AM
    SMS-SLP-M14-LPM14 successfully created. 9/1/2004 8:36:00 AM

-- 
Luke Packard [MSFT]
SMS 2003 Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
This posting is provided "AS IS" with no warranties, and confers no rights.
"vanguard" <vanguard@discussions.microsoft.com> wrote in message 
news:57669231-4FBB-4800-89FC-E9FCA9DDD794@microsoft.com...
> What am I looking for in these logs?
>
> Here is what I get in the sitecomp.log
>
> LDAP://CN=System Management,CN=System,DC=ad,DC=alphatech,DC=com container
> exists.~  $$<SMS_SITE_COMPONENT_MANAGER><Mon Aug 30 15:34:52.703 2004 
> Eastern
> Daylight Time><thread=2380 (0x94C)>
> Polling complete.  $$<SMS_SITE_COMPONENT_MANAGER><Mon Aug 30 15:34:52.703
> 2004 Eastern Daylight Time><thread=2380 (0x94C)>
> Waiting for changes to the "C:\SMS\inboxes\sitectrl.box" or
> "C:\SMS\inboxes\sitecomp.box" directories, servers will be polled in 1
> hour...  $$<SMS_SITE_COMPONENT_MANAGER><Mon Aug 30 15:34:52.765 2004 
> Eastern
> Daylight Time><thread=2380 (0x94C)>
>
> And here is what I get in the Hman.log
>
> ~Created site control notification for site BUR
> $$<SMS_HIERARCHY_MANAGER><Mon Aug 30 00:00:08.250 2004 Eastern Daylight
> Time><thread=2088 (0x828)>
> STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server"
> COMP="SMS_HIERARCHY_MANAGER" SYS=ALPHA-X SITE=BUR PID=1476 TID=2088
> GMTDATE=Mon Aug 30 04:00:08.296 2004
> ISTR0="C:\SMS\inboxes\hman.box\BGH188CA.CT2" ISTR1="ALPHATECH" ISTR2="BUR"
> ISTR3="13" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" 
> NUMATTRS=0
> $$<SMS_HIERARCHY_MANAGER><Mon Aug 30 00:00:08.296 2004 Eastern Daylight
> Time><thread=2088 (0x828)>
> ~Did not detect any site control change for site BUR
> $$<SMS_HIERARCHY_MANAGER><Mon Aug 30 00:00:08.359 2004 Eastern Daylight
> Time><thread=2088 (0x828)>
> ~Wait for site control changes for maximum 3600 seconds...
> $$<SMS_HIERARCHY_MANAGER><Mon Aug 30 00:00:08.421 2004 Eastern Daylight
> Time><thread=2088 (0x828)>
> ~Wait for site control changes for maximum 3600 seconds...
> $$<SMS_HIERARCHY_MANAGER><Mon Aug 30 00:00:13.484 2004 Eastern Daylight
> Time><thread=2088 (0x828)>
> ~Wait for site control changes for maximum 3600 seconds...
> $$<SMS_HIERARCHY_MANAGER><Mon Aug 30 01:00:18.562 2004 Eastern Daylight
> Time><thread=2088 (0x828)>
> ~Wait for site control changes for maximum 3600 seconds...
> $$<SMS_HIERARCHY_MANAGER><Mon Aug 30 02:00:23.640 2004 Eastern Daylight
> Time><thread=2088 (0x828)>
> ~Wait for site control changes for maximum 3600 seconds...
>
> Thanks for your help with this.
>
>
>
> "Luke Packard [MSFT]" wrote:
>
>> You shouldn't have had to create the System container as that would 
>> already
>> be there.  What do the sitecomp.log and hman.log files report when
>> attempting to publish?
>>
>> -- 
>> Luke Packard [MSFT]
>>
>> SMS 2003 Technical FAQ:
>> http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
>>
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>>
>> "vanguard" <vanguard@discussions.microsoft.com> wrote in message
>> news:EE0491C1-7A76-49A1-B6D7-712FA82F517F@microsoft.com...
>> > Hi all I'm a little stuck,
>> >
>> > After installing SMS on one of our member servers in our test bed, I
>> > initially didn't extend the schema when prompted. So when the install 
>> > was
>> > done I ran Extadsch.exe command line tool to extend the schema (no
>> > errors).
>> > Then I ran the ADSIEdit to create the "system" folder and "system
>> > management"
>> > folder,
>> > and gave full control to the object container and its child objects, 
>> > then
>> > I
>> > rebooted the server.
>> >
>> > Then I went through and found the system management folder and didn't
>> > see any site or site system objects. Nothing was in the folder, could 
>> > you
>> > please tell me what I'm doing wrong?
>> >
>> > thanks
>> > -- 
>> > Vanguard
>>
>>
>> 


Relevant Pages

  • Re: Extending the Active Directory Schema for SMS 2003
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... If the SMS Service account has full rights to the System ... unless you turned off AD publishing. ... >>>>> Did you give the Site server full control over the System Management ...
    (microsoft.public.sms.setup)
  • Re: sms in forest in multiple domains
    ... I should clarify - it's really the site server for the site that is doing ... publishing its own data, meaning either the SMS service account (standard ... Windows Enterprise Management Division User Assistance ... Check out the SMS Technical FAQ: ...
    (microsoft.public.sms.setup)
  • Re: SMS SP3 client problems
    ... I had extended the schema and yes the data was publishing there. ... From the client side, the client installs and as reported in th setup log succeeds, but it never seems to show up in the admin console. ... The 1st time I set up SMS I rember being able to tell SMS that they should ihnstall the client no matter who or what is logged into the computer. ...
    (microsoft.public.sms.admin)
  • Re: Why SMS is writing in Active Directory?
    ... Perhaps it is a bad conception of SMS but why is it trying to write into AD ... > If you haven't extended the schema publishing to AD wouldn't work ... > MVP SMS ... >> I dont have extended the schema and I have an ...
    (microsoft.public.sms.admin)
  • Re: AD Publishing & Retrieval
    ... the SMS information is published to the global catalog for ... This makes the information for each site publishing to Active ... the SMS Servers belong. ... they belong to domains where the SMS computer accounts don't have any ...
    (microsoft.public.sms.admin)