I created a msi package which will copy files and folder from production location to users machine and registers the required dll in local users machine.
Local users don't have admin rights on any machine now. but installer which i created registers some dll, here is the problem. Registeration logic fails when non admin users tries to run the installer. I got some feed back from my system admin to "We need to change the Installsheild permissions from executing as the 'interactive user' to executing as the 'Launching User'. this way when he MSI executes and calls the installscript service to start it will start up as the user who kicked off the installer, not as the logged on user (standard user) who doesn't have rights to install software. "
I dint really not able to proceed with this suggestion. Can some one help me .
Thanks, Sach
If I understand what you're asking, InstallShield 12 changed the InstallScript MSI architecture to avoid this problem; if you can upgrade and rebuild, this problem should just disappear.
If you cannot upgrade, you can search the Internet for terms like isscript.msi launching user to find suggestions on how to modify the DCOM service to run as the launching user. Removing the "Interactive User" value from the relevant AppId registry key isn't exactly supported, but lots of people have had success with it.
If these are third party installations over which you don't have control, Stack Overflow isn't the correct forum.