0
I am looking to review user account permissions across a Windows Domain Network. I want to get rid of computer accounts with local admin rights and replace them with regular user accounts. This is all OK but the issue lies in the few applications that require UAC prompts to open.
This question has been asked before across many sites (and may be outdated now) but the fixes pointed to hacks including Windows Task Scheduler, Compatibility Toolkits and 3rd party applications. This is not really feasible with hundreds of users, and a large percentage of the users using a (trusted) UAC prompted application. Do I really have to give local elevated rights to many of the users? The high majority of users are using Windows 7 Pro.
My question is:
How do you allow regular user accounts access to UAC prompted applications without giving them access to an admin password, elevating their local account, IT populating the prompt, turning off UAC or using 3rd party applications to circumvent UAC.
James
Posted 2015-03-02T13:27:29.620
Reputation: 11
Those other articles/workarounds you've found are still accurate. – Ƭᴇcʜιᴇ007 – 2015-03-02T13:34:37.750
Thanks Techie007 - They are still accurate but not feasible. Adding an application and then configuring it separately for each user (hundreds) is not a reasonable solution. In one instance of the workaround being needed, then yes but not when there are many users.
I just don't want to go down the route of local admins (security issues), workarounds (deployment would be costly in hours) or disabling UAC (security issues).
There must be a solution (not in the duplicate link) that IT Departments with large user bases use?
Can this be removed as a duplicate question? Thanks. – James – 2015-03-02T14:07:43.650
You've seen the solutions. The real solution is to force your vendor to produce a version that's programmed properly. One thing to consider is why it's throwing the UAC prompt. Figure out what resources its trying access that needs elevated permissions, and modify the permissions on that resource. That may be enough to get the prompt to stop (again, this highly depends on why the UAC prompt is being thrown specifically by your program). – Ƭᴇcʜιᴇ007 – 2015-03-02T14:16:44.537
They were solutions for single-user problems - not replicable across a large user base. The real solution that was suggested is again not really feasible as I cannot force the vendors to do anything. – James – 2015-03-02T15:58:05.287