forums.wsusoffline.net

At the moment I am waiting for the office updates; more than 40 minutes are elapsed - is this still normal?
Probably an indicator would be helpful so I can see that something is going on . . .

Regards from Munich
Klaus

edit: verwaisten Beitrag gelöscht, Thema verschoben

Finished - it took nearly three hours. Under directory ...\client\ofc a new file
<UpdateTable-ofc-glb.csv>
was created.
At the moment nearly 200 files are checked - still running . . .

Regards
Klaus

Hi Klaus,

sorry, but that's done in minutes on my system(s).
Which equipment do you use?

Regards
Torsten Wittrock

Data and binaries are stored on a NAS system connected via WLAN to a Lenovo Thinkpad T61 where the actual job is running, internet connection and NAS network connection via DLAN @ 144 MBits. During database creation the notebook's network indicator was blinking all the time and I monitored the resulting file using an editor: Discovered a new entry after about 30 seconds.

Klaus

Hi Klaus,

hmm, I just added a time measurement for testing this part:

Code: Select all

12:28:53,37 - Determining dynamical update urls for ofc glb (please be patient,
this will take a while)...
12:29:47,61 - Done.


This is done on an actual Dell 6410 with local disk access.

I don't know what to do with this now...

Regards
Torsten

Internet connection checked - no problems discovered (Downloaded .cab file with 684 KB/second).
Second run today; same problem: File <UpdateTable-ofc-glb.csv> is growing very slowly: About one entry per 45 seconds (monitoring with PSPad editor).
Started at 17:41, after 10 minutes I discover 15 entries - any ideas what's probably going wrong (all other packets are loading within acceptable time)?

Main question is now: What's going on during this check process? Is the catalog file `../client/wsus/wsusscn2.cab' accessed the whole time. I discover
network activity without doing anything else, probably a locally cached copy would help to speed up - can I adjust the update tool accordingly?

Regards
Klaus

Hi Klaus,

I propose to download directly on the remote machine (server system) or to do it locally and copy/sync the repository afterwards.

Regards
Torsten Wittrock

Hi Torsten,

a local hard disk drive attached via FireWire does the job in about 1 minutes (or even faster) - conclusion: A run of OffLine-Update storing data on a wireless connected network drive is really not
recommended . . .

Many Regards from Munich and have a happy Christmas

Klaus