Is there any way to rollup the XP Post-SP2 hotfixes into a single install?

[Seymour Butts]

It's getting to be a real pain having to manually install 40+ (and
growing daily) hotfixes from Microsoft everytime someone brings me an
unpatched XP/SP2 system. I know MS is working on an SP3 or rollup in
the near future but is there an unofficial rollup or even script that
is available to save me a half hour of aggravation everytime I gotta
bring an SP2 system up to date? I don't need a slipstream or patching
program to put them into the OS install, that does me no good. Just a
simple 1-click and install all post-sp2 hotfixes.

Thanks

 

[badgolferman]

It's getting to be a real pain having to manually install 40+ (and
growing daily) hotfixes from Microsoft everytime someone brings me an
unpatched XP/SP2 system. I know MS is working on an SP3 or rollup in
the near future but is there an unofficial rollup or even script that
is available to save me a half hour of aggravation everytime I gotta
bring an SP2 system up to date? I don't need a slipstream or patching
program to put them into the OS install, that does me no good. Just a
simple 1-click and install all post-sp2 hotfixes.

Thanks

Here's one solution:
http://www.windowsitpro.com/Windows/Article/ArticleID/42191/42191.html

 

[Rebecca]

It's getting to be a real pain having to manually install 40+ (and
growing daily) hotfixes from Microsoft everytime someone brings me an
unpatched XP/SP2 system. I know MS is working on an SP3 or rollup in
the near future but is there an unofficial rollup or even script that
is available to save me a half hour of aggravation everytime I gotta
bring an SP2 system up to date? I don't need a slipstream or patching
program to put them into the OS install, that does me no good. Just a
simple 1-click and install all post-sp2 hotfixes.

Thanks

http://img212.imageshack.us/img212/8863/bartgooglethumb0bj.gif

 

[Spuds]

It's getting to be a real pain having to manually install 40+ (and
growing daily) hotfixes from Microsoft everytime someone brings me an
unpatched XP/SP2 system. I know MS is working on an SP3 or rollup in
the near future but is there an unofficial rollup or even script that
is available to save me a half hour of aggravation everytime I gotta
bring an SP2 system up to date? I don't need a slipstream or patching
program to put them into the OS install, that does me no good. Just a
simple 1-click and install all post-sp2 hotfixes.

Thanks

http://www.autopatcher.com/
Very slick.

 

[Grinder]

It's getting to be a real pain having to manually install 40+ (and
growing daily) hotfixes from Microsoft everytime someone brings me an
unpatched XP/SP2 system. I know MS is working on an SP3 or rollup in
the near future but is there an unofficial rollup or even script that
is available to save me a half hour of aggravation everytime I gotta
bring an SP2 system up to date? I don't need a slipstream or patching
program to put them into the OS install, that does me no good. Just a
simple 1-click and install all post-sp2 hotfixes.

In addition to the excellent advice already dispensed, I like to add
that you can search for "Windows XP" slipstream to find out how to roll
service packs and updates into a single install.

 

[kony]

It's getting to be a real pain having to manually install 40+ (and
growing daily) hotfixes from Microsoft everytime someone brings me an
unpatched XP/SP2 system. I know MS is working on an SP3 or rollup in
the near future but is there an unofficial rollup or even script that
is available to save me a half hour of aggravation everytime I gotta
bring an SP2 system up to date? I don't need a slipstream or patching
program to put them into the OS install, that does me no good. Just a
simple 1-click and install all post-sp2 hotfixes.

Thanks

What's wrong with just enabling automatic updates, leaving
the system sit idle so it's downloading them at peak speed
automatically, then rebooting at which point it displays
something akin to a shield on the reboot window signifying
you have things ready to install? It's about as hands-off
as it gets, and if your users "need" to have updates done
for them, they might benefit more from the updates being
automatic, risking the small chance an update could cause a
problem, rather than the larger security risk of NOT having
the updates in a timely manner.

 

[Spuds]

What's wrong with just enabling automatic updates, leaving
the system sit idle so it's downloading them at peak speed
automatically, then rebooting at which point it displays
something akin to a shield on the reboot window signifying
you have things ready to install? It's about as hands-off
as it gets, and if your users "need" to have updates done
for them, they might benefit more from the updates being
automatic, risking the small chance an update could cause a
problem, rather than the larger security risk of NOT having
the updates in a timely manner.

Not an optimal solution if the user was on a dialup connection. Downloading
all the patches since SP2 takes eons.

 

[badgolferman]

http://www.autopatcher.com/
Very slick.

Have you actually used this and how does it work?

 

[Null]

Have you actually used this and how does it work?

Yes I have, and it works very well.

 

[XModem]

Good advice [

What's wrong with just enabling automatic updates, leaving
the system sit idle so it's downloading them at peak speed
automatically, then rebooting at which point it displays
something akin to a shield on the reboot window signifying
you have things ready to install? It's about as hands-off
as it gets, and if your users "need" to have updates done
for them, they might benefit more from the updates being
automatic, risking the small chance an update could cause a
problem, rather than the larger security risk of NOT having
the updates in a timely manner.

 

[kony]

Not an optimal solution if the user was on a dialup connection. Downloading
all the patches since SP2 takes eons.

True, but, we're talking about the poster doing it now,
plus, later if the owner only has dial-up, that IS the
method that'll have to be used unless you're suggesting they
bring the system back to the OP every time MS releases
another patch??

 

[-nos1eep]

It is further alleged that on or about Sun, 02 Apr 2006 22:47:10 GMT,
in alt.os.windows.xp, the queezy keyboard of kony <[email protected]>
spewed the following:

|On Sat, 01 Apr 2006 22:27:22 -0500, Spuds
|
|>
|>>On 1 Apr 2006 18:10:20 -0800, "Seymour Butts"
|>Not an optimal solution if the user was on a dialup connection. Downloading
|>all the patches since SP2 takes eons.
|
|
|True, but, we're talking about the poster doing it now,
|plus, later if the owner only has dial-up, that IS the
|method that'll have to be used unless you're suggesting they
|bring the system back to the OP every time MS releases
|another patch??

What a great idea! At a minimum $40 bench fee, this could add up.
I might even be able to buy the 35', 1000HP, Aero-Tek cigarette boat
that I have been drooling over.
The number of security patches issued for 2005 total 55. This compares
to 45 patches for 2004, 51 for 2003, 72 for 2002, and 60 for 2001. Woo
hoo! I'll be rich!

 

[Spuds]

True, but, we're talking about the poster doing it now,
plus, later if the owner only has dial-up, that IS the
method that'll have to be used unless you're suggesting they
bring the system back to the OP every time MS releases
another patch??

I think the original context was for a tech to reconfigure a client's machine.
You wouldn't want to send the client away with the OS needing patches. I
think it's a given that the client is responsible for updates after the fact.

Not sure why you'd conclude the user would have to bring the machine back.
It's infinitely easier installing patches via dialup, as they come out, rather
than several hundred at a shot.

 

[kony]

I think the original context was for a tech to reconfigure a client's machine.
You wouldn't want to send the client away with the OS needing patches. I
think it's a given that the client is responsible for updates after the fact.

Not sure why you'd conclude the user would have to bring the machine back.
It's infinitely easier installing patches via dialup, as they come out, rather
than several hundred at a shot.

I'd conclude it because you wrote above "Not an optimal
solution if the user was on a dialup connection."

" Downloading all the patches since SP2 takes eons."


Here's how it'd play out:

OP enabled automatic updates. They immediately start
downloading THEN, at that time. OP comes back to system,
which has updated itself, reboots and tests that it works
ok. System then has automatic updates enabled and that
stays enabled when owner takes it home.

It is never a situation where, as you suggested, anything
would take eons because the system has already begun
updating itself right after the feature is enabled... system
doesn't know where it's home is and wait till it gets "home"
to do that.

 

[Joe Morris]

It's getting to be a real pain having to manually install 40+ (and
growing daily) hotfixes from Microsoft everytime someone brings me an
unpatched XP/SP2 system. I know MS is working on an SP3 or rollup in
the near future but is there an unofficial rollup or even script that
is available to save me a half hour of aggravation everytime I gotta
bring an SP2 system up to date? I don't need a slipstream or patching
program to put them into the OS install, that does me no good. Just a
simple 1-click and install all post-sp2 hotfixes.

Not much of a problem. Assuming that you've downloaded all of the
appropriate patches, build a script that installs all of the current
ones using the no-interaction and no-reboot options (most patches
do this with the switches /PASSIVE and /NOREBOOT but you need to
check each patch to verify this). At the end run the current version
of QCHAIN to flush out any conflicts, then reboot. (I usually also
set the /NOBACKUP switch; I don't want users uninstalling patches.)

If you know that the target system is unpatched you can make the
installation of each patch unconditional. If you're using the
script to update systems that might be partially patched, you can
add tests for each patch to see if it's present and run the installer
only if necessary.

And at the end, consider running Windows Update as a sanity check.
If everything's up to date it won't install anything, but if something
odd has interfered with a patch installation process, using Windows
Update should detect the incomplete installation and repair it.

There are a few patches -- typically service packs -- which must be
followed by a reboot before additional updates are performed. Be
sure to read the KB articles about the patches you want to install.

Joe Morris