2017 Deployment doesn't honor custom Revit.ini

[chicks007]

I have created a deployment for 2017 software, including Revit and wanted to set custom template locations, etc. My issue is that the custom revit.ini file defined in the deployment is not honored/read. I have tried unsuccessfully both browsing to the revit.ini file (same location as image) and typing in a UNC path to the file, then selecting import in the deployment. After an install, when Revit launches it reports missing template location with no custom revit.ini settings honored. If I take the custom revit.ini file and manually copy it to the "usercache" folder and then launch Revit all the custom settings are there, no errors reported. Why won't the deployment read/honor the custom settings in revit.ini? All of our PCs use the same drive letter mapping(s) and even using UNC path to the ini file fails. In the same deployment a UNC path is used for locating a log file that works. The same deployment sets custom mapped drive locations for AutoCAD content that work fine. Any ideas, thanks, Carl

[JeffDaughton7498]

Has anyone found a solid solution to this issue?  We are experiencing the same issue and the work-around proposed above by copying the revit.ini file from the user appdata folder to the programdata folder does appear to work.  In fact, I customized that ini file in the user appdata folder before copying it to the progromdata folder and those were immediately recognized in Revit 2017 when I launched it.

For reference, here are the ini file locations.

C:\Users\MY USERNAME\AppData\Roaming\Autodesk\Revit\Autodesk Revit 2017\Revit.ini  (I customized this and then copied to location below)

C:\ProgramData\Autodesk\RVT 2017\UserDataCache\Revit.ini   (This file is not there after the initial install)

It seems rediculous to me that a solution has not been proposed by Autodesk for this.  Or at least I haven't found one yet if it does exist.

-Jeff

[jhe_arteliaDK]

Same problem here. A speedy solution would be appreciated.

I would hate to have to batch copy the Revit.ini file to 100+ each machine when installing. Especially since it has been working flawless in previous versions of BDSP.

[jhe_arteliaDK]

I didn't see Tony's proposed solution when I wrote my first post 🙂

I have now tried adding the 4 lines and it works fine when creating new Deployments.

Anyway......it's simply not good enough, Autodesk! If you know the solution, which is quite simple. It can't be that big a problem to fix the Suites we all download from the Accounts portal and put them out there.

It would be common courtesy to us, your customers, who pay quite a lot of money for your software.

-Jesper

[dtiemeyer]

I can confirm that I was experiencing this issue with BDSP2017 and the following steps fixed it:

1) deleted my previous deployment image
2) altered the Setup.ini file used to create deployment images (as outlined by Tony's post on Page 2 of this thread)
3) Created a new deployment using the edited settings but selecting the generic Revit.ini option
4) Deployed to a test machine, verified error-free, harvested the Revit.ini file
5) Created a company-specific Revit.ini from the generic one on the test computer (verified every single path, including the removal of one trailing backslash "\" that was dis-similar to the others)
6) Used the .\Tools\Create & Modify a deployment  tool to start with the 'generic' deployment as a template then created a customized deployment with my customized Revit.ini
7) Deployed the customized version and it worked fine, including my customized Revit.ini settings.

[BIMologist_ · Accepted solution]

To confirm that Tony's solution WORKS. If you are Creating the deployment for the first time Modify the SETUP.ini in the Installer folder based on Tony's instructions or below. If you already have created a deployment then follow instructions to fix it.

Here are my findings as I was only running into this with the Suite based Deployments not raw REVIT deployment created using Revit installer

1. No need to RECREATE The deployment
2. Use Notepad to Edit ini Files Imgx64.ini AND any existing named ini files that are deploying Revit in them. e.g. GBBN_Revit_AutoCAD_2017.ini
3. In both files change the [ProductSelectionDlg2] section (I have the cut paste at the end of the post)
4. Modify your EXISTING deployment(s) with Revit in it. You will have to do it in each named deployment
5. Click the Generic ini, collapse the Revit section, Expand again and switch to custom ini / browse and import (may not be necessary to do this step), Collapse
6. Expand Revit Content Libraries section and VERIFY your selections (it messes up for me every time and others have reported the same)
7. Add any ADDONs . Do not use APP manager to add any Revit official Addins, they will fail to deploy. Can't find the knowledge article that gives you instructions on how to add them to the Addon section. Updates are fine to install EXCEPT RECAP. If you add the ADDON MSI make sure to add this as the parameter INSTALLDIR="C:\Program Files\Autodesk\" (thanks Tony M)
8. Generate the deployment.
9. Verify that the Customsettings folder got created and it will have the Custom Revit.ini file prefixed with deployment name i.e. GBBN_Revit_AutoCAD_2017_Revit.ini. You can also verify that the MST file now has the REVITINIDEPLOYGBBN_Revit_AutoCAD_2017_Revit.ini

If it did not work then the REVITINIDEPLOY will just have Revit.ini with NO deployment name prefix

Hope this helps and saves you headaches recreating deployments.

*****BEFORE*************

[ProductSelectionDlg2]
UI_CREATOR=ProductSelectionDialog2
UI_SOURCE=Setup\SetupAcadUi.dll
BACKGROUND_IMAGE=SetupRes\AutoCAD.png
UI_POSTCONSTRUCT=SetInstallPathEditorStatus
UI_POSTCONSTRUCT_SOURCE=Setup\AcSetup.dll

*****AFTER*************

[ProductSelectionDlg2]

UI_CREATOR=ProductSelectionDialog2
UI_SOURCE=Setup\SetupAcadUi.dll
BACKGROUND_IMAGE=SetupRes\BDS.png (I changed this in addition) used to be AutoCAD.png
UI_CONSTRUCT_SOURCE=Setup\RevitContentPackUI.dll
UI_CONSTRUCT=SelectionDlgConstruct
UI_POSTCONSTRUCT=SetInstallPathEditorStatus
UI_POSTCONSTRUCT_SOURCE=Setup\AcSetup.dll
UI_FINALIZE=RevitCreateCustomIni
UI_FINALIZE_SOURCE=Setup\RevitSetup.dll

Please join the Revit iQ webinars part of the AEC Webinar series.

Webinar Link
http://forums.autodesk.com/t5/revit-architecture/build-your-revit-iq-webinar-series/m-p/6413092/high...
Youtube Recordings
https://www.youtube.com/playlist?list=PLY-ggSrSwbZqlmW7-QY2sopGGKMve6GFg
Box Link Dataset
Datasets and Slides: https://autodesk.box.com/s/tb7b8v6n1fvip6ms53i5dl53xzsew3mr

[Anonymous]

I do not find a "setup.ini" file that is in the same location of the setup.exe, so are you referencing the "MYdeploymentNAME.ini" files?

[Anonymous]

I do not find a "setup.ini" file that is in the same location of the setup.exe, so are you referencing the "MYdeploymentNAME.ini" files?

[Anonymous]

Absolutely!

[JrodSchultz]

Just did this on a existing Revit deployment that wasn't working, after adding the extra lines of code to the appropriate "ini" files it now works with the custom Revit.ini file.

Thanks for the fix!

[BIMologist_]

---

@Anonymous wrote:

I do not find a "setup.ini" file that is in the same location of the setup.exe, so are you referencing the "MYdeploymentNAME.ini" files?

---

MYdeploymentNAME.ini" files?

yes GBBN_Revit_AutoCAD_2017.ini = MYdeploymentNAME.ini

[Anonymous]

Thank you I was able to get it to work with that assumption.