App not installing for all users
I am trying to publish Scansoft PDF professional via GP. It is an installshiled packaged app. Has exe, isscript and msi in the folder. I pre-instaled the isscript and published the msi and transform to the end user via GP. I created a transform using installshield tuner to supply all answers/serail number etc. It will install without if it is run from an admin account, but not to all users. if average joe installs it, it gives an eror about ereg, but eventually finishes and work, but again not to all users. If I browse to the directory the app is installed in and try running it I get a runtime error. The ALLUSERS property is set to 1 and ApplicationUsers property is AllUsers. If I run the setup.exe that came with the package manually as admin, it install to all users fine. Anybody have any tips? if I cant get per machine using joes access, thats no big deal, as long as with the admin account it will deploy for all users.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
AngelD
18 years ago
There may be some customactions running in "Execute Immediate" which may be run with administrative rights. If so try change the sequence so they are executed in Deferred instead.
Posted by:
aa006
18 years ago
Not sure you did this or not... using wise Under Administrator Options..install for Profile : Change it to Per-machine installation.. try this .. good luck
Posted by:
mls15000
18 years ago
I dont have wise to try that method. I just did the ultimate no no and repackaged it for now. Once I am done getting all these apps repackaged and finish our XP deployment, we will start developing our sms enviroment and i can go back and change it.
Posted by:
mls15000
18 years ago
I had ALLUSERS=1 already, it didn't work. Not worried about it now. Going to repackage it once our sms enviroment is in place.
Posted by:
bheers
18 years ago
ereg is the custom action for electronic registration,
Run the Msi in an non admin account with a log file, and when it fails, do not click finish / close, open the log file and see at what point the install is stopping, if it is a custom action, comment the custom action in the transform and try again.
Hope this helps
Run the Msi in an non admin account with a log file, and when it fails, do not click finish / close, open the log file and see at what point the install is stopping, if it is a custom action, comment the custom action in the transform and try again.
Hope this helps
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.