kmfkfacts.blogg.se

Adjustments to these services may need to be made at the group level as changes made locally can be overwritten by the group policy.

If the server is deployed on the MIT WIN domain, be mindful of group policies around TSM, antivirus, and other services. Web services will need to be turned on in order for server administrators to access the FileMaker Server Admin Console. Turn off Indexing Service (Windows) or Spotlight (Mac). Anti-virus softwareĪnti-virus software should be completely disabled, or at least set to exclude the live hosted files from scanning (see “Backup and recovery” above). The FileMaker Server\Data\Backups folder may be safely backed up by TSM. Mac: /Library/FileMaker Server/Data/DatabasesĪny non-FileMaker process that accesses the live hosted files runs a risk of file corruption. Win: C:\Program Files\FileMaker\FileMaker Server\Data\Databases Set up TSM account and exclude the Databases directory: See FileMaker Server Port Settings at MIT for the port settings required by FileMaker Server. Power settingsĬonfigure server machine to always be on (never asleep or hibernating) Ports and firewall settings If not managed by IS&T or residing in an MIT data center, should be kept in a lockable inner office and removed from general traffic UPS highly recommended. Server should be server-class physical or virtual machine. Use IS&T-managed servers whenever possible. Server Machine Hardware and physical security In a changing computing landscape these recommendations in no way offer a guaranteed maintenance or risk-free hosting environment. The following web page offers MIT-specific configuration recommendations to help mitigate against security risks in the FileMaker hosting environment. Only experienced server administrators should attempt to do so, particularly where databases with sensitive data and/or mission critical functions will be housed. NOTE: IS&T recommends that IS&T Managed Servers be used for hosting FileMaker databases.