Configure file and print services - Administering Windows Server 2012 R2 - page 84

Thought experiment
Using FSRM to manage file system usage
In this thought experiment, apply what you've learned about this objective. You can
find answers to these questions in the “Answers” section at the end of this chapter.
You are the network administrator for TreyResearch.net. The company uses a single
main public share as a file-sharing resource to allow users to share and swap files,
as well as to host shared internal corporate resources. Lately, there has been a large
increase in file system usage, and adding additional disk space isn't an easy option
on the hosting server.
1. What reports can you use to get a clear understanding of which files are taking
up the most space and who their owners are?
2. Could you use quotas to control how much space each user is allowed to use on
the share?
3. What file screens could you put in place to ensure that inappropriate files are not
saved on the share?
4. How could you use file screen exceptions to allow the saving of sanctioned files
even if they might violate the file screens in question 3?
Objective summary
■ The FSRM role can be installed on both full installations and Server Core installations.
■ Quotas, which can be hard or soft, can act on a specific path or on a path and all
subfolders of the path.
■ Quotas can be created from scratch or can be based on quota templates.
■ Notification actions include sending an email, entering an alert in the event log,
running reports, and executing a command.
■ Executing commands based on a quota, file screen, or file management task should be
done with the least privilege possible to accomplish the goal.
■ File screens can be active or passive.
■ File screens are based on file name patterns, not on file content.
■ There are 10 standard storage reports,
■ Storage reports can run on a schedule or can be run interactively.
■ File management tasks can be set to run on a schedule, or continuously on new files.
■ File management tasks can be set to notify users days before the task actually runs to
prevent data loss.