Posted on 03-11-2021 05:33 AM
Hello,
I have seen that the FortiClient is causing difficulties for some users. However, I have just been able to create a relatively simple solution with which the config files can also be made to work by default.
My requirements:
macOS 11.2.3 (intel) / Jamf Pro / DEPNotify 1.1.6
That´s all. I had success with this. FortiClient is running perfect with custom settings. No restart needed.
Posted on 03-11-2021 06:10 AM
Repackaging the dmg from EMS to run the install.mpkg with the fct_data does the same. How are you handling the configuration profiles for PPPC/System Extension and possibly WebFilter?
Posted on 12-02-2021 07:28 PM
How did you repackage? Just in Composer like this?
Mine doesn't seem to work.
Posted on 12-02-2021 07:29 PM
This is what I created, however doesn't want to install.
Posted on 12-03-2021 03:48 AM
Does your post install script call the installer? I just drop the non-flat package and other files from their DMG into a directory inside of tmp and just call it with a post install script similar to the below:
installer -pkg /private/tmp/FortiClient/Install.mpkg -target /
Posted on 03-11-2021 07:51 AM
I send a new plist to the computer after the client is installed. 1-2-3 all done. Or is it 1-2....
Posted on 04-21-2021 10:47 AM
I gave this a go before seeing the thread but just wanted to confirm this method does work for deploying with a profile for any of those needing to get this done.
Posted on 04-21-2021 11:40 PM
@andrew.nicholas Sorry for the late reply: I created the config profile using PPPC Utility. We do not currently use the web filter.
Posted on 12-02-2021 07:35 PM
Is it okay to roll out the same "/Library/Application Support/Fortinet/" folder to all machines though? I actually was testing this myself and Fortinet support said;
"Dear Customer,
The installation to copy folder to another machine is actually not supported officially. This may cause duplicate UID issue triggering duplicate entries on EMS.
Also, the FortiClient license is received once it connects to EMS when retrieving the endpoint profile configs."
Have you had any issues with duplicate entries etc?
Posted on 12-03-2021 12:29 AM
Hi Gabriel,
within our network team I haven't heard anything about having duplicate EMS entries....
Posted on 02-11-2022 03:25 PM
Hello,
Do you have a step by step for your process. Ive run into some roadblocks with composer. I'm not clear on this. Seriously thank you..
Posted on 02-11-2022 03:26 PM
Hello,
Do you have a step by step for your process. Ive run into some roadblocks with composer. I'm not clear on this. Seriously thank you..
Posted on 03-07-2022 11:39 PM
Ditto here as @aramirez_tch said looks like some of this might not be working the same in newer Jamf instances or V7.X.X of FortiClient. Still going to give all this another go here in 12.2.X
Posted on 03-08-2022 05:44 AM
the new way we currently go: the whole DMG file, which also holds the preferences, I package as a PKG, put it in private/var/tmp and then there is a command that starts the installation: in the payload files and processes the following command:
installer -allowUntrusted -pkg /private/var/tmp/FortiClient/Install.mpkg -target /Applications/
This has worked very well so far.
Posted on 08-12-2022 03:49 PM
Thank you! You saved me much pain.
Posted on 08-26-2022 02:46 PM
Hi, mickl089
Could you elaborate a bit how you package this?
I followed your steps by steps instruction to deploy FortiClient, however the FortiClient deployed without VPN option.
Where did you create "private/var/tmp" directory? from a snapshot or just simply made some folders?
Any details will be helpful, thank you.
09-19-2022 09:56 AM - edited 09-19-2022 10:11 AM
Create a new directory wherever you want it to reside using composer. Take the .dmg installer and convert it into a source and rebuild it as a package.
In mickl089's example, 'private/var/tmp/FortiClient' and dump the contents of the .dmg in that directory.
Have your post-install script invoke the install. Just make sure you have it in the same directory.
installer -allowUntrusted -pkg /private/var/tmp/FortiClient/Install.mpkg -target /Applications/
Posted on 02-14-2024 09:11 PM
This screenshot helped me a lot! I was able to install the file and then run "installer -pkg /private/tmp/FortiClient_7.2.0/Install.mpkg -target /" afterward
Posted on 03-08-2022 04:23 PM
For users that aren't admins, some are seeing this is in our test deployment. Is anyone familiar with this, and any way to configure it to not prompt users?
Posted on 03-10-2022 12:42 AM
I agree with the question, I also have this with almost every FortiClient installation.
Posted on 03-16-2022 10:15 PM
We will jump on a call with them and hopefully get this working, but they do not have a lot of experience with macOS, so we've been told our best effort on support.
03-17-2022 07:26 AM - edited 03-17-2022 07:29 AM
My understanding is that Apple’s OS is designed with user engagement as part of the system security. Maybe you’ll need a script to temporarily elevate account permissions so that the user can provide an account and password for the installation? There are a couple of tools already scripted out there; I think Jamf even has a rights elevation script.
We have run into this with another process we’re running and that’s the only way around it.
Posted on 03-21-2022 08:17 PM
My team and I have been testing the script to demote all of our users to standard as part of our path to FedRamp and some customer requirements. So I'll see if I can't script this to include elevating the user rights simultaneously and temporarily while installing this. But it is incredibly disappointing to hear about FortiClient and another item in the Con column for this software when it comes to using it with macOS for us. Sadly our team wasn't involved in the PoC on this. We recently got handed this to be done ASAP on 2,000+ macOS devices.
Posted on 05-30-2022 11:56 AM
anything for this ?
Posted on 06-02-2022 10:15 AM
For which part?
Posted on 06-03-2022 08:03 AM
get rid of Full Disk Access & allow Forti Tray - all the messages when we do the install through jamf
07-21-2022 06:16 PM - edited 07-21-2022 06:21 PM
Just a quick update and info share for our free implementation of FortiClient 7.0.3. Thanks to Mickl for providing the bulk of this process!
#!/bin/bash
#Stops all running FortiClient processes
killall FortiClientAgent
killall FortiClient
#Initiates silent uninstall of current Forticlient
/Applications/FortiClientUninstaller.app/Contents/Library/LaunchServices/com.fortinet.forticlient.uninstall_helper
#Run FortiClient 7.0.3 Installer
installer -verboseR -pkg "/private/tmp/FortiClient_7.0.3_Source_Files/FortiClient 7.0.3.mpkg" -target /
#Copy vpn.plist from tmp to FortiClient config folder
cp /private/tmp/FortiClient_7.0.3_Source_Files/vpn.plist "/Library/Application Support/Fortinet/FortiClient/conf/"
Posted on 12-09-2022 09:48 AM
Where might a fella find the mpkg? When I get the installer from the internet, it is an online installer.
3 weeks ago
Hi :)
sadly we are having problems with the deployment of Forti...unfortunately for me is a unknown world so i think i'm making more mistakes that i want, because i cannot follow everything you wrte :( sorry!
we get the failed Policy with the error:
Installation failed. The installer reported: installer: Package name is FortiClient
installer: Upgrading at base path / installer: The upgrade failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “FortiClientVPNSetup_7.4.0.1645.pkg”.)
my questions:
1. what do you mean by:
#Copy vpn.plist from tmp to FortiClient config folder cp /private/tmp/FortiClient_7.0.3_Source_Files/vpn.plist "/Library/Application Support/Fortinet/FortiClient/conf/"
thanks a lot to everyone that can help me :)
3 weeks ago
it works! thanks a lot @Baravis now just trying to deploy the VPN Config
Posted on 09-19-2023 06:54 AM
Hi.
how to charge the configure and parameters? I need help