• No results found

Configuring file management tasks

In document Exam REF 70-411 Windows Server 2012 R2 (Page 100-105)

FSRM enables you to run file management tasks, which enable you to take actions on files based on the file’s properties. You can schedule tasks to run daily, weekly, or monthly; and to generate reports after the task runs. You can also have the task send a warning notification to users before it runs.

To create a file management task, select File Management Tasks in the console tree of the File Server Resource Manager console and click Create File Management Task in the Actions pane. The Create File Management Task dialog box shown in Figure 2-27 opens.

FIGURE 2-27 The Create File Management Task dialog box

Enter a name for the task and then click the Scope tab. Specify which folders the task will run against. On the Action tab, specify what action to take, as shown in Figure 2-28. You can set different settings depending on the action being taken.

ptg12909234

FIGURE 2-28 The Action tab of the Create File Management Task dialog box

On the Notification tab, you can set warnings and actions to take before the file manage-ment task runs, as shown in Figure 2-29. You can send email, enter an event in the event log, or run a custom command or script. You can set multiple notifications prior to the file man-agement task to provide plenty of warning.

ptg12909234

FIGURE 2-29 The Add Notification dialog box

On the Report tab, you can enable a log file, an error log file and an audit log file, along with generating a report. On the Condition tab, you can add conditions to limit the file management task to act only on files with specific property conditions. Finally, on the Sched-ule tab, you can specify how often a task runs. You can also set the task to run continuously against new files that match the property classifications in the condition.

You can also create file management tasks with the New-FsrmFileManagementJob cmdlet. This cmdlet uses an FsrmScheduledTask object, an FsrmFmjAction object, and an FsrmFmjNotification object. For details, see http://go.microsoft.com/fwlink/?LinkID=289420.

ptg12909234

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.

ptg12909234

Objective review

1. The company provides a public transfer share to allow users to easily share files. With-out using excess privilege, you have to ensure that all files are deleted after they have been on the server for 3 days. What PowerShell command should you run as part of the file management task?

A. get-childitem -recurse | where-object {$_.CreationTime -ge (get-date).Add(-3)}

| remove-item

B. get-childitem -recurse | where-object {$_.CreationTime -le (get-date).Add(-3)}

| remove-item

C. get-childitem -recurse | where-object {$_.CreationTime -ge (get-date).Add-Days(-3)}

| remove-item

D. get-childitem -recurse | where-object {$_.CreationTime -le (get-date).AddDays(-3)}

| remove-item

2. In the scenario of question 1, what command security should the script run as?

A. Local Service B. Domain Users C. Local System D. Protected Users

3. You need to allow users to store files for sharing with other users. These files are stored on the D:\UserShare folder of SRV2, which is shared as \\srv2\share. Each user’s use of the space is limited to 250 MB. When users reach 200 MB, they should be warned via email and the Administrator account should also be notified by email. How can you implement this?

A. Create an FSRM quota on the D:\UserShare folder of SRV2 based on the Monitor 500 MB Share template, but change the Limit to 250 MB.

B. Create an FSRM quota on the D:\UserShare folder of SRV2 based on the 200 MB Limit With 50 MB Extension template.

C. Create an FSRM quota on the \\srv2\UserShare share based on the Monitor 500 MB Share template, but change the Limit to 250 MB.

D. Create an FSRM quota on the \\srv2\UserShare share based on the 200 MB Limit Reports To User template, but change the limit to 250 MB.

ptg12909234

Objective 2.3: Configure file and disk encryption

Windows Server 2012 R2 supports two different types of file and disk encryption: BitLocker and the Encryptying File System (EFS). BitLocker uses a Trusted Platform Module (TPM) ver-sion 1.2 or later when available to provide whole-disk encryption, but can use a removable USB key when a TPM is not available. EFS is useful for user-level file and folder encryption on both client computers and remote file servers.

This objective covers how to:

Configure BitLocker encryption

Configure the Network Unlock feature

Configure BitLocker policies

Configure the EFS recovery agent

Manage EFS and BitLocker certificates, including backup and restore

In document Exam REF 70-411 Windows Server 2012 R2 (Page 100-105)

Related documents