Customize the personalization file

  1. Use a text editor to open the Assisted Install.txt file on your networked volume.

    Note  The Assisted Install.txt file is a cross-platform file. The same Assisted Install.txt file can be used for installing on Windows, macOS, and Linux systems.

  2. Modify the following variable settings as needed.

    To

    Do this

    Accept or don't accept the End User License Agreement (EULA)

    For silent installations only, type one of the following after License Accepted=

    • 1 (one) to accept the EULA terms

    • 0 (zero) not to accept the EULA terms (default)

    See About silent assisted installations (Windows), About silent installations (macOS), or About silent installations (Linux).

    Important  If you keep the default of 0 (zero), the installation will stop.

    Windows and macOS: Enter an organization name for all installations

    Type a name after Organization=

    When specifying a variable for Organization=, type the organization name exactly as it appears on the software download page.

    Windows: If you enter no value, the installer defaults to the name that was used to register Windows.
    Specify the deployment options

    Type one of the following after Deployment Options=

    • 0 (zero) to install a server machine (default)

    • 1 (one) to install a Claris FileMaker WebDirect™ secondary machine

    If you are setting up a multiple-machine deployment, you need to provide an Assisted Install.txt file for installing on the primary machine and an Assisted Install.txt file for installing on the FileMaker WebDirect secondary machines.
    Windows and macOS: Specify the FileMaker Server user account

    Type one of the following after FileMaker Server User=

    • 0 (zero) to run FileMaker Server under the default account (Local System for Windows, fmserver for macOS)

    • 1 (one) to run FileMaker Server under a different account

    If you specify FileMaker Server User=1 for a silent installation, the installation will stop. See About silent assisted installations (Windows) and About silent installations (macOS).
    Specify the Admin Console user name

    Type the user name to be used for signing in to Admin Console as the server administrator after Admin Console User=

    The user name is not case sensitive.

    If you enter no value, the default user name admin is used.
    Specify the Admin Console password

    Type the password to be used for signing in to Admin Console as the server administrator after Admin Console Password=

    The password is case sensitive.
    Specify the Admin Console PIN Type the four-digit PIN value to be used in the command line interface (CLI) for resetting the Admin Console password after Admin Console PIN=
    Windows and macOS: Specify whether, after installation, Admin Console automatically opens on the primary machine, and whether the Deployment assistant automatically starts on secondary machines

    Type one of the following after Launch Deployment Assistant=

    • 0 (zero) to suppress opening Admin Console (primary machine) and starting the Deployment assistant (secondary machine)

    • 1 (one) to open Admin Console (primary machine) and start the Deployment assistant (secondary machine) after installation (default)
    Specify the path for the FileMaker® license certificate

    Type the fully qualified path for the license certificate file after License Certificate Path=

    For example:

    • Windows: C:\Users\user name\Downloads\LicenseCert.fmcert

    • macOS: /Users/user name/Downloads/LicenseCert.fmcert

    • Linux: /home/user name/Downloads/LicenseCert.fmcert

    Notes

    • Windows: Use only ASCII characters for the folder location of the license certificate.

    • If you omit the path for the FileMaker license certificate, the installer looks for a file with the filename extension .fmcert in the following paths:

      • the default Downloads folder on the machine where the installer is located

        • Windows: C:\Users\user name\Downloads

        • macOS: /Users/user name/Downloads

        • Linux: /home/user name/Downloads

      • the installer folder (the folder where the installer is located)

      • the LicenseFile folder

        • Windows: drive:\Program Files\FileMaker\FileMaker Server\CStore\LicenseFile, where drive is the drive on which FileMaker Server is being installed

        • macOS: /Library/FileMaker Server/CStore/LicenseFile on the machine where FileMaker Server is being installed

        • Linux: /opt/FileMaker/FileMaker Server/CStore/LicenseFile on the machine where FileMaker Server is being installed
    Windows and macOS: Suppress or display the Customer Information, Deployment Options, User Account, and Admin Console Account dialog boxes during installation

    Type one of the following after Skip Dialogs=

    • 0 (zero) to display the dialog boxes during installation

    • 1 (one) to suppress the dialog boxes

    When you specify 1 (one), users don't have to enter information in the installer.

    If you entered FileMaker Server User=1 (and Deployment Options=0) above, the FileMaker Server User Account dialog box still displays.

    If you entered no value for Admin Console Password= or Admin Console PIN= above, the Admin Console Account dialog box still displays.

  3. Save the changes you have made to Assisted Install.txt as plain text.

    • Windows: Assisted Install.txt and Setup.exe must be in the Files folder during installation.

    • macOS: Assisted Install.txt must be in the same folder as the FileMaker Server installer application during installation.

    • Linux: Assisted Install.txt must be in the same folder as the FileMaker Server RPM (CentOS) or DEB (Ubuntu) installer during installation.