Unable to Build Activation File

Symptoms

Activating the Core Server results in the error:  "Unable to Build Core Server Activation File."

Causes

1. The Core Servers Device ID does not exist in the following registry location. HKLM\Software\LANDesk\Common Api
   NOTE: on Windows 2008 R2 server the relevant keys are under theHKLM\Software\Wow6432Node\LANDesk and the files are under the directory C:\Program Files (x86)\LANDesk\Shared Files

2. The .crt file referenced in the registry of the Core Server does not match the .crt in the Program Files\LANDesk\Shared Files\Keys folder.

3. Through the GPO the group policy "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" has been enabled.

Resolution

1. The Core Servers Device ID does not exist in the following registry location. HKLM\Software\LANDesk\Common Api The device id should be created on install or during an inventory scan of the Core Server.
   If it is not copy this key from HLKM\Software\Intel\LANDesk\Common Api

1. Browse to the HLKM\Software\Intel\LANDesk\Common Api\UniqueID key.

2. Export the key.

3. Edit it to reflect the new path: HLKM\Software\LANDesk\Common Api

4. Import the modified key.

5. Retry to activate the core server

2. The name of the certificate created on install is referenced in the following registry key:HKLM\Software\LANDesk\ManagementSuite\Setup\CertName This file needs to exist in the C:\Program Files\LANDesk\Shared Files\Keys.

• For the activation process to work properly the original .crt and .key file have to be present in the C:\Program Files\LANDesk\Shared Files\Keys folder.

• If the server has been reinstalled it needs to be the Cert Created during the most recent install.

• It is possible that after the install the user may have deleted or renamed these files. If this is the case the files will need to be renamed back to the original name. If the original .crt, and .key files were deleted the core will need to be rebuilt.

Open the Core Server Activation Utility.  Click the Licenses button.  Check for anything that says something like "Upgrade-Sub". If its expired, or there, call the LANDesk Licensing queue to have the licensing team deauthorize the core server.
After its done, try to reactivate the core.

3. Disable the  group policy "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" and reboot the core server before to retry the activation process.

    More details about this particular issue are availalbe here: http://community.landesk.com/support/docs/DOC-6382