AutoPatcher Forum

I'd like to see a program that can create scripts for Autopatcher using WSUS Offline. Have it tap into however WSUS works with the Skip download box checked. Version 6.2 was the last to support downloading Office 2000 updates. 6.5.5 was the last to support downloading Windows 2000 updates.

The current 6.7 release has added Windows 7/Server 2008 and the latest Office but for Windows it only goes back to XP. It still supports every Office version after 2000 but I bet it'll be dropping Office XP soon.

So now to support everything I have 6.2 just for Office 2000, 6.5.5 just for Windows 2000 and 6.7 for everything else.

What I don't like much about WSUS Offline is there's very little control over what its installer installs. With some way to create Autopatcher scripts from WSUS Offline, I could have everything in Autopatcher plus the 3rd party software WSUS Offline doesn't do.

sorry, but we don't do scripts for WSUS. can be an idea look at their foruns about an way to create scripts for them

[]s

I want to create scripts FROM wsus offline FOR Autopatcher, so Autopatcher can support Office 2000, Windows 2000, Windows 7, the latest MS Office and whatever else wsus offline supports (or previously supported) that Autopatcher does not.

in this case, you will require this. the part about create an script isn't required, except if you wish put it online. for personal usage, you only will require create the .apm files, as explained in that documentation. autopatcher once had office 2000, so no problem with that. about the MS Office part of your request, autopatcher can't recognize office 2010. plus: it has several issues when detecting x64 stuff, including registry keys locates at the x64 part of windows registry. there's plans to that, but the autopatcher team is reduced to an skeleton crew and due that, we can't predict when or if this feature will be added

[]s

I think this is pretty cool, you're going to learn a lot about the process by creating a custom release - I hope you see it through.

To parrot what Cristiano has already said, you wont need to include the creation of a script, you already have the files or will download them directly - simply build a folder structure within \modules and build functional apm files to detect and install the updates. If you decide to share your work a script will be needed.

Remember - you can't distribute Microsoft updates - Microsoft requires users to download the updates directly. This is what got AutoPatcher in hot water and resulted in APUP - please don't archive (exe, iso, rar, zip, etc) your efforts as an AutoPatcher project and offer it for download.

I'd like to have something anyone can put with Autopatcher so they can either use apup to download updates or copy them over from wsus offline.

Wsus offline can be a PITA at times. With verification on it'll simply quit if there's any problem instead of logging the error and going to the next file. With verification off it ends up re-downloading some files if the only difference is a date mismatch. If Microsoft's server kills the connection while a file is being downloaded, it quits. Then it complains about a mismatch on that file and quits when it's run again with verification on instead of just downloading the file again. The only time it doesn't panic and quit is when verification is off and Microsoft's server rejects a connection to *begin* downloading a file. Then wsus offline will go to the next file.

Whomever maintains wsus offline hasn't bothered to fix any of that and it doesn't look like it ever will get fixed. That's one of the reasons why I prefer Autopatcher.

if i'm not mistaken, that issue is created by one main reason: a lot of guys wanna something, but only a few have good will enough to do something about. when someone starts to help, that person realizes that is almost working alone and also has his own life to take care about. when no one helps, nothing is done. personally, i don't think that wsus doesn't have that same issue than we do

[]s