We are working on migrating from Novell to Active Directory. During the transition, We are going to evaluate our drive mappings in light of current standards to see if what we have been doing still fits, is in alignment with best practices, simplify administration of the resources, etc. At present, we have 11 different drive mappings that are mapped. This seems, to me, to be a few too many and rather confusing for end users. These drive mappings also appear to relate to some older convention that existed in the organization that ended being something like the following:
- K:\ - Mapping of physical CD-ROM drive of Novell server
- N:\ - IT administrative scripts and utilities
- S:\ - Another user's home folder, if needed
- T:\ - dBase III mapping (this should hopefully disappear after the migration)
- U:\ - Project or other group shares
- V:\ - Project or other group shares
- W:\ - Work (departmental or unit work share)
- X:\ - Applications share
- Y:\ - Home folder
- Z:\ - System volume
This is a very confusing structure for users, both end users and IT, within our organization. I would like to ask for industry best practices and how others design their drive mappings. What are some things that one should be aware of and how do you compensate or control those items? What are things that should be considered from a management and maintenance perspective?
Our clients are going to be Windows XP, Windows Server 2003, Windows 7 Pro, and Windows Server 2008. Later on we would like to incorporate Linux and Macintosh OS X (10.6 or newer) clients into our drive mappings as well.
Any help, ideas, resources, or links that you can provide would be greatly appreciated.