sepiemoini

Thanks, @SysEPr! The post took a while to show up but I was able to verify all of this yesterday morning. All is well here and I even ran the silent install feature too. Here's how I was able to achieve that: mkdir "/Library/Application Support/ESET/" mkdir "/Library/Application Support/ESET/esets/" mkdir "/Library/Application Support/ESET/esets/cache/" touch "/Library/Application Support/ESET/esets/cache/do_not_launch_esets_gui_after_installation" This script ran just before the installer via an MDM policy. I then ran a post-install script to activate the product using the script below. sudo /Applications/ESET\ Endpoint\ Security.app/Contents/MacOS/esets_daemon --wait-respond --activate key=<KEY> The directions for the above command found here didn't include the full path so I had to investigate a bit and looked inside the wrapped PKG file (there was a post-install script showing the full path) inside the provided DMG.

Greetings, all! @TomasP @brandobot I too am testing this in Jamf for a client and was wondering if you could share your configuration profile details. More specifically, here's what I was also able to confirm: codesign --verify --verbose /Applications/ESET\ Endpoint\ Security.app /Applications/ESET Endpoint Security.app: valid on disk /Applications/ESET Endpoint Security.app: satisfies its Designated Requirement vm-admins-MacBook-Pro:~ vm-admin$ codesign --display --verbose /Applications/ESET\ Endpoint\ Security.app Executable=/Applications/ESET Endpoint Security.app/Contents/MacOS/esets_gui Identifier=com.eset.ees.6 Format=app bundle with Mach-O thin (x86_64) CodeDirectory v=20200 size=39438 flags=0x0(none) hashes=1227+3 location=embedded Signature size=9053 Timestamp=Jan 29, 2019 at 1:05:07 PM Info.plist entries=29 TeamIdentifier=P8DQRXPVLP Sealed Resources version=2 rules=13 files=424 Internal requirements count=1 size=176 Based on the above details, I would like clarification on what should be entered in the Code Requirement field within the Jamf Pro PPPC payload that has since become available natively in the web console. Keep in mind that the above details are consistent with what others have previously posted. Can you please verify these details? I have provided a screen capture below for reference. I have a hunch it's this: 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