This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Update multiple instances (InstallScript Project) without admin privleges
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 20, 2010
05:27 AM
Update multiple instances (InstallScript Project) without admin privleges
Hi everybody,
we have an InstallScript Project supporting multiple instances. Now we wan't that our users are able to update their installations without having admin privileges.
Unfortunately when an unser without admin privileges starts the setup there is no possibility to choose the instance. He can only install a new instance (that works). When an administrator runs the setup he sees all instances (including the one installed by the non-admin user).
If we pass the instance's guid to the setup with "/ig{guid}" everything works fine for normal users, too. So the problem seems to be that InstallShield doesn't search for existing instances (even thoose installed by the same user!) when started by a non-admin user.
The same behavier can be seen when enabling multiple instances for the ALLUSERS Sample Project.
Our only idea for a workaround is to force non-admin users to pass the instance's guid.
Does anybody have a clue how InstallShield can be told to search for other instances when executed by a normal user?
Thanks!
we have an InstallScript Project supporting multiple instances. Now we wan't that our users are able to update their installations without having admin privileges.
Unfortunately when an unser without admin privileges starts the setup there is no possibility to choose the instance. He can only install a new instance (that works). When an administrator runs the setup he sees all instances (including the one installed by the non-admin user).
If we pass the instance's guid to the setup with "/ig{guid}" everything works fine for normal users, too. So the problem seems to be that InstallShield doesn't search for existing instances (even thoose installed by the same user!) when started by a non-admin user.
The same behavier can be seen when enabling multiple instances for the ALLUSERS Sample Project.
Our only idea for a workaround is to force non-admin users to pass the instance's guid.
Does anybody have a clue how InstallShield can be told to search for other instances when executed by a normal user?
Thanks!
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 22, 2010
07:27 AM
Update: It was a mistake, that the /ig switch works for non admin users. In that case an error message is displayed because the instance was not found.
Any ideas anybody?
Any ideas anybody?