Within the company we have too many file servers and then programs, macros, shortcuts, links and hyperlinks that point to files on these file servers. We are attempting to consolidate our storage using a central storage a SAN. In the same process remove all the servers.
In the process we want to rationalise and make file name paths more meaniingful.
So at the moment we have server named after greek gods, cartoon characters etc...
A unc path \\<servername\\share\directory....
So we get things like
Which makes learning managing and cataloguing a nightmare.
I don't want the address of a file to be related to the machine it is stored on. If it is a project file I want the address of project files on the the network to be \\Projects\My Project\ but I don't want to create a server called Projects. Otherwise we have to create multiple servers that have to administred just for the menaingful filename locations.
We work over multiple sites so we have been looking at NameSpaces through DFS
The problem is and this why I want to ask you can't create a Namespace whose UNC does not either start with the domain name of the server name. We want to replicate file across sites to reduce network traffic and have people pointing to a share \\Projects\