InterviewSolution
Saved Bookmarks
InterviewSolution
| 1. |
Solve : Adding Network Configuration Operators through Active Directory??? |
| Answer» <html><body><p>I feel retarded for askin but I'm stumped...<br/><br/>I have certain users that are apart of the <strong>NETWORK CONFIGURATION OPERATORS</strong> and <strong>REMOTE DESKTOP USERS</strong> built-in Windows 2003 <a href="https://interviewquestions.tuteehub.com/tag/active-367234" style="font-weight:bold;" target="_blank" title="Click to know more about ACTIVE">ACTIVE</a> Directory Groups.<br/><br/>By adding the Users to these Groups this has no effect. So what do I have to do within a GPO to apply these settings across a domain. I know I can locally do this to each computer but I <a href="https://interviewquestions.tuteehub.com/tag/need-25476" style="font-weight:bold;" target="_blank" title="Click to know more about NEED">NEED</a> these Users to modify TCP/IP and Remote Desktop into <a href="https://interviewquestions.tuteehub.com/tag/every-243531" style="font-weight:bold;" target="_blank" title="Click to know more about EVERY">EVERY</a> computer in the domain - so adding it locally is to much admin overhead.<br/><br/>XP workstations...2003 serversI don't have my vm setup to AD right now to test this out but here are two ways of doing what you're trying.<br/><br/>First I don't think by adding your users to the mentioned groups in AD automatically adds them to those groups in the local pcs. So if you want to add your users to those groups via policy then the one you are looking for is called Restricted Groups. This will make sure they are put in the groups in the local pcs. It's under computer <a href="https://interviewquestions.tuteehub.com/tag/config-929024" style="font-weight:bold;" target="_blank" title="Click to know more about CONFIG">CONFIG</a>/windows sets/security sets/.<br/><br/>The other way is to create a domain group and then using the delegation wizard to give it the rights you want them to have. Whether or not these rights exist you'll have to find out when you use the wizard. <br/><br/>Last but not least, no one knows the answer to everything so you shouldn't feel retarded for asking this. Asking questions, practicing and reading as much as material as you can is how you learn your craft. Bye.Yea I already tried messing with the Restricted Groups in AD but no go...I'll try again today and reply back a little later. Thanks...Delegation wizard doesn't offer what I need. That seems to only be for AD controls, such as creating/deleting GPO's, etc.<br/><br/>As for Restricted Groups...<br/> - Created a new GPO "TESTGPO" (Enforced it in the correct OU with the users/computers)<br/> - Withing "TESTGPO" I added the restricted group "Group1"<br/> - In the "Members of this Group" section I added "User1"<br/><strong> - In the "This Group is a Member of" section there is no possible way to add AD Built-in groups<br/>With that being said...How do I give "User1" the right to only modify TCP\IP on every computer in the domain?</strong><br/><br/>Again, "Group1" is a member of the AD Built-in group "Network Configuration Operators" and "User1" is a member of "Group1". I've never had to mess with the security of a group but I added Authenticated Users with Full Control, nothing.I think you're supposed to used Remote & Network groups in the GPO that you want restricted. Then you add members such as GROUP1 or USER1 into it. In this situation you don't have to worry about THIS GROUP IS A MEMBER OF. That is just for more granular control of what group it should or shouldn't belong to. We don't really need this because we already are specifying the Network Config group and its members in the first tab. Not sure if I made sense or not. But here's a quick summary:<br/><br/>You had restricted group being group1 > members user1 ><br/><br/>group is a member of > network config (which you found out can't be done)<br/><br/>So ...<br/><br/>Restricted group should be Network Config > members should be group1 or user1<br/><br/>no need for GROUP IS A MEMBER OF <br/><br/>Here is a link to a good article on restricted groups:<br/><br/><a href="http://www.windowsecurity.com/articles/Using-Restricted-Groups.html">http://www.windowsecurity.com/articles/Using-Restricted-Groups.html</a><br/>DRIVENBYWHAT I LOVE YOU<br/><br/>I knew it would be something simple I didn't try. Never <a href="https://interviewquestions.tuteehub.com/tag/even-976335" style="font-weight:bold;" target="_blank" title="Click to know more about EVEN">EVEN</a> thought to add the Built-in groups to the Restricted Group GPO setting...don't ask me why. Probably would of never figured it out, considering I already had it in my head Built-in Groups couldn't be added there.<br/>Thanks again...err I wish I had that intuition to just sit and figure these types of problems out. Overlooking something this simple is really frustrating. Not to mention, this is a setting that almost every Domain Admin should know and need.<br/><br/>SOLVED!<br/>Glad I was able to help you out. Happy administrating.</p></body></html> | |