![]() ![]() ![]() Then you need a policy on JSS, which will include the DMG which will place the FortiClient installation DMG into /Users/Shared folder, then you need the installation script to run After (second one in my post) and if there is currently FortiClient/FortiNet is installed - you need the removal script (the first one in my post). ![]() Rm -rf /Users/Shared/FortiClient_Installer.dmg # Detach the volume and remove the DMG with installer usr/sbin/installer -verbose -pkg "$pkgToinstallManual" -target / PkgToinstallManual="$mountPoint"/Install.mpkg""Įcho "pkgToinstallManual is: $pkgToinstallManual" MountPoint=$(/usr/bin/hdiutil info | /usr/bin/grep "^$device" | /usr/bin/cut -f 3) # Using the device, determine the mount point Sudo rm -rf /Applications/FortiClient.app Sudo rm -rf /Applications/FortiClientUninstaller.app #delete FortiClient app and uninstaller from Applications to see if then FortiNet 7.x will install with AV component #open /Applications/FortiClientUninstaller.app #run FortiClientUninstaller from the Applications Folder Note: If this is an upgrade policy from previous version, it must have a removal script (run Before) of the current FortiNet client for the re-install policy, what works for me currently is:Ĭd "/Library/Application Support/Fortinet".You need to obtain the FortiClient DMG installer from FEMS server. So at this point I was able to put the cleanest policy to get FortiClient 7.x installed freshly and upgrade 6.x version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |