Broken share paths with file server rename?
Posted on 2006-11-08
I am going to be re-building the office file server and in the process, rename it to conform to our new naming convention.
A rename of this file server will likely create numerous ‘broken-links’ for users who have 'hard-coded' mappings in file paths that reference the OLD server name.
Will a CNAME in DNS, such as 'OLDSERVERNAME’ pointing to the correct IP of 'NEWSERVERNAME', fix this type of issue?
Also, looking for ANY potential exceptions, caveats, etc… (applications, static mappings, ..)
Thanks for your insight!