Re: MBSA patch package distribution issue

Are you sure it sent the bits? More likely it just sent the updated
package definition.The package definition specifies the program details, MIF
collection details, etc. (and which DPs the package should be on).

That is a common point of confusion. The distribution manager log
messages are the same either way (but the bits distribution will have bonus
messages in relation to package compression, etc.). Package definitions
always go to all child sites (because you might have admins lower in the
hierarchy that would be interested). But the bits only go where you specify.

But removing all the DPs from the package will cause it to be removed
from all the child DPs except the 5 that are left. So that causes work on
the child sites to do that removal. And later when you add the package back
to the sites, the bits will have to be sent back to them.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

<markcedwards@xxxxxxxxx> wrote in message
news:1113583324.462809.181040@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> We separate out our MBSA security packages by OS... We have 3 packages-
> Win2k Server, WinServer 2003 and Win2k/XP. We do this mainly to keep
> the size of the package relatively small, and because not every one of
> our 238 sites needs the Win2k Server package. Why send 120MB of
> 2kServer hotfixes over our slow WAN links when not necessary...
>
> Anyway, I went to update the Server 2003 package this week. Instead of
> distributing it to ALL 238 sites, I wanted to see if our package would
> delta or true up (I believe 5 deltas is the default) by sending to just
> 5 of the sites. In the Distribute Software Updates wizard, I removed
> all DPs except the five I wanted.
>
> I then began watching in amazement as the sched.log on our site server
> showed the updated 130MB package being sent to ALL 238 SITES!!! So,
> not only did I get unlucky and it was time for the package to true
> up... but apparently the wizard doesn't really distribute it the way I
> wanted it to.
>
> Anyone else notice this?
>
> Also, does anyone know how to "read" the .DLT.x.rf$ files in the SMSPKG
> dir so that you could determine beforehand that a package needed to
> true up?
>


.

Relevant Pages

  • Clients not downloading package from one DP
    ... There is one SMS 2003 site in our environment with multiple DPs. ... I've set the package to be distributed from two servers for testing ... The download failed because the content ... The content on the distribution point ...
    (microsoft.public.sms.swdist)
  • Re: Package Distribution filling up boot partition
    ... DPs configured with a 10GB boot partiiion and 70GB F: ... One of the DPs did not have all the files from the distribution, ... compressed copy of the package being despooled to the C: ...
    (microsoft.public.sms.admin)
  • Re: Forcing package distribution to start immediately
    ... Unless you have restricted schedule for senders this will happen as soon as ... If you have more than 3 DPs for the site then you ... can increase number of threads per package settings from SMS Admin UI. ... See SDK for details. ...
    (microsoft.public.sms.swdist)
  • Re: SMS Package Failed DP
    ... a package was pushed to this DP along with several other DPs. ... Site Status for the Primary that the DP falls under- the package is still ... my guess is that it is stuck somewhere in SQL and needs to ... Once removed shut down your temp server. ...
    (microsoft.public.sms.admin)
  • Phantom Distribution Points
    ... SMS tries to send the or the new package ... to the DPs that were removed. ... Anyone know the sql statement to delete these ...
    (microsoft.public.sms.admin)
Loading