Blockchain is a technology that underpins the success of Bitcoin and other digital currencies, but it has uses far beyond finance. Learn how blockchain works and why it is proving disruptive to other areas of IT.
Solved
Best practice for creating share drives via GPO in server 2008 R2
Posted on 2012-04-07
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
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
Active 3 days ago
Window s 2008 has the basics of these already defined in the starter GPOs.
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.
My method is thus:
A GPO for common multiple drive mappings (Everyone gets S: for shared storage, P: for company policy documents, etc.)
A GPO for specific role-based drive mappings (L: for legal documentation, T: for templates, I: for IT department, etc.)
A GPO for user or one-off mappings (Oddball mapping needed for specific users)
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.
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
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
A hard and fast method for reducing Active Directory Administrators members.
Group policies can be applied selectively to specific devices with the help of groups. Utilising this, it is possible to phase-in group policies, over a period of time, by randomly adding non-members user or computers at a set interval, to a group f…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility.
Directly connect an external storage device such as a USB drive, or CD\DVD burner:
If the device is a USB drive, ensure i…
Suggested Courses
Course of the Month7 days, 10 hours left to enroll
715 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.