HCS Blog

Prior to macOS Sierra if you wanted to find out whether or not a Caching Server is running on your network you could open up the Console.app and search for "AssetCache" in the logs. This no longer works in macOS Sierra.

Now in Sierra you can use a new tool: AssetCacheLocatorUtil
Enter this command in the Terminal.app and watch it give you detailed information.
It will, in a very verbose manner, tell you if and where a Caching Server is located. It even indicates if "personal caching" is supported. What is personal caching? Simply put it's the server caching personal iCloud data.

To learn more about caching server visit the link below.
https://help.apple.com/serverapp/mac/5.2/#/apd74DDE89F-08D2-4E0A-A5CD-155E345EFB83

Yosemite Server (Server.app 4.0) supports SMB3 by default. You can add encryption and digital signing as well.

To verify your connection to that specific share is encrypted, run this command in Terminal.app

I have seen where you try and run the changeip command for simple reasons. IE sudo changeip -checkhostname

But you get a message that the command can not be found.

If you install FileMaker Server web publishing services on an OS X Server machine it takes over the default http and https ports, 80 and 443 respectively.  What this means is that you cannot have FileMaker Server web publishing and built in OS X Server web services (ie. - Profile Manager) on the same machine.  Even if you then uninstall Filemaker web services, you may find that it holds on to the ports and you will not be able to load default OS X Server web pages.  You can usually check this by going to Activity Monitor, and search for httpd.  You may see multiple services owned by fmserver, which is the indication that FileMaker web services has taken over.

You can manually unload the processes but it will load itself up at next restart.  So try going to /Library/LaunchDaemons and look for com.filemaker.httpd.graceful.plist , com.filemaker.httpd.start.plist , and com.filemaker.httpd.stop.plist.  Remove them and restart.  Always back up these files first as a precaution.  I would also recommend stopping and starting OS X Server web services and/or Profile Manager and clearing your browser cache.

To Enforce naming in Profile Manager (Server.app 3.2.1)

1. The Device needs to be iOS 8