Do you want to deliver your projects faster and more efficiently? Then you need to read AUGI AEC Edge. It is jam packed full of industry best practices, best of class Autodesk Revit advice, and case studies and white papers from industry experts.
AUGI AEC Edge is a brand new publication dedicated to delivering mission-critical information to Architects, Engineers, Designers, and Contractors using Autodesk AEC products.
The image above is a screen capture from the AUGI AEC EDGE microsite. Check it out and download your copy today.
When a new build is available for Revit, you’ll probably want to get it installed as quick as possible, but who wants to wait for all the content to be installed? During your client deployment creation select “skip content creation” and create your deployment. Aha…that seemed easy enough but unfortunately, this may result in your new build not finding the various libraries that you intend your users to utilize.
Here is a tip for you: You can predefine all the correct file locations by editing an ini file.
Navigate to your new deployment, find the “Revit Building” folder inside the “Revit Setup” folder within the “Admin Image” folder. There you will find a file named Revit.ini. This file gets copied to your hard drive’s program folder when the deployment is run, so make your standard changes to this file prior to pushing your installs.
You can predefine the file locations by adding them to this ini file. Find the strings between [Directories] and [Design Pane] and edit them to point at your company standard folders.
Library=BIMappsDataOffice LibraryRAC 2008ContentImperial Library, Metric
Library=BIMappsDataOffice LibraryRAC 2008ContentMetric Library, Imperial
Detail Library=BimappsDataOffice LibraryRAC 2008ContentImperial
LibraryDetail Components, Metric Detail Library=BIMappsDataOffice
LibraryRAC 2008ContentMetric LibraryDetail Components, Training
Files=BimappsDataOffice LibraryRAC 2008ContentTraining, Haskell
LibraryHaskell StandardsShared ParametersIssue_Date.txt
This will keep all your users accessing a consistent set of standard files.
Note: The installer doesn’t appear to overwrite an existing Revit.ini file in that same location, so be sure to uninstall the previous build or rename this file prior to running the new deployment.
Don’t get me wrong, I’m happy that the “January incident” is fixed, but giving this latest build the identity of SP3 leaves the original SP3 build of 20071109_2345 lost to history. I celebrated that build because of the things it fixed and because it was the first time that I didn’t have to wait for the MEP release to be posted. If you saw my blog on November 19th, you’ll remember the party that was thrown!
Nevertheless, the “Failed to open document” error is no more with the latest release, so create your deployments and announce them to your users. Now get back to work!
Looks like the fix for problems associated with the Jan 2008 bug are now available. Had problems recently opening older files? Trouble editing schedules or groups?…Install the latest build 20080101_2345 to fix these problems and more! It is definitely time to upgrade and install the latest Revit Builds! Learn about and download the latest builds using the links below.
Click on the Web Update Enhancement List links below to read about the changes and fixes provided in the latest builds.
Want to download the latest English builds directly? Get it/them at Autodesk by clicking on these links:
Don’t forget to read up on the content changes. I’ll include this important reminder until the next full release.
Thank You Autodesk for understanding the need to release all the disciplines tools at the same time!…