itmu best practice

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

itmu best practice

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> itmu best practice

Page: [1]

Message

<< Older Topic Newer Topic >>

itmu best practice - 8/29/2008 6:14:13 PM

jseber1982

Posts: 67
Score: -2
Joined: 5/16/2007
Status: offline

How do you have your patches set up?

1 package with everything.. 1 for each month...1 for each app.. or what?

The reason for this is because one of our remote offices is complaining that each month.. the entire itmu patch file of 700megs is getting sent to every machine,, even though only a small patch is being added to it. Is there a setting or something that will fix this?

All of our primary servers are right here in atlanta.. approx 300 secondaries around the country.. and then 30 up in canada..

The pipe between us and Canada is very small. All of the secondaries up in Canada go across the pipe. I figure it would be better on bandwidth to move the Canada primary from Atlanta to up in Canada somewhere.

I thought that itmu did delta updates to the itmu file.. there must be a setting or something

< Message edited by jseber1982 -- 9/2/2008 2:24:43 PM >

_____________________________

Justin Seber
Enterprise SMS Admin
Overclocking Guru
jseber1982@yahoo.com

Post #: 1

RE: itmu best practice - 8/29/2008 7:14:49 PM

mbaird

Posts: 60
Score: 0
Joined: 9/13/2001
Status: offline

Our corporate Office tried the monthly approach for awhile and did not like it. They had problems with keeping everything current, especially new computers and units that were offline for a few months. Some patches might be needed from two years ago so you will need a package that is all inclusive. I use an approach where there is a package for each operating system and they accumulate all the patches since we started. The folders get somewhat large but we do not have any remote users who download the updates. All user runs the patch program whether they are local or remote.

(in reply to jseber1982)

Post #: 2

RE: itmu best practice - 8/31/2008 8:12:50 AM

tbiggi

Posts: 64
Score: 1
Joined: 9/13/2001
Status: offline

The ITMU, as with any package, will do a delta update to the package but:

The SMS client will download the entire package even if it only needs one patch. (Note: SCCM2007 w/WSUS only downloads what is needed).
Since you updated the package it is a new version so even though you are downloading the same package there will be multiple versions on the SMS client (assuming you are using download then execute option.

We have a larger environment than you do an use the monthly method. A single package is not a good option for us because of the very, very large size. Instead, I keep collections, queries and reports for the monthly patches and can rerun the advert as needed. That could also be setup on a recurring schedule.

Tom

(in reply to mbaird)

Post #: 3

RE: itmu best practice - 9/2/2008 8:33:46 AM

hcortez463

Posts: 781
Score: 63
Joined: 4/8/2005
Status: offline

I used to this this at my other job but it worked great as i was running everything from The DP. nothing got downloaded to cache. Like Tbiggi said, new version, it will redownload everything downand install only what it needs. What i would recomend is created a package with all patches as a maditory adv to all PC, then created one for each month from that point on and asigne to same collection. That way you keep your comliace intact and new PC will only download the new packages not the entire (big) one that has allready been installed. Hope that makes sence

_____________________________

If it Helps, Please rate....

(in reply to tbiggi)

Post #: 4

RE: itmu best practice - 9/2/2008 10:26:25 AM

ctour

Posts: 21
Score: 0
Joined: 8/8/2008
Status: offline

We had a baseline, which is XP SP2. We deployed SP2 to those without SP2(a collection without SP2), and individual updates for those with SP2(another collection with SP2).

(in reply to hcortez463)

Post #: 5

RE: itmu best practice - 9/2/2008 2:19:31 PM

jseber1982

Posts: 67
Score: -2
Joined: 5/16/2007
Status: offline

thanks for the replies guys.

I guess what i will do.. is keep the package that is currently in production since all machines have it. I will then start a new package so that the old 700meg one will not be pushed anymore except to new machines

_____________________________

Justin Seber
Enterprise SMS Admin
Overclocking Guru
jseber1982@yahoo.com

(in reply to jseber1982)

Post #: 6

RE: itmu best practice - 9/5/2008 8:09:52 AM

lbriggs

Posts: 94
Score: 2
Joined: 7/10/2003
From: Hartford, CT
Status: offline

Due to the size of our infrastructure, we try to keep the patch package sizes as low as possible so that we do not cause havok in our smaller link sites. Typically we divide up the patches by product: OS, OFFICE XP, OFFICE 2K3, OFFICE2K7, etc, and then use query based collections to make sure we're not sending patches to machines that do not have the product installed. It is rather time consuming, but in the long run I feel it is more efficient, and is a better use of network bandwidth.

As a personal rule, I try to make sure each patch package is under 50 meg. Unfortunately with the SQL patches of last month, I was unable to get the patch package under 150 meg (after removing the Itanium and x64 bit patches).

(in reply to jseber1982)

Post #: 7