One of the most common and frustrating issues our support team deals with is trying to get everyone in an organization on the same level "Revit" playing field. If you utilize the worksharing features of Revit, Revit Architecture, or Revit MEP, then you're probably familiar with this issue.
Everyone in the worksharing group has to use the same version or build number of Revit, or face the consequences of data corruption and design errors. One of the most common support inquiries we get for Revit is, “My update won’t apply because of the following error message...”
As complicated as many have made it, I’m going to simplify the process for you...
What should you know?
Each software update contains a "Readme" file, which provides you with the build number for the update version you have received. Revit 2015 has a variety of updates for basic users, but subscription customers will receive even more updates. Some updates will apply directly to the previous build, while others will apply to, what I call, a “shortcut path.” You can try hunting down the applicable builds from each individual "Readme," but I caution you... You'll probably not be able to bill for this lost time.The simplest and sure fire method, to maintain the correct Revit build number, is to install ALL incremental updates in the correct order, like this:
Install OEM Build (First customer Ship)
Next, Install Update Releases 1, 2, 3, 4, 5, 6, 7, 8, 9, and finally 10
I know... You're saying to yourself, "That's a lot of updates!" It's true, this method can take a good amount of time to complete all the updates. The good news is, there are shortcuts available for those willing to go the extra mile and do some initial planning.
Looking for more information about Revit Build Numbers?
Click on Revit Build Numbers to find more information on what each build number actually means.
You can also locate your build number and update version in the "Help/About Revit" menu, as shown in the image below.
Now for some shortcuts!
If you' ve decided you want to get everyone on the latest build (currently Update Release 10 for 2015), then you'll need to see what versions everyone is currently using . You can't simply upgrade from a random build number to the latest; that would be too easy and make too much sense. This is where the aforementioned planning comes into play. There's a pretty good chance you'll have to select your path, uninstall Revit completely, and then re-install Revit and corresponding updates in order. Here's a shortcut:
Install OEM First Customer Ship
Install Update Release 3
Install Update Release 7
Then, Install Update Release 10
Other routes are available and described in more detail in the article, Revit and Revit R2 Service Pack Update Path.
So for Revit R2 users, you can either jump right into R2 from the OEM First Customer Ship or you can apply it to the UR3. Once R2 is installed, you have to install the R2 Update Releases, which are separate and distinct to the non-R2 Update Releases. These can be found in the "Application Manager," once R2 is installed or downloaded manually from the accounts website. The article mentioned above also describes theses paths.
For CAD Managers applying these updates via software distribution, deployment installations, or group policy, I highly advise the shortcut method. This will save time, bandwidth, and help ensure uptime in the event of a rebuild.
What more should you know?
On a final note, Revit Architecture, Revit MEP, and Revit are all separate products. They will have their own separate updates. The same information above applies to each product. The 2016 versions are the most recent and are still releasing updates, as they come out. Please note, the same update rules apply there, as well. I recommend using the latest build for all users, selecting an upgrade path to use for all, and notating it somewhere, so you can be consistent across the board. Planning and documenting this process will simplify it for future reference.
Advanced Solutions is always interested in what our customers are up to with their design data and software implementations. Don't hesitate to share any cool models with us by emailing an A360 link to firstname.lastname@example.org. This will help our support team learn about the many intricate phases of modeling, as well as give us more customer based insight regarding usage, features, and troubleshooting. And, who knows, you may find your model in a future customer showcase on our blog.
If you are having technical issues with your Autodesk software, you can contact Justin and the technical support team by clicking this link...