1. Information Services & Technology
FileMaker 13 Server

2. System Recommendations
Operating System*
Windows Server 2012 Standard Edition (64-bit)
Windows Server 2008 R2 SP1 (64-bit)
*Version stated is the minimum requirement. FileMaker Server may also work with later operating systems certified by FileMaker, Inc. Operating systems not listed in the table above have not been tested and are not supported. (from FileMaker)

3. Hardware Requirements
Hardware Requirements Database Server Minimum CPU: Dual Core RAM: 4 GB Hard Drive: 80 GB or more, dependent on file size, requirements minimum 10 GB free space Recommended CPU: 4-Core RAM: 8 GB Hard Drive: 80 GB or more, dependent on file size, requires minimum 10 GB free space

4. Ports used by FM 13 Server

5. Advantages of using Managed Server Services
1) Installation, maintenance (patches/upgrades) of OS 2) Installation of FileMaker 13 server and upgrades 3) Login management 4) IIS management (including SSL certificate management) 5) System monitoring 6) TSM nightly backups 7) Virtualized server in VMware farm – SAN attached drives More info at

6. IIS SSL certificate Installation
Open IIS. Double-click on Server Certificates

7. Cert Request
Choose Create Certificate request, fill out info and click next

8. Credentials
Choose default Cryptographic service provider but choose 2048 as bit length. Click next

9. Drive Options
Same file name – recommendation FQDN.req Click finish

10. Request
Send an to requesting an SSL certificate for the hostname. Inline the request file generated. Include OS and IIS version Do not make multiple certificate requests into one /RT case as this will be rejected.

11. Installing certificate IIS
– 4th link down (certificate only) save and copy to server

12. Installing Certificate – IIS (Cont.)
From IIS -> Server Certificates -> Complete Certificate Request

13. Installing Certificate – IIS (Cont.)
Path to file, Friendly name is FQDN, Personal certificate store – clidck OK

14. Installing Certificate – IIS (Cont.)
Certificate will now be listed

15. Installing Certificate – IIS (Cont.)
In IIS expand sites, highlight FMWebSite, click Bindings

16. Installing Certificate – IIS (Cont.)
In Site binds, highlight https port 443, click edit

17. Installing Certificate – IIS (Cont.)
From drop down, choose newly installed certificate.Click OK. Repeat for port 16000

18. Installing certificate for FileMaker Server
You need to export certificate from IIS -> Server certificates -> Export

19. Installing certificate for FileMaker Server (cont.)
From FM Support:
Often, the signed certificate and the private key file are combined into a single file. The CERTIFICATE IMPORT command allows you to specify the same file for both items:
fmsadmin certificate import c:\Documents\combinedCertificate.pem
--keyfile c:\Documents\combinedCertificate.pem --keyfilepass password
Note: The CERTIFICATE IMPORT command only supports the .pem file format. If you have a private key file that is a .pfx or .pf12 file (a file in either PKCS #7 or #12 format), you need to convert the private key file to the .pem file format before using the fmsadmin CERTIFICATE IMPORT command to import it.
The following is an example of how to use OpenSSL to convert a PKCS #12 file to the .pem file format:
openssl pkcs12 -in keyStore.pfx -out keyStore.pem –nodes

20. Some Gotchas
Although following the procedures from FileMaker, the SSL connection form FileMaker Pro still says secured with FMI certificate When installing Updaters, do it from C drive After installing updater, Admin Console from local port sluggish – use port Use Server 2012 standard 64 bit OS, R2 Admin Console unusable After updater was run on Server 2008 R2, could not connect to FileMaker databases from Pro

21. Basic Security
Server in locked cool room – always log off Limit local admin acess – separate accounts Run local firewall – open only FM ports Keep server updated with latest Microsoft patches Keep FileMaker Server updated

22. Questions?
???