Package installation fails with Error 1001 on macOSSolved

Participant
Discussion
8 months ago

Hi,

Our company wanted to deploy the ESET Endpoint Security and ESET Endpoint Antivirus packages generated from the ESET portal to all our macOS devices. We tried installing the packages via the Required Apps policy in Hexnode. But the package installation failed with an error code: 1001. We did install Rosetta and retry the app installation, but the error persisted. So far, we have not configured any System Extensions or PPPC policies on the device.

What could be the reason for the installation failure? Kindly provide a solution for the case.

Thanks

Replies (1)

Marked SolutionPending Review
Hexnode Expert
8 months ago
Marked SolutionPending Review

Hey @Timothy, Thanks for posting.

The packages contain a plugin that is causing the installation failure. The ideal workaround would be to install the ESET packages using scripts. Kindly follow the below-mentioned steps:

  1. It is required for you to apply System Extensions and PPPC policies on the macOS device before pushing the installation script. You can also choose to apply VPN and Firewall policies.

    System Extensions:

    (i) Navigate to Policies > New Policy or existing policy > macOS > Configurations > System Extensions, and click on Configure.

    (ii) Under the ‘System Extensions’ section, list the specific system extensions that need to be allowed for Mac.
    Team Identifier: P8DQRXPVLP
    Bundle ID(s): com.eset.endpoint, com.eset.network, com.eset.firewall, com.eset.devices

    PPPC:

    (i) Navigate to Policies > New Policy or existing policy > macOS > Security > Privacy Preferences and click on Configure.

    (ii) Click on +Add new preference and specify the preference for the ‘All Files’ service as ‘Allow’. Then, click on Select Apps.

    (iii) Under ‘Specify Bundle IDs/Path’, add the following information:

    ESET Endpoint Antivirus-

      • Main product identifier EEA
        Identifier: com.eset.eea.6
        Identifier Type: Bundle ID
        Code Requirement:identifier “com.eset.eea.6” and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = P8DQRXPVLP
      • Device identifier
        Identifier: com.eset.devices
        Identifier Type: Bundle ID
        Code Requirement:identifier “com.eset.devices” and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = P8DQRXPVLP
      • Realtime identifier
        Identifier: com.eset.endpoint
        Identifier Type: Bundle ID
        Code Requirement: identifier “com.eset.endpoint” and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = P8DQRXPVLP
  2. ESET Endpoint Security-

      • Main product identifier EES
        Identifier: com.eset.ees.6
        Identifier Type: Bundle ID
        Code Requirement:identifier “com.eset.ees.6” and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = P8DQRXPVLP
      • Device identifier
        Identifier: com.eset.devices
        Identifier Type: Bundle ID
        Code Requirement:identifier “com.eset.devices” and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = P8DQRXPVLP
      • Realtime identifier
        Identifier: com.eset.endpoint
        Identifier Type: Bundle ID
        Code Requirement: identifier “com.eset.endpoint” and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = P8DQRXPVLP 
  3. Deploy the installation script to the Mac using the Execute Custom Script action:

    (i) Navigate to the device details page of the macOS device and select Actions > Execute Custom Script.

    (ii) The script provided requires certain arguments for the installation to work:

    • Argument 1 (Required): Type ‘EES‘ (if you are installing ESET Endpoint Security) or ‘EEA‘ (if you are installing ESET Endpoint Antivirus).
    • Argument 2 (Optional): Specify the license key, username of the security admin and password in the format PID:SecurityAdmin:Password, for example, 123-ABC-456:user=security.admin@email.com:pass=SecurityAdminPass.
    • Argument 3 (Optional): Specify HTTP Proxy in the format: http://10.0.0.100:3128.

    There are two methods to pass the argument to the script:

    a. Directly edit the script by replacing $1, $2, and $3 present (in the 8th, 9th, and 10th lines of the script) with the arguments (in the same order) mentioned above.

    b. Under the Execute Custom Script action, pass the three arguments (in the same order mentioned above) separated by a space inside the Arguments section.

Once the script is deployed, the ESET package(s) gets silently installed in the macOS device. The installation time can be long.

Make sure you follow these precautions before executing the ESET installation script:

  1. Install Rosetta 2 on macOS systems without Intel chips. Run the command sudo softwareupdate –install-rosetta either in Terminal or via the Execute Custom Script action for the installation.
  2. The macOS device should not have any other installation policies assigned for any previous versions of the ESET security solution.

I hope you are satisfied with our solution. Kindly reach out to us for further queries.

Regards,
Julian Refn
Hexnode UEM