In this movie we will look at the Administration Tab in the FileMaker Server Configuration. Unlike FileMaker Server 7 or 8, FileMaker 9 and 10 allow remote administration by default and the standard protection against unauthorized access is the original Admin Console account and password that was asked for in the installation process and that you can change here. Once FileMaker Server is installed, you can additionally select the required membership in the FMS Admin Group. This last option is tied in with external authentication that we will discuss more fully in a separate movie. External authentication allows you to use accounts and groups that exist outside of FileMaker to authenticate users and administrators. With outside of FileMaker we mean either locally in the operating system of the FileMaker Server machine or broader on a centrally-managed domain like Windows Active Directory of OS X Open Directory. Let's explore what is required to make this FMS Admin Membership Group work. When FileMaker Server is installed on OS X, it actually creates a group called FMS Admin on the local machine. And you can check that in, that info if you're running on 10.4 or if you're running on 10.5 like we are here, you're best bet is to use the Workgroup Manager. Here under Groups we see that the installation process for FileMaker Server actually created a FMS Admin Group and it has added the FileMaker Server User as its default user but it has also added my account, the account that I was logged in for during the installation process as a member of the FMS Admin Group. Now, when I quit out of this Admin Console, first let's save the changes. The change that we made was to allow member of the FMS Admin Group to log in. If we quit out of the console and log back in again, we will be presented with the default login dialog and if we now specify my own OS X user accounts and we just verified that it was added to the FMS Admin Group, then we see how we can actually log in to the Admin Console. But can I still log into this FileMaker Server from an Admin Console in Windows even though it requires an account that exists only on the Mac? Let's try. Here we are on a Windows machine and let's try and open the Admin Console for our FileMaker Server running on OS X. Here we are presented with the same login dialog so let's go ahead and specify the OS X accounts. And as we can see, it just works. To show you in some more detail how it actually works, this is what happens. When we are presented with the login dialog, the credentials that we enter get sent to FileMaker Server. FileMaker Server then checks if the FMS Admin Group setting is enabled. If it is, it'll check with the operating system to see who is actually a member of the FMS Admin Group. If FileMaker Server finds a match for the account that we've provided, then FileMaker Server will grant access to the console. Now, this works on the premise that accounts and access to accounts are governed by the local FileMaker Server machine. If the FileMaker Server machine is part of a broader domain, then it's slightly different. The credentials that we enter still get sent to FileMaker Server. FileMaker Server will check if the FMS Admin Setting is enabled. If it is, it will ask the domain controller for a list of members of the FMS Admin Group. Then it'll check those members against the credentials that we sent through the login dialog. If there is a match, FileMaker Server will grant access to the Admin Console.