Claris FileMaker Pro 19 Network Install Setup Guide

Before you configure your installation, decide how you want to install the software. The installation method determines how personalized information is entered when users install FileMaker Pro.

For some installation methods, you can edit the file, Assisted Install.txt, to provide the personalized information before users install the product. See About the personalization file.

Installation method	How personalization information is supplied to the installer
Installing FileMaker Pro using a networked volume (Windows)—Recommended method	Edit Assisted Install.txt to standardize all networked FileMaker Pro installations. This method lets you customize the installation.
Installing from the command line with msiexec (Windows)	Users or scripts provide the personalized information at the command line.
Setting up silent assisted installations (Windows)	Edit the Assisted Install.txt file before performing a silent installation. User interaction with the FileMaker Pro installer is kept to a minimum. The installer reads personalization information from the file, and installation screens do not display.
Saving personalization information in the .msi installer (Windows)	Embed personalization information directly in the installer .msi file. Because the changes persist in your .msi file, you can remove the Assisted Install.txt file.

For FileMaker Pro to run, users must have specific versions of these Microsoft software components installed on their computers:

• .NET Framework
• Visual C++ libraries and the Windows Runtime (provided in the Visual C++ Redistributable Package)

The required Windows updates must also be installed. See FileMaker Pro technical specifications.

If you use Setup.exe (in silent or full user interface mode) and the required Microsoft components aren't installed, Setup.exe runs the included Microsoft installers for these components. The FileMaker Pro installer continues after it detects that the Microsoft components are installed.

Note:The Microsoft installers for these components require internet access to download the necessary files.

However, if you use the .msi file, make sure these Microsoft components are installed before users start FileMaker Pro. The .msi file installs FileMaker Pro without checking whether the components are installed, but FileMaker Pro won't run without them.

If necessary, users can install the Microsoft components manually:

1. Open the FileMaker Pro installation folder.

2. Open the Files folder, then:

   To install	Do this
   .NET Framework	Open the DotNet folder. Double-click the icon.
   Visual C++ Redistributable Package	Open the Redist folder. Double-click the x64 icon.

3. Follow the onscreen instructions.
4. Install the required Windows updates for the Microsoft components.

The Bonjour service must be installed for hosts on your local network to be discovered. If Bonjour isn't installed or if the Bonjour service isn't running, users won't be able to view hosted files on your local network in the Hosts dialog box. Without Bonjour, they must manually enter the names or IP addresses for hosts on your local network.

Using Setup.exe (in silent or full user interface mode) installs Bonjour automatically; using the .msi file does not. Users can also install Bonjour manually. See Installation Guide.

To make FileMaker Pro installation files available on your network:

1. Create an installer folder on a networked volume for the installation files.
2. In your software download, locate the installation files in the Files folder. Then, copy the files to the folder you created on your networked volume.

3. Copy the license certificate file to the installer folder you created (where the .msi file is). See About the license certificate file.

4. To set up an assisted installation, edit the Assisted Install.txt file located in the installer folder you created, and save the changes as plain text. See About the personalization file.

To install FileMaker Pro, tell users to:

1. Mount the volume containing the installation files.
2. Double-click Setup.exe.

Users can install FileMaker Pro from the command line without using Assisted Install.txt. A command line installation requires you to run the Command Prompt as administrator.

1. Copy the license certificate file to the same folder that the .msi file is in. See About the license certificate file.
2. Choose Start menu, then search for Command Prompt. Right-click Command Prompt and choose Run as administrator.

3. In the Administrator: Command Prompt window, enter a command.

   For example:

   msiexec -i "ProductName.msi" AI_USERNAME="John Lee"

   Property names must be in all-uppercase letters. The user name property is optional. See Setting personalization properties in Assisted Install.txt.

   If the .msi file is on a mapped network drive, you may need to enter net use * \\server\share in the Command Prompt window first so that the command above can access the mapped network drive.

   Alternatively, you can create your own script that performs the command, then run your script on users' computers.

   Note:For more information about msiexec, see docs.microsoft.com.

Users can perform a silent installation, which keeps interaction with the FileMaker Pro installer to a minimum. Required installation information is read from the Assisted Install.txt file, and installation screens aren't displayed. See About the personalization file.

1. Copy the license certificate file to the same folder that the .msi file is in. See About the license certificate file.
2. Choose Start menu, then search for Command Prompt. Right-click Command Prompt and choose Run as administrator.

3. In the Administrator: Command Prompt window, enter a command.

   To	In a command window, type
   Install without a user interface (silent installation)	"pathname\setup.exe" /qn
   Uninstall without a user interface (silent uninstallation)	"pathname\setup.exe" /x /qn
   Install when required—advertise to current user (silent advertised installation)	"pathname\setup.exe" /q /ju
   Install when required—advertise to all users (silent advertised installation)	"pathname\setup.exe" /q /jm
   Install and display a dialog box indicating whether the software was successfully installed	"pathname\setup.exe" /qn+
   Install and display a progress bar and Cancel button during installation	"pathname\setup.exe" /qb+
   Install to a non-default location on the user's computer	"pathname\setup.exe" /qb+ INSTALLDIR="installpath"

Alternatively, you can create your own script that performs one of these commands, then run your script on users' computers.

Notes

• pathname is the location of the installer folder you created on the networked volume. If pathname is for a mapped network drive, you may need to enter net use * \\server\share in the Command Prompt window first so that the commands above can access the mapped network drive.

• installpath is the desired location of the FileMaker product folder on the user's computer. The path cannot contain spaces unless it is enclosed by double quotation marks. The following example path would install into the FileMaker Pro folder inside the Applications folder on drive C:

  "C:\Applications\FileMaker Pro"
• The installer will reboot the computer if required.

You can embed personalization information in the .msi installer. If you choose this method, make sure that you make no other changes to the .msi file.

You use the Microsoft Orca editor for this task. See msdn.microsoft.com.

1. Copy the license certificate file to the same folder that the .msi file is in. See About the license certificate file.
2. Use Orca to open the .msi file.

3. In the Property table, enter values for the properties you want to set.

   See Setting personalization properties in Assisted Install.txt.

4. Save the .msi file.
5. Tell users to run the installer by double-clicking the Setup.exe file located on the mounted volume, by using the command line, or by running a script that you create.

Users can check for updates and install them within FileMaker Pro by choosing Help menu > Check for Updates, unless this feature has been disabled (see Setting personalization properties in Assisted Install.txt). Users must have an internet connection and Windows administrator privileges to update FileMaker Pro.

Alternatively, you can download the updater and install it manually, or from the command line, or using Microsoft System Center Configuration Manager (SCCM).

To install an update manually:

1. Download the ProductUpdaterName.exe file from Downloads and Resources.
2. Quit FileMaker Pro.

3. Double-click the ProductUpdaterName.exe file.

   The files are extracted to a folder in the same location as the .exe file, then the updater starts.

4. Follow the onscreen instructions.
5. Quit the updater and open FileMaker Pro.
6. To verify that the update was successful, choose Help menu > About FileMaker Pro and check the version number.

To install an update from the command line:

1. Follow steps 1 to 3 for a manual installation, but click Cancel after the files are extracted.
2. In the folder that's created, locate the Setup.exe file.

3. Follow the instructions in Setting up silent assisted installations (Windows) to run Setup.exe with the /qn, /qn+, or /qb+ command-line switch.

   The updater doesn't support the other switches.

To install an update using Microsoft SCCM:

1. Follow steps 1 to 3 for a manual installation, but click Cancel after the files are extracted.
2. In the folder that's created, locate the ProductUpdaterName.msp file under Files\Files.

3. In SCCM, create an update package that includes ProductUpdaterName.msp. In the package setup, use the following command line for a silent installation:

   msiexec.exe /p ProductUpdaterName.msp /qn

4. Deploy the package.

1. Create a working folder on a local drive.
2. Download the FileMaker Pro .dmg file and double-click to open it.

3. Copy these files from the open .dmg file to the working folder:

   • the FileMaker Pro.app bundle

   • the personalization file, Assisted Install.txt

     To set up an assisted installation, edit the Assisted Install.txt file and save the changes as plain text. See About the personalization file.

   • the License Agreements folder

4. Copy the license certificate (.fmcert) file to the working folder.

   See About the license certificate file.

5. On the Product Documentation Center, download "Apple Remote Desktop Deployment script for FileMaker Pro" (fmp_osx_deployment.zip).
6. Double-click the fmp_osx_deployment.zip file to extract the script (AppleRemoteDesktopDeployment.sh).
7. In /Applications/Utilities, start Terminal.
8. Type cd "<path to script>", then press Return.
9. Type sudo chmod +x ./AppleRemoteDesktopDeployment.sh, then press Return. When prompted to provide a password, enter an administrator password.

10. Type ./AppleRemoteDesktopDeployment.sh "<path to working folder>", then press Return.

    The script creates a customized .pkg file in the working folder, ready to be deployed.

Use one of these methods to deploy your customized .pkg file to users:

• Make the .pkg file available for your users to download. Tell users to double-click the downloaded .pkg file and follow the onscreen instructions to install FileMaker Pro.
• Use Apple Remote Desktop or another computer management system to remotely install the .pkg file silently on multiple Mac computers in an organization.

Users can check for updates and install them within FileMaker Pro by choosing Help menu > Check for Updates, unless this feature has been disabled (see Setting personalization properties in Assisted Install.txt). Users must have an internet connection to update FileMaker Pro.

Alternatively, you can:

• Download the updated application from your Electronic Software Download page or from the Subscription page in Claris Customer Console. (See About the license certificate file.) To install the updated version, see Installing FileMaker Pro in macOS.
• Download the updater .zip file from Updates and release notes and make it available to your users. Tell users to double-click the .zip file, then double-click the .pkg file inside the folder and follow the onscreen instructions.

Note:Property names (AI_*) must be in all-uppercase letters. Variable settings aren't case sensitive.

Note:In Windows, the AI_SHORTCUTS and AI_SKIPDIALOG properties determine whether the installer prompts the user to create a shortcut.

You can set a property, AI_NONEWDATABASES, that prevents users from creating FileMaker Pro custom apps. If the option is set, FileMaker Pro displays an alert message when users:

• choose File menu > Create New
• create a file in the Create window
• export to a FileMaker Pro file
• choose File menu > Save a Copy As
• open the New File dialog box
• recover a FileMaker Pro file
• convert a file (like tab-delimited or FileMaker Pro .fp7) to a new FileMaker Pro file
• execute an Apple event to open a file in another format
• execute the Apple events do menu command to create a file
• perform a script that does any of the above
• choose a custom menu item that does any of the above

To create custom apps, users must reinstall FileMaker Pro with the AI_NONEWDATABASES property set to 0.