Hi!
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