# Managing and Installing license via SmartUpdate

## Solution

Check Point provides several methods for installing your licenses. SmartUpdate is the recommended method for managing your licenses.

Note: **For R80.20.M1**, refer to "Using SmartUpdate" section in [R80.20.M1 Installation and Upgrade Guide](https://sc1.checkpoint.com/documents/R80.20_M1/WebAdminGuides/EN/CP_R80.20_M1_Installation_and_Upgrade_Guide/html_frameset.htm)

When you add a license with SmartUpdate, it is stored in the Licenses & Contracts Repository. The SmartUpdate provides a global view of all licenses available and all of the assigned licenses. To activate the license once it is in the Repository, it has to be attached to a Security Gateway and registered with the Management Server.

1. Log into SmartUpdate and go to the "Licenses & Contracts" tab

2. Select 'Add License'. You can choose to import the license file or to manually enter the licensing details

- From File - Import the license file generated through the User Center.

- Enter Manually - Copy the 'cplic put' command found in the License email body and click the 'Paste' button. The license fields will be automatically populated.

The **Security Management** Licenses will automatically attach to the Management Server. No additional steps are required.

For the **Security Gateways,** as opposed to the Security Management, there are two options to generate the license: Local and Central.

If importing a Local license, the license will automatically attach itself to the object with the same IP address.

If importing a Central license, the Gateway license will be placed in the SmartUpdate License Repository.

3. Right-click on the Security Gateway object you wish to install the license on

4. Select "Attach License"

5. Choose the Gateway license you have imported

6. Click 'Attach'

**Note:** some Security Gateway Blades generate an additional license which must be installed on the Security Management Server. These licenses are most easily identified by the '-M' in the feature string (e.g., _CPSB-ADNC-M_).

#### NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.