Important information

12 Important Information
• The information about the number of open files is not shown correctly
after a session is closed and reopened.
The number of Open Files section under Share Folder Management →
Shared Folders → Sessions is not shown correctly after the session is closed
and re-established. The number of open files still shows 0 after the same
session is closed and reopened. It shows that a session has been established
between the Network Attached Storage (NAS) system and the shared
folder/file but does not update the number of open files as 1.
The operating system is fully functional even though the session is not
updated properly.
• The File Screening management feature of FSRM does not block a file
when a user renames and copies the blocked file.
File Screening does not block a file after a user renames and copies the
blocked file into a specified folder or volume.
File Screening checks only for the filename during the file screening, when
a user tries to copy the blocked files. If a user renames the blocked file and
tries to copy it, File Screening does not block the file; it allows the user to
copy the file into the specified folder or onto a volume.
This issue occurs with both Active and Passive screening types.
According to Microsoft, this behavior is not an issue, but is working as
designed. Microsoft does not have plans to release any fixes or
workarounds for this issue.
• Multiple clients are allowed to open and edit the same shared file
simultaneously.
Multiple clients are allowed to open and edit same shared file
simultaneously when they are accessed from different client systems.
If you create a folder, copy a text file on the NAS system, and share the
folder with multiple users that have
Full control or Read + change
permissions on that folder, and then you open the text file, you can log in
from one client system, using the user ID that has
Full control or Read +
change
permission and access that text file. You can modify the file and
save that file from the client system. This issue does not occur when the
user opens the already opened text file from the client system. The client
user is able to delete that file when the file is opened by some other user on