Mapping users to network shares without using drive letters

Our file server is Windows 2008 R2 with Windows 7 clients mainly, a handful of Windows 8.1 and a few XP clients.

I would like to stop using drive letters for mapping users to network shares and would prefer to map by any arbitrary name I choose.  We only have and need 1 file server to host all users data on a VM in the SAN so I don't see DFS as a solution since there is only 1 file server in the environment.  I know you can map by UNC name \\server\sharename but when it comes to Group Policy Preferences and AD user profiles home directory, it seems you must pick a drive letter to map to the share.

I'd like to use Group Policy Preferences to do this but want to get away from the "mapped drive letters".  

For example, if I was sharing Departments and had HR, Accounting and Sales subfolders, etc... under the root of Departments and was using Access Based Enumeration and Sally needed to get to HR and Accounting , how would I accomplish her having her view to her data in  My Computer show "Departments" (or any name of choice) instead of Z:\server\departments or \\server\departments?

Thank you
LVL 1
msandhorstAsked:
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.

Thomas GrassiSystems AdministratorCommented:
you can use the set-location

Create a powershell script

https://technet.microsoft.com/en-us/library/ee176962.aspx

HTH

Tom
David Johnson, CD, MVPOwnerCommented:
login.cmd
md c:\department
mklink /d  C:\department\ShareName \\Server\ShareName\Directory

Open in new window

logout.cmd
rd c:\department /s/q

Open in new window

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
msandhorstAuthor Commented:
Login scripts are not preferred since GPO preferences are a better way of mapping users to shares.  Is there a way to do this using GPO preferences?
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Thomas GrassiSystems AdministratorCommented:
msandhorstAuthor Commented:
Thanks for the help, it shouldn't require using powershell scripts to do something as simple as a network share.  It seems were getting off track. There must not be an easy way to get away from mapped network drives and choosing a name for the share.
David Johnson, CD, MVPOwnerCommented:
using the mklink method that I proposed works. We use this when we start running out of drive letters.
kevinhsiehCommented:
This is a small environment. No way should you run out of drive letters. That, and there isn't really a good way in the Windows UI to not use drive letters unless you want to have shortcuts to UNC paths on the desktop. Yes, the mklink method can work but is highly unusual.

I suggest that a DFS namespace is appropriate for most environments, from single server to very large organizations. DFS namespace allows you to do two things: change file servers without breaking existing drive mappings, shortcuts, or UNC references within documents, and consolidate drive mappings and shares to a single entry point. I provide a single main drive letter that can be used to access ALL of the shares on 15 servers. Organize the DFS namespace properly and users should have no problems. Obviously navigating 1000 shares through a single namespace would be a challenge for people, but a dozen or two shouldn't be a problem. Heck, you could have a single drive with 100 links in a flat namespace if you wanted.
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
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.