Windows 2012 R2 -- "SYSVOL" everyone read access ?

I setup a new server in my
domain and the below defaulted
read-access for EVERYONE, therefore
anyone can read these files by going
to \\ServerName and clicking on the
"SYSVOL" or "NETLOGON" shares.
  ** C:\Windows\SYSVOL\sysvol
  ** C:\Windows\SYSVOL\sysvol\DomainName.ROOT.TLD\scripts

1. Can I remove the read-access for EVERYONE ?
2. Why does it default to this ?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I'm pretty sure that the default permissions and it's supposed to be that way for proper usage. You could experiment with adding in authenticated users, but you potentially could be cousin issues by doing that.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Will SzymkowskiSenior Solution ArchitectCommented:
This is by default. Do not remove read access for all users. This is required so that users can read the files to get the proper group policies and logon scripts etc.

This is by design.


Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Is this new server already a DC? If not, after becoming one, I believe it will replicate the permissions with the current DC.
Will SzymkowskiSenior Solution ArchitectCommented:
New DC or not, Sysvol needs to be shared and have everyone read access to the share. This is where all of the Group Policies reside along with the logon scripts. If you mess with these permissions group policy will stop working and AD will not work properly.

For a deeper understanding: what people fear, is to disclose Information like Passwords or license keys that might be embedded in scripts.
Please think  about this: when we do Things with Passwords or license keys, do those scripts Need to be readable by user accounts? No. They would normally be processed in Computer policies, not user policies. So you might want to do adjustments IF you indeed fear to disclose such info.

What you could do, is look at the policies affected. Make sure, those are Computer policies and then you can adjust their ACLs in the Group policy Management console (for example, in Addition to admins, let only the Group Domain Computers read and apply those policies and not "authenticated users".
This change will do no harm.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.