SMS software distribution and AD OUs

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

  • Re: SMS software distribution and AD OUs
    ... I don't fully agree with "The consultant's suggestions is to persuade the AD ... This being done you can start designing your SMS infrastructure e.g. ... 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: Transfer files using SMS 2003
    ... When a distribution point is available locally ... Download program from a remote distribution point ... Did you read that table I referenced in the Scenarios and Procedures for SMS ... all local machines in my netwoRK. ...
    (microsoft.public.sms.admin)
  • Re: Ran ccmclean on site server, what are implications???
    ... Right click on the package>all tasks> Update distribution points ... i have scheduled the sync tool to run at 13pm and in package microsoft tool ... Afterwards i tried running sync tool. ... If this works then you can work backwards to make sure it works thru sms. ...
    (microsoft.public.sms.setup)
  • 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: Multiple Distribution Points
    ... If you decide you need additional distribution points, ... Navigate to a Site Systems. ... Check out the SMS Technical FAQ: ... >> Check out the SMS Technical FAQ: ...
    (microsoft.public.sms.misc)
Loading