Skip to main content
petrklinkovsky
petrklinkovsky
New Member
November 10, 2025
Question

Import of xml config on MacOS replaces all manually created VPN profiles

  • November 10, 2025
  • 1 reply
  • 959 views

Hi all,

 

we use FortiClientVPN free 7.4.3 on MacOS Sequoia 15.7.1. When we did import of FCT xlm configuration then all manually created VPN profiles had been removed. When we did import of same xml config to windows FCT 7.4.3 then all manually created profiles are kept and new config from xml is added. Does anybody have same behavior on Mac? Can it be fixed in some way?

 

Another question is about managing this imported xml configuration - we don't have option in FCT to remove this Company VPN profiles - there are only options about view configuration but we are not able to remove this profile. Is it by design or can we customize it?

 

Thank you.

 

Best regards
Petr

1 reply

funkylicious
SuperUser
funkylicious
SuperUser
November 10, 2025

hi,

is by any chance this FortiClient installed on Mac managed/connected to an EMS server ?

if so, this would explain the Company/Corporate VPN Profile being read only.

"jack of all trades, master of none"
    petrklinkovsky
    petrklinkovskyAuthor
    New Member
    November 10, 2025

    Hi,

    this xml profile is created on EMS server but unfortunatelly some of Mac clients will not be managed by EMS - they are some contributor so they don't have licence for full FCT.  They have to use only free FCT.

    BR

    Petr

    funkylicious
    SuperUser
    funkylicious
    SuperUser
    November 10, 2025

    i would suggest then, creating a xml profile from a computer using the VPN Only version of FortiClient which you should export and import on all endpoints which will not be EMS managed and use the one exported for connected ones ( although if you connect them to EMS the profiles will be automatically pushed to the workstation ).

     

    https://community.fortinet.com/t5/Support-Forum/Exporting-importing-a-single-VPN-connection/m-p/211539#:~:text=0%20to%201%20to%20designate%20it%20as%20a%20partial%20config%20(so%20it%20will%20merge%20instead%20of%20replace 

     

    L.E.

    https://community.fortinet.com/t5/Support-Forum/Importing-IPSec-tunnel-configuration-to-FortiClient-via-XML/m-p/417346 

    "jack of all trades, master of none"
    Terms & ConditionsAccessibility statement