Re: distribution points

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

From: David Randall [MS] (davidra_at_microsoft.com)
Date: 09/16/04


Date: Thu, 16 Sep 2004 07:52:52 -0700

Jeremy,

You can configure your packages to pre-download the patch, then run at a
specific time. This may help you with your problem.

I'm wondering why you choose at logon for doing the patch installation? I
know it is a convenient "first possible time" to install a patch, but from
the user's point of view, this may be somewhat frustrating if the patch
installation slows down their logon time. Just a thought.

At any rate, if you'd like to pre-download the patch to the computer and
install it later, define a time at which you want the patch to become
available for download. This is the "available after" time on the
Advertisement. In your case, I might pick sometime in the early morning (4
am) or sometime in the late evening (10 pm) if the machines are normally
left on-line. If they are normally turned off at night, then I'd pick
sometime around lunch when the systems are typically used less. Then, in
the Schedule tab, add your schedule. You can use the At Logon trigger, but
I'd suggest picking a time that's 15 minutes to 2 hours after most users log
in. That way the package installation occurs soon after logon (good for
security), but won't impact their system during the same time that other
processes are starting up and the system is becoming fully initialized.

Let us know how that goes, or if you think that solution may work for you.

Dave Randall
SMS Team

-- 
-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jeremy Byrne" <J.Byrne@lboro.ac.uk> wrote in message 
news:%23ZTCI%238mEHA.1152@TK2MSFTNGP11.phx.gbl...
> It is mostly when trying to push a patch out at log on, it seems to not do
> everyone as though it can only handle doing so many the rest it leaves 
> till
> the next time they log on, usually the next day. So when we have a patch 
> we
> need to go out at log on and we want everyone done in the same day we end 
> up
> having to put it in a log on script rather than through SMS. Saying that
> though it is not everytime this happens sometimes it works fine, we just
> cant figure out why sometimes it takes a few days to push something out 
> and
> other times it goes all in one day.
>
> How often do you think you should have all of your discovery processes set
> ours are currently set to every 4 hours, but sometimes they fail and the
> server has to be rebooted to bring them back. Usually after we have had
> network problems.
>
> "David Randall [MS]" <davidra@microsoft.com> wrote in message
> news:%239SDaA1mEHA.2708@TK2MSFTNGP10.phx.gbl...
>> Sounds like a relatively medium load for one DP.  I'd say you're probably
>> fine for now with just the one DP.
>>
>> However, can you clarify a bit more about what you mean by: "seems to
>> struggle somewhen when distributing" ?  There are several links in the
>> process from site server to client install, and maybe we can tune some of
>> those links for you.
>>
>> Dave
>>
>> -- 
>> -- 
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Jeremy Byrne" <J.Byrne@lboro.ac.uk> wrote in message
>> news:u1lhcazmEHA.2588@TK2MSFTNGP12.phx.gbl...
>> > Hi David,
>> >
>> > Thanks for the advice, the set up we have at the minute seems to
> struggle
>> > somewhat when distributing sometimes and I was wondering if we needed
> more
>> > distribution points. At the minute we have one. We have 200 clients
> (going
>> > up each day though) and around 50 advertisements for various things 
>> > from
>> > Office to small bespoke packages for just a few clients. Then of course
> we
>> > have all of the patches and updates on top of that as well. We do have 
>> > a
>> > very very fast network though.
>> >
>> > Anyway I'm going to have a read of those documents but in the mean time
> if
>> > anyone has any suggestions to make our sms system distribute quickly.
>> > Please
>> > let me know.
>> >
>> > Jeremy.
>> >
>> > "David Randall [MS]" <davidra@microsoft.com> wrote in message
>> > news:%23js3uSzmEHA.556@tk2msftngp13.phx.gbl...
>> >> Jeremy,
>> >>
>> >> This is fairly open ended recommendation request.
>> >>
>> >> That said, distribution points are meant to get SMS packages close to
> the
>> >> desktop computers that will be installing the software.  Therefore, 
>> >> the
>> >> number of distribution points per site is somewhat dependent on the
>> >> infrastructure of your network, and how well connected client 
>> >> computers
>> > are
>> >> to your file servers acting as distribution points.
>> >>
>> >> At the following link, you'll find a few pertinent documentation
> pieces:
>> >> http://www.microsoft.com/smserver/techinfo/productdoc/default.asp
>> >>
>> >> 1.  The SMS 2003 Capacity Planner Tool and Guide
>> >> 2.  SMS 2003 Concepts, Planning, and Deployment Guide
>> >>
>> >> There may be some other people who have practical experience with # of
>> >> clients per DP, but honestly, the best answer is "it depends."   That
> is
>> > to
>> >> say, you need to have a rough estimate of the number of packages 
>> >> you'll
>> >> be
>> >> deploying, the number of total clients you have, the average size of
> your
>> >> packages, and the frequency of deployment.  Along with the network
>> >> profile
>> >> (available bandwidth), that will determine your optimum number of 
>> >> DP's.
>> >>
>> >> Dave Randall
>> >> -- 
>> >> -- 
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >> "Jeremy Byrne" <J.Byrne@lboro.ac.uk> wrote in message
>> >> news:%23FRqpHxmEHA.748@TK2MSFTNGP15.phx.gbl...
>> >> > How many distribution points do you recomend having? or how many
>> > machines
>> >> > for one distribution point and how many for two, three four etc??
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
> 


Relevant Pages

  • Re: native texlive and yum
    ... 1-month old broken dependency on the latex binary) I have decides to ... *nonrelated" packages. ... Is there a way for forcing their installation without installing ... packages requiring a LaTeX distribution. ...
    (Fedora)
  • Re: [SLE] Help understanding YOU
    ... Click on that entry and the pertinent packages involved in the patch ... updates supplied by SuSE for YaST installation). ... For example, on my system, YOU currently shows a security patch for KDE 3 ...
    (SuSE)
  • Re: SOL9: How-to find which package a file is in?
    ... If a patch modifies software that is not currently installed and said software is subsequently installed you will need to identify and apply or reapply all the necessary patches. ... So, downloading the entire installation media, along with latest ... Find necessary packages by greping */pkgmap ...
    (comp.unix.solaris)
  • Re: determining the smallest Linux installation to run a particular app
    ... >> Because my Linux app needs to be distributed with the OS, ... >> to minimize the overall size of the distribution, ... >> the smallest set of packages that are required to run my app. ... if your installation is kickstart based or your ...
    (comp.os.linux.setup)
  • Re: debian
    ... Linux Standard Base Core Standard http://www.linuxbase.org/spec/ ... installation of add-on application software packages. ... built for the specific distribution and release that they have. ...
    (alt.linux)