I guess the easy part was creating the deployment and with the help of our IT department, pushing that using GPO went on without a hitch. But, even this part took some thinking... Thoughts below.
- Create deployment - easy
- Revit.ini portion of deployment didn't work, so we had to push the .ini after the install was complete. Easy, but definitely should be working within the deployment
- Extensions - Why don't they let you install these as part of the deployment. Another thing you have to do after the fact... Thanks IT for Scripting the install of these (3) elements!
Upgrading projects not that painful other than we have our staff clean, purge, review and fix warnings, etc. prior to the upgrade. Not a bad thing to do anyways, so we do it... Then upgrade. Oh yea, we have all our consultants upgrade too. They have multiple versions anyways, so that's typically not been a problem. We all share our updated models and off we go!
Now, updating our content that are not .rfa files is another story... There are a few options for updating .rfa files. This is easy
- Old Batch upgrade tools
- File Updater Add-in
- CTC's Family Processor
We also reload all the families in any .rvt files that contain content, like Drafting Views, etc.... Why is it anyway that Revit thinks a family is "different" once it's upgraded to a new version, so if you load a drafting view for example, it adds a (1), (2), etc. after Detail Components (now named Detail Items - another big pain...!). That forces us to reload any content in those projects...
Well, that is enough food for though today...