Solved! Go to Solution.
There are different ways of doing this for different version of revit:
Refer to these blog for further details:
another blog that is helpful :
Hope this helps
Its not a hard as it looks.
From Rod Howart's blog, revit-api-running-your-add-ins-from-network,
(C:\Program Files\Autodesk\Revit Structure 2012\Program) and make the following change: look for the <runtime> tag, and just after it’s opening, put: <loadFromRemoteSources enabled="true" /> making it: <runtime> <loadFromRemoteSources enabled="true" /> <generatePublisherEvidence enabled="false"/></runtime>
This is what you will need to change in Revit.exe.config
This file can be found in your deployment at:
(I'm using Revit Architecture - this might be different for other flavours)
I hand edited the Revt.exe.config file after creating the deployment.
You also need to change your .addin files to point to the network path, then add those files to your deployment. The path in my deployment I added was:
Again I hand edited the .addin files to point to the correct UNC pathname for the addin, then I used the 'Additional Files' panel of the Modify Deployment Wizard.
I also did some hand-editing of a few other files to customise our deployment -
\AdminImage\x64\RAC2013\Program Files\Autodesk\Root\Program\Autodesk\RAC 2013\UserDataCache
was edited to load default company material libraries for each user.
was edited to provide default custom colours, default paths, default setups copied from a clean install. I let the deployment create this file initially from a master revit.ini file, then added changes by had as required.
I found it very useful to keep a log of everything I did, and I created a seperate folder that contained masters of all my edited files in a folder structure that matches the deployment - I can just drag-and drop the entire folder tree to instantly customise a deployment.
This deployment succesfully worked on 35 machines - it was my first time using the deployment tool!