Contents Chapter 1 Autodesk Installation Overview and FAQ . . . . . . . . . . . . . 1 What's New in the 2014 Installation Guide . . . . . . . . . . . . Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . Prepare for Installation . . . . . . . . . . . . . . . . . . . . Select Install Type . . . . . . . . . . . . . . . . . . . . . . . Change Product Language . . . . . . . . . . . . . . . . . . Specify License . . . . . . . . . . . . . . . . . . . . . . . . Configure and Install . . . . . .
Network Administration and Deployment . . . . . . . . . . . . What's New in the 2014 Network Administrator's Guide . About Deployments . . . . . . . . . . . . . . . . . . . . . Language Pack Deployment . . . . . . . . . . . . . . . . . Check Deployment Readiness . . . . . . . . . . . . . . . Ensure .NET 3.5 Support for Windows 8 . . . . . . . . . . Determine the Installation Type . . . . . . . . . . . . . . Determine the License Server Model . . . . . . . . . . . . Configure Individual Products . . . . . .
Using Other Features of Network Licensing . . . . . . . . . . . . 86 Frequently Asked Questions about Network Licensing . . . . . . 102 Chapter 4 Autodesk Navisworks 2014 Installation Supplement . . . . . . 105 System Requirements . . . . . . . . . . . . . About Language Packs . . . . . . . . . . . . . Uninstalling Language Packs . . . . . . File Exporters . . . . . . . . . . . . . . . . . . Autodesk Navisworks Uninstall Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
Autodesk Installation Overview and FAQ 1 What's New in the 2014 Installation Guide The Installation Overview and FAQ is now part of a consolidated Installation Help online document that includes the Network Administrator's Guide, Licensing Guide, and product-specific supplements. This new structure is expected to be easier to use and to maintain. The product installers now also install an Autodesk Uninstall Tool that makes it much easier to uninstall a suite or several products in a single operation.
Prepare for Installation Before starting to install, check the following details: ■ Confirm that your computer meets the minimum system requirements. If in doubt, click System Requirements at the bottom of the installer screen. ■ Find the certified and recommended computer hardware for the products or suites you are planning to install. For more information, go to www.autodesk.com/hardware.
■ The Windows 8 update for Microsoft Security Advisory ( 2749655) is not installed. If any of these conditions cannot be resolved, then the System Administrator or user must manually enable .NET 3.5 on each Windows 8 computer before running the Autodesk installer. For more information and procedures, see the following MSDN article. Select Install Type Here is some basic information to help you choose the right path. ■ Install is recommended for individual users or small groups.
Change Product Language IMPORTANT This topic does not apply to Autodesk products that provide each language version on separate media. For these products, you must specify the product language when purchasing, and cannot change it. For some Autodesk products, such as AutoCAD, you can select the product language at the time of installation, using this drop-down menu on the installer: Language Selection Menu If the language you want is not on this menu, your available options vary by Autodesk product.
specific Autodesk product, and includes an installer. You must install the Autodesk product before installing a language pack. Each installed language pack creates a separate icon on the Windows Start menu, such as "Inventor French (Francais)" that you can use to start the product in that language. Depending on your product, language packs may be available on the installation media or from a website. A language pack installer provides an option to create a language pack deployment for a particular product.
Licenses are distributed across a pool of multiple servers in the network. You enter the name of each server in the pool. ■ Redundant License Server Three servers are available to authenticate each license. You enter the names of the three servers. Configure and Install Installation Path This path specifies where the product folder will be installed. If you change the location, use only valid ASCII characters in the install path. Configuration Most products have a number of configuration settings.
If your computer is disconnected from the Internet, you will see a website address where you can activate a product later when you are connected. Record the website address, product name, serial number, product key, and request code. You will need to enter this data on a web page to activate the product. For more information on activation, go to Autodesk Licensing and select the FAQ link.
Frequently Asked Questions For advice and assistance with topics not covered here, go to Autodesk Support, click your product name, and search in the Knowledgebase for your product. What if I have lost my serial number or product key? Check your product packaging or purchase records, if available, or contact Autodesk Customer Service for assistance.
How does a trial license work in a product suite or bundle? A single trial period, usually 30 days, applies to all Autodesk products in the suite or bundle. When the first product is started, the trial period begins for all products. If the user does not activate one of the products before the trial period ends, access to all of the products is denied. After the trial period ends, the user can restore access to the products by entering an activation code.
Access to the list varies by version of Windows: ■ Windows 7 or XP: Click Start menu ➤ All Programs. ■ Windows 8: Right-click Start screen ➤ All Apps. In the tool window, select the products to be uninstalled. If uninstalling one of your selected products would prevent another product from operating correctly, you will see a warning message about also uninstalling the related products. The Uninstall Tool does not uninstall service packs or locally installed Help files.
Autodesk Network Administrator's Guide 2 Network Administration and Deployment What's New in the 2014 Network Administrator's Guide The Network Administrator's Guide is now part of a consolidated Installation Help online document that includes the Installation Overview and FAQ, Licensing Guide, and product-specific supplements. This new structure is expected to be easier to use and to maintain. Other improvements are as follows: ■ Deployment path length validation.
.MSI or .EXE packages. For more information, see Include Additional Software (page 17). ■ Scripted uninstall file. Each deployment now includes a batch file that you can use to automatically uninstall all or part of a deployment. For more information, see Uninstall Deployed Products (page 24). About Deployments A deployment provides an efficient way to install one or more Autodesk products with a standard configuration on multiple computers.
some or all of the products in a deployment. The two files are _Uninstall.txt and Product_Uninstall_ReadMe.txt. Language Pack Deployment Some Autodesk products, such as Inventor and Revit, can use separate language packs to add one or more additional language versions to an installed product. Each language pack provides user-interface strings, message text, and documentation in a specific language, without duplicating the product software.
Deployment Checklist For any Windows 8 computers, ensure that the Microsoft .NET 3.5 Framework can be installed, or manually enable it before deployment. Locate your product serial number and product key. These are found on the outside of the product packaging, or in an email message if you downloaded your product or upgrade from Autodesk. Identify a network location for deployments, and create a shared folder to contain deployments.
If the Autodesk installer is unable to install .NET 3.5 or an earlier version on Windows 8, the following message appears: An Internet connection is required to install a Windows component. Please connect and re-launch the installer. The .NET installation is prevented by any of the following conditions: ■ An Internet connection is not available during installation. ■ The computer is configured to use Windows Server Update Services (WSUS) instead of Windows Update.
A major advantage of a network license is that you can install the product on more systems than the number of licenses you have purchased (for example, purchase 25 licenses, but install on 40 computers). At any one time, the product runs on the maximum number of computers for which you have licenses, so you get true floating licenses.
custom deployment. Configuration details for different products are covered in product supplements to Installation Help. It is recommended that you review these supplements, and determine the right settings for each product in your deployment. To configure product settings, on the Create Deployment page of the installer, ensure that the product is selected for installation, and then click the product in the scrolling list. The configuration panel opens.
Before creating a deployment, store any additional software in a single location that is easy to find. To add software to a deployment, click Add, browse to the file location, and then click the file. The file name and path are added to the management table. Buttons for deleting files and moving them up or down in the list become active when the table contains at least two files. Horizontal and vertical scroll bars are added when the table extends beyond the window.
Once merged, a service pack cannot be removed from the administrative image. To extract a Microsoft Installer Patch (MSP) file from a service pack 1 Download the service pack from the Support site for your product. 2 Review the service pack Readme file for information about patch usage. 3 Open a Windows command prompt and enter the patch file name followed by the /e switch and a target file name. Here is the general command format: \.exe /e \.
install the program. Any subfolders inside a network shared folder are automatically shared. IMPORTANT If your deployment folder 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 deployments in a location at or near the top directory of the drive, such as \\serverXX\Deployments.
4 On the Configure page, Administrative Image section, specify the following data: a Enter a descriptive name for the deployment that identifies the user group, platform, or other attribute to differentiate this deployment from others. b Enter the path or browse to the shared network folder where you want to create and store your administrative image.
7 On the Product Information page, select your license type, and enter your serial number and product key. If this data is valid, green check marks appear. 8 If you are sure that the product information is correct, click Next. 9 On the Create Deployment Configuration page, select the products to include in the deployment. 10 If you need to configure settings for a product, click the product name to open the configuration panel where you can review and change settings.
3 In the tool panel, browse to the 32- and 64-bit deployments, and then enter a descriptive name for the combined deployment. The combined deployment is saved in the same folder as the 32- and 64-bit deployments. Modify a Deployment Inside each deployment folder is a Tools folder that contains a shortcut (.LNK file) named Create & Modify a Deployment.
To modify a deployment 1 Open the shared network folder that contains the deployment. 2 In the Tools folder, double-click the Create & Modify a Deployment shortcut. The installer opens at the Modify Deployment page. 3 Click through the deployment configuration pages, and select the required options. 4 Click Create Deployment. Direct Users to the Administrative Image After you have created the deployment, users can install the program using the shortcut (.
Alternative Distribution Methods Overview of Distribution Methods In addition to standard deployments, you can use the following alternative methods of distributing Autodesk programs on Windows platforms: ■ Batch files ■ Group Policy Objects (GPOs) ■ Microsoft System Center Configuration Manager (SCCM) ■ Imaging software Each method is described in a separate set of topics in this guide: ■ Batch Files for Deployments (page 25) ■ Group Policies for Deployments (page 28) ■ Microsoft SCCM for Deployme
Sample Installation Batch Files The sample batch files in this section install AutoCAD in typical configurations for stand-alone or network licensed versions. To make it easy to copy this sample batch file and substitute your own information, the same names are used throughout for variables. Notes is the drive letter where the media is mounted or the setup.exe file is stored Install options used here include /t (setup is executed by script) and /qb (display a basic user interface).
ACADSERIALPREFIX=ACADSERIALNUMBER= ADLM_PRODKEY= ADLM_EULA_COUNTRY= InstallLevel=5 ACADSTANDALONENETWORKTYPE="3" ACADLICENSESERVERTYPE="Single Server License" ACADLICENSETYPE="Network License" ACADSERVERPATH=" 000000000000" Notes For network licenses, ACADSTANDALONENETWORKTYPE identifies the type of license being installed. It has three possible values: 0 for both network and stand-alone, 1 for stand-alone, and 3 for network.
ACADSERVERPATH=" 000000000000 27005; 000000000000 27005; 000000000000 27005;" Notes thru are valid network license servers with redundant licenses. Run Batch Files After creating a batch file, you move it to a server or use a mapped drive letter or a UNC (universal naming convention) path. If you place it on a server for users to run, create a shared folder on the server, and then add users to the share with the rights they need.
The following section outlines the advantages and disadvantages of using group policies. Advantages ■ Works well with deployment functionality. ■ Allows you to add custom files to a deployment. ■ Allows deployment to computers rather than to users. Disadvantages ■ Prohibits the passing of command-line parameters to an MSI executable. You must use scripts instead. ■ Prohibits customization of application settings, other than what is set while creating a deployment.
NOTE For more information, go to Microsoft TechNet and search for "Group Policy Management Console". To assign a deployment to a computer 1 Start the Group Policy Management Console (gpmc.msc). 2 Right-click the organizational unit where you want to create the group policy object (GPO). Then select Create and Link a GPO Here and name the Group Policy. 3 Edit the policy. 4 In the Group Policy Object Editor dialog box, under Software Settings, right-click Software Installation, and click New ➤ Package.
Adding a Language Pack If your product uses language packs, you may need to add a language pack to your package. To add a language pack 1 In the Group Policy Object Editor dialog box, under Software Settings, right-click Software Installation for the same object, and then click New ➤ Package. 2 In the Open dialog box, navigate to the location of the administrative image that you specified when creating the deployment. Navigate to Img\\\\lp.msi. Click Open.
2 In the Open dialog box, navigate to the location of the administrative image that you specified when creating the deployment. Navigate to Img\\\ps.msi. Click Open. The used in the examples is en-us for US English. Examples For x86 deployments: \\server123\Deployment\Img\x86\en-us\ For x64 deployments: \\server123\Deployment\Img\x64\en-us\ 3 In the Deploy Software dialog box select Advanced and click OK.
NOTE If problems arise, an entry is logged in the system's Event Viewer, under Applications. GPO Requirements for Deploying Revit Interoperability These instructions apply to group policy object (GPO) deployments of Revit Interoperability components with 3ds Max, 3ds Max Design, Inventor, or Showcase. The product-specific MSI files are as follows: ■ RXM2014.msi for 3ds Max or 3ds Max Design ■ RXI2014.msi for Inventor ■ RXS2014.msi for Showcase In addition to the main GPO transform file (gpo.
6 Include this MST file along with gpo.mst and the transform file for the Revit Interoperability MSI. Microsoft SCCM for Deployments Microsoft System Center Configuration Manager (SCCM) allows you to manage software distribution to selected target systems through a remote process. For more information about this topic, go to Microsoft TechNet and search for "System Center Configuration Manager". Each deployment includes a folder \SMS_SCCM scripts, which contains four documents to help you
Set Up a Source Directory for SCCM When you use SCCM to deploy Autodesk products, you set up the source directory using the Create Deployment process in the installer. The Create Deployment process creates an administrative image that is used by SCCM to distribute the Autodesk products to the target systems. The location of the administrative image is the package source directory. To learn more about deployments and setting up the source directory for Autodesk software, see About Deployments (page 12).
4 In the Distribute Software wizard, click Next. 5 In the Package dialog box, select Create a New Package and Program without a Definition File. Click Next. 6 In the Package Identification dialog box, enter the information for Name, Version, Publisher, Language and any comments. Click Next. 7 In the Source Files dialog box, make selections for where SCCM retrieves the files and how it manages them. Select “Always Obtain Files from a Source Directory”. Click Next.
Click Next. 13 In the Advertise Program dialog box, select Yes to advertise the program to users. Click Next. 14 In the Select a Program to Advertise dialog box, select the package you want to advertise. Click Next. 15 In the Select Program ➤ Advertisement Target dialog box, select the collection of people to whom you want to advertise, or create a new collection. 16 In the Select Program ➤ Advertisement Name dialog box, enter or change the name of your advertisement.
To create a software uninstallation package using SCCM 1 Click Start menu ➤ All Programs ➤ Microsoft System Center ➤ Configuration Manager 2007 ➤ ConfigMgr Console. 2 In the Configuration Manager Console window, expand Software Distribution. 3 Right-click Packages ➤ Distribute ➤ Software. 4 In the Distribute Software wizard, click Next. 5 In the Package dialog box, select Create a New Package and Program without a Definition File. Click Next.
Click Next. 13 In the Advertise Program dialog box, select Yes to advertise the program to users. Click Next. 14 In the Select a Program to Advertise dialog box, select the package you want to advertise. Click Next. 15 In the Select Program ➤ Advertisement Target dialog box, select the collection of people to whom you want to advertise, or create a new collection. 16 In the Select Program ➤ Advertisement Name dialog box, enter or change the name of your advertisement.
IMPORTANT Autodesk does not recommend or support the distribution of products using imaging software. However, if you plan to use this method of distribution, please review the following instructions carefully. The use of imaging software can result in conflicts with product licensing, incomplete installations, and problems with activation.
Distribute Network Licensed Products You can use a master image to distribute network licensed products. To distribute a network licensed product to multiple computers using a master image 1 Create a network deployment for a network licensed product. For more information, see Create a Deployment (page 20). 2 Install the product from the deployment onto the master computer. NOTE A license server must be running, and each computer must be connected to the network in order for the product to obtain a license.
NOTE When you restore the disc image, any files that were altered are put back in their original state and ready to use again. The license files are preserved, and no reactivation of products is necessary. Clean a Master System and Restore the Operating System If you have already run your Autodesk product on the master computer, the master computer should be properly cleaned before creating a master image.
Licensing Questions What is the difference between a stand-alone license and a network license? A stand-alone license supports one or more Autodesk products for an individual user. Similarly, a multi-seat stand-alone license supports a specific number of users. While the software can be installed on additional computers in your facility, the license specifies a maximum number of concurrent users. A network license supports a specific maximum number of concurrent users on computers connected to a network.
SAMreport-Lite can help you better manage your software licenses. For more information, click SAMreport-Lite. Deployment and Networking Questions Where should deployments be located? Create a network share folder in the top directory of the drive where you want to store deployments, such as \\serverXX\Deployments. This location minimizes the possibility of your deployment path exceeding the path length limit set by the Windows operating system.
You can create another deployment later, and include additional products, but to do this you need to create a new administrative image from the installation media. What are profiles of user preferences? A profile is a collection of user settings for AutoCAD or another Autodesk product. Profiles are not used by all products.
How do I extract an MSP file? This topic applies only to Windows platforms. A Microsoft Patch (MSP) file is usually contained in a Service Pack executable that you download from the Support website for your product. To extract the MSP file from the executable, run the patch program from the Windows command prompt using the /e switch. The syntax is as follows: \.exe /e \.msp Pay particular attention to the location where the files are extracted.
How do I install tools and utilities after installing my product? Run the installer again from the downloaded package or the original media, and click Install Tools & Utilities on the first screen. The installer guides you through the process of selection, configuration, and installation of tools and utilities. When should I reinstall the product instead of repairing it? Reinstall your product if you accidentally delete or alter files that are required by the program.
Glossary activate Part of the Autodesk software registration process, it allows you to run a product in compliance with the product's end-user license agreement. administrative image A collection of shared file resources created by the deployment process and used to install the program to network computers. deployment The process of installing Autodesk products to one or more computers on a network. hot fix Autodesk terminology for a minor application patch that contains a few code fixes.
Autodesk Licensing Guide 3 Introduction What's New in the 2014 Licensing Guide The Licensing Guide is now part of a consolidated Installation Help online document that includes the Installation Overview and FAQ, Network Administrator's Guide, and product-specific supplements. This new structure is expected to be easier to use and to maintain. Other improvements are as follows: ■ Updated Network License Manager tools with FLEXnet 11.11.
■ A network license supports a specific maximum number of users on computers connected to a network. A software utility known as the Network License Manager (NLM) issues a license to each user who starts an Autodesk product, up to the number of licenses purchased. When a user closes all Autodesk products, typically the license is returned to the NLM, and is available to other users.
Capacity Applies to a usage-based license. In this model, the user pays a fee that varies according to the amount of time that the product is actually used. Term Applies to a term-based license. In this model, the user pays a fee for a specified term, which can be renewed. Term-based licenses require named users. Activation Activation is the process of verifying the serial number and product key of an Autodesk product, and licensing it to run on a specific computer.
Simplified Licensing The licensing process has been simplified for some customers with stand-alone term licenses, including students at educational institutions. The licenses are pre-registered so that the customers are not required to enter serial numbers and product keys or follow the activation process. These customers are encouraged to download products from an Autodesk website using the Install Now option, which automatically installs the product on the user's computer.
when started for the first time if an Internet connection is available, and if the serial number and product key combination is registered correctly with Autodesk. A multi-seat stand-alone license can be deployed efficiently to multiple computers on a network from an image created by the Create Deployment option in the installer. For more information about multi-seat stand-alone installation and deployments, see the Network Administrator's Guide for your product, or go to www.autodesk.com/licensing.
4 In the Product License Information dialog box, click Save As. 5 In the Save As dialog box, name the file, choose a location where you want to save the file, and then click Save. 6 In the Product License Information dialog box, click Close. Update Your Serial Number You typically update your serial number for a stand-alone license when you purchase a new license in order to change the license type or behavior.
NOTE In some cases, you must restart the product to display the updated serial number. 7 In the Product License Information dialog box, click Close. Manage a Term License Each Autodesk term license contract identifies a term expiry date and a number of allowed users. Users log in to the Autodesk My Accounts portal to download products associated with a specific contract.
The License Transfer Utility is a custom stand-alone installation option. During installation, a shortcut is created. A shortcut is installed once per product, per computer. You can transfer a license to another computer temporarily or permanently. For example, a temporary transfer enables you to use the Autodesk product on a mobile computer while your main computer is being repaired or replaced. License transfers rely on the product serial number or product key.
To export a license 1 On the computer where you want to export the license, start the License Transfer Utility. ■ Windows 7 or XP: Click Start menu ➤ Autodesk ➤ [Product Name] ➤ License Transfer Utility. ■ Windows 8: Right-click Start screen ➤ All Apps ➤ License Transfer Utility – [Product Name] ■ Mac OS X: Open Applications/Autodesk/[Product Name]/Licensing/License Transfer Utility.
activation to the importing computer. The presence of an active license allows your Autodesk product to run on that computer. To import a license 1 On the computer where you want to import the license, start the License Transfer Utility. ■ Windows 7 or XP: Click Start menu ➤ Autodesk ➤ [Product Name] ➤ License Transfer Utility.
Troubleshoot a Stand-Alone License Error Preserving a License When Hardware Changes If you replace or reconfigure hardware on the computer where your Autodesk product license resides, the stand-alone license might fail, with the result that you will not be able to use your product. To prevent damage to your product license, use the License Transfer Utility to export your license file before changing the hardware. After the hardware change, you can import the license file back onto the computer.
2 Reinstall the operating system and reinstall the Autodesk product. 3 Paste the license folder to the same location from which you originally copied the folder in step 1. You can now run your Autodesk product. Changing the System Date and Time Your product license allows for time changes to the system clock within two days of the current time. If you set your system clock back or forward more than two days, the next time you start your product, you will see a reminder to correct the system clock.
For a stand-alone license, you need to export the license before re-imaging the computer. You can use the License Transfer Utility to export the license to the Autodesk server. After the re-imaging, import the license to the correct computer. Restoring Access to a Term License The most common reasons for being denied access to a term-licensed Autodesk product are as follows: ■ The user ID you entered does not represent an authorized user. To change or check permissions, see your license administrator.
Advantages of the Single License Server Model ■ Because all license management takes place on a single server, you have just one point of administration and one point of failure. ■ Of the three license server models, this configuration requires the least amount of maintenance. Disadvantage of the Single License Server Model ■ If the single license server fails, the Autodesk product cannot run until the server is back online.
least two license servers are still functional. The Network License Manager is installed on each server, and the license file on each server is the same. In the redundant license server model, all servers must reside on the same subnet and have consistent network communications. (Slow, erratic, or dial-up connections are not supported.) Advantage of the Redundant License Server Model ■ If one of the three servers fails, all licenses that are managed in the server pool are still available.
Hardware and software requirements for the network license server Hardware/Software Requirement ■ Windows 7 Home Premium ■ Windows 7 Professional ■ Windows 7 Ultimate ■ Windows 7 Enterprise ■ Windows 7 Starter (32-bit) Windows XP 32- or 64-bit. SP2 or later for 64-bit systems; SP3 or later for 32-bit.
Hardware and software requirements for the network license server Hardware/Software Requirement FLEXnet 11.11.0.0 Virtual Machine Support Hardware Virtualizer Virtual OS Intel PC 64 Windows 2012, 2008 or 2003 R2 Windows 8, Windows 7, Windows Server, or Windows XP; 32- or 64-bit on all platforms. servers running on VMware® ESX 4.0 or 5.0 (License Manager Only) Linux System Requirements for the Network License Manager NOTE The Network License Manager supports Ethernet network configurations only.
Linux hardware and software requirements for the network license server Hardware/Software Requirement NOTE The Network License Manager uses TCP packet types Internet browser Qt 4.7.2 FLEXnet 11.11.0.0 Mac OS X System Requirements for the Network License Manager NOTE The Network License Manager supports Ethernet network configurations only. Mac OS X hardware and software requirements for the network license server Hardware/Software Requirement Operating system Mac OS® X version 10.5.
Understanding Your Network License How Your License Works When you start an Autodesk product, it requests a license from the license server through the TCP/IP network. If a license is available, the Network License Manager assigns a license to the computer, and the number of available licenses on the license server is reduced by one. When you exit a product, the license returns to the Network License Manager.
downgrade your suite license to a single AutoCAD license if the suite license is required by another user. In this situation, AutoCAD is holding onto a suite license that it may not need. The only way to return that license to NLM is to shut down AutoCAD. License cascading is a process by which network licenses are automatically switched or substituted by the NLM according to a hierarchy of value.
The network license server(s) must be accessible to every user who runs one or more products that require a network license. The following table defines each license file parameter. For more information, see the License Administration Guide, installed with the Network License Manager.
Definitions of license file parameters Line Parameter Definition Example from any license files on the same license server that have a date earlier than the defined Issue Date INCREMENT SIGN Encrypted signature used to authenticate the attributes of the license file SIGN=0 SIGN2=0 Feature Code Product supported by the license file 51200ACD_2013_0F Expiration Date Amount of time the licenses are available permanent Number of Licenses Number of licenses supported by the license file 25 VENDO
Definitions of license file parameters Line Parameter Definition Example Serial Number Serial number of the Autodesk product 123-12345678 SIGN Encrypted signature used to authenticate the attributes of the license file SIGN=6E88EFA8D44C License File Examples The Autodesk network license file contents reflect the license server configuration and the licensed products, as shown in the examples provided.
Example of a License File for a Redundant Server Here is an example of a completed license file for a redundant license server model: NOTE The redundant server model requires the addition of a port number (the default is 27005) for each server. Example of a License File for Combined Autodesk Product Versions You can combine a license file for different releases of the same Autodesk product or for different Autodesk products, and run all products from one license server.
Package License File Types and Examples Autodesk offers a package license file option, which allows the use of a suite of products that are packaged and sold together. The package license file contains a set number of licenses for four different versions of your software. Running an instance of any one of the versions uses one license in the package. Packaged license files support prior versioning for subscription users.
Example of a Package License File for a Single or Distributed Server Here is an example of a completed package license file for a single or distributed license server model: Example of a Package License File for a Redundant Server Here is an example of a completed package license file for a redundant license server model: 74 | Chapter 3 Autodesk Licensing Guide
Example of a Package License File for Combined Autodesk Product Versions Here is an example of a completed package license file for combined Autodesk product versions: Network Licensing | 75
Losing Your Connection to the License Server When an Autodesk product is running, it communicates with the license server at regular intervals using a method known as the “heartbeat” signal. If the heartbeat signal is lost, the server tries to reconnect. If the server cannot reconnect, the user receives a license error. If the product stops working because it has lost a connection to the server, you must shut down the product, and then restart it.
Running the Network License Manager The Network License Manager is used to configure and manage the license servers. When you create a deployment, the installer prompts you for information about the license manager, such as license server model and server name. Install the Network License Manager IMPORTANT Do not install the Network License Manager on a remote drive. When you install the Network License Manager files, you must provide a path to a local drive.
4 Click Close when you see the Install Succeeded message. By default, the Network License Manager tools are installed in the following directory: /usr/local/flexnetserver. In addition, scripts to help set up your license server are installed in the following directory: /Library/StartUpItems/adsknlm. Linux procedure 1 Open a shell as a super user (using su -).
To obtain the host name and ID using the LMTOOLS utility IMPORTANT Do not run LMTOOLS on a remote computer. You should be logged in with Administrator rights when working with the LMTOOLS utility. 1 Click Start ➤ All Programs ➤ Autodesk ➤ Network License Manager ➤ LMTOOLS Utility. 2 In the LMTOOLS utility, click the Systems Settings tab. 3 Locate the Computer/Hostname box. Copy the host name and paste the information into a text editor. 4 Locate the Ethernet Address box.
IMPORTANT If you have a firewall between the license server(s) and the client computers, you must open some TCP/IP ports on the server for license-related communication. Open port 2080 for adskflex, and open ports 27000 through 27009 for lmgrd. Configure the license server using one of the following procedures. You should be logged in with Administrator rights when working with the LMTOOLS utility. NOTE If your license server is running, you must stop it before performing any system maintenance.
This is the path to the license file obtained through autodesk.com or the location where you placed the license file if you obtained it offline. 7 In the Path to the Debug Log File box, enter a path to create a debug log, or click Browse to locate an existing log file. It is recommended that you save to the C:\Program Files\Autodesk\Autodesk Network License Manager folder. The log file must have a .log file extension. For new log files, you must enter the .log extension manually. 8 To run lmgrd.
To configure automatic start-up of a Mac OS X license server 1 Create a directory titled flexnetserver under the home directory; for example, /usr/local/flexnetserver. 2 Move the following files: lmgrd, adskflex, lmutil, and your product license file (.lic) into the flexnetserver directory created in Step 1. 3 If it does not already exist, create the directory StartupItems under /Library using the sudo command. For example, sudo mkdir StartupItems.
7 Create a property list file named StartupParameters.
■ You have received the network license file from Autodesk that contains the product licenses; for example, productlicense.lic. To configure automatic start-up of a Linux license server 1 Extract the FLEXnet IPv4 server files into the following directory: /opt/flexnetserver. 2 Copy the .lic file into the flexnetserver directory created in Step 1. 3 Open a terminal window in root mode. 4 Go to the directory /etc/. 5 Locate the rc.local file. 6 Edit the rc.
■ Check the boot.log file created in /opt/flexnetserver/ to see if lmgrd and adskflex have started. Uninstall the Network License Manager Before uninstalling the Network License Manager, you must stop the license server. For more information, see Stop and Restart the License Server (page 91). Either before or after the uninstall, you must manually delete files that you created for use with the Network License Manager, such as log files, license files, and the options file.
Linux procedure 1 Open a shell as a super user. 2 Execute the following command to verify the package number of the Network License Manager that you installed: rpm -qa |grep adlm 3 Execute the following command to uninstall the Network License Manager package: rpm -e adlmflexnetserver-#.rpm where # is the package number. 4 If you edited your rc.local file to configure your license server (for example to start lmgrd), remove those commands from the rc.local file.
Help ➤ About and consult the Product License Information dialog box, or in some products, place your cursor over the Borrowing icon in the status tray (lower right corner of the screen). When the borrowing period expires, the borrowed license is automatically returned to the license server. When your computer is reconnected to the network, you can run your Autodesk product from the network or borrow a license again.
2 In the Borrow a License window, on the calendar, click the date when you want to return the license. This date must be within the valid date range set by your network administrator. The valid date range is displayed in this window. 3 Click Borrow License. 4 In the License Borrowed message, click Close. The license is borrowed, and you can now use your Autodesk product with your computer disconnected from the network.
The Borrow a License window is displayed, presenting the following options: Calendar Sets the date when you plan to return a borrowed license. The return date must be within the range specified by your network administrator. Borrow a License Borrows the license from the network license server based on the specified return date. Cancel Cancels the borrowing action; no license is borrowed.
To check the license expiration date Access to this command varies by product, and includes one or both of the following options: ■ In the status tray, right-click the License Borrowing icon. ■ Click Help menu ➤ About ➤ Product Information or Product License Information. In the Product License Information dialog box, see the License Expiration Date. RETURNLICENSE Command Use this command to return a borrowed Autodesk product license earlier than the return date specified when you borrowed the license.
Windows Utilities for License Server Management FLEXnet provides two utilities for managing the license server. The default location for these tools is in this folder: C:\Program Files\Autodesk\Autodesk Network License Manager. ® LMTOOLS Utility (lmtools.exe) Provides a Microsoft Windows graphical user interface for managing the license server. lmutil.exe Provides a set of command-line options for managing the license server. You can use LMTOOLS or lmutil.
5 Click the Start/Stop/Reread tab. 6 Click Stop Server. 7 Close LMTOOLS. To restart a Windows license server 1 Do one of the following: ■ Windows 7 or XP: Click Start ➤ All Programs ➤ Autodesk ➤ Network License Manager ➤ LMTOOLS Utility. ■ Windows 8: Right-click Start screen ➤ All Apps ➤ LMTOOLS Utility. 2 In the LMTOOLS utility, click the Service/License File tab. 3 Select the Configure Using Services option. 4 Select the service name for the license server you want to start manually.
sudo /sbin/SystemStarter restart adsknlm To stop a Linux license server Enter the following in Terminal: ./lmutil lmdown -q -force To restart a Linux license server Enter the following in Terminal: ./lmgrd -c acad.lic -l debug.log NOTE Replace acad.lic with your license file name and debug.log with your log file name. Update FLEXnet from a Previous Version Autodesk 2014 products require FLEXnet version 11.11.0.0 or later. If you are currently using an earlier version of FLEXnet, you need to update.
To verify the file version of Windows tools 1 Do one of the following: ■ Windows 7 or XP: Click Start ➤ All Programs ➤ Autodesk ➤ Network License Manager ➤ LMTOOLS Utility. ■ Windows 8: Right-click Start screen ➤ All Apps ➤ LMTOOLS Utility. 2 In LMTOOLS utility, click the Utilities tab. 3 Enter the location of the file, or click the Browse button to locate the file and click Open. The default file location is as follows: C:\Program Files\Autodesk\Autodesk Network License Manager\lmutil.
■ Windows 8: Right-click Start screen ➤ All Apps ➤ LMTOOLS Utility. 9 In the LMTOOLS utility, click the Start/Stop/Reread tab. 10 Click Start Server. 11 Close LMTOOLS. To determine the installed version of FLEXnet, you need to verify the version of the following files: ■ lmgrd ■ lmutil ■ adskflex NOTE Version 11.11.0.0 of the FLEXnet license manager that ships with Autodesk products is backwards compatible, and will administer licenses for products from versions 2002 through 2014.
2 Stop the Autodesk Network License Manager service by entering the following in Terminal: sudo ./lmutil lmdown -q -force 3 Note the location where the Network License Manager is installed and then uninstall the Network License Manager by entering the standard Mac OS X commands, for example, rm. 4 Install the Network License Manager. 5 Start the Autodesk Network License Manager service by entering the following string in Terminal. NOTE In the string, replace product.lic and debug.
Set Up and Use an Options File With an options file, you set configuration options that determine how a license server manages licenses. An options file sets parameters that the license file reads and the lmgrd program executes. The options file on each server specifies the license-handling behavior for that server. By managing the contents of the options files, you can specify the same behavior on all license servers, or implement particular differences among the servers.
To create an options file on a Windows platform You should be logged in with Administrator permissions when working with the LMTOOLS utility. 1 Open a text editor, enter the parameters you want, and then save the document as a file named adskflex.opt to the same location where you saved the license file. NOTE Be sure to save the file with the extension .opt. The default extension .txt is not recognized by the Network License Manager.
To create a report log 1 In a text editor, open the options file, adskflex.opt. 2 In the options file, enter the following syntax on its own line (REPORTLOG must be uppercase): REPORTLOG [+]report_log_path ■ Windows example: REPORTLOG +"c:\My Documents\report.rl" means that a report log named report.rl is located in the folder c:\My Documents. ■ Mac OS X or Linux example: REPORTLOG +"/Users//NLM/report.rl" means that a report log named report.rl is located in the folder /Users//NLM.
To set license borrowing parameters 1 In the options file, enter the following syntax on its own line (BORROW_LOWWATER must be uppercase): BORROW_LOWWATER feature_code n In the BORROW syntax, “feature_code” is the name of the product in the license file, and “n” is the minimum number of licenses that must remain on the server. When this number is reached, no more licenses can be borrowed.
server if the product is idle on a computer for more than the timeout period you define. IMPORTANT License timeout is not supported by all Autodesk products. If a user's license is lost because of the idle timeout, the product attempts to claim a new license once the user uses the product again. If no license is available, the user can save work before the product shuts down.
Frequently Asked Questions about Network Licensing This section outlines some common questions and their solutions with regards to software licenses and licensing your product(s). For additional advice and assistance, go to Autodesk Support, click your product name, and search in the Knowledgebase for your product. What is the difference between a stand-alone license and a network license? A stand-alone license supports one or more Autodesk products for an individual user.
How does the licensing process use the Internet? Internet communication is required to complete the process of license activation. If you are not connected to the Internet when you install an Autodesk product, you can operate in trial mode for a specified period, typically 30 days. When you choose to activate the software and enter your registration data, your computer communicates with Autodesk over the Internet. An activation code is provided for you to enter in the fields of a product dialog box.
104
Autodesk Navisworks 2014 Installation Supplement 4 This section contains information that is specific to the installation, configuration, and licensing of the following Autodesk Navisworks software: ■ Autodesk Navisworks Manage ■ Autodesk Navisworks Simulate ■ Autodesk Navisworks Freedom ■ Autodesk Navisworks File Exporters System Requirements See the following sections for hardware and software requirements.
■ Microsoft Mouse-compliant pointing device ■ Microsoft Internet Explorer 7.0 or later ® ® Deployment Requirements Hardware and software requirements for the location of the administrative image ■ 10 GB hard disk Hardware and software requirements for client machine ® ® ■ Microsoft Windows 8 (64-bit) or Microsoft Windows 7 (32 or 64-bit) (Service Pack 1) Home Basic, Home Premium, Professional, Enterprise, or Ultimate (recommended) ® ® ■ Intel Pentium 4 or AMD Athlon™ 3.
About Language Packs Each Autodesk product is installed with a default language. A language pack is a mechanism used by some Autodesk products to provide another language for the user interface and the documentation. Each language pack contains only the text strings and documents required to support a user working in the specified language; it does not duplicate the core product software.
The syntax for the shortcut is "drive:pathname\roamer.exe" - lang [language pack]. So for example, the following entry starts the program from a folder named Autodesk Navisworks in Italian language: "C:\Autodesk Navisworks\roamer.exe" -lang it-IT NOTE To run the product in a different language you must have already installed the corresponding language pack. 3 Click OK to save the changes. Uninstalling Language Packs You can uninstall language packs without uninstalling the main product.
IMPORTANT Do not use registry cleaning programs or attempt to modify the registry entries yourself to uninstall Autodesk Navisworks. Failure to follow the official uninstall procedure will result in the inability to re-install the software.
110
Index .NET 3.
issues 42 methods 25 modifying 23, 44 new features 11 overview 12 Showcase 33 verifying installation 32 DirectX 9.
L language pack 13 language pack, adding 29 languages 3, 4 license cascading 67 sharing 67 substitution 67 License Administration Guide 90, 100 license borrowing 86 configuring 99 expiration dates 86 returning licenses 89 third-party licensing tools 86 license data 53 license file example combined product versions 72 combined product versions, package license 75 distributed license server 71 generic 71 redundant server 72 redundant server, package license 74 single license server 71 single or distributed se
LMTOOLS utility 80, 86, 91 obtaining server host names and IDs 79 lmtools.exe utility 91 lmutil.
R re-imaged computers 60 reactivating licences 59 redundant license server 5, 62 license file example 72 package license file example 74 redundant license server model 16 reinstall product 47 reinstalling operating systems 59 remove deployment 24 repair product 9 report log files, creating 98 restart Windows license server 91 restore damaged installation 41 operating system 42 return dates for licenses 86 returning borrowed licenses 86, 89 RETURNLICENSE command 90 Revit Interoperability 33 running batch fil
U verifying group policy deployments undeployment 24 uninstall product 9, 47 uninstalling Network License Manager on Windows 85 updating FLEXnet tools 93 upgrading Network License Manager 77 usage-based license 49 user profile settings 45 W V vendor daemons 116 | Index 67 web-based installation 8 Windows configuring license servers 80 Network License Manager system requirements 63 obtaining server host names and IDs 78 Windows 8 2, 14 32
