Network shares are specific to the suer who created them. When the server side of the installation runs, it runs as SYSTEM (or LocalService or something), which won't have visibility of your network shares. This is probably why your deferred custom action doesn't work. If you tried to run it as impersonated it might work. As for why the installer works, I'm not sure. I imagine Windows Installer must have some magic in it for handling mapped drives.
Rob Alexander Gnauck wrote: > Hello, > > i still have problems with my custom actions on Windows Vista. > > With lots of workarounds and > Execute='deferred' Impersonate='no' flags > we got them working now on Vista in the most cases. > > The case where they don't work is when the program or parts of the > program get installed on a network share. > The MSI installer service is running under the local system account, and > of course the local system account has no permissions to write data on a > network share. So the defereeed actions fail. > > Why is the installer able to install the files on a network share but my > deferred elevated custom action is not able to write a file in the same > directory on a network share? > > Is there any solution for this problem? > > Thanks > Alex > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
