Re: SMS software distribution and AD OUs

Hi,

I don't fully agree with "The consultant's suggestions is to persuade the AD
guys to allow an OU structure to support the segregation of the sites."
In your scenario, I would be tempted to start redesigning your AD. You
should first convince you're AD guys to set up AD Sites according to the
connectivity ("well connected" - as rule of thumb >= T1 - opposed to "slow
link"). This being done you can start designing your SMS infrastructure e.g.
all "well connected" can be served by the same Primary ... and use AD Sites
as SMS Site Boundaries. For the "slow link" it will most likely be a trade
off between:
- Secondary Sites (Proxy MP + DP): again using AD Sites as SMS Site
Boundaries. Secondaries give you server to server bandwidth throttling, etc
- Protected DP: beware when sending out hugue packages down to the DP, no
throttling whatsoever!
- Nothing: e.g. 3 workstations behind a 128k.
- Third parties: e.g 1E SMS NomadBranch.

This being said an OU structure can serve to geographically, functionally,
etc... organize workstations and target accordingly. You could also use
groups to accomplish this and use the AD System Group Discovery to fill your
Collections ... but neither will be ideal ...

Cheers,
Serge


"NoneAtThisTime" <jim.bezdan@xxxxxxxxx> wrote in message
news:1138658790.936416.318140@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> We are looking at implementing SMS in our company. The plan is to
> divide it into two child primaries, each with about 28 separate sites /
> distribution points and 7500 clients under each primary (adv clients
> only). The reason for the split between two primaries is due to the WAN
> infrastructure. The current AD sites are too broad to use as SMS site
> boundaries, so I will have to use subnets to define them. Connectivity
> to some locations spans DS3 to 128k.
>
> Here is the problem: Our SMS technical consultant raised the issue that
> since we have a flat OU structure (all 15,000 workstations in one OU/
> 15,000 users in another), how would we target workstations at each
> location for software distribution? We thought about using subnets as a
> way of defining collections, but there is the risk of a laptop
> receiving something they shouldn't when visiting a remote office if we
> don't time our inventory interval accordingly. The consultant's
> suggestions is to persuade the AD guys to allow an OU structure to
> support the segregation of the sites.
>
> Has anyone encountered a situation like this or have an idea for
> targeting workstations based on location that we are missing? We
> thought about using groups, but it seems an OU structure would be more
> in line with how AD was intended to work.
>
> BTW, I didn't design the OU structure; I just have to live with it
> unless I can persuade them to change it. All opinions and suggestions
> are welcome.
>


.

Relevant Pages

  • SMS software distribution and AD OUs
    ... We are looking at implementing SMS in our company. ... distribution points and 7500 clients under each primary (adv clients ... The reason for the split between two primaries is due to the WAN ... 15,000 users in another), how would we target workstations at each ...
    (microsoft.public.sms.swdist)
  • Re: Require some documentation whether SMS is supported across mul
    ... no. SMS is pretty flexible. ... secondary in a different forest, but you can have a primary site in one ... the accounts and groups used by SMS ... domain or do i have to install child primaries? ...
    (microsoft.public.sms.misc)
  • Re: Site Topology Design
    ... Keep your SMS agents assigned to the two primaries. ... server with your two primaries reporting to it. ...
    (microsoft.public.sms.setup)
  • Re: Site Topology Design
    ... > Keep your SMS agents assigned to the two primaries. ... Set up a central SMS ... > server with your two primaries reporting to it. ...
    (microsoft.public.sms.setup)
  • Re: Two primary sites
    ... "Kim Oppalfens" wrote: ... Afaik sms 2.0 secondary sites can perfectly be children of sms ... > What is the reason you can't install 2 primaries, ... I can use one secundary site for holding site? ...
    (microsoft.public.sms.admin)
Loading