Production installation

To install a production copy of BigFix, you must first purchase a license from HCL or from an authorized reseller.

During the installation you can choose different types of setup depending on the license input file you have:
   I want to install with a BES license authorization file 
   I want to install with a Production license that I already have 
   I want to install with an existing masthead 
BES license authorization file
After you purchase a license from HCL you receive a BigFix license authorization file. You must use this file the first time you run a production installation. If you have not yet purchased a license, visit the website http://www-01.ibm.com/software/tivoli/solutions/endpoint.

The sales agent will want to know how many clients you intend to install. Based on this, the agent creates, signs, and emails you a License Authorization file, which will have a name like CompanyName.BESLicenseAuthorization.

If you run this installation and do not have access to the Internet, a temporary request (beslicense.request) is generated to request a production license (license.crt) from the BigFix License Server and a license.pvk private key file. You can leave the installation in pending status until you receive the production license.

Copy the request named request.BESLicenseRequest on to a machine with access to Internet, visit the BigFix website, post your request, and download your certificate. After you downloaded the certificate, copy it to the machine on which you are installing the server and continue the installation. If you exited the installation, to install the server you must run the installation using the option that requires an existing Production license file.
Note: The DNS/IP address that you choose becomes a permanent part of your deployment and must never change. For flexibility, it is strongly recommended that you use a DNS name instead of a static IP address.
The installation program collects further information about your deployment and then creates the digital signature key license.pvk and a file called the action site masthead. This file combines configuration information (IP addresses, ports, and so on.) and license information (how many Clients are authorized and for how long) together with a public key that is used to verify the digital signatures.
Production license
Use this option if you have already the production license license.crt and the private key file on the machine on which you are installing the server, but did not complete the server installation.
An existing masthead
Use this type of installation to reinstall the BigFix server or a DSA server. The input file needed to run this installation is the action site masthead file that was generated during the first installation. The action site masthead has the extension .afxm and acts as a configuration file with parameters such as the BigFix server IP address or server name, port number, and locking behavior. It contains information necessary for the digital signature security scheme that BigFix uses (the masthead contains the public key information), and the licensing information that allows BigFix users to run BigFix with a specified number of users for a specified length of time. The BigFix Server installer requires the masthead file be in the server installation folder.

After the production installation a user (default name is IEMAdmin) is created to logon to the BigFix Console and BigFix Web Reports.