I have a client who has a handful (6) of Mac Pro machines running mostly Adobe CC and have been connected to a Mac server (Mac Mini running Sierra and Mac Server app) for a number of years. Lately, nothing but issues with users losing access to their own files and not being able to open each others files. Permissions on the files seemingly change on-the-fly, and when someone suddenly gets "can't open file because it's already open or not accessible" type messages, we go in and refresh the permissions and most of the time that fixes it. But, we're wasting a ton of time doing this. So... We started looking at replacing the aging Mac "server" with a Windows server. Since Apple is losing interest in anything "Server", it seems it's destined to disappear. I've setup a "test" Windows Server 2016 and shared out a volume and connected the Mac clients to it over SMB, and they did some testing and it seemed to work OK, with no permissions issues. So, once I make the switch, I'm wondering if anyone might have been down this road and have any tips to help ease the transition? It seems we will have issues with CC files because the many parts of the CC project will be at a new path, so the users will have to re-link the objects again. I saw that Apple even stores the protocol used as part of the file path, such that if a file is at afp://ourserver/clientfiles, even with the same server name and path, it will not find the file at smb://ourserver/clientfiles. We found this out when testing the SMB protocol on the Mac clients on the Mac server. I wondered about putting Apple File Protocol software on the Windows server (Acronis Files Connect) but is SMB as bad as Acronis makes it sound? Their software is crazy expensive, so it's not really an option for a small shop. If anyone has been down this path and has any suggestions or advice, it's greatly appreciated. Thanks.