The non admin install dream
Posted: Thu Apr 05, 2007 8:51 am
I have been reading article upon article about how vista has made the non administrator install possible with file and registry virtualization.
But when I ran my IA setup.exe as a standard user on Vista Ultimate the behaviour of the setup was no different than that of a lowly user in XP.
The behaviour of the setup was as follows: Setup proceeds through all of the dialogs without any problems untill the next button is clicked on the startinstallation dialog and the files actually need to be writen to the target PC. Now I know by default the User profile is denied write access to the program files directory. And that is the reason why I get the "You have insufficiant priviledges to write to this directory $TARGETDIR$"
All I want to know is why can't I use IA to check write access priviledges to my installation directory before I rech the installation point and then give him a dialog to run program as administrator? Instead of setting him up for diassapointment when it's time to actually write the files to his PC.
Comming back to the Vista issue I mentioned earlier the whole concept of storing your program's system data in user specific folders makes no sense to me. Wont having a separate copy of the software for each user cause a maintanance nightmare for the admin who has to make sure that each user is on the latest version of your software? Not even mentioning what the effect might be on your centralized application data if it gets opened by an incompatible version of your software.
But when I ran my IA setup.exe as a standard user on Vista Ultimate the behaviour of the setup was no different than that of a lowly user in XP.
The behaviour of the setup was as follows: Setup proceeds through all of the dialogs without any problems untill the next button is clicked on the startinstallation dialog and the files actually need to be writen to the target PC. Now I know by default the User profile is denied write access to the program files directory. And that is the reason why I get the "You have insufficiant priviledges to write to this directory $TARGETDIR$"
All I want to know is why can't I use IA to check write access priviledges to my installation directory before I rech the installation point and then give him a dialog to run program as administrator? Instead of setting him up for diassapointment when it's time to actually write the files to his PC.
Comming back to the Vista issue I mentioned earlier the whole concept of storing your program's system data in user specific folders makes no sense to me. Wont having a separate copy of the software for each user cause a maintanance nightmare for the admin who has to make sure that each user is on the latest version of your software? Not even mentioning what the effect might be on your centralized application data if it gets opened by an incompatible version of your software.