You are absolutely right, it's not best practice
You could use a "restricted groups" policy targeted at the computers to define the membership of the local admins group. Make sure you are able to set the policy for desktops and servers separately, don't do this at domain level, target specific OUs
Better than domain users would usually be to add a domain group called "PC Admins " or somesuch, to include your techies who need remote access to the machines (if that applies to your environment).
If you actually need regular Joe User to have admin rights because of a badly written, broken, third-rate, worthless application then I would always suggest adding the local user "interactive" rather than domain users. This means that the user logged in at the console has admin rights over their box, but not over any other on the network, specifically this means they can't go through the admin share of the CEOs PC and read all those juicy docs he keeps on his local machine or in My Documents.
When adding Interactive via a Restricted Groups policy, you need to specify this as a local group by prefixing it with the context, so:
NTAuthority\Interactive should do the trick.
Computer Configuration\Windows Settings\Security Settings\Restricted Groups
(For basics on setting up an RG policy if you can't find it, do a quick Search as it has been discussed before)


LinkBack URL
About LinkBacks
Reply With Quote