7 Replies Latest reply on Dec 5, 2013 10:29 PM by steveromig

    Windows Server for FMP Server 13

    tdahlborn

      Upgreading in 2014, I am trying to support a 20 users with filemaker pro server 13 and users with the full client FMP, they need to update server software and hardware.

       

      The client is evaluating using a Mac Mini Server or a Windows Server. The question relates to filemaker pro clients connecting to the databases on a Windows server. They have been told they will need a CAL, since this is considered "file sharing" for each workstation/user connecting to the Windows Server. Of course this drives the cost way up verses the Mac Mini that doesnt charge anything.

       

      Can anyone clarify ?

        • 1. Re: Windows Server for FMP Server 13
          steveromig

          tdahlborn wrote:

           

          Upgreading in 2014, I am trying to support a 20 users with filemaker pro server 13 and users with the full client FMP, they need to update server software and hardware.

           

          The client is evaluating using a Mac Mini Server or a Windows Server. The question relates to filemaker pro clients connecting to the databases on a Windows server. They have been told they will need a CAL, since this is considered "file sharing" for each workstation/user connecting to the Windows Server. Of course this drives the cost way up verses the Mac Mini that doesnt charge anything.

           

          Can anyone clarify ?

           

          I assume when you reference "CAL" you are referring to a Client Access License.

           

          The answer in this scenario is "No"  You only need a concurrent connection license when you are connecting with either FileMaker Go 13 or FileMaker WebDirect to FileMaker Server 13.  FileMaker Pro 13 clients do not require a concurrent connection license to connect to a file that is hosted using FileMaker Server 13.

           

          Hope this helps.  Let me know if you have any further questions.

           

          Steve Romig

          FileMaker, Inc.

          • 2. Re: Windows Server for FMP Server 13
            robwoof

            If someone is talking about CALs for FileMaker, they clearly know nothing about FileMaker.

             

            Windows servers used as File Servers require CALs (Client Access Licences) for the number of users connecting. 20 users->20 CALs. FileMaker is NOT file sharing in that sense. So even if you have a Windows server hosting FileMaker, CALs are irrelevant.

             

            HTH

            Rob

            • 3. Re: Windows Server for FMP Server 13
              tdahlborn

              Steve

               

              thanks for the update, so i get this correct: Filemaker Pro Server 13 with 20 FMP clients, They can purchase a Windows Server with the base clients, most come with 5 users, and not have to be concerned about accessing the hosted databases with  thrir 20 FMP Clients.  The person advising, mentioned that the database files are located on the server so a CAL would be needed. They would be considered "shared".

               

              It seems to be a "grey" area for getting confirmation. Adding the "CAL"s increases the total budget.

               

              Tom

              • 4. Re: Windows Server for FMP Server 13
                robwoof

                Tom,

                 

                Again: the person advising you about CALs doesn't understand FileMaker and FileMaker Server. He/she is thinking that users will mount a network share and open the files directly (like, say, a shared Excel spreadsheet). This is not how it works. In fact, this is how it MUST NOT happen.

                 

                Instead, FileMaker Server opens the files and shares them as FileMaker files, not as shared documents on a file share.

                 

                Update: for example, Windows CALs are not required on Windows servers that are used as web servers. Windows CALs are not required on Windows servers serving Oracle, MySQL or MSSQL Server databases. It's the same kind of thing. The users use the "FileMaker Server" service, provided through the FileMaker Server process. No Windows client access; no Exchange access, no CAL.

                 

                Since your users are using FileMaker Pro, not FM GO or WebDirect, there is no per-user licencing required.

                 

                Rob

                • 5. Re: Windows Server for FMP Server 13
                  tdahlborn

                  thanks for the answer.... I have been searching for this confirmation and explaination for a long time. On the Microsoft site they explain it this way:

                   

                  CALs are required for every user or device accessing a server.

                   

                  It seems diffferent in everytime new server software is released.

                  • 6. Re: Windows Server for FMP Server 13
                    robwoof

                    ... and Microsoft are experts at making things clear <cough, cough>.

                     

                    Maybe there are administrators of Windows FileMaker Servers out there who can share their experience, but I am 99.9% sure that the CALs sentence quoted above does not apply to FileMaker Server connections.

                     

                    Rob

                    • 7. Re: Windows Server for FMP Server 13
                      steveromig

                       

                      Maybe there are administrators of Windows FileMaker Servers out there who can share their experience, but I am 99.9% sure that the CALs sentence quoted above does not apply to FileMaker Server connections.

                       

                      It does not.

                       

                      However, you do have to buy concurrent licenses if you wish to connect to a file hosted with FileMaker Server 13 using either FileMaker Go 13 or FileMaker WebDirect as clients.

                       

                      The way concurrent connections work is this.  Say you had ten (10) people in your office that need access to a file hosted using FileMaker Server 13 using FileMaker Go 13 as a client.  But not all ten of them will ever access the file at the same time.  Let's say, at any given time the maximum number of people accessing the file is six (6).  So in the FileMaker Server 13 model, you do not have to obtain a concurrent connection for the number of people in your office (10) but only for the maximum number of people you think will ever access the file at once (6).  In other words, you do not have to purchase connections based on individuals in the office but instead you purchase connections based on how many you think you will ever need at one time.

                       

                      Out of the box, FileMaker Server 13 supports one concurrent connection and you can buy additional concurrent connections in groups of five.

                       

                      FileMaker Pro 13 clients do not require concurrent connections so you can have, in theory, an unlimited number of FileMaker Pro clients connect to your files hosted with FileMaker Server 13.

                       

                      Steve Romig

                      FileMaker, Inc.