Below, you will find a list of all known software or configurations that can result in some loss of Files Connect functionality.
If you have more than one Active Directory server, and Files Connect is installed on your domain controller, you will encounter AD replication issues by doing the Network Reshare and Kerberos authentication steps.
Users are unable to input a password for protected volumes on computers running Mac OS X El Capitan (10.11) and higher. This is an issue in Mac OS X 10.11 and higher.
Volumes with volume passwords set in Files Connect cannot be mounted via Finder.app, and prevent browsing the server on which they are located.
Note: The volume password is distinct from the password that a user needs to access the server.
Files Connect can send messages to AFP connected clients but Mac OS X 10.9 and above no longer natively display these server messages.
In versions older than 10.6.3 the Filename Policy Violation Report depends on a catalog index, which doesn't exist for reshare volumes.
The Files Connect service can’t be sharing data at the same time as a DFS Replication job is run on that data. If it is, there is a risk of corrupting data.
Print accounting is not supported on 64 bit operating systems.
The print service does not support bi-directional communication. If Files Connect cannot find an unidirectional print driver, you will be unable to use Files Connect printing.
Expanding local drives while they are being shared via Files Connect is not supported. The recommended procedure is to remove all affected Files Connect volumes from Files Connect, expand the desired drive(s) and re-add the volumes in Files Connect.
When using Files Connect Network Reshare feature to share a DFS namespace, attempting to move folders from one root folder to another will result in an error.