badangel.blogg.se

When specifying a Custom Revit.ini to be used with your deployment, although the Configurable Folders paths are updated, content will not be installed to these locations during the deployment creation or installation of the deployment. When installing from a deployment with a custom Revit.ini, the custom Revit.ini may not copy to the client machine if the client machine and the server the deployment install is started from are not on the same network domain or workgroup.Ĭustomize Application Settings within Deployment Image

To avoid this, ensure that you have Write permission on your Microsoft Windows machine when creating your deployment with the Custom Folder option. If you specify a folder location that has Read Only permission at the user level according to the Microsoft Windows User Access Control, then Revit MEP may become unstable. In the Revit MEP 2013 Deployment Wizard the Path for Configurable Folders allows you to specify a custom folder in which to copy support content. To prevent this error set the User Access Control in Windows Control Panel to Never Notify. When installing or uninstalling the procedure may fail if content had been redirected to be on a shared network location using a mapped drive.

Install or Uninstall may fail if content is on a shared network location using a mapped drive Before you install Revit MEP 2013, close all applications.