Your question, your audience. Choose who sees your identity—and your question—with question security.
Best practice for creating share drives via GPO in server 2008 R2
I want to create a few shared drives in server 2008 R2 and have them linked to GPO. I want is so that when users log in they have shared drives appear as network drives and everyone should have there own personal shared drive on the server. What would be a "best practice" configuration method. Any help or suggestions please.
Thanks
Thanks
Asked:
2 Solutions
Going off of what MidnightOne states, there is no real need to have different GPOs anymore with server 2008R2.
The current best practice is to map drives based on Group Membership. The link below shows directly how M$ recommends implementing this policy. From here you can map whatever is needed, and under the common tab, under Item-Level Targeting, you can use any sort of variable for having only specific groups of users, receive mapped drives. Regarding the scope and security filtering, depending on your AD structure, I usually have it at the top of the Domain/Forest/OU and keep the security filtering default. This is because all specific mapping is done in Item-Level targeting and therefore no need to change the scope.
http://blogs.technet.com/b/askds/archive/2009/01/07/using-group-policy-preferences-to-map-drives-based-on-group-membership.aspx
Logon scripts unless specifically needed in your environment (haven't found a reason for them yet) bog down the system and create slow logon times. Group policy is clean, easy, and efficient and is considered the current best practice.
-Jared
The current best practice is to map drives based on Group Membership. The link below shows directly how M$ recommends implementing this policy. From here you can map whatever is needed, and under the common tab, under Item-Level Targeting, you can use any sort of variable for having only specific groups of users, receive mapped drives. Regarding the scope and security filtering, depending on your AD structure, I usually have it at the top of the Domain/Forest/OU and keep the security filtering default. This is because all specific mapping is done in Item-Level targeting and therefore no need to change the scope.
http://blogs.technet.com/b/askds/archive/2009/01/07/using-group-policy-preferences-to-map-drives-based-on-group-membership.aspx
Logon scripts unless specifically needed in your environment (haven't found a reason for them yet) bog down the system and create slow logon times. Group policy is clean, easy, and efficient and is considered the current best practice.
-Jared
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.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
My method is thus:
As far as each user's personal storage, that can be done by mapping to \\SERVER\SHARE\%username% - the %username% variable fills in with the user's SAM.
If you're feeling adventurous, you can use Kixtart and scripting logic to create one logon script that parses the user's groups and assign drive mappings based on that. For large companies I've seen it used preferentially due to the enormous upkeep required for having dozens of logon scripts otherwise.