Manually adding updates - hash issues

Re: Manually adding updates - hash issues

Postby boco » 14.10.2013, 18:25

The file in custom has exactly the same name and the same structure as the main file. The big gotcha with the main file is that it will be overwritten during an update, while the custom files aren't touched.
Microsoft update catalog: http://catalog.update.microsoft.com/v7/site/
Windows Install media download: https://support.microsoft.com/en-us/help/15088/windows-create-installation-media
boco
 
Posts: 2398
Joined: 24.11.2009, 17:00
Location: Germany

Re: Manually adding updates - hash issues

Postby rb51 » 15.10.2013, 14:00

aker wrote:If you have a direct link to the msu or cab file, just paste it with an empty line at the end into the cutom text file.
The link could be:
Code: Select all
http://dowload.microsoft.com/.../Windows6.1-KB123456-x86.msu

If you don't have one, please disable the cleanup option in UpdateGenerator.

@WSUSUpdateAdmin
Wie wäre es im Client-Ordner mit einem "custom"-Ordner, der nicht durch den UpdateGenerator bereinigt wird?
So könnte man zwar weiterhin die superseded Updates löschen, jedoch custom-Updates wie Hotfixes oder Updates aus dem Update Katalog würden nicht gelöscht.

Hi aker, thanks for your reply....

It might involve some manual process but it think I've found a way of getting the direct link to the msu's.

I will give it a try and see what happens....thanks again
rb51
 

Previous

Return to Installation / Updating

Who is online

Users browsing this forum: Google [Bot] and 29 guests