Unlike it’s predecessor AutoCAD, attempting to use Revit remotely is strongly discouraged. This is for many reasons among those being much larger files sizes, unknown network availability and currently, Revit just does not lend itself to a remote environment. While it may seem to impress the client that you can make changes as they describe them, it is not worth the potential embarrassment caused possibly even by factors not in your control. 


Even if the environment variables on the workstation are correct and even if there is a strong data circuit available (> 100 mbs) if you attempt to reach a file located on Revit Server, you still do not have the benefit of the local accelerator that is located in LAD/LAN office. Revit Server models are not that same as local Revit models by their nature. This lack of availability to a local Accelerator is what causes Revit to appear to “freeze”. It is not frozen but is simply trying to do what it was instructed to do…open a file on the Revit Server…except without the benefit of the local Accelerator. It is still trying to use the Accelerator but because it is no longer local, it has the same effect as if the Accelerator Given enough time (this could be hours depending on the model size).


There are two recommended methods for working remotely with Revit. These would be remoting into an internal system or working on copies of the models you need.


Remoting into an internal system

This would be the preferred method. It simulates the same performance we see in the office. Steps to follow would be…

  • Preplan which system will be remoting into and ensure Revit is working correctly and that the presenter has logged into it while in the office to prevent a long login time (if an unused system, they could just leave it logged in and have Revit open
  • Confirm they can remote in to the internal system using VPN from the system that will be on site using our guest wifi connection with hardwire disconnected
  • Once confirmed, this should work the same on the client site provided they have a good data access (>25mbs)


Using local files

While there should be no performance issues when working on local files, they would no longer be linked and would just serve as a reference for changes that would be replicated on the live model when you return to the office which may be beneficial as sometimes you may not take the normal process to simply create a displayable change for the client. Steps to follow would be…

  • Open and create detached local files for those models needed
  • Relink locally as needed
  • Test and confirm correct model functionality
  • Check out a license for Revit on the system you will be taking and test all for correct operation while not connected to the any network or wifi connection