If you’re stepping into the world of database management and development with Claris FileMaker Server, you might know that officially, it’s supported only on server editions of Windows. Despite this, there’s a way to set it up on Windows 10/11 for testing or development purposes. Here’s how you can do it.

Disclaimer

Before we proceed, it’s important to note that running FileMaker Server on non-server Windows editions is not supported by Claris. This guide is intended for educational purposes or for setting up a test environment.

Step-by-Step Installation

To get started, you’ll need to configure some Windows features to mimic the server environment as closely as possible. Here’s what needs to be enabled:

I. Internet Information Services (IIS)

Claris FileMaker Server relies heavily on IIS for web publishing and other web-related services. You’ll need to enable the following IIS-related features:

1. Web Management Tools:
   • IIS Management Console: Essential for managing IIS settings.
2. World Wide Web Services:
   • Application Development Features:
     • .NET Extensibility 3.5 & 4.6: Needed for running applications built with .NET.
     • Application Initialization: Improves the responsiveness of your web applications.
     • ASP & ASP.NET 3.5 & 4.6: These are scripting frameworks required by FileMaker Server for its web publishing capabilities.
     • CGI: Supports the execution of scripts like PHP which might be used in your FileMaker web applications.
     • ISAPI Extensions & Filters: Allows for custom extensions to IIS.
   • Common HTTP Features:
     • Static Content: This is required to serve static web pages.
   • Security:
     • Basic Authentication: Provides an authentication method for your IIS web server.
     • Windows Authentication: This might be necessary for intranet environments.
   • Performance Features:
     • Static Content Compression: Helps in optimizing the speed of web content delivery.

II. FTP Server (Optional)

This is useful if you need to transfer files to and from your server securely.

III. Health and Diagnostics

FileMaker Server benefits from the logging features provided by IIS:

• HTTP Logging: Essential for diagnosing web server issues.
• Tracing: Allows you to trace the HTTP request life cycle, making it easier to pinpoint issues.

Configuration

After enabling these features, you’ll have to set up your IIS to work with FileMaker Server:

1. Set up your website in IIS, which will host the FileMaker WebDirect or any custom web publishing.
2. Configure your application pools to use the correct .NET framework versions as required by FileMaker Server.
3. Ensure that the IIS user has the necessary permissions to the directories where your FileMaker databases will reside.

Post-Installation

After installing FileMaker Server:

1. Check for updates: Always make sure you have the latest version of FileMaker Server installed for optimal performance and security.
2. Backup regularly: Even though it’s just a test environment, make it a habit to back up your databases regularly.
3. Monitor performance and logs: Regularly check the IIS logs and FileMaker Server logs for any unusual activity or errors.

Conclusion

Setting up a test environment for Claris FileMaker Server on a non-server edition of Windows might be useful for developers and those new to FileMaker. However, always remember this setup is only for testing or development purposes and is not meant for production environments. As you grow in your FileMaker journey, you should invest in a supported server environment to take full advantage of what FileMaker has to offer.

Remember, experimenting and learning are the keystones of mastering any software. Happy FileMaking!

Please note, the steps outlined above are based on the assumption that you have a basic understanding of Windows features and IIS. If not, additional research or guidance may be necessary.