1. Log on to the ePO console.
2. Go to Menu, Configuration, Solidcore Rules.
3. On the Certificates tab, select Actions, Upload to open the Upload Certificate page.
4. Browse to and select the certificate file to import, and then click Upload.

Application Control 6.2.x

1. Log on to the ePO console.
2. Go to Menu, Configuration, Solidcore Rules.
3. On the Publishers tab, select Actions, Upload to open the Upload Certificate page.
4. Browse and select the certificate file to import, and then click Upload.

1. Log on to the ePO console.
2. Navigate to the Solidcore policy.
3. Select the Updater Processes tab and click Add.
4. Specify whether to add the updater based on the file name or SHA-1.
   
   NOTE: If you add the updater by name, the updater is not authorized automatically. When you add the updater by SHA-1, the updater is authorized.
    
5. Enter the location of the file (when adding by name) or SHA-1 value of the executable or binary file.
6. Enter a unique identification label for the executable file.
   
   Example: If you specify WebMER Changes as the identification label for the Mer.exe file, all change events made by Mer.exe are tagged with this label.
    
7. When adding an updater by name, specify conditions that the binary file must meet to run as an updater.
   1. To allow the binary file to run as an updater without any conditions, select None.
   2. To allow the binary file to run as an updater only when it has loaded the specified library, select Library.
      
      Example: When configuring Mer.exe as an updater to allow the gathering of diagnostic data, specify wuweb.dll as the library. This action ensures that the iexplore.exe program has updater permission only until the web control library (wuweb.dll) is loaded.
   3. To allow the binary file to run as an updater only if the specified parent starts it, select Parent.
      
      Example: When configuring Mer.exe as an updater to allow diagnostic data gathering, specify WebMERClient.exe as the parent. Using the parent makes sure that only the correct program is allowed to run as an updater.
   4. When adding an updater by name, indicate whether to disable inheritance for the updater.
      
      Example: If Process A (that is set as an updater) starts Process B, disabling inheritance for Process A makes sure that Process B does not become an updater.
       
8. When adding an updater by name, indicate whether to suppress events generated for the actions performed by the updater. Typically, when an updater changes a protected file, a File Modified event is generated for the file. If you select this option, no events are generated for changes made by the updater.
9. Click OK.