The Coexistence Utility

The coexistence utility (eACoexist) that  supplies, lets you resolve potential conflicts with other programs on the local computer.
capamsc141
The coexistence utility (eACoexist) that 
PAM Server Control
supplies, lets you resolve potential conflicts with other programs on the local computer.
When the coexistence utility runs, it performs the following actions:
  1. Checks that
    one
    of the following conditions apply:
    1. PAM Server Control
       is not running.
    2. You have the ADMIN attribute.
    If neither conditions apply, the utility exits.
  2. Locates the response.ini file, as follows:
    • When the utility runs during installation, it uses the path
      media_drive
      :\Coexistence\_
      architecture
    • If
      PAM Server Control
      is installed on the computer, it uses the following registry key value:
      HKLM\SOFTWARE\ComputerAssociates\AccessControl\AccessControl\SeOSD\ResponseFile
    If the file does not exist the utility exits.
  3. Locates the coexistence plug-ins directory, as follows:
    • If you run the utility and pass a parameter from the command line, it uses this parameter as the path of the plug-in.
    • When the utility runs during installation, it uses the path
      media_drive
      :\Coexistence\_
      architecture
    • If you run the utility with no parameters, it concatenates the string "\Coexistence" to the following registry key value:
      HKLM\SOFTWARE\ComputerAssociates\AccessControl\AccessControl\SeOSPath
    If the directory does not exist, or there are no coexistence plug-ins in the directory, the utility exits.
  4. Executes the discovery process.
    To do this, it enumerates the executables in the coexistence plug-ins directory and executes them one by one, as follows:
    1. Stores the result of the plug-in execution in %windir%\EACDiscovery.ini
      The utility automatically deletes this file on successful completion of the plug-in discovery process.
    2. Checks that the output file EACDiscovery.ini exists.
      If the file does not exist, the utility continues to execute the next plug-in.
    3. For each product section in EACDiscovery.ini, concatenates the section (product) name and version value and checks whether the response file contains the matching section.
      The response.ini file contains a section for each coexisting program. If a section name appears with a version number, for example, eTrust Audit-1.5, the utility performs the action only for the specified version.
    4. If a matching section exists in the response file, executes the action that is set by the value of the Act-Utility-0 in that section, as follows:
      • Issues a warning that the discovered product is not compatible with
        PAM Server Control
        .
      • Stops the discovered services of the product.
        The utility retrieves the discovered services of the product from the EACDiscovery.ini file.
      • Same as bullet 2, but during
        PAM Server Control
        installation.
      • Starts the services if the discovered product.
        The utility retrieves the services of the discovered product from the EACDiscovery.ini file.
      • Creates trusted program rules (SPECIALPGM) for the processes of the discovered product and starts
        PAM Server Control
        .
        The utility retrieves the processes of the discovered product from the EACDiscovery.ini file. It also retrieves the respective program type (pgmtype) from this file. It then creates a temporary script file (
        ACInstallDir
        \Data\discoveryscp) that it executes when 
        PAM Server Control
        starts.
      • Same as bullet 2, but during 
        PAM Server Control
        uninstall.
      Each section can contain more than one action. For example, you can have Act-Utility-0, Act-Utility-1, and Act-Utility-2 that are executed in that order.