Solved

Restrict Clients from viewing Domain Structue/OUs using GPMC

Posted on 2007-04-05
11
678 Views
Last Modified: 2012-05-05
Server 2003 SP1 and AD 2003
Clients (workstations) - XP PRO.  Domain users are local administrators on the client machine.

GPMC can be used on any client to view policies that apply to each OU.  I want to restrict it such that no client machine can view GP policies per OU.  For example, I have an OU for Sales.  I don't want a user in the Finance department to be able to run GPMC on their machine and be able to browse the OUs in the domain and see what login scripts, policies, etc they are using.  

For that matter, I don't want any client able to view the Domain/OU structure!

Thanks,

0
Comment
Question by:top_rung
  • 6
  • 5
11 Comments
 
LVL 26

Expert Comment

by:MidnightOne
Comment Utility
Unless they have domain admin rights on the domain, they shouldn't have the access rights to use the GPMC or ADUC tools against a domain controller.
0
 
LVL 14

Author Comment

by:top_rung
Comment Utility
yeah, that is what i expected, but they can use the GPMC.  The users are only Authenticated Domains users.  No administrative rights whatsoever except on their local machines.    

They can not make any changes, but they can view the structure and such.  :-\
0
 
LVL 26

Expert Comment

by:MidnightOne
Comment Utility
Do the clients -require- admin access on t he local machines? Although that's a separate problem, it will keep them from installing the admin tools and other idiocy.
0
 
LVL 14

Author Comment

by:top_rung
Comment Utility
Yes they require it - being developers and such.  That company policy won't change unfortunately.

I just can't believe that it is that simple to browse the hierarchy on the domain controller.  This is a problem because employees using the tool are seeing the tiers of management and the varying share rights based on OU names and script names.  

I need to restrict it if at all possible.

0
 
LVL 14

Author Comment

by:top_rung
Comment Utility
up'd points
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 
LVL 26

Expert Comment

by:MidnightOne
Comment Utility
Unfortunately, you won't ben able to stop them from getting at the logon scripts at all; these are housed at %logonserver%\netlogon and all users have RX privileges to that share and files.

It's possible to use GPO software installation to remove the admin tools from the user's workstations, but given the myriad versions this may be cumbersome at best.

Do the users have the tools installed locally?
0
 
LVL 14

Author Comment

by:top_rung
Comment Utility
Yes, the users have the tools installed locally.

Again, it isn't simply the viewing of the scripts, but more so the AD structure.

So you think the only solution is to remove the tools and either restrict install or live with it?


0
 
LVL 26

Expert Comment

by:MidnightOne
Comment Utility
Here's a possibility to add to the logon script, presuming you can put the admin tools installer in the netlogon foloder

msiexec /x %logonserver%\netlogon\adminpak.msi /qn /quiet

This performs an immediate stealth uninstall of the admin tools.

HAND

MidnightOne
0
 
LVL 14

Author Comment

by:top_rung
Comment Utility
haha, that's cool and funny.  They will install it repeatedly and it will be removed everytime they log on.  The only problem with that is they will install it after they are logged on and use it during that session :-\

I am going to try that (at the least) to see how annoyed they get with it.  
0
 
LVL 26

Accepted Solution

by:
MidnightOne earned 500 total points
Comment Utility
Unless you have either the political backing to cause the developers great pain if they persist or the go-ahead to remove them from the local administrator's group of their systems, you're pretty much out of luck.

MidnightOne
0
 
LVL 14

Author Comment

by:top_rung
Comment Utility
That is the answer I needed.  Pretty crummy that is works that way.  

Thanks for you suggestions!

0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now