Avoiding Local Admin Account Usage

Posted by Dry_Condition_231@reddit | sysadmin | View on Reddit | 29 comments

Hello all, hopefully this is an appropriate sub for this kind of question. A piece of lockdown browser software for test proctoring has run perfectly as a standard user when run as admin. Trusted user enters admin credentials, and away the software goes while untrusted user can continue with standard user account. However, a recent update seems to now require an admin account to be signed in to launch at all. When run as admin from a non-admin domain account, the software starts, does some of the lockdown stuff, and never shows the window, essentially locking the computer. How would you approach this situation? I could create a domain account that is added to the local admin group of this set of computers and share that credential. This group of trusted users does a fine job of password security for their individual user accounts but I know the second a shared credential is made, it's written down, printed, and posted within 5 feet of every place it can be entered with this group. I know some places use software to shift around the context certain programs are run in without having to enter admin credentials. I don't think that will work here because the software doesn't run as a standard user at all, run as admin or not. I wish I could just disallow the software; It will fall of deaf, luddite ears within my organization and I'll just gain reputation as the no-help, paranoid IT guy. It's another school we're doing proctoring for and we're obviously not included in their decision-making but I'm probably going to make a case to their IT anyways. I have a ticket open with the software developer. As the ticket works out and their suggestion is "use an admin account," I'll obviously harp on their poor practices as developers as well. Maybe it will actually lead to an improvement in their software (lol). Anyways, any other ideas or suggestions? TIA