Before creating deployments for
Revit, consider these guidelines.
- Roaming user profiles: If your organization uses roaming user profiles, use the same deployment to install the software on all computers that will be used by a particular user (or set of users). This strategy ensures that each user's
Revit settings are available on all computers that he or she uses.
- Use short paths: When creating a deployment, there is a practical limit to the combined length of file paths. From the top level of the deployment (the Image folder), you can use a maximum of 100 characters for the combined length of the following: the server name, the share name, and the folder structure where the deployment is created.
To avoid problems caused by long paths, use short names for these values entered during Deployment creation from Autodesk Account, Enter settings page:
- Deployment name
- Deployment image path
-
Use local or mapped drive: When creating the deployment configuration it is best to use a local or mapped drive location for the initial download of the deployment image. Once downloaded the deployment image can be moved to a UNC based path location.
- Plan your Revit Server implementation. If you plan to implement Revit Server for your organization, take time for proper planning before creating deployments. In a deployment, you can specify the Revit Server Accelerator to which users connect. See
Revit Server Installation.
- After creating a deployment, do not attempt to use the Create & Modify a Deployment tool to modify the Revit.ini file included with the deployment. If you need to make a change to Revit.ini for the deployment, create a new deployment.