Question: are the APM files downloaded from www.autopatcher.com? Or are those actually generated somehow?
Both. You will create em for each update, you will zip em up in a 7z file and then upload them to the server - see any script, at the end of a list of apm files - DownloadFrom=http://www.autopatcher.com/releases/office2007/office_2007_critical_glb_20120313.7z
Just grab an existing apm file or 2, remove all the details inside, use these as templates. Make sure to use a smart naming scheme so the file and folder match, just be consistant and clean if possible... see the docs
- the original file.
- the apm file, the exe dropped and .apm added.
- notice the underscore?
Sometimes the file will allow for it, sometimes you will need to be creative. Here's a couple raw templates (apm, script) to look at - http://www.autopatch...dpost__p__15374
Question: What are the RTI files and are they downloaded or automatically generated?
The RTI tool will create a file (.rti) to sign the release, to make it official. You (?) will do this after the release looks good. It isn't important when building a new script. Without the .rti file the release will show unofficial. You would need to be a team member before getting the tool, this may have changed.
Question: (this one is specific)
Regarding the Office 2007 SP3 script I have the following observations:
1) KB2526086 (SP3) and it's download is listed nowhere (i assume this is because it is assumed it was manually downloaded?
2) The APM office_2007.apm seems to be the main APM for the SP3 release. Should it contain reg keys to identify if SP3 has been downloaded?
1) In most cases when you see sp3, sp2, etc - this is a requirement, it must already be installed on the users machine. It is up to the release manager to include the service pack or not in the package - in most cases no, too big. A service pack would be an addon, another script altogether. I'll repeat this again, make sure that no other update is getting installed if you're updating a machine to the next level service pack - do this first, reboot!
2) See the docs
The apm files you mention are categories, and the best way to see how this works is to start clean, no other files except the 3 apm files listed here in the \modules folder - office_2007.apm, office_2007_moc.apm, office_2007_viewers.apm - Mess with the dates, notice how the categories change order. Also, look at the categories, notice no parent, the other apm files will list one of these 3 as parent - pay attention to this. Did I mention, see the docs
When you have a few apm files (parent categories) in the \modules folder fire up AutoPatcher, experiment.
Question: It seems that you bundle the updates with Office 2007 with the actual Service Pack update itself. I say this because I also downloaded the SP1 and SP2 addons pack for Office 2007. SP1 was actually downloaded as a part of the SP1 addon pack.
The scripts may not be consistant here, if the service pack is small enough to bundle it may be a good idea, normally it is simply a requirement. If the service pack is not an available addon package, there may be links to the service pack - see the Windows XP and Windows 7 hotfix depot pages.
If you bundle the service pack make sure the user installs only the service pack, reboots, then proceeds with additional updates - see update detections for help with prerequisites, the docs
For consistency (in my opinion) it would make sense to put the Service Packs as their own downloads, and then to require a reboot for the rest of the updates, or to include the Service Pack and all the latest updates for that service pack (if it is possible to install the service pack without rebooting and then install all the updates and then experience no errors).
I like your first idea, the service as a separate download, an addon pack.
I'm just a little confused how the SP1 addon pack includes the SP1 update file, but the SP3 script does NOT include the SP3 file and does not include the reg checks for it either.
Did the SP3 link change maybe?
AutoPatcher needs the help of volunteers, everyone has their own way, again, they're not always consistant. See what you think, get the size, get additional opinions. In some cases it may be easier to offer the link to the user rather than trying to find a detection that works with AutoPatcher, this can really be problematic - do you want the responsibility
At this point I'll just be doing trial and error until I figure it out. The current scripts are a bit confusing. I'm going to try a solution that involves always using a "clean start" so all files will be downloaded regardless. Once I get that done, I'll try the file checking. I still got lots to learn.....
Build a package a few files at a time, run AutoPatcher to at least see if the update is visible, the title and description are good - trial and error. Again, read the docs fully, for both the scripts and apm files, and look at some existing scripts.
Edited by _def_x_, 07 May 2012 - 02:36 AM.