• Download the EEDK tool from https://community.mcafee.com/t5/Community-Tool-Exchange/EEDK-9-6-1-Download-Links/m-p/566112​. For information about the EEDK tool and all its options, see the EEDK documents that are available with the tool package.
• See the "Understand the Linux installation workflow" section of the Change Control and Application Control 6.1.0 Installation Guide - Standalone mode (PD24677).

 Steps:

1. Identify all kernels where kmod rpm distribution is needed using the EEDK script.
2. Execute builds on the designated testbeds for each of these kernels. The kmod rpm package is then created and available in the <installation_directory>/dks folder of the testbed.
3. Place the following files on a Microsoft Windows system:
   • EEDK script (shipped with this release)
   • solidifier-kmod-<MAC_MCC_ver>.<distribution>.<kver>.<arch>.rpm 
     NOTE: This file is the kmod rpm package built for target kernel version <kver>. This package is found in the <installation_directory>/dks folder of the testbeds needed for each kernel.
      
4. Click EEDK.exe and run the EEDK tool. Edit the following fields:
   • Command to Run – Enter the value as ./<eedk_script> [MAC/MCC version].
     NOTES:
     • The <eedk_script> is the name of the EEDK script shipped with this release.
     • The Application Control/Change Control version argument is optional and must be specified in the form <Major>.<Minor>.<Patch>-<Build> (Example: 6.1.0-9500). If you provide the version information, the script copies the kmod packages only for the specific MAC/MCC version to the /opt/solidcore directory. If the script does not find the rpm file for the specified version in the package, it considers that no version information is provided.
     • Specify the version information. If you do not, the script copies the kmod packages of any MACC version available to the /opt/solidcore directory.
        
   • Product Name – Specify a name to distinguish the package from the previously created packages. For example, specify the Product Name as MACCEEDK.
   • Product ID – Specify an ID to distinguish the package from the previously created packages. For example, specify the Product ID as 5000.
   • Product Version – Specify a version to distinguish the package from the previously created packages.
   • Source path – Specify the path to files that you placed on the system in step 3.
   • (Optional) Product Description – Provide a description. The text in this field is the product name listed in the Master Repository of ePO. Use this field to distinguish the EEDK package from other packages in the Master Repository.
   • Product Detection Key – Do not change the default value.
   • Product Detection Key Value – Do not change the default value.
   • OS Support – Select the Linux option.
   • Advanced Options – Do not modify because this option is not used for this package.
      
5. Navigate to Tools, Options to specify the build folder where you want the created package to be stored. 
   NOTE: This folder is also used to store the temporary files that are created during the package creation.
    
6. Click Save to save the build folder and return to the main screen of the tool.
7. Click Build Package to build the package using the EEDK tool.
8. Check in the created package in the ePO Master Repository.
9. Verify that the name entered in the Product Description field is listed in the Master Repository after you have checked in.
10. Create a product deployment task for this EEDK package using ePO, and push it to the target endpoints.
    NOTES:
    • Pushing the product deployment task creates the /opt/solidcore directory on the endpoints and copies the respective kmod rpm packages to it.
    • This step must be performed before you deploy the Solidcore client on endpoints or boot endpoints in the new kernels that are not pre-compiled.
       
11. Perform one of the following steps:
    • Solidcore client installation or upgrade – Push the product deployment task for the Solidcore client from ePO to the target endpoints.
    • For Kernel upgrade (Solidcore client is already installed on endpoints) – Restart the endpoints in the new kernel.