Manually Insert Update to WSUSOffline

[hesisaboury]

Hello,
I've downloaded MS update ISO files for 5 month and now i want add these update to my wsus offline , if it's possible PLZ
Guide me.

Best Regards

[aker]

Hi hesisaboury,
welcome.
Do you want tod add files to download list, add these Download-Links to the files in .\static.
Adding an ISO for installing is not needed. WSUSOU downloads and installes all needed patches.

[hesisaboury]

Thanks for Response,
i want to extract iso file and use it's files in wsusoffline instead of downloading them again with wsusoffline . if there is a way PLZ explain it

Best Regards,

[aker]

Sorry,
not working.
The filenames differ and its very difficult to find the correct name and rename all files of the ISO.

[hesisaboury]

OK,
the other problem is "Verify Download Update" checkbox , i guess it does not allow downloading update and it stops update , i wanted t know is it important or not ?, if it is how can i
solve my problem....

Best Regards

[boco]

The downloading stops if the generated checksum files are inconsistent and don't match with your updates. Delete the text files in .\client\md\ and try again.

[Denniss]

AFAIR the main folder in a CD/DVD or ISO is basically the client subfolder of a Wsusoffline updater (WOU) installation. To integrate older updates into a newer WOU installation please copy the following folders from your CD/DVD/ISO into the client subfolder of your new WOU installation:
w60, w60-x64, w61, w61-x64, wxp, win, w2k3, w2k3-x64, dotnet, oxp, o2k3, o2k7, msse, wddefs, wsus.
You may not have all of these subfolders in your CD/DVD/ISO.
If the new installation was already used to download updates, do not copy wsus, wddefs, msse and delete the client\md folder. You need to download updates again to clean out old updates and get some new ones.

Do not copy the bin, cmd, static or opt folder as it may overwrite newer WOU file versions. Do not copy the md folder if you want to integrate the older updates into an already used new WOU version - this folder contains checksum tables and if they don't match, downloads stop with file verification error.

[boco]

@Deniss: The OP downloaded update ISOs from MS if I read correctly. I doubt that MS uses WSUSOU (would feel honored if they did ).

Example of a WSUSOU file name:

windows6.1-kb2393802-x86_a3cbe279014841f1ef55099762c9487605a5ef06.cab

First is the real OS name and kernel version (e. g. Windows6.1 is Windows 7).
Then we find the MS Knowledge Base number. Previously also updates existed starting with a Q, but they seem to have vanished.
This is architecture. Currently x86 or x64.
It's a seemingly cryptic number, but in reality it's the SHA1 checksum of the update and can be easily calculated.
File extension. MS usually distributes in executable (.exe), diamond cabinet (.cab), virtual hard disk (.vhd) and Windows IMage (.WIM) format. Only the two former are present in WSUSOU so far.

[Green Lantern]

i have till now used Autopatcher for windows offline updating. Now i m thinking of using wsus. is there way to insert the updates i have downloaded through autopatcher to wsus , so that i don't have to downloaded the same updates again, only new updates only.
i more thing does wsus verify the already installed updates. so that wsus installs only yet not installed updates......plz guide me

[boco]

The problem is the file name format WSUS expects. The Autopatcher updates would probably named differently, I guess. You'd need to construct the file names like I posted above and put them into the right directory under .\client. Even then, it's possible they'll be re-downloaded because WSUSOU relies on accurate file times.

Short version: Generally not worth the hassle, except maybe for very big updates like Service Packs.