Re: fan-out distribution
- From: "Steve Thompson" <stevethompson@xxxxxxxxxxxxx>
- Date: Wed, 27 Dec 2006 10:22:45 -0500
"Mustafa" <Mustafa@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1608F272-A3E4-4848-84A1-9D07D7B18660@xxxxxxxxxxxxxxxx
I have a question about fan-out distribution behavior. The SMS
documentation and concepts guide does not go thru too much detail about
this
and I want to understand it a little better.
We are going to have a 3 to 4 tier SMS hierarchy. We will do all of our
software distribution from the Central Site. There are going to be
instances
when we want to do a global roll out where we want the 2nd tier sites to
handle distribution of packages to their children sites - I understand
this
to be what fan-out distribution offers.
However, there are going to be times when we want to send from the Central
Site to only one leaf site in the hierarchy (targeted distribution to one
office) - in this case, will we be able to control NOT to do fan-out - and
just send directly from Central Site to that leaf site (which may be in
the
4th tier) - to avoid the time delays in propagating down the hierarchy?
The way you'd control that scenario, at your central site create a target
collection that limits the target computers to the specific "leaf site" or
more commonly the "child site". For example, that collection can be based on
site code membership.
There will always be some delay propagating through the sms site hierarchy,
usually the delay is not that significant. If the delay is not acceptable,
you could always create your packages at the central site, send those
packages to the child site that are needed (use specific distribution
points), then create the advertisement at the specific child site.
Steve
.
- Prev by Date: Re: Please Help With Boundries 2!
- Next by Date: Re: Best way to copy files in a program?
- Previous by thread: Re: Please Help With Boundries 2!
- Next by thread: Re: Best way to copy files in a program?
- Index(es):
Relevant Pages
|
Loading