Best Pratice for deploying fileshares to users
Posted on 2011-10-18
I'm in the process of trying to cleanup our existing file share system.
We currently host our shares (50+) on server 2003 and deploy shares to users using windows NT style login scripts. With each assigned to users individually in Active Directory.
AS you can imagine, this is become quite problematic as the number of fileshares keeps increasing, a number of users need access to files from different departments and drive letter mappings are overlapping frequently causing alot of unnecessary confusion for the users and making an administrative nightmare for IT.
I am also aware of a number of issues in server 2008, Vista and 7 that prevents drives mapped in this manner from displaying correctly in applications and would like to avoid hacking registry settings to make it work.
I've used some technologies like Access-based enumeration, and deploying scripts via AD before but never to this extent. I also completely new to the new options available in server 2008.
If I were willing to start fresh with how we deploy fileshares, what would be the best practice in a server 2008 domain?
What options do I have for deploying shares? what works best?
How would I setup an individual to have access to multiple departments shares simultaneously?
Is there a way to still provide specific drive letters to some users and they are quite dependent on them?