Running MSI without Admin Privileges on Win7
Hello,
I am working in a Windows 7 Environment with SCCM 2012 deployment. But for some packages, client wants to deploy them using their internal deployment tool called OnDemand. Client running this tool without admin Privileges, so the installation failing with the message "1925. You do not have sufficient Privileges to complete the installation for all users of the machine. Log on as an administrator and then retry this installation. Client do not want to run the tool with admin privileges for specific reason and want to update the packages so they run without admin privileges. Does anyone have idea how to achieve this.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
jagadeish
10 years ago
Tell your client to not to use their own internal tool for making the application on demand.. SCCM 2012 provides more control to the administrators during application deployment by defining if the application is optional or required. Deploy such application in optional mode.
Posted by:
anonymous_9363
10 years ago
>Client do not want to run the tool with admin privileges
They won't have a choice if the installation package writes to any system resources, e.g. HKLM, %ProgramFiles%, etc., etc.
You *may* find that if the package is an MSI, it has a LaunchCondition which checks for admin privileges. This can be bypassed by adding an impossible-to-meet condition to that. Of course, that may still not prevent a successful installation, given the above.
It's part of your job as the packager to advise clients on this type of situation. Having said that, when faced with particularly stubborn clients, I have resorted to totally re-working the installation but, again, the client needs to be told that there will be a time-hit involved in that.
They won't have a choice if the installation package writes to any system resources, e.g. HKLM, %ProgramFiles%, etc., etc.
You *may* find that if the package is an MSI, it has a LaunchCondition which checks for admin privileges. This can be bypassed by adding an impossible-to-meet condition to that. Of course, that may still not prevent a successful installation, given the above.
It's part of your job as the packager to advise clients on this type of situation. Having said that, when faced with particularly stubborn clients, I have resorted to totally re-working the installation but, again, the client needs to be told that there will be a time-hit involved in that.
Comments:
-
Thank You VBScab for the reply. The package installing files to C:\windows, so it definitely need admin rights. Client guy is a developer with some packaging knowledge. He want to move the files to appplication directory under program files and create a manifest/private assembly. - kewl.ravs 10 years ago
-
Same issues apply, as the program files folder tree is read only for non admin users. If you move the files to ProgramData then you might have a chance but you are heading for a world of pain. In order to avoid needing admin rights your install must be entirely within the user context, which precludes installation by any process that uses a local system account, as this does not have access to any user profiles.
Tell your client that he is a dick and needs to understand the cost and security risks of his anal position on this whole matter. - EdT 10 years ago
Posted by:
vjaneczko
10 years ago
I run into far too many clients that have rules & guidelines but don't know why they exist ("We've always done it that way.") so I usually don't attempt to conform to their existing process; I tell them the recommended way to get the app installed and help them rewrite the process. If I hear "it's what I want", I usually dig in a bit and make a stink until I'm done explaining with logic & reason the challenges or issues with their complex, unnecessary (dare I say Stupid?!) desires. If they still insist, then it is what it is but it's not good nor will it every be.
