I've wanted to accomplish exactly the same thing in several organizations I've worked with, and, unfortunately, there isn't a good solution. You're left with several options, each of which isn't wholly satisfying:
- Add all users to the administrators group on every machine in your domain. This obviously raises security concerns as every user now has admin control over every computer.
- Create separate policies for each user in the organization. This is not a scalable solution!
- Use a middle-ground solution that divides computers into Active Directory Organizational Units (OUs) and assigns rights based upon OU membership. You'll still have the same security concerns as the first option, but it's a little more workable, as an individual's admin rights are limited to systems in the OU.
Let's all hope that Microsoft does something to address this in a future version of Group Policy!
For more information:
- Do the Group Policy Object and 'Password Never Expires' flag interact? Read more.
- Learn about the pros and cons of using stand-alone authentication that is not Active Directory-based.
Dig Deeper on Active Directory security
Related Q&A from Mike Chapple
Examine the important differences between stateful and stateless firewalls, and learn when each type of firewall should be used in an enterprise ... Continue Reading
Explore the differences between wired and wireless network security, and read up on best practices to ensure security with or without wires. Continue Reading
Choosing to encrypt confidential data with AES or DES encryption is an important cybersecurity matter. Learn about the important differences between ... Continue Reading