Re: Network share support
Posted: 26.05.2010, 20:00Any update yet?
BrentNewland wrote:Any update yet?
No, sorry, not for the next release to come, but maybe for the one after.
Regards
Torsten Wittrock
forums.wsusoffline.net
Forums for questions, problems and suggestions concerning WSUS Offline Update
https://forums.wsusoffline.net/
Network share support
Page 2 of 2
Posted: 26.05.2010, 20:00Re: Network share support
Posted: 14.06.2010, 11:58No, sorry, not for the next release to come, but maybe for the one after.
Regards
Torsten Wittrock
Re: Network share support
Posted: 15.06.2010, 00:15WSUSUpdateAdmin wrote:BrentNewland wrote:Any update yet?
No, sorry, not for the next release to come, but maybe for the one after.
Regards
Torsten Wittrock
Awesome, any idea how long before it makes its way into the trunk?
Re: Network share support
Posted: 02.08.2010, 17:58So when can we expect it to hit the trunk?
Re: Network share support
Posted: 19.08.2010, 15:28Sorry for delay and up with this thread.
I hope to get it done soon (next 2-3 weeks).
RTW
I hope to get it done soon (next 2-3 weeks).
RTW
Re: Network share support
Posted: 25.08.2010, 11:42Hi!
I read through/over/across your postings again yesterday.
I think the changes you suggested are much too complex and they also deal with several features (UNC support, UAC, logging, ...).
So let's go a little bit back to the current state and your requirement:
- The update installation process runs without any problems if you start it from a mapped network share, regardless of the starter application you use (UpdateInstaller.exe or Update.cmd/DoUpdate.cmd), except for the "autorecall" feature under XP.
- The update installation process can't be started from an unmapped UNC network path, since cmd.exe does not support UNC names as the current directory.
And here comes the solution:
- If you like to use calls to Update.cmd/DoUpdate.cmd to start the installation process, you may use "net use ..." in your underlying command script to do the drive mapping before you call Update.cmd/DoUpdate.cmd.
- If you prefer UpdateInstaller.exe, this script should do the drive mapping if started from an unmapped UNC path. That's what I now implemented in http://trac.wsusoffline.net/browser/trunk (r129).
Thanks & regards
Torsten Wittrock
I read through/over/across your postings again yesterday.
I think the changes you suggested are much too complex and they also deal with several features (UNC support, UAC, logging, ...).
So let's go a little bit back to the current state and your requirement:
- The update installation process runs without any problems if you start it from a mapped network share, regardless of the starter application you use (UpdateInstaller.exe or Update.cmd/DoUpdate.cmd), except for the "autorecall" feature under XP.
- The update installation process can't be started from an unmapped UNC network path, since cmd.exe does not support UNC names as the current directory.
And here comes the solution:
- If you like to use calls to Update.cmd/DoUpdate.cmd to start the installation process, you may use "net use ..." in your underlying command script to do the drive mapping before you call Update.cmd/DoUpdate.cmd.
- If you prefer UpdateInstaller.exe, this script should do the drive mapping if started from an unmapped UNC path. That's what I now implemented in http://trac.wsusoffline.net/browser/trunk (r129).
Thanks & regards
Torsten Wittrock
Re: Network share support
Posted: 18.09.2010, 00:50I guess that's progress. I haven't tried it on vista or 7, but can I assume that those don't support automatic restart and recall over the network either?
My main goal was to be able to run a single script, have it install whatever updates it needs to, automatically restart and continue updating, and just continue doing so until it's completely up to date. Even if it has to install service packs, even if it's Windows XP. However, I can see how the code I wrote was a bit long in the tooth (although with some minor tweaking and testing I'm sure it would work great).
BTW, not sure if this has been fixed recently or not, but after IE8 installs it finishes the update process and asks you to restart. I am able to type in "doupdate" and it installs the rest of the updates just fine (this is in XP btw).
My main goal was to be able to run a single script, have it install whatever updates it needs to, automatically restart and continue updating, and just continue doing so until it's completely up to date. Even if it has to install service packs, even if it's Windows XP. However, I can see how the code I wrote was a bit long in the tooth (although with some minor tweaking and testing I'm sure it would work great).
BTW, not sure if this has been fixed recently or not, but after IE8 installs it finishes the update process and asks you to restart. I am able to type in "doupdate" and it installs the rest of the updates just fine (this is in XP btw).