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
LVL 6
vmaganAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

MidnightOneCommented:
Window s 2008 has the basics of these already defined in the starter GPOs.

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.

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
jaredr80Commented:
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
vmaganAuthor Commented:
Thank you guys for the great advice. I have more than enough info now.
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 2008

From novice to tech pro — start learning today.