In this movie we will explore the configuration options available under General Settings in the FileMaker Server Console. This first tab is all about describing your installation. You can enter a description and some information about who is the administrator or owner of this particular FileMaker Server. The Server Name you set up here is the name that will show up in the FileMaker Pro's Open Remote Dialog where users can find any local servers and files that are hosted on it. So the name that shows up here is the name that you specify to here. At the bottom we find information about the current license for this installation and when we click the Change License key, we can get even more details and we can upgrade from regular FileMaker Server to Server Advanced by entering a new key. In the second tab we can configure FileMaker Server to send out email notifications and or warnings happen related to FileMaker Server. First you need to enter your SMTP information. Note that FileMaker Server does not support an SMTP server that requires a SSL connection. So that rules out any one of you with a gmail account, for instance. So what we have set up here will actually not work. In the second pane is where you enable the feature that will let FileMaker Server send out those notifications based on your SMTP information and you can specify multiple recipients by separating the email addresses with a comma. And lastly, here at the bottom you need to choose whether you want emails only on errors or on both errors and warnings. Note that what you set up here has no relation at all with the ability to send server-side email from inside scripts in your solution. For that feature, you set up the SMTP information in the script itself. And that feature actually does support SSL SMTP connections. So the email notification information here or the configuration settings have only to do with FileMaker Server sending out notifications when an error or warning happens. On the Admin Console Tab, we can restrict who is able to launch the Admin Console from what IP Addresses. Note that if you make changes to this setting, you will have to restore FileMaker Server before they take effect. In the second panel we can change the user account and passwords that was initially set up during installation. And here we can also include anyone in the FMS Admin Group to have access to the Admin Console. That FMS Admin Group is an operating-system level user group that can exist on either the local FileMaker Server machine or in the domain in an active directly that's on Windows or Mac Open Directory. More about that in a movie on external authentication. The last setting on this tab is to enable FileMaker Server to check for updates automatically. It will do that whenever it launches. If you want to force an update check, you can go to the Help in the Admin Console Menu and choose Check for Updates. Note that this particular setting also has an affect on what's shown on the FileMaker Server Start Page. If we bring up that Start Page, you'll see that this is a Software Updates Section here that also shows the current version of your FileMaker Server. Now, if you go back to our console and disable this function, save out to changes, go back to the Start Page and reload that page, you will see that this Software Updates Section has totally gone. The next and last step tells FileMaker Server whether or not to automatically open the files when the FileMaker Server serves or daemon launches. Typically you want to turn this off and give yourself or any administrator the chance to check the files in case the server crashed. If we have a quick look at the Services Control Panel on Windows where this particular FileMaker Server is installed, this is where we will find the actual FileMaker Server service and you'll note that it is set up to automatically launch whenever Windows launches. So that's when the machine boots. The Admin Console, however, is set up to not automatically open any of the files. So what this means is with the operating system configured as it is, basically configured to start the FileMaker Server service on boot, that will allow anyone, any administrator to connect to the Admin Console either locally or remotely but FileMaker Server will not automatically start hosting any files. If you don't let the operating system start the FileMaker Server service, then you will not be able to connect to it from the Admin Console. So this setting here in the Admin Console is only about opening the files or not.