Are users in each office trying to access and work live of central files in the other office? Have you a fast line connecting the two? You're pretty brave to be doing so if not.


As for the links dropping out :

Chances are the links aren't being made (intially) using "relative" paths - which will only look as far back as they need to (ie. ...\F\project\Model.rvt )

They've (probably) been set up to look at "absolute" paths - which will look all the way back to the file root (ie. server\F\project\Model.rvt )

Seeing as your servers will (I imagine) have different names, the "absolute" path method is going to lose the file when in the "other" office.


BUT

That still shouldn't be happening, if you are working live between offices, since Revit/your computers will still be able to "see" the other server... it should just mean slow-loads from the remote location.

we are using local copies of the project(s). Yes, re-loading can sometimes be painfully slow if the file has to go to the office 300 miles away to get information. I don't think the intent was to have the two offices working on these projects; it just turned out that way. (Vacations, deadlines, Revit-capable workers... "Hey, I know you're 300 miles away, but can you help me with the stairs on this project? We haven't done any, yet.)

We do have the paths set to "Relative."

Thanks, though! I'll be sure to remind them should it come up again.

Seeing as you're bouncing around central files from one office to another then, could you not also bundle up the relevant consultant models and send them with also?

Or better yet, have your IT setup synchronisation between your two offices?

We're in a similar situation ourselves, (almost the same distance) and have recently had great (test) results using DFSR to keep our two sites' project folders identical... yes, it doesn't play nicely with Revit central models (which we should soon get around with a move to Revit Server in 2012) - but for "static" received files, it could prove handy.

oops... maybe I misled you. We have only one Central file. Depending on the project, it's either in the C or R office. But we may need help from workers in the opposite office to jump in and work on the project. So, they're using a local copy of the file (as in a workshared local copy.) We're not shipping the central file back and forth.

So, you're thinking Revit Server is going to work in these type situations? I understand the concept of Revit Server, but we have others in our C office that are balking. If Revit Server is going to ease out the kinks, maybe I should sell it harder. (Those in the R office are less experienced with Revit and most have probably never even heard of it.)