For some reason I had to run curl with sudo or I'd get a permissions error. Just pinging back to say that solution to this helped move me forward with delivery and installation from Jamf school for Forticlient 6.4.2.
I reached out to their support but have not heard back yet anyone have any input that could possibly assist me on this. I deploy the configuration with no success and failure each time: In the payload (UUID: BC074ED4-9CFA-47DE-BE63-10B973280A90), the key 'Authorization' has an invalid value. And immediately following the uninstall I am hit with "Please Approve enSilo Kernel Extension in System Preferences and then Security Panel.įrom this information I gathered I was able to locate "enSiloCollector" and attempted to create a Configuration Profile using the PPPC Utility.app (I have not been having much success with this app since Big Sur) Since I am on Big Sur I toggled the compatibility toggle and proceeded to add the required Privacy Settingsįrom the information gathered here I now know the following: So back to the drawing board when I run the uninstaller I notice that "enSiloCollector" wants access control to my system preferences and finder. Warnings: Please approve Fortinet Endpoint Protection and Response Platform Kernel extension in the device. When returning to the Admin console the machines state is "Degraded" with the following information. At first glance it was refreshing seeing nothing pop up at me requesting permission for anything and it looked that it had installed as I saw the icon on my menu bar. To my local downloads folder and then uploaded it to JAMF Pro for the install. pkg enSiloInstallerOSX_3.1.0.201_FortiEDR_Connect_3.pkg In my case the enSiloClient I am having issues with. I don't know how to get the configurations for autoreg host, etc. conf files need to be deployed another way. You can pull the pkg from this by mounting the dmg then just dragging or copying our the pkg. If you have Forticlient EMS, your EMS deployments should include a dmg when you build them. I'm hoping that a supported utility like Composer will allow us to break through some challenges with apps like Forticlient. For single *.app deployments, Packages has worked well but for anything with like an mpkg linking to other stuff or data deployed to nested folders, plug ins, etc. I sent a request for access to it and am waiting so I can try working with this instead of Packages. I've been working with Packages as we use School, but now the KB is updated to suggest Composer, which seems referenced far more (from Pro users) here in the forums. I am working through this as well for 6.4.2.
0 kommentar(er)
