Nearly all Autodesk products can be installed via a deployment. This holds true for Autodesk InfraWorks, although there are a few key distinctions about how to create a deployment for InfraWorks versus some other Autodesk products. Backing up a little bit -- a deployment is an efficient way to install one or more Autodesk products with a standard configuration on multiple computers. The files required for installation are stored on a workstation in the network, in a folder from which the product can be distributed to all workstations. Typically, this is a task that a Software Administrator will perform.
The main difference for installing InfraWorks to multiple seats through a deployment is that InfraWorks does not reach out to a network license server to determine who is licensed. Instead, InfraWorks communicates with cloud services to determine if you are entitled to the product once you log in. Therefore, to create a deployment of InfraWorks, you must create a multi-seat standalone deployment that does not connect to a license server but instead allows you to push an installation package out to multiple machines.
(Subscription administrators such as Contract Managers and Software Coordinators can add or remove users to their InfraWorks 360 contract using the Autodesk Accounts portal available through manage.autodesk.com. You can read a blog post I wrote about this process, here: http://autodesk.typepad.com/bimagination/2016/10/software-administrators-how-to-assign-an-infraworks-license-to-a-user.html)
So, this article explains how to create a multi-seat standalone deployment for InfraWorks. Use this procedure to create a new deployment from the installer. In the process, you can create a default deployment by accepting the default configuration, or you can create a custom deployment by customizing the settings in the deployment.
1) Close all running applications on your computer.
2) Start the InfraWorks installer by running Setup.exe.
Note: You cannot create a deployment using the Install Now option from the Autodesk Desktop App. You must use the Browser Download or Download Now options in order to get an installer from which you can create a deployment. Extract the installer from the downloaded package before you begin.
- For InfraWorks 360 2017.3, you can use this direct download link to download the installer: http://efulfillment.autodesk.com/NET17SWDLD/2017/IW360P/DLM/Autodesk_InfraWorks_2017_3_Win_64bit_DLM.sfx.exe?authparam=1510215839_e743a8a941738bece9ef219c4d670df6&ext=.exe
3) On the first page,you can select a language for your installation/deployment instructions (the default is English), and then click Create Deployment.
4) On the Create Deployment > Configure [name] Deployment page, enter a name and network path in the Administrative Image section.
- Deployment configuration name: Enter a descriptive name for the deployment that identifies the user group, platform, or other attribute to differentiate this deployment from others.
- Administrative image path: Enter the path or browse to the shared network folder where you want to create and store your administrative image. Users will install from this location so it must be a shared folder where users have read-write access. Note: When you specify the path to the administrative image, the use of a Universal Naming Convention (UNC) path is strongly recommended to ensure that the path will be the same for all users over the full lifecycle of the product. Also, if your administrative image is nested inside a series of subfolders, you risk exceeding the path length limit set by the Windows operating system. Avoid this possibility by placing your administrative image in a location at or near the top directory of the server, such as \\serverXX\Deployments.
- Target Platform: InfraWorks is only supported on 64-bit operating systems, so this option is read-only.
- Include only products required by this deployment configuration:
- If selected, the deployment cannot be modified in future to include additional products.
- If unselected, the administrative image will include all possible products, so the current deployment can be modified in any way.
5) On the same page, Installation Settings section, select one or more of these options:
- Run installations in silent mode: Runs the installation in background, without prompting the user for any input. Note that silent mode can automatically restart the user’s computer without warning after installation.
- Create a log file in each workstation’s temp folder: Enables users to review and troubleshoot their own installations.
- Create a network log file: Creating a log file in a central location supports the network administrator in reviewing data for all installations. The default location is a Log folder in the same folder as the admin image. The network log file must be in a shared folder where users of the deployment have read-write access. Otherwise, log data for user installations cannot be written to the log file.
6) Click Next.
7) Review and accept the Autodesk software license agreement, then click Next.
- Autodesk InfraWorks: Expand the Autodesk InfraWorks section to view and enable/disable available sub-components.
- Autodesk Desktop App: You can uncheck Autodesk Desktop App to prevent the Autodesk Desktop App being installed with the deployment. This can be useful for software administrators who wish to prevent user control of InfraWorks release updates.
- Include additional software: If you expand the Include additional software section, you are given the option to add other components to your deployment. You cannot include a separate product (such as AutoCAD Civil 3D) in an InfraWorks deployment, but you can include plugins such as the RiverFlow2D plugin from Hydronia, LLC. to enable Flood Simulation capabilities in your InfraWorks deployments, by referencing .MSI or .EXE install files from your local system. Click Add and browse to the .MSI or .EXE installers for desired add-on components to include them in your deployment.
10) When you are finished configuring your deployment, click Create.The configuration settings you choose apply to every instance of InfraWorks installed from the deployment. After the deployment is created, these settings can be changed only by modifying the deployment. After the deployment is created, the Deployment Configuration Complete page opens, showing the path to the new deployment and a link for registering products online.
11) Make the deployment available to your users. The deployment creates an InfraWorks installer shortcut in the location you specified during deployment configuration. You can share the shortcut with your users via a network share, or install it on their systems.
12) When a user installs InfraWorks using your deployment, and then signs-in, Autodesk cloud services will use their login information to determine if they are entitled to a seat of InfraWorks, and either grant access or prevent it.