Re: Central Site info not flowing down

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Already had the computer accounts added to the Site to Site group and the
servers have been bounced. On the the sender.log and this is the only error
I can find in the sender.log - There is no existing connection, Win32 error =
1240. I've searched but can't find any info on this
--
Stan


"Cathy Moya [MS]" wrote:

> Sounds like a security issue. Check the address account you are using from
> the primary parent to the other primary children, the ones that aren't
> showing up.
>
> If you are using standard security, make sure the address account is added
> to the Site to Site Connection (SMS_SiteToSiteConnection_sitecode) group.
>
> If you are using advanced security, add the computer account of the computer
> initiating the connection to the Site to Site Connection group on the
> computer receiving the connection. This means that all child site servers
> should be added to the Site to Site Connection group on the parent site.
> Parent site server computer accounts should be added to the Site to Site
> Connection group on all children (and grandchildren if you want to use a
> direct sender to them.) Also, remember when you add an account to a group,
> including a computer account to a group, the change does not take effect
> until the next logon. For a computer account, that next logon is when the
> computer next restarts, so a reboot might fix things if you did the adding
> already.
>
> If it still isn't working, take a look at the sender.log file. It's pretty
> informative.
>
> Be patient after making changes. This was always the most complicated lab in
> the old SMS courses because it was easy to misconfigure something and
> sometimes it took a while for SMS to readjust after we found and fixed the
> security issue.
>
> BTW, if you are using Windows 2000 server, adding computer accounts to
> groups can be tricky. Here's a link to a doc with the procedure:
> http://www.microsoft.com/technet/prodtechnol/sms/sms2003/security/spsecsms03/spsec_10.mspx#ECAA
>
> Hope that helps!
>
> --
> Cathy Moya, CISSP, MCSE: Security
> Technical Writer, Windows Enterprise Management Division User Assistance
>
> Check out the SMS 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.
>
>
>
> "Stan" <thestan01@xxxxxxxxx> wrote in message
> news:05D625E5-53A5-43C0-B767-57E5593E2599@xxxxxxxxxxxxxxxx
> > SMS 2003 1 central site, 3 primary sites reporting up and numerous
> > secondary
> > sites. From one primary site the collections, packages, etc. from the
> > central
> > site can be seen from it's sms console. The other 2 primary sites can't
> > see
> > this information. Anyone got any idea why they can't see the collections?
> > We
> > use the central site to push out software updates, common programs etc.
> > --
> > Stan
>
>
>
.

Relevant Pages

  • Re: Secondary Sites on DCs and Advanced Security.
    ... If you are putting site servers on DC's, then yes the computer accounts will ... Your upgrade order looks fine, top level site first then work ... > Secondaries on DCs report to the Domain Admins Group? ...
    (microsoft.public.sms.setup)
  • Re: Moving clusters to a different OU
    ... you are approaching this correctly - by moving computer accounts into ... I'm unaware of any functionality impact to the cluster by simply moving the ... > need to apply some Group Policy to the servers, I have created an Org Unit ...
    (microsoft.public.windows.server.clustering)
  • Re: Group Policy.. windows update.. auto restart of servers.. prev
    ... Put the VM computer accounts for the servers into their own OU - this could ... link the GPO with the setting you ... Settings applied by GPOs linked to the child OU will take precedence over ...
    (microsoft.public.windows.group_policy)
  • Re: Moving clusters to a different OU
    ... answered my question...it seems there is no harm moving servers to different ... you are approaching this correctly - by moving computer accounts into ... > Remember that the Cluster Service requires certain rights to the computer ... >> about if I want to move those nodes into this newly created Org Unit? ...
    (microsoft.public.windows.server.clustering)
  • RE: Computer accounts in NTFS permissions
    ... Security filtering in Group Policy for computer policies works using ... LocalSystem) goes and talks to the domain controller, ... Computer accounts in NTFS permissions ... computer security principal in NTFS ACLs won't have any effect. ...
    (Focus-Microsoft)