JeffHenry

This Microsoft Docs page might help. Look at the How To section, just a few scrolls down. https://docs.microsoft.com/en-us/iis/configuration/system.webserver/defaultdocument/ Best, Jeff

From a quick glance, i noticed that your Substitute references $DeleteField and not $DeleteText. Try changing that since you specified $DeleteText in the second step.

Thanks for this article, OP. It worked great for me. Yes, I did this on Mac. Just tweaked some of the filenames and directories to my liking. You'll need to follow the Mac tutorial though. https://bluefeathergroup.com/blog/lets-encrypt-ssl-certificates-for-filemaker-server-for-mac/

Very cool method! I second a webviewer. If you are familiar with HTML/Javascript/CSS, you can create some really cool loading animations.

With Teams, you are limited to the number of connections you purchase. Basically, you used to just buy connections for FileMaker Go and WebDirect, but with the new Teams licensing, FileMaker Go, WebDirect, and FileMaker Pro are all included together. Because of this, you are probably spending less on individual FileMaker Pro licenses, but getting the flexibility that a 10 person team, for example, could all use FileMaker Pro, FileMaker Go, or WebDirect. So lots more flexibility and probably cheaper if you do need those FileMaker GO and WebDIrect connections. However, if anyone has a licensed copy of FileMaker Pro (Legacy style), they can connect to your server without using a connection seat. With Legacy, it's really good if you don't need the other two technologies, because you only have to pay for FileMaker Pro and Server. FileMaker Server 16 does still have one concurrent connection from my understanding. I would see what use-case you fall most under than price out the two different packages of Teams vs Legacy and see if one gives you a better bang for your buck.

Hi, My experience has been positive for the most part. SSL issue: I believe that FileMaker Server 16 incorporates stricter SSL requirements, mainly the necessity to include the Intermediate SSL as well as the Signed SSL. For example, I had FileMaker Server working fine without Intermediate SSLs from GoDaddy, but when FileMaker Server 16 launched, I experienced the same error unless I included the Intermediate SSL that came with the bundle. So I wouldn't chalk that up to being an issue, but rather FileMaker making sure the server is more secure. Stranded Connections: I've been experiencing hanging connections since FileMaker Server 14. Not necessarily new, but would love to see it fully resolved. You can always try disconnecting the connections that are older than 24 hours through the Admin Console. Scripting: That sounds like your scripting may not be ensuring that the correct context is in use when deleting records. I would add some validation to make sure you are working in the right layout and with the correct found set. If your script was ran locally from a button on a layout, FileMaker Pro will know what context you are running the script in, but if you introduce PSOS without telling the script to go to the correct layout, or re-obtain the found set, it's going to give you bad results. Also, note that any OnFirstWindowOpen script triggers will execute when running PSOS, so make sure those scripts have some sort of catch for If [ PatternCount ( Get ( SystemVersion ) ; "Server" ) ] to Exit Script. That way you aren't getting put in a different context by an opening script. Though I don't know your scripting, so maybe you already have this in place. I personally haven't had any issues with PSOS on FileMaker Server 16. I would recommend adding some logging to your PSOS scripts to find the true cause. IMO, FMS 16 has some good security measures and the Save As PDF and new API are awesome. I would just suggest a little more troubleshooting before giving up on it - Jeff