We just migrated one our main file server with our Revit projects over to a new server. The new server took a new name. The old one was left in place with different duties. This all went fine until we started to open up our local/central files. The central file is now considered a local file to the file on the old server. Since we renamed the folder structure on the old server, its path could not be found. This is what raised the red flag. These files are using the full UNC path. All this is something that we never really thought of and do not know if there is a set way to do this for future migrations. (understanding that this is not something you do often, but eventually may be done) Has anyone come across this? Is it dealt with in anyway.
I am told that our IT staff used XCOPY to get the files over onto the new server. Our current solution was to open up the Central file (now a local copy) and resave it as a new central file then recreate new local copies from this. I would rename both old local and old central file/backupfolder in lieu of overwriting the files so the backup folders/contents are forced to recreated themselves.
I have found some threads regarding this issue but non of them really give the answer I was looking for. Renaming the new sever the same as old server was not an option and even though we are using mapped drives, Revit appears to be using the UNC path instead, unless we are missing something.
If anything this is a big heads up to have all your ducks in a row (local files saved to central) prior to migrating your data severs.
Any comments/thoughts would be great.
jamie