5 replies to this topic

[SLConsultingsvc]

I cannot seem to find this info on the site or the user guide so I will ask here. How far behind the current updates does the APUP typically stay? I updated a test 2000 machine and found that the October updates are missing. Is there a way that I can custom add newer updates to to the program? Thanks in advance.

[Cristiano]

well, to make the history short, we don't have an release maintainer to w2k anymore. due that certain updates will be missing in deed. there's an warning when you run apup about that

> Is there a way that I can custom add newer updates to to the program?
yes. you just need download the updates and then take an existing module as template. just don't forget that the updates must stay in a folder with the same name of the module, plus _files

we can elaborate more, if you wish

[]s

[SLConsultingsvc]

Cristiano, on 11 November 2009 - 05:36 PM, said:

well, to make the history short, we don't have an release maintainer to w2k anymore. due that certain updates will be missing in deed. there's an warning when you run apup about that

> Is there a way that I can custom add newer updates to to the program?
yes. you just need download the updates and then take an existing module as template. just don't forget that the updates must stay in a folder with the same name of the module, plus _files

we can elaborate more, if you wish

[]s

So if I downloaded KB956844, I would simply drop it in the critical folder under a folder called KB956844_2K_enu.apm_files?

[Cristiano]

almost that. you need:
- make an copy from any other module from the same category;
- rename kbxxxxxx_2k.enu.apm file to the new kb number;
- open the .apm file and edit the proper fields to match with the new ones, like detection description etc. just remember: UniqueID= must be really unique. so, an idea is edit the field and put the kb number in there;
- in order to work properly, the detection need to be right. so, you can install the update in one machine and take the detections from that machine. almost all the detections are in the same place, with the name of the new kb. the file md5 is the md5 from the .cat file that acts as detection;
- then, change the [Installation] field to match with the name of the update, as is in the template module;
- now, save it and set an new folder, with the exact name of the .apm file plus _files. in your sample, if you have an .apm file with the name KB956844_2K_enu.apm , then your folder must have the name KB956844_2K_enu.apm_files. now, put the update in there

it's done. now, at the next autopatcher run, it shall show your customized module. we have some documentation for that. it's old and lacks a lot of things. if you wish, i can find the link for that and paste in here

[]s

[LostUser]

Quote

it's done. now, at the next autopatcher run, it shall show your customized module. we have some documentation for that. it's old and lacks a lot of things. if you wish, i can find the link for that and paste in here

That would be nice. I thought I found something at the neowin.net archives but can't find it again. I have made a good number of notes on where to get the info for the .apm files. Also, I didn't realize the md5 hash came from the .cat file, I thought it was the KB######.exe ... my mistake there.

[Cristiano]

ok. you can get that documentation from here. but it is lacking some infos

> neowin.net archives
i have all those too. most of those infos was related only to the old way of distribution and there's a couple of changes between that and the apup system

[]s