"please make sure that the customer correctly removed the system extension and rebooted the mac.
Hi for the long wait before my reply, but our peeps in charged to manage the FireEye appliance had to upgrade it to a newer version, therefore that's why I had to put on hold the testing.Anyways, I just received the v.34.28.1 to test with, but I need to make sure now that I'm following the correct path.Ĭould you please tell me how are you doing with upgrading from a lower version to v.34.28.1? Previously, we have been using a script to remove ALL the necessary files/folders/entries before you install the new version.From FireEye tech, I've got this instruction: An error occurred while running scripts from the package “xagtSetup_33.51.1.pkg”.)Įrror running script: return code was 1."Īgain, I've already created the required Config Profiles as per the FireEye guide, still No Bueno! Contact the software manufacturer for assistance. (The Installer encountered an error that caused the installation to fail. Script result: installer: Package name is FireEye Agent Running script FireeyePostinstall v.33.51.1. Successfully installed FireEyewPostinstall v.33.51.1 PROD.pkg. " Installing FireEyewPostinstall v.33.51.1 PROD.pkg. Hi been trying to get this upgrade to v.33.51.1 for more than a month and it's still failing for us.Engaged some FireEye tech for this issue and he sent the same guide that you provided the screenshots from, but it doesn't seem to go through the installation, failing somewhere while running the xagtSetup (see below):
Prior versions of the Fireeye Client for Mac OS packaged and performed silent installs without issue and we're hoping someone here has seen and figured a work around. They plan on adding support in future releases. When reaching out to Fireeye support they initially offered assistance after a few emails gave a blanket " Silent uninstallation with MDM solutions is not currently supported on macOS 11. We’ve been pretty liberal with the PPPCs and have had the prior kext which doesn’t appear to be used in Big Sur both included and not. Even added to system extensions, approved kernel extensions to see what would happen: Intervention was still required.
We've testing out the initial app install and get an install prompt that requires manual intervention.
It's the same dialog on a standard install. Installing via Jamf Pro Cloud pkg is causing a dialog for the user to consent to the system extension.
Last week our cyber security team provided us the newest Fireeye client for Mac OS 11.