Quick Links - Also see the menu above and more choices on the right side of the blog (too much, but all good stuff)

\/ ...and now BIMbuilder.com Blog Posts... \/

Wednesday, August 17, 2011

And the Revit.ini file strikes again... RT @RevitClinic #Revit


Source: http://revitclinic.typepad.com/my_weblog/2011/08/and-the-revitini-file-strikes-again.html

And the Revit.ini file strikes again...
BIM -The Revit Clinic
You may remember a few posts about the Revit.ini file and Revit 2012:
Before diving into this post, I recommend you check out the above posts if you haven't already.
With UR1 for Revit 2012 products, the way the UserDataCache Ini file (C:\Program Files\Autodesk\Revit Architecture 2012\Program\UserDataCache\Revit.ini) propagates to the users directory (%USERPROFILE%\AppData\Roaming\Autodesk\Revit\Autodesk Revit Architecture 2012\Revit.ini) have changed with the addition of a new Update tag.
There are also some important details to understand about the hostname field that will impact your ability to roll out company wide changes to your users Revit.ini files.
First, here are the details about how these fields work in the ini to propagate changes:
2012 behavior for RAC, RME or RST at startup as product is initializing:
Note: all keys are read from the [Install]  section of Revit.ini for either the user's file or UserDataCache (UDC) file.
If Hostname key in user's file does not match UDC Hostname key:
no further processing, InstallGUID and ReinstallGUID are skipped
If InstallGUID key exists in UDC and value does not match InstallGUID key in user's file
  • delete all files in user's roaming profile folder (top level files only, no subfolders processed)
    • %USERPROFILE%\AppData\Roaming\Autodesk\Revit\ e.g.   C:\Users\\AppData\Roaming\Autodesk\Revit\Autodesk Revit Architecture 2012
  • re-copy all files from UDC into user's roaming profile folder
else if Update key exists in UDC and value does not match Update key in users' file  (new for UR1)
  • parse list of Section/Key pairs and overwrite user's values for any non-null values in UDC Update key
    • i.e.  for each UDC Section/Key read the value, and overwrite the user's Section/Key value
      • e.g.  Update=Documentation|OnlineHelpServer
      • format:  Update=Section|Key;Section|Key;Section|Key
  • write UDC Update value into user's file
else If ReinstallGUID key exists in UDC and value does not match ReinstallGUID key in user's file
  • overwrite user's values for these keys for any non-null values in UDC file (hard-coded list only)
    • FamilyTemplatePath
    • DataLibraryLocations
    • DefaultTemplate
  • write UDC ReinstallGUID value into user's file
The first item is probably the most important one for you if you want to roll out changes to a lot of users at once (after you have already installed).  It turns out that the hostname field is the first check Revit makes when comparing the UserDataCache ini with the ini in the users directory.
If the names don't match, then nothing else parsed through in the ini file.  The Hostname check was added because of roaming profiles so as a user logged into different machines their Revit.ini wouldn't get overwritten due to different InstallGUIDs per install.
In case you need to roll out changes to your user ini files from one source there are two options you can look at:
  1. If you remove the Hostname entry from *all* user's Revit.ini files and from the UDC Revit.ini, then you can more easily propagate changes and/or overwrite entire Revit.ini files.  
  2. If you delete all user's Revit.ini files on all machines, and update all UDC Revit.ini with the new settings and remove the Hostname entry, then a new Revit.ini file would be copied from the UDC the next time the user runs Revit.
Both of these options should have the desired affects and allow you to roll out changes to other users. Happy INI ing...

0 comments:

  © Blogger template ProBlogger Template by Ourblogtemplates.com 2008

Back to TOP  

[Valid Atom 1.0]