Re: collection lock down

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Richard (anonymous_at_discussions.microsoft.com)
Date: 07/08/04 

Date: Thu, 8 Jul 2004 08:15:32 -0700

your, right
 
i can see this file:- attempting to replicate file
\\BARCLAY\SMS_SO3\inboxes\coll_out.box\tz7firu1.PSD to
site ST1 SMS_COLLECTION_EVALUATOR 08/07/2004 3:18:57 PM
500 (0x1F4)
Resetting update flags for collection SO300028
SMS_COLLECTION_EVALUATOR 08/07/2004 3:18:57 PM 500 (0x1F4)
Deleting file \\BARCLAY\SMS_SO3
\inboxes\colleval.box\SO300028.UDC; processing
completed. SMS_COLLECTION_EVALUATOR 08/07/2004 3:18:57
PM 500 (0x1F4)

 
 however even having done a forced collection update, from
the parent it still has not passed the info to the child
even also by forcing the child to do the same.
 
the also give you some idea we are running to seperate
domains for this ie our S03 site is on one and our ST1 is
on another. but both have the same accounts set up on
them.
however what i have notice is the the message Id is
relating to an error in connecting to the SMS_site Share
on the child site fomr the parent.
 
what i have also noticed is that some one has created a
site account under the connection accounts under site
system on the parent called site1 wihte admin rights and
domain admins, but not done it for the child site is this
a must.
 
aslo becasue the site was build by some else we have no
idea what the smsservice account password is.
 
thankyou

>-----Original Message-----
>It should occur right away, as a result of the site
attachment to the
>parent. You'll need to refresh the collections on the
child to see the
>locks. It also occurs as a result of a collection update
on the parent, so
>you can also cause it to occur by manually updating the
parent's collections
>(they automatically update once a day by default). You'll
see an entry in
>colleval.log on the parent about replicating a PSD file
to the child site,
>with one PSD file per collection updated.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Richard L" <rlewischaplin@btinternet.com> wrote in
message
>news:2826701c46433$39125930$a501280a@phx.gbl...
>>
>>
>> Hi,
>>
>> cna anyone tell me when a Primary site of connected to a
>> central Primary site, when and how long does it take for
>> the collections on the Cetral site to appear within the
>> 2nd primary site as locked down.
>>
>> also what are the setting i ned to look for to ensure it
>> is correct i have checked the logs and both sites are
>> talking to each other.
>>
>>
>
>
>.
>

Relevant Pages

  • Re: SMS Heirachy
    ... Heres an extract from the HMAN.LOG on the child site. ... However if on the parent site i want to ... Windows Enterprise Management Division User Assistance ...
    (microsoft.public.sms.setup)
  • Re: Duplicate server entries for the same site code
    ... I think so - if the child site is no longer referenced at the parent. ... >> run PREINST /DELSITE to clean up references to the site if any>> ... >>> Neither log on the parent server reports any entries for either server. ...
    (microsoft.public.sms.setup)
  • Re: 2 AD domains same physical switches and router ?
    ... Currently the remote sites resources live on our parent companies ... I'm not really wanting to have to put static dns entries onto the ... the workstations and user accounts to be part of your Active Directory ...
    (microsoft.public.windows.server.networking)
  • Re: 2 AD domains same physical switches and router ?
    ... Currently the remote sites resources live on our parent companies ... workstations and user accounts to be part of your Active Directory ... Instead of the website you're using, try using OEx (Outlook Express ...
    (microsoft.public.windows.server.networking)
  • Re: Locked objects in primary child site
    ... collections, packages, ads, etc on the child site. ... Be aware that not all objects will replicate to child. ... replicate up the hierarchy, not down, so you won't find parent site clients ... upgrading to sms 2003, you should consider transferring clients from old ...
    (microsoft.public.sms.admin)