forums.wsusoffline.net

Still have my GPL doubts about the second fase. Here are non GPLed products packed
with GPLed ones. But it happens at the users site and under his control. So it is not far
away from making a backup or copy for self use.

The end user may not distribute these iso's. So far is clear.

Tijd voor een CupaSoup

I didn't find clear information about tcc license on their site. The GPL essentially says you can't include proprietary software. I don't believe TCC is Open Source, as it is a subset of their paid product.

Anyway, if you want to get an opinion that actually counts, please wait for the WSUSOU dev to reply.

Okay, once again:

1) You can already start the updating process from a network share.
2) If your network share is unmapped, UpdateInstaller.exe will automatically map it for you.
3) If you prefer a direct call of Update.cmd or DoUpdate.cmd, you'll have to map your network share by "net use ..." before. This is reasonable in my opinion.
4) To avoid this technical limitation of cmd.exe, one could use your TCC shell. Much quicker and easier though, one could hack the registry as described in the Microsoft article mentioned above ( http://support.microsoft.com/kb/156276). Anyway, what would you earn? You'ld just save one "net use" call, but
5) This would not bring back the missing autorecall feature! The automatic recall feature would still be unavailable, because the new, temporary user which is automatically logged on won't have access to the share, mapped or unmapped, persistent or not. That's the main restriction when you use a network share as source, that's the feature people cry for, it's a logical problem and therefore I suppose we won't get it solved in a satisfying way.

I hope this clarifies.

Regards
Torsten Wittrock

Ok. Thanks Torsten.

Not that I myself ever wanted to run from network shares.
Autorecall. That might be a show-stopper. I will think that one over.

Eric-Jan.

Hi!

I just had an idea today - try http://trac.wsusoffline.net/browser/trunk (r297).


RTW