A client is installing a major revision to their software. I have prepared the Setup.exe using Inno Setup. The client reports that he must give users Admin rights to run the new app's launcher while the launcher for the older app (VFP7 with Setup.exe by InstallShield) doesn't need these extra rights. It stands to reason that users need the ability to copy a file from server to local drive for the update to work but why should there be any differences in the default rights granted by InnoSetup and InstallShield when creating the app directory? I don't even see a way to change permissions on the app directory in InnoSetup....

The actual launcher code is identical for the apps except for file and directory references. They run side by side on each workstation. Why does one copy command succeed where the other fails?

Update: It would appear that InstallShield's default behavior is to grant users modify privileges while Inno Setup's default behavior prevents this (Inno Setup documents this.) Does anyone know for sure about InstallShield's behavior? How would I add this permission to the InnoSetup script? I'm guessing the directory would have to be created explicitly by adding a [Dir] section since the creation of the app directory isn't explicitly specified but is implied by the exe placement.