Thanks so much for al the work that has gone into making this available. I'm using AutoPatcher to keep from having to download all the post-SP3 updates as I refurbish older machines by reinstalling all the software from scratch.
My question is... am I missing anything by using one machine to download all the patches and then using that to update a different machine? In other words, when I use a Fujitsu laptop to fetch all the updates and then burn that to CD to run on a Dell desktop, is AutoPatcher missing some files because it was assembling a download list based on what was on the Fujitsu laptop?
Are there any pointers I need to know to help streamline the process for my particular application of the program?
Secondarily, can I use AutoPatcher on an XP system to download and burn the Vista updates? I'm guessing I'd need to create a separate folder (at the least), if this is even possible.
Thanks in advance for any help.
JEFF
0
Using AutoPatcher to update multiple machines
Started by SVJeff, Nov 10 2012 06:40 PM
2 replies to this topic
#2
-
- Veterans
-
- 1,460 posts
audi 5k
- Gender:Male
Posted 10 November 2012 - 09:16 PM
Hi SVJeff 
It's also nice to get a newly built or refurbished machine patched before hitting the inter-webs or having to use MU/WU for hours on end. AutoPatcher tries to offer as many updates as possible, each machine will likely need a few more files to be fully compliant with MU/WU.
Very common question, and the answer is no, or yes - I'm confused. You can use any machine that can run APUP (apup.exe) - Win2K thru Win7, and get the latest release or update an existing release. APUP downloads a release based on the script which gets updated every Patch Tuesday. OTOH, MU/WU scans your system and offers patches accordingly.
As well, if you run AutoPatcher (autopatcher.exe) on an XP machine for example, an update that is not suitable for XP will be hidden (hopefully). If you look at the .apm file, there are prerequisites that need to be met - XP SP3 x86, IE7... for example, this update will not be visible on an XP machine that is still at SP2 or is running IE6 or IE8.
If you look at the apm file (in any text editor) there are numerous other categories too, "DotNetFramework=", "WindowsInstaller=", "DirectX=", etc, these matter when its time to install the update. The categories (system prerequisites) help target the right system.
XP is pretty old in OS years, you might look at updating your install disc by slipstreaming as many patches as possible. There are a few you will need to install on a running system but you could get a lot of the OS patched at the disc level. Check out the RyanVM forums or MSFN.
Don't try to get all the updates installed in one pass. I also recommend updating big picture items one at a time - reboot. For example - IE6 to IE7 or IE8, .NET 3.5, 4.0, 4.5, DirectX, etc. You want a successful install on these items, small patches can be chained together of course - this is what AutoPatcher does.
See my first comment.
I have always used separate folders for the OSes, the addon packs can go in one folder - JMO
C:\apup
..................\AddonPacks
..................\Sevenx64
..................\Vistax86
..................\XPx86
I then have 3 shortcuts for each release... named for the release (notice the icon)...?
... autopatcher.exe /nolicense ::: don't forget to use the /nolicense switch to bypass the EULAs.
... apup.exe /log ::: don't forget to use the /log switch to have a log file ready when needed.
... apup.log ::: to quickly have access to the log file, will open in default application - notepad usually.
Again, JMO
Quote
I'm using AutoPatcher to keep from having to download all the post-SP3 updates as I refurbish older machines by reinstalling all the software from scratch.
It's also nice to get a newly built or refurbished machine patched before hitting the inter-webs or having to use MU/WU for hours on end. AutoPatcher tries to offer as many updates as possible, each machine will likely need a few more files to be fully compliant with MU/WU.
Quote
My question is... am I missing anything by using one machine to download all the patches and then using that to update a different machine? In other words, when I use a Fujitsu laptop to fetch all the updates and then burn that to CD to run on a Dell desktop, is AutoPatcher missing some files because it was assembling a download list based on what was on the Fujitsu laptop?
Very common question, and the answer is no, or yes - I'm confused. You can use any machine that can run APUP (apup.exe) - Win2K thru Win7, and get the latest release or update an existing release. APUP downloads a release based on the script which gets updated every Patch Tuesday. OTOH, MU/WU scans your system and offers patches accordingly.
As well, if you run AutoPatcher (autopatcher.exe) on an XP machine for example, an update that is not suitable for XP will be hidden (hopefully
). If you look at the .apm file, there are prerequisites that need to be met - XP SP3 x86, IE7... for example, this update will not be visible on an XP machine that is still at SP2 or is running IE6 or IE8. If you look at the apm file (in any text editor) there are numerous other categories too, "DotNetFramework=", "WindowsInstaller=", "DirectX=", etc, these matter when its time to install the update. The categories (system prerequisites) help target the right system.
Quote
Are there any pointers I need to know to help streamline the process for my particular application of the program?
XP is pretty old in OS years, you might look at updating your install disc by slipstreaming as many patches as possible. There are a few you will need to install on a running system but you could get a lot of the OS patched at the disc level. Check out the RyanVM forums or MSFN.
Don't try to get all the updates installed in one pass. I also recommend updating big picture items one at a time - reboot. For example - IE6 to IE7 or IE8, .NET 3.5, 4.0, 4.5, DirectX, etc. You want a successful install on these items, small patches can be chained together of course - this is what AutoPatcher does.
Quote
Secondarily, can I use AutoPatcher on an XP system to download and burn the Vista updates? I'm guessing I'd need to create a separate folder (at the least), if this is even possible.
See my first comment.
I have always used separate folders for the OSes, the addon packs can go in one folder - JMO
C:\apup
..................\AddonPacks
..................\Sevenx64
..................\Vistax86
..................\XPx86
I then have 3 shortcuts for each release... named for the release (notice the icon)...?
... autopatcher.exe /nolicense ::: don't forget to use the /nolicense switch to bypass the EULAs.
... apup.exe /log ::: don't forget to use the /log switch to have a log file ready when needed.
... apup.log ::: to quickly have access to the log file, will open in default application - notepad usually.
Again, JMO
#3
-
- Project Manager
-
- 1,163 posts
Just an awesome guy.
- Gender:Male
- Location:California, USA, Earth, SOL, Milkyway
- Interests:Programming and being a know it all pest.
Posted 10 November 2012 - 09:33 PM
Autopatcher(apup) will download all updates for what ever OS you select. This does not include drivers or anything specific to say HP or Dell.
edit: doh def x got it before me. darn kids.
Actually many of those are being removed to save space and confusion. So he might not be able to find them except in the template apms. AP auto-fills them in with ANY if not specified.
everything else is a sterling response as usual.
edit: doh def x got it before me. darn kids.
Quote
If you look at the apm file (in any text editor) there are numerous other categories too, "DotNetFramework=", "WindowsInstaller=", "DirectX=", etc, these matter when its time to install the update. The categories (system prerequisites) help target the right system.
everything else is a sterling response as usual.
Edited by ViroMan, 10 November 2012 - 09:37 PM.
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users
