For my needs, I found my solution: 'NETDOM COMPUTERNAME' allows me to make aliases. I only need to add a DNS record, and the rest is taken care of. http://technet.microsoft.com/en-us/library/cc835082(WS.10).aspx
--Matt Ross Ephrata School District Ed Ziots <[email protected]> , 8/6/2014 4:22 AM: Maybe a dfs tree and add these servers as targets. Or migrate the shares to new servers and then add to dfs. Z On Jul 25, 2014 2:50 PM, "Matthew W. Ross" <[email protected]> wrote: Hey everyone. I have a few odd-ball servers that are all acting as file servers. I want to consolidate them to a single server, but I wouldn't mind keeping the server names the same to keep everything looking the same for the end users. My simplistic example: Server1 with 'drivers' and 'scratch' shareServer2 with 'apps' share. I want to make a single server that will respond weather you go to \\server1\drivers or \\server2\apps. There are no collisions in the share namespaces. I could make the server a single windows PC, and enter the DNS entry for both of them to point to the same system. Would that be sufficient? --Matt Ross Ephrata School District
