/build/static/layout/Breadcrumb_cap_w.png

Package only installs if the logged in user is "Administrator"

Hi, i'm trying to deploy a SW-Package via LanDesk.
The SW is an .MSI and it installs remotely only if the logged in user have admin or poweruser rights.
The launchconditions-table is empty. Requiere administrative priveligies is set to "no".
I can't find any custom action in the package that could be the issue for this problem.
I'm using AdminStudio.
Have someone any ideas??

Thank's

0 Comments   [ + ] Show comments

Answers (10)

Posted by: naveen.packager 13 years ago
Green Belt
0
Check the ALLUSERS Property. Set it to 1 for per machine installation.
Posted by: anonymous_9363 13 years ago
Red Belt
0
I'd also check in the LaunchCondition table for 'Privileged' or, more likely, 'IsAdmin' (or similar).
Posted by: kleynpackager 13 years ago
Orange Belt
0
I have already try to set the ALLUSERS Property->No success result.
The LaunchCondition table is completely empty.

Any another ideas??
Posted by: naveen.packager 13 years ago
Green Belt
0
Have you checked the log file?
Posted by: kleynpackager 13 years ago
Orange Belt
0
Yes, I've checked the log, but I didn't find anything that attempts to my problem
Posted by: pjgeutjens 13 years ago
Red Belt
0
Something is off here.. since you're pushing with LANDesk I would assume the install is actually happening under LOCALSYSTEM credentials, and the logged on user would actually have no impact at all on the installation...

I'm thinking the issue is with the landesk package, not the actual Msi.

Rgds,

PJ
Posted by: kleynpackager 13 years ago
Orange Belt
0
I think so too, bad that there is no solution for this problem.
But our another packages are working great. (since 3 years landesk).

Thanks

Goodbye
Posted by: jmaclaurin 13 years ago
Third Degree Blue Belt
0
As both a LANDesk admin and Software packager, I am going to guess that your install is attempting to access the users desktop (user interaction), likely to display a dialogue and since the localsystem account does not have one, then that is likely why its failing. Test your installation without LANDesk and ensure that all dialogues are satisfied. It may be something simple as a prerequisite is missing.
Posted by: hari4243 13 years ago
Purple Belt
0
hey...

use the wisescript "supperms.exe"

and add that in CA then you'll get that try that...it'll work surely..
Posted by: anonymous_9363 13 years ago
Red Belt
0
That's not much of a solution if the OP isn't using a Wise product, is it?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ