On a Windows file server, files and folders that are owned by built-in Active Directory groups (such as the “Administrator group”) are not synchronized to Filr as part of the normal Net Folder synchronization process.
If you have files and folders that are not synchronizing due to this limitation, change the owner of the entry on the NTFS file system to be a user rather than a group. Doing so ensures that the entry is synchronized to Filr.
There are many ways to configure Windows file servers to support user Home folders. In general, folder sharing from Filr for Active Directory users works successfully. However, if NTFS permissions on a Windows file system are not set up in a way that is compatible with Filr, when Active Directory users share a folder from their Home folder with another user, files in the shared folder might not be visible.
To ensure that files within a folder (in an Active Directory user’s Home folder) are shared when a folder is shared, ensure that inheritance is disabled for each user’s Home directory. You must also explicitly grant rights for subfolders in the Home directory.
In addition, Filr supports Microsoft’s Access Based Enumeration (ABE), which is available on Windows Server 2003 through Windows Server 2012. Home folder shares work properly when the Windows file system is set up using ABE.
If the OES file server is online and Filr can communicate to that server through NCP or CIFS, Filr might retrieve incorrect information from that server if it has internal or system errors (such as NDSD being down). If Net Folders do not appear to have the correct contents in Filr, check the health of the file server and ensure that it is configured and running as expected.
DFS junctions on Windows and OES are not currently supported in Filr. Support for this feature will be available in a future Filr release.
If users have file system rights to a folder on an NSS volume, and the Filr administrator configures a Net Folder and grants the users rights to access the Net Folder within Filr, users cannot see the Net Folder in Filr if:
There are no file system trustees assigned to the volume
There are no eDirectory trustees present (including treeadmin and ncp server)
If a user moves or renames a file directly from the file server (instead of using a Filr client to do the move or rename), any shares that are associated with that file in Filr are removed. This means that users who gained access to a file via a share in Filr no longer have access to the file if the file was moved or renamed from the file server. Additionally, the file is not displayed in users’ Shared by Me and Shared with Me views.
If this situation occurs, files must be re-shared in Filr.
When testing the connection for a Net Folder Server, the test connection is successful when the path in the
field contains forward slashes (/). However, files and folders are not successfully synchronized to Filr through the Net Folder Server. Instead, backslashes (\) must always be used in the field when configuring a Net Folder Server.