Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Not applicable

HOWTO: Custom Unattended FortiClient Install

#################### PLEASE NOTE - The instructions below were developed for FortiClient 1.2 MR2. As of FortiClient 1.2 MR3, the FortiClient Release Notes contain the best information for creating a custom unattended installation. Please use that as your guide. You can find the release notes at http://kc.forticare.com/. The information below is obsolete. #################### The following series of post will show you how you can put together a custom unattended setup of the FortiClient VPN software. Goals:[ul]
  • Unattended Install
  • Deselection of unnecessary components (the Firewall and Anti-Virus components in this case)
  • Include FortiClient license key
  • Include VPN tunnel information[/ul] For this task you will need the following:[ul]
  • FortiClientSetup_1.2.172.zip or the latest FortiClient from the support website.
  • MaSaI Editor from http://www.masaieditor.com (thanks UKWizard )[/ul] * Note: If all you want is an unattended installation with the Firewall and Anti-Virus components deselected, you can download a pre-edited 1033.mst file attached to this post. ** Note: These instructions were developed using FortiClient 1.2 build 172 and MaSaI Editor 1.8.1654.0. The instructions may not work if any other versions are used. Ok, let' s get started! When unzipping the client, you may have noticed that it contains 3 files.
     12/15/2004  03:35 PM             3,584 1033.mst
     12/15/2004  03:35 PM            34,304 2052.mst
     12/15/2004  03:35 PM        12,220,928 FortiClient.msi
                    3 File(s)     12,258,816 bytes
    Briefly, the FortiClient.msi file is the main installation file. The other two .mst files are language oriented transform files. Region code 1033 is English. Region code 2052 is Simplified Chinese. For purposes of this HowTo, we will only be using the 1033.mst file. The file 2052.mst can be deleted or ignored. After you have downloaded and installed the MaSaI Editor, you may notice that it starts in " Trial" mode. The editor gives you full functionality for 20 days before it turns into the " Free" edition. The downside of this period of full functionality is that it adds a pop-up window during the install of each saved project stating that the project was edited and saved using the trial MaSaI Editor. The Free version gives very limited functionality, but does not add the annoying prompt into your projects. Since we only need the limited functionality provided by the Free version for this project (and we do not want the annoying pop-up window displayed to our easily confused users), we will abort the trial period and convert the Editor into the Free version. STEP 1 - Aborting the MaSaI Editor Trial Period Open the MaSaI Editor. On the title bar, it will state " MaSaI Editor Trial" . Go to Help then Enter Update Serial Number..., and enter anything you wish. After clicking Ok, the program will report that the serial number is invalid. Simply click Ok to dismiss the error message and you should notice that the window title bar has changed to just " MaSaI Editor" . You are now working in the limited Free mode. If this doesn' t work for you, try closing the editor and re-opening it again.
  • 20 REPLIES 20
    Not applicable

    Can you forward the command line syntax for starting VPN automatically to me?
    UkWizard
    New Contributor

    IPsec or PPTP ?
    UK Based Technical Consultant FCSE v2.5 FCSE v2.8 FCNSP v3 Specialising in Systems, Apps, SAN Storage and Networks, with over 25 Yrs IT experience.
    UK Based Technical Consultant FCSE v2.5 FCSE v2.8 FCNSP v3 Specialising in Systems, Apps, SAN Storage and Networks, with over 25 Yrs IT experience.
    Not applicable

    IPSEC
    UkWizard
    New Contributor

    Here you go, enjoy. Start and keep window open ipsec -k your_tunnel_name Start and run in background start /B ipsec -k your_tunnel_name stop the tunnel when running in background ipsec quit
    UK Based Technical Consultant FCSE v2.5 FCSE v2.8 FCNSP v3 Specialising in Systems, Apps, SAN Storage and Networks, with over 25 Yrs IT experience.
    UK Based Technical Consultant FCSE v2.5 FCSE v2.8 FCNSP v3 Specialising in Systems, Apps, SAN Storage and Networks, with over 25 Yrs IT experience.
    Not applicable

    Thanks. I knew about the ipsec command but could not figure out how to keep the command window hidden. Now I know.
    UkWizard
    New Contributor

    bad timing really, as they have just released a newer client which explains how to do unattended installs now anyway. including importing policys
    UK Based Technical Consultant FCSE v2.5 FCSE v2.8 FCNSP v3 Specialising in Systems, Apps, SAN Storage and Networks, with over 25 Yrs IT experience.
    UK Based Technical Consultant FCSE v2.5 FCSE v2.8 FCNSP v3 Specialising in Systems, Apps, SAN Storage and Networks, with over 25 Yrs IT experience.
    Not applicable

    Yeah, I noticed.. But our approach still applys, what we what to accomplish is a simple installation where users are able to personalize the VPN settings using there username pre-shared key and virtual IP We modify the MSI according to the release notes of MR3, and wrap the whole thing up using inno installer This to install the personalize app and adding shortcuts and documentation to the users desktop. This future is kept out of the MSI pack, making it easy to replace Forticlinet whit a never version at least as long as Fortinet does not decide to change the structure of the VPL file The INNO scrip is realy only 10 lines [Run] Filename: {app}\UserConfig.exe Filename: msiexec.exe; Parameters: " /i {app}\FortiClient.msi TRANSFORMS=custom_12204.mst ISX_LICENSE=1234567890abc /qn REBOOT=" " ReallySuppress" " " [Files] Source: ..\..\..\Elektromekan\Elektromekan_ETS.rdp; DestDir: {commondesktop} Source: ..\..\..\Elektromekan\Elektromekan VPN Explained.txt; DestDir: {commondesktop}; Flags: isreadme Source: ..\..\..\Elektromekan\userdata.reg; DestDir: {app} Source: ..\..\..\Elektromekan\UserConfig.exe; DestDir: {app} Source: ..\..\..Elektromekan\VPN_genvägar.URL; DestDir: {commondesktop} Source: ..\..\..\Elektromekan\e-vpn.msi; DestDir: {app} [Icons] Name: {commondesktop}\UserConfig.lnk; Filename: {app}\UserConfig.exe; WorkingDir: {app}; IconFilename: {app}\UserConfig.exe; IconIndex: 0 Name: {commonstartmenu}\UserConfig.lnk; Filename: {app}\UserConfig.exe; WorkingDir: {app}; IconFilename: {app}\UserConfig.exe; IconIndex: 0
    Not applicable

    Jbult, It is great you placed the " how to" in the forum. But the way Fortinet use this way to install Forti Client for a roll out you still need more knowledge about how to use the msi file and need to know the table etc. How is you feeling about this, I was more thinking of some kind of package tool which is more userfriendly. Another question: If we make the changes in the registery different from default how is the fortiClient uninstall reacting on this. Does it know of the changes? Or are we getting in troubles when we need to install a new version of FortiClient? I like to here from you. regards, Harry
    Not applicable

    ORIGINAL: harvoo It is great you placed the " how to" in the forum. But the way Fortinet use this way to install Forti Client for a roll out you still need more knowledge about how to use the msi file and need to know the table etc. How is you feeling about this, I was more thinking of some kind of package tool which is more userfriendly.
    There are two methods you can use. First, you can pay for the MaSaI Editor which will allow you to repackage the MSI file with your changes included. Second, you can zip the MSI file and your transform (MST) file in an self-extracting executable which also allows you to execute a command (your install command syntax) after extraction. Another way is mentioned in the knowledgebase (http://kc.forticare.com/default.asp?id=790). This would be the best way to do it, but I have not been able to get this to work. Perhaps it only works with FortiClientSetup_1.2.066.exe mentioned in the document.
    Another question: If we make the changes in the registery different from default how is the fortiClient uninstall reacting on this. Does it know of the changes? Or are we getting in troubles when we need to install a new version of FortiClient?
    Yes, either method above, the Windows Installer will record that you used a special MST or MSI file to install. You' ll likely have to uninstall the FortiClient first, before installing a newer version. The way that is mentioned in the knowledgebase would be upgradeable, but as I said above, I was never able to record an install in the way mentioned. At least that' s been my experience so far. But uninstalling and reinstalling is still easier for me than going through the pain of walking my remote users through a custom install. Hope that helps. BTW... I just confirmed that FortiClientSetup_1.2.204.exe /r does not work in the way mentioned in the knowledgebase. Disappointing really...
    skyhigh
    New Contributor

    BTW... I just confirmed that FortiClientSetup_1.2.204.exe /r does not work in the way mentioned in the knowledgebase. Disappointing really...
    Creating custom and unattended installations and documentation. Please note that the article http://kc.forticare.com/default.asp?id=790 is specifically designed FortiClient 1.2.109 (MR1) and below. All releases after version 1.2.109, use a completely redesigned installer that does not support the " /r" (record mode) cmdline switch. If you are planning to customize an unattended FortiClient installations you should read the appropriate document: If you have FortiClient 1.2 MR2 or higher (including FortiClient 2.0), you should follow: http://kc.forticare.com/default.asp?id=1080 " Creating unattended Installation FC 1.2 MR2 or higher" If you have FortiClient 1.2 MR1 or lower, you should follow: http://kc.forticare.com/default.asp?id=790 " Creating Unattended installation FC 1.2 MR1 or lower" Creating transforms The rest of this document describes why you should use transforms to create your installations for FortiClient 1.2 MR2 or higher. We are doing as much as possible to make upgrading from one version to the next as easy as possible for you. When customizing FortiClient 1.2 MR2 (or higher) you should not modify the mst file that are packed with the MSI (1033.mst). This is a language transform file that modifies the installer GUI (1033 is the language code for US English) that is automatically generated when we build the FortiClient installer. There is a chance that 1033.MST file will change in future releases, and if that happens then you may need to repeat the entire customization process for the new version. We want to help you to avoid having to do this. By far the best thing to do, and it will save you time in the long run, is to create your own MST file (naming it appropriately) and applying it to the MSI on the command line like this: msiexec /i FortiClient.msi TRANSFORMS=myMST.mst Obviously for silent installations, use: msiexec /qn /i FortiClient.msi TRANSFORMS=myMST.mst As long as you follow the bulleted editing rules in http://kc.forticare.com/default.asp?id=1080, it is very likely that you will never need to create a new transform for FortiClient from scratch again. Each time a new version of FortiClient is released, if you need to, you should be able to simply update the transform you already have and apply it to the new FortiClient MSI package. That should free up your time for more important things. Customizing the MSI in Detail We have created 3 components specifically for you to populate with custom registry fragments. REGISTRY_MST_VPNSettings for VPN modifications. REGISTRY_MST_AVSettings for anti virus modifications. REGISTRY_MST_FWSettings for firewall modifications. We think of these components as " Yours" and all other components as " Ours" . You should avoid putting your custom registry fragments into " Our" components. At the same time we will avoid making any changes to " Your" components. This is because we cannot guarantee the state of " Our" components in future versions - we may need to disable some of them. If we happen to disable the one component that you chose to hold your customization, then your customization will be inadvertently disabled. It is extremely unlikely that we will ever disable any of " Your" three components that are listed above. VPN settings To install custom tunnels, you should export HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\IPSec and import it into REGISTRY_MST_VPNSettings. AV settings To install custom AV settings you should export HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\FA_AV HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\FA_EMAIL HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\FA_FMON HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\FA_REGMON You should import the fragments into REGISTRY_MST_AVSettings. FW Settings To install FW settings (including advanced FW rules), you should export HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\FA_FW Caution! - you should delete all FA_FW\Zones\Address\ subkeys that have bracers " {}" , as these are machine specific. HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\FA_FW\Zones\Address\{617EA3E1-3B4E-4C6C-8B05-8D52F48CE451}_0 You should import your edited ref fragment into REGISTRY_MST_FWSettings Licensing To automatically install a license you should create a new entry in the Properties table called ISX_LICENSE. You should set it' s value to be your license key.
    Fortinet Technical Support
    Fortinet Technical Support
    Announcements

    Select Forum Responses to become Knowledge Articles!

    Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

    Labels
    Top Kudoed Authors