Why aren't the Revit 2013 deployment custom Revit.ini settings used when installed to the client workstation?
This is from Autodesk Wiki
Check the user's permissions. When a deployment is created with an imported custom Revit.ini, permissions that prevent the install from being able to copy from the network resource can stop the custom settings from being installed. For instance, if the current user on the client machine is not a domain account, there can be authentication issues that prevent the file from copying. This will be most common when the client or server are not on the same domain, or when one is part of a workgroup and the other is part of a domain..
I think that is not the correct answer.
here is why it does not work
The problem seems to be a bug in the Installer. The MST file that is generated has a bug. x64\AdminImage\CustomSettings\\GBBN Revit Arch 2013 x64_Revit.ini Notice the double backslash \\ in front of the custom INI file.
The log shows Property(S): REVITINIDEPLOY = \\netapp1\projects1\ACADarch\LocalSupport\Install\RevitArch2013\x64\AdminImage\CustomSettings\\GBBN Revit Arch 2013 x64_Revit.ini
notice again the double backslash Property(S): CONFIG_FOLDER_VIEW_UPDATE = IES Content,C:\AcadUSERCUSTOM\Acadarch\Revit\Revit2013\IES\;Library Content,<>;Template Content,<>;Family Templates,<>;Project Path,C:\RevitLocal; So the MST is refering to the Revit.ini file for information and it cannot find the info due to the error
hope this helps
The solution is probably to work with the inifile.xml editing till they fix this