Download and Licensing Instructions Home
NOTE: For instructions on accessing the Revenera Product and License Center, see Accessing the Revenera Product and License Center.
The InstallShield 2014 and 2015 downloads are available in the Flexera Product and License Center.
IMPORTANT NOTE: A node-locked license is to be used by one user on one machine or virtual image, and may not be installed on shared computers. Any other use is a violation of the license agreement. Please ensure you are choosing the license that is registered to you. If you have any questions, please refer to your End User License Agreement.
The following installations are available for download from the Flexera Product and License Center:
To download any of the installations:
NOTE: If you do not have an account in the Flexera Community, see Accessing the Revenera Product and License Center for instructions.
If you purchase concurrent licenses of InstallShield 2014 or later, or its add-ons such as InstallShield Collaboration or the Standalone Build, a new version of the FlexNet Licensing Server software is required for the licensing server that you set up to manage your organization's licenses. This software includes improvements that are not available in earlier versions of the software.
NOTE: If you are not using InstallShield 2014 or later, or the versions of InstallShield Collaboration or the Standalone Build that ship with these versions of InstallShield, but you are using the earlier versions of these products, refer to the appropriate version of InstallShield instructions that are posted at the following site: Instructions for Flexera Product Downloads and Licensing.
The following table explains how to set up the licensing for the type of license that you purchased.
License Type | Description of License Type | Instructions |
---|---|---|
Node-locked license of InstallShield or InstallShield Collaboration | This type is tied to a specific user and machine. A node-locked license requires a product activation code to activate the product. This model is the traditional option. |
To activate the product: Launch the product that you want to activate. The activation wizard opens. Use this wizard to enter your activation code. |
Node-locked license of the Standalone Build | This type is tied to a specific user and machine. A node-locked license for the Standalone Build requires a Flexera-generated license file for the machine on which you install the Standalone Build. |
To set up a node-locked license of the product: |
Concurrent license of InstallShield, the Standalone Build, or InstallShield Collaboration |
This type enables sharing or floating of licenses among a maximum number of simultaneous users. The product on each user's machine must be connected to a license server that your organization sets up. This license type requires you to activate the licenses on the license server using an activation code, which is available through the Flexera Product and License Center. The license server software enables users to borrow a license for InstallShield or InstallShield Collaboration from the license server for a specified number of days. Using a borrowed license enables you to use the product while being disconnected from the same network as the license server. |
To set up the license server: See Setting Up Your License Server for Concurrent Licenses. To connect a machine that has the product to the license server: See Connecting Machines to Your License Server for InstallShield. To learn how to borrow a license of InstallShield or InstallShield Collaboration: See Borrowing InstallShield or InstallShield Collaboration Licenses from the License Server. |
Following are frequently asked questions and answers about downloads and licensing for InstallShield.
Question | Answer |
---|---|
What is the Product and License Center? |
The Flexera Product and License Center is where you perform InstallShield-related tasks such as the following:
|
How do I create a new user account for myself in the Product and License Center? | If a user account has not been set up for you in the Product and License Center yet, you can create one for yourself, as long as you have your account ID. For more information, see Accessing the Revenera Product and License Center. |
I'm having trouble downloading installations from the Product and License Center. What can I do? |
The Product and License Center offers several methods for downloading products. Examples include:
If you are having trouble using one method to download the product, you may want to try a different method. For example, if the browser FTP method does not work because your organization's firewall blocks FTP, you may want to try the HTTPS method. To change the available download options for all download links and buttons that are displayed for your user account in the Product and License Center:
To change the available download options for a specific download in the Product and License Center:
|
How do I add users, modify users, or remove access for users in the Product and License Center? | See the Account Administrator Tasks section of the Accessing the Revenera Product and License Center instruction page. |
How do I figure out who in my organization generated our license files? |
To look up who generated license files and see details about those license files:
|
What Flexera technology does the Product and License Center use? |
The Product and License Center uses FlexNet Operations, an electronic software delivery service that gives software producers and high-tech manufacturers the power to cost-effectively distribute their products to customers worldwide.
For more information on FlexNet Operations, see the Flexera Web site: |
Question | Answer | ||||||||
---|---|---|---|---|---|---|---|---|---|
How is a node-locked license of InstallShield or InstallShield Collaboration different than a node-locked license of the Standalone Build? |
The following table highlights the main differences.
|
||||||||
What's the best way to download my license file for the Standalone Build? | When you click the Save All button on the View Licenses page in the Product and License Center, your browser typically displays a dialog box that lets you save the license file. The options on the dialog box, as well as the behavior of this dialog box, may vary, depending on the browser and browser version that you are using. For example, Internet Explorer lets you specify the location where you want to save the file. Firefox may save the file automatically to the default download location, or enable you to open the file in an application that you select. For help on downloading files and saving them on your computer, consult the documentation of the browser that you are using. | ||||||||
Can I run the Standalone Build installation on my development machine silently (without the user interface) for a concurrent license? |
Yes, you can run the Standalone Build silently from the command line if you purchased concurrent licenses. Use the following command-line statement:
In the above statement, the value of 2 for the LICENSETYPE property indicates that you are using a concurrent license of the Standalone Build. MyServer represents the name of the machine that has the FlexNet Licensing Server software; 1234 represents the custom port number (if one is used). In most cases, the PORTNUMBER=1234 part should be omitted from the command-line statement. |
||||||||
If I'm using a node-locked license, can I install the Standalone Build without setting up the licensing information at the time of the installation? |
Yes, you can install the Standalone Build without specifying the licensing information during the installation. For example, if your build machine is not connected to the Internet, you may want to install the Standalone Build on your build machine; you would need to obtain the license file for your build machine on a different Internet-connected machine. Once you have obtained the license file, you can manually add it to the proper location on your build machine. The license file must be called License.lic, and it must be added to the System folder in the Standalone Build Program Files folder: Standalone Build Program Files Folder\System\License.lic |
||||||||
Can I run the Standalone Build installation on my development machine silently (without the user interface) for a node-locked license? |
Yes, you can run the Standalone Build silently from the command line if you purchased a node-locked license. Use the following command-line statement: In the above statement, the value of 1 for the LICENSETYPE property indicates that you are using a node-locked license of the Standalone Build. The value of the IS_BROWSE_FILEBROWSED property should be the path to the license file that you want to use for the Standalone Build. |
||||||||
What do I do if I obtain a new build machine? Can I move the Standalone Build and my license file to that machine? |
If you obtain a replacement build machine, you can move your license from your old build machine to your new build machine. In order to move your license to your new build machine, you must first return your license to your account in the Product and License Center. Returning the license makes it available again so that you can obtain a new license file for a different machine. Note that there is a limit to the number of times that you can return a license: you can return a license only one time per entitlement per year. An entitlement is the purchase of the Standalone Build (or of a product, such as InstallShield Premier Edition, that includes the Standalone Build). To return a license in the Product and License Center:
The Product and License Center processes your return request and refreshes the License Information page so that the license you returned is no longer displayed. Now you can generate a new license for the new build machine. You can also install the Standalone Build and the new license file on your new machine. |
||||||||
I generated the license file for the Standalone Build but I entered the wrong host ID. How do I regenerate the correct license file? |
You can follow the same return-the-license procedure that is described in the previous question. NOTE: There is a limit to the number of times that you can return a license: you can return a license only one time per entitlement per year. |
Question | Answer |
---|---|
What are the system requirements for the FlexNet Licensing Server? |
The FlexNet Licensing Server software manages license check-out and check-in requests from users who have concurrent licenses. If you have purchased concurrent licenses of a Flexera product, you need to install the FlexNet Licensing Server software on a machine in your environment. When you are determining which machine to use as the FlexNet Licensing Server, note the following:
|
How do I start the FlexNet Licensing Server service? |
You can start the Windows service for the FlexNet Licensing Server by using Services in the Administrative Tools area of the Control Panel. The default name of the service is: FlexNet Licensing Server Manager (The name of the service is configurable when you are installing the FlexNet Licensing Server.) |
How do I get reports that show usage information for my organization? |
The FlexNet Licensing Server can save a report log file that contains feature usage information. To create a report log file and view reports, you need to purchase Flexera's software license administration solution, FlexNet Manager. FlexNet Manager provides exceptional visibility into license usage data and helps you create insightful reports on critical information like license availability and usage. For more information on FlexNet Manager, see the Flexera Web site: |
I've purchased concurrent licensing for more than one Flexera product. Can I use the same machine to manage concurrent licenses for all of these products? | Yes. You can use the same machine for managing more than one. |
I have a FlexNet Licensing Server machine to manage concurrent licenses of an old version of a Flexera product. That machine uses lmgrd, the command-line tool. Do I need to switch to lmadmin for my new Flexera concurrent licenses? |
Yes, you must switch to lmadmin. To switch from lmgrd to lmadmin, you must first uninstall the earlier version of the FlexNet Licensing Server. Then install the latest version, which has lmadmin. You can obtain the latest version of the FlexNet Licensing Server software from the Product and License Center. For instructions on how to do this, see "Setting Up a Concurrent License Server" on page 13 of the Flexera Product Download and License Guide for InstallShield 2016 and Later (PDF). Note that lmgrd and lmadmin should not be installed on the same machine. |
What do I do if I obtain a new licensing server machine? Can I move the FlexNet Licensing Server software and activate my licenses on that machine? | Yes, you can. For instructions, see "Moving Licenses to a Different License Server" on page 20 of the Flexera Product Download and License Guide for InstallShield 2014 and 2015 (PDF). |
If your organization has purchased concurrent licenses of InstallShield, InstallShield Collaboration, or the Standalone Build, a FlexNet Licensing Server that you set up in your environment manages how many instances of the product can be run simultaneously. Each user who wants to launch one of these products needs to establish a connection with the licensing server to check out and check in licenses when needed.
The version of the FlexNet Licensing Server that is available for InstallShield 2014 and later (and for InstallShield Collaboration or the Standalone Build versions that were released with those versions of InstallShield) requires you to activate the licenses on the licensing server using an activation code, which is available through the Flexera Product and License Center.
When you are determining which machine to use as the FlexNet Licensing Server, note the following:
Item | Description |
---|---|
Machine selection |
The FlexNet Licensing Server machine can be any machine in your network. Typically, the licensing server system components reside on a central machine in the network.
|
Supported operating systems |
The FlexNet Licensing Server machine must be a Windows-based machine. The following versions of Windows are supported: Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016. NOTE: Aalthough the FlexNet Licensing Server has support for other operating systems, concurrent licensing for InstallShield 2014 and later and its ad-ons requires one of the aforementioned specific versions of Windows. |
Networking | The FlexNet Licensing Server machine must be able to communicate with the Flexera product through a TCP/IP port. A valid number is any unused port number between 0 and 64000. The default port range is 27000 through 27009. You may need to adjust your firewall settings to allow this communication. |
Required software |
The license server manager that is installed as part of the FlexNet Licensing Server installation is lmadmin, the Web-based application. lmgrd, the command-line tool, is not supported.
|
The server installation for the FlexNet Licensing Server software is available for download from the Flexera Product and License Center.
To download the installation for the FlexNet Licensing Server software:
NOTE: If you do not have an account in the Flexera Community, see Accessing the Revenera Product and License Center for instructions.
To set up the FlexNet Licensing Server software on the licensing server:
Install and configure the FlexNet Licensing Server software on the licensing server, and obtain the activation code. For instructions, see "Setting Up the FlexNet Licensing Server Software on the Licensing Server, Obtaining an Activation Code, and Activating" on page 14 of the Flexera Product Download and License Guide for InstallShield 2014 and 2015 (PDF).
If your organization has purchased concurrent licenses of InstallShield, InstallShield Collaboration, or the Standalone Build, a FlexNet Licensing Server that you set up in your environment manages how many instances of the product can be run simultaneously. Each user who wants to launch one of these products needs to establish a connection with the licensing server to check out and check in licenses when needed.
Once you or someone in your organization has set up the FlexNet Licensing Server, you need to identify the FlexNet Licensing Server that you are using on the machine where you install InstallShield or InstallShield Collaboration.
To identify the FlexNet Licensing Server for InstallShield or InstallShield Collaboration:
The wizard connects your machine with the license server to verify whether your machine can check out and check in a license for the product.
NOTE: If you want to be able to use your new concurrent license of InstallShield on the same machine that is used to check out a concurrent license of InstallShield 2009
or InstallShield 2008, download the following update and install it on your client machine:
InstallShield 2008 and InstallShield 2009 Concurrent License Update
When you install the Standalone Build, the installation prompts you to identify the FlexNet Licensing Server that will be managing concurrent licenses for the product.
To install the Standalone Build and identify the FlexNet Licensing Server that is managing your organization's concurrent licenses:
The installation installs the Standalone Build on your build machine. The installation also creates a file called Server.ini. This file is installed in the System folder in the Standalone Build Program Files folder:
Standalone Build Program Files Folder\System\server.ini
The Server.ini file should contain the following lines:
[FlexNet Publisher Server] Server=Port@ServerName
In the above example, Port is the port number, if a custom port number is used. In most cases, the port number is omitted. ServerName is the name of the machine that has the FlexNet Licensing Server software.
NOTE: When you are installing the Standalone Build on a build machine, you can do so without specifying the license server name and port number, as long as you later manually add this information in the server.ini file in the aforementioned directory. The Standalone Build does not run without this information (or without its own node-locked license file).
If you need to be disconnected from the same network as the FlexNet Licensing Server, you can (while you are connected to the same network) borrow the license of InstallShield 2014 or later, or the version of InstallShield Collaboration that ships with those versions of InstallShield, for a specified number of days. Once you have borrowed the license, you can use the product while being disconnected from the network.
Once the borrowed license has expired, the product stops working until you are connected to the same network as the license server and a license is available for check-out.
NOTE: The FlexNet Licensing Server software that ships with InstallShield 2014 and later can manage concurrent licenses for earlier versions of InstallShield; however, InstallShield 2013 was the first version of InstallShield that has support for borrowing. Thus, you can borrow licenses for InstallShield 2013 and later versions.
To borrow a license:
To return a license before it has expired: