Now your users application has the nessesary permisions to write to its folders.īut the app may ask to write something in the systems registry.
USING NEOLOAD WITHOUT LOCAL ADMIN PRIVILEGES 2016 FULL
Press ok.Ĥ) In "Permissions for -user name-" box, mark the checkboxes to give him full control (or just "modify") rights. make a folder named "User Apps" or something like this.Ģ) Select the app folder properties (by clicking with right mouse button on it), go to "security" tab and press "edit" to change its permissions.ģ) Press "Add" and enter the name of the user you want to run the app. What application is it that won't work for you? -Noelġ) Move the Application to a folder outside "Program Files". The installer is escalated so that it can accomplish these things, then the application can run for that user and access what it needs.
Does it need to write to the registry in a protected location? Same thing as above: Set the permissions to allow the user to read/write to that/those registry location(s).įYI, installers that work successfully within the modern UAC-based security model often do exactly what I described above. Does it need to write to a location on the disk that is otherwise protected? For example, into a subfolder of C:\Program Files? If so, you can open the protections of the folder/files it needs to access so that your non-privileged users would be able to access them. What does the application need that it is not getting? Personally, I'd start with the first one above. Make the users administrators over their computers. Now, you could do one or some of the following: - Figure out just why the app is crashing and work around that. The only way to do that is to escalate, which involves the UAC prompt. To run with administrative privileges, an application (run by a non-admin user) must be escalated. The problem is that what you are proposing goes dead against the Windows 7 security model. You may well be out of luck here, unless you change the givens in this problem.
0 kommentar(er)
