Best practice for ANYTIME that you update a windows server is to stop all user interactions with the server, back it up, then update.
We have always disconnected all users from any server (mac or PC) and turned off the filemaker server before installing updates.
At best, you can get away with it. At worst, you could corrupt your entire FMS installation to the point of needing a complete OS reformat and FMS reinstall. I wouldn't recommend taking the risk.
If you do close databases and stop FM Server, please be aware that there is a bug in Windows version that will delete (or apparently delete) any Administrator Groups setup. Either way, the users of these will not be able to access the admin console. Restarting the server hardware without closing databases manually (so FM Server closes the files) retains the groups - not good practice, but good to be aware of.
FileMaker have acknowledged this bug and we're hoping for a fix in a future update.
More than that... you probably do not want to patch the OS unless you've tested it on a test server first to see if anything breaks.
Taken from Windows 10 release Wim, should be interesting:
"Microsoft has promised mandatory updates for Windows 10. You can’t turn them off."
But you wouldn't use a desktop OS for your server, right?
And I'm pretty sure the "professional" version of Win10 will allow you to disable that. No big company will want patches to be installed automatically...
I think it will be a day or two before we find out here.....
On every quartely basis, the team is updating the patches in the Microsoft windows server 2008
So, I am not sure whether the Filemaker services has to be stopped in both the database and web server
Yes. Absolutely, positively, close the files, make sure they are closed properly. You can then choose to stop the FMS server service altogether and set the startup to manual. That will save you some time.
Make absolutely sure that FMS will not auto-host files when the machine boots up.
Can you tell me what happens if I am not stopping any of the services as well not closing any of the databases. Does it is right procedure ?
Since I am going to do directly in Prod environment let me know the answer for the above query.
The main thing is closing the files. If you don't close the files then you risk that any OS patch that needs to reboot the machine will not wait on FMS to close the files and will possibly damage them.
When you stop the FMS service and set it to manual then you save time on the next machine reboot in case the OS patching needs to reboot the machine more than once.
You don't want FMS to auto-host files because if they were not closed properly then FMS will run them through a verification process which may take a very long time depending on the size of the files. And also, you may not catch the fact that the files were not closed properly before and it will taint all future backups.
A good practice is to turn off all automatic updates on the server, since some of them will force a restart and very probable will damage your databases or even the FMS.
periodically , backup all your databases, server scripts, turn off FMS and perform the OS updates, restart and you should be up and running again !
good luck !
Make absolutely sure that FMS will not auto-host files when the machine boots up
Can you please explain the above statement, how does FMS will auto-host files?
FMS is configured out-of-the-box to automatically start all of its services AND automatically host any files in the proper folders.
That is a bad practice; in case the server or FMS crashes you do not want those crashed files to automatically open, you want an admin to have the chance to restore from a backup before users start adding and changing data in potentially damaged files. The setting to turn off is the one highlighted below:
Understood. Thanks Wim