NTP Software Quota & File Sentinel™ - AxanTech · 2009. 6. 13. · 8 NTP Software Quota & File...

NTP SoftwareQuota & File Sentinel™

Version 4.0

Installation andUser’s Guide

ii

CopyrightCopyright © 2002 NTP Software. All rights reserved.

Quota & File Sentinel, Enterprise Application Services Extension, and the EASE logo are trademarks of NTP Software.

Windows, Windows NT, and Windows XP are registered trademarks of Microsoft Corporation.

Product and company names mentioned herein may be trademarks or registered trademarks of their respective companies.

Document #5598EFLast Updated March 11, 2002

iii

Preface ...........................................................................................................7

Introducing Quota & File Sentinel ................................................................9What is Quota & File Sentinel?............................................................................ 10What Can I Do With Quota & File Sentinel?......................................................... 11How Does Quota & File Sentinel Work? .............................................................. 13Quota & File Sentinel and EASE ......................................................................... 13What’s New in Quota & File Sentinel 4.0............................................................. 14

Installing Quota & File Sentinel...................................................................17Before You Install .............................................................................................. 18System Requirements ......................................................................................... 18Part I: Basic Installation ...................................................................................... 19Installing EASE and Quota & File Sentinel............................................................ 19Upgrading from Quota & File Sentinel (QFS) 3.0 to QFS 4.0 ................................ 26Part II: Advanced Installation Tasks...................................................................... 28Distributing Quota & File Sentinel ....................................................................... 28Installing Quota & File Sentinel on a Microsoft Cluster Server ................................ 31Installing on a Cluster Server First........................................................................ 32Uninstalling Quota & File Sentinel ....................................................................... 33Upgrading Evaluation Versions to Production Versions.......................................... 34

Configuring Quota & File Sentinel..............................................................35Overview of Configuring Quota & File Sentinel..................................................... 36Configuring Mail Messaging ................................................................................ 36Configuring Popup Messaging............................................................................. 41Configuring for SNMP........................................................................................ 42Configuring System Security ............................................................................... 44Removing users and groups from the list .............................................................. 45Fine Tuning Quota & File Sentinel for Maximum Performance............................... 45

Quota & File Sentinel v4.0Table of Contents

iv

Using Quota & File Sentinel .........................................................................47Part I: Basic Tasks .............................................................................................. 48Overview of Creating Policies .............................................................................. 49Creating Disk Quota Policies ............................................................................... 50Setting General Properties .................................................................................. 52Setting Quota Limits ........................................................................................... 52Setting Thresholds.............................................................................................. 54Setting the Files and File Types to Manage (Disk Quota “File” Policies Only)............ 62Setting Directories or Shares ............................................................................... 63Setting Users and Groups.................................................................................... 63Setting Other Recipients ..................................................................................... 64Creating File Control Policies .............................................................................. 65Setting General Properties .................................................................................. 66Specifying the File Patterns to manage ................................................................. 66Setting Control Options ...................................................................................... 67Setting Directories and Shares ............................................................................. 69Setting Users and Groups.................................................................................... 69Creating File Removal Policies ............................................................................. 71Setting General Properties .................................................................................. 71Setting How Often to Remove Files (Lifetime Tab) ................................................ 72Setting Thresholds.............................................................................................. 73Setting Directories or Shares ............................................................................... 77Setting Users and Groups.................................................................................... 78Setting Other Recipients ..................................................................................... 79Creating Server Policies ...................................................................................... 80Part II: Advanced Tasks....................................................................................... 81Suspending Policy Enforcement ........................................................................... 82Using the Overdraft Feature (disk quota and file removal policies)............................ 84Using Variables in Messages ................................................................................ 85Setting Object Status Indicators............................................................................ 87

Creating Reports ..........................................................................................89What Is the Report Module? ................................................................................ 90Installing the Report Module ................................................................................ 90Starting the Report Module ................................................................................. 91Configuring the Report Module............................................................................ 92Creating New Reports ........................................................................................ 93

v

Copying Reports................................................................................................ 96Printing Reports................................................................................................. 97Modifying Reports.............................................................................................. 98Exporting Report Data ..................................................................................... 102

Understanding EASE ..................................................................................103What Is EASE? ................................................................................................ 104Hierarchy Configuration ................................................................................... 108Remote Installation .......................................................................................... 110Managing the Hierarchy ................................................................................... 111Managing Security ........................................................................................... 115Managing EASE Networks ................................................................................ 117

Index...........................................................................................................121

vi

Preface

Thank You

Thank you for purchasing NTP Software Quota & File Sentinel with EASE technology. Quota & File Sentinel is an application that lets you easily implement and maintain appropriate storage management strategies and policies throughout your enterprise.

What’s In the Box

The Quota & File Sentinel box contains:

• Quota & File Sentinel CD-ROM

• Registration card

• Technical Support card

• Quota & File Sentinel Installation and User’s Guide

If an item is missing, or in the unlikely event the CD-ROM is defective, please contact the Fulfillment Department at NTP Software, Monday through Friday, 8:30 AM to 5:00 PM Eastern Standard Time, (603) 622-4400.

8 NTP Software Quota & File Sentinel Installation and User’s Guide

About This Guide

This guide describes how to install, configure and use NTP Software Quota & File Sentinel with EASE. Some users may prefer to use the Quota & File Sentinel online Help to learn how to use this product. Others may prefer to use this manual.

Getting Help

If you have difficulty installing or using Quota & File Sentinel with EASE, you can get help using any of the following methods:

• Read this manual

• Search the online Help

• Visit the NTP Software Customer Support web site: http://www.ntpsoftware.com/support

• Send e-mail to NTP Software Customer Support at [email protected]

• Call NTP Software Customer Support, Monday through Friday, 8:30 AM to 5:00 PM Eastern Standard time, at (603) 626-0986

Note: When contacting customer support, if you purchased a customer support contract, be sure to include your customer support contract number.

NTP Software Professional Services

Not sure how to deploy Quota & File Sentinel in your specific environment? Don't have time or bandwidth to install Quota & File Sentinel? Need assistance or training? Let NTP Software's certified Professional Services Engineers assist your organization by coming to your site and aiding you in the rapid deployment of our products. Our engineers can help your organization in whatever areas you request, including planning, installation, training, customization and much more. Our engineers are experts in our solutions so you don't have to be. This allows you to work on other critical issues in your organization. Please visit our Professional Services web site at http://www.ntpsoftware.com/proserve or call us for more information.

Chapter 1

Introducing Quota & FileSentinel

This chapter introduces you to NTP Software Quota & File Sentinel.

Ahead in this chapter

• "What is Quota & File Sentinel?" on page 10

• "What Can I Do With Quota & File Sentinel?" on page 11

• "How Does Quota & File Sentinel Work?" on page 13

• "Quota & File Sentinel and EASE" on page 13


What is Quota & File Sentinel?

NTP Software Quota & File Sentinel™ lets you control how much disk space your users consume, manage what they put on your servers, and get real-time data on storage performance and the loads placed on that storage. It lets you create and enforce usage policies so you can preserve and optimize system performance and availability for everyone.

With Quota and File Sentinel, you select the rules you want to implement for controlling quotas and file access. It's easy to define the users, areas, files, and file types you want to control. You do this by creating disk quota policies and file control policies.

Disk quota policies let you assign space limits to users and groups of users. There are two types of Disk Quota polices: Folder and File.

• A Folder policy is one where you apply quota limits to entire folders. For example, you could create a Folder policy that says "when the folder or share reaches 100 MB, deny writes"

• A File policy is one where you apply quota limits to the size of particular files or file types within a particular folder. For example, you could create a file disk quota policy on a directory called C:\users that limits the size of all .doc files within that directory to 100 MB.

You can set multiple (up to 200) threshold levels for each type of policy. For example, you can set a threshold level at 70% of a quota limit, and when a user managed by the quota policy reaches that threshold, they automatically receive a message saying they are at 70% of their quota limit. For each threshold, you can choose to send popup messages and/or email messages to users, and you can choose who to send the message to.

You can also exempt users and groups from any policy. For example, if you want everyone in the group "Administrators" to be subjected to the rules of a certain policy except user "jsmith", you can do that. You also select the directories and/or shares you want to manage, and most importantly, you set a quota limit for that policy.

File control policies let you restrict access to specific files or file patterns (types). This lets you protect your system by not allowing opening of, say, .MP3 files or VB script files for certain users, groups, and areas. You can also select to control writing to or creating certain files or file types.

File removal policies let you automatically delete files from folders or shares that Quota & File Sentinel is managing after x hours, days, weeks, or months. This type of policy is especially useful for managing temporary contract workers. For example, you may have a contract employee who will only be working at your site for six weeks. After the six weeks, you want to clean up any files left behind by the user. You can create a File Removal Policy that will automatically remove the files after the six weeks are up AND that puts a quota restriction on the contractor for the duration of their stay.

You can configure certain options about the deletion. For example, you can choose to delete files based on their creation date, modified date, or their last accessed date. The quota policy begins the moment a user creates a file.

What Can I Do With Quota & File Sentinel? 11

NTP Software Quota & File Sentinel gives you two levels of protection - at the user level ("Who do you want to control"?) and at the directory/share level ("What areas do you want to control?").

What Can I Do With Quota & File Sentinel?

Limit the size of network objects for all users - You can define a maximum size for directories and shares. Quota & File Sentinel can block any WRITE by any user that will exceed that limit. You can define actions and notification options for when the object passes a limit threshold, both exceeding a threshold and going below a threshold.

Limit the size of network objects for object owners. In addition to object limits, you can set limits on objects on the basis of object ownership (Windows account IDs).

Notify - Quota & File Sentinel has an internal mail client that can send email notifications to object owners, object users, and/or anyone you want to include on a notification list. In addition to email, QFS can send popup notifications in real-time. Furthermore, whenever a Deny Write threshold is reached, the operating system automatically generates a notification message to the user performing the operation, informing them that they are out of disk space.

Set actions and notifications for a wide range of limit conditions - You can configure up to 200 thresholds for each limit. Each threshold can have its own notification options, including customized message text for each different type of recipient.

Automatically include new users - Because Quota & File Sentinel uses Windows account IDs and groups to set disk space limits, adding a new Windows account ID to a group automatically applies Quota & File Sentinel limits on the user.

Dynamic Quotas - This self-maintaining feature enables administrators to control new users without the need to reassign quotas or file control settings. An original quota is put on a parent object. Every time a directory is created under that object, the quota is automatically applied.

Combine policy members - A Quota & File Sentinel disk quota policy defines a size limit, notification settings, and the objects under control of the policy. You can also combine the policy objects, which expands your options for managing disk space.

File control - Using file control policies, you can identify particular files or file patterns (file types) and prohibit certain actions on them (reads, writes, etc.). You could use this feature to screen for .MP3, for example, and configure the file control policy so that no one could write to .MP3 files. Perhaps you want to minimize the risk of external viruses invading your site. You can do this by creating file control policies that prevent users from saving VB script files received in an email.

Exempt users from policies - For all policy types (that is, disk quota policies, file control policies, and file removal policies), you can create an exception list of account IDs. This enables you to specify user accounts and groups that you want to be exempt from control by the policy.


Keep track of your disk status - The Quota & File Sentinel Report Module lets you produce fully formatted reports on the status of your monitored disks. You can create custom formatted reports, web-ready reports, and even export report data into other report engines.

Distribute Quota & File Sentinel remotely - With the remote installation feature of EASE, you can deploy Quota & File Sentinel throughout your network without leaving your seat.

How Does Quota & File Sentinel Work? 13

How Does Quota & File Sentinel Work?

The heart of Quota & File Sentinel is the Quota & File Sentinel Service and the Quota & Sentinel File System Filter.

The Quota & File Sentinel Service monitors disk operations and can enforce limits on the amount of disk space allotted to users and objects. The service works with the file system filter, which monitors file access operations (reads, writes, or saves) and can block them according to the choices configured in the file control policy.

You manage Quota & File Sentinel through the EASE Admin program. The Quota & File Sentinel admin client runs within the EASE environment. EASE has a feature called property inheritance that enables you to manage one set of Quota & File Sentinel configuration parameters and have them affect multiple Quota & File Sentinel servers. See the EASE online help for more information on EASE property inheritance.

Quota & File Sentinel and EASE

Quota & File Sentinel operates within the NTP Software Enterprise Application Services Extension™ (EASE) environment. EASE brings enterprise network management to server-based applications. You administer Quota & File Sentinel and all EASE-enabled applications from the EASE Admin interface. Each server where EASE is running holds an identical data store, which is updated whenever you make a change to the EASE environment or change a setting in an EASE-enabled application. EASE is installed along with Quota & File Sentinel.

The EASE environment gives you enterprise management capabilities for your EASE-enabled applications. The EASE property inheritance feature enables you to configure once for use in many places. Drag-and-drop functionality means that when your company reorganizes, you can react immediately. Remote installation allows you to add Quota & File Sentinel to new servers remotely.

For more information about EASE, see the "Understanding EASE" on page 103, or refer to the EASE online Help.


What’s New in Quota & File Sentinel 4.0

Here’s a brief summary of the new features and enhancments you can look forward to in Qutoa & File Sentinel 4.0.

• Distinguished paths (EASE related) -Policies now show the full location and origin of the policy. If you are 4 containers deep on an inherited policy, it will show you the full path from where the policy was inherited.

• EASE Security Properties - EASE Security properties are now enforced on every machine to which they are replicated.

• Event Viewer - The service start up message in the event viewer now indicates which restrictive mode QFS is started in. The least restrictive mode is the default.

• File Removal Policies - Automatically delete files from folders or shares that Quota & File Sentinel is managing after x hours, days, weeks, or months.

• File Quota Policies - Create policies that limit the size of particular files or file types within a particular folder. For example, you could create a file quota policy on a directory called C:\users that limits the total size of all .doc files within that directory to 100 MB.

• File Filter Version - Now appears in the help/about screen. The information varies depending on the server environment you are located in when you open help/about (the information is specific to each server).

• HTML Email - QFS 4.0 now supports HTML email and includes an HTML editor that you can use when defining thresholds and messages for each policy.

• Inherit Directory Connector Properties - When specifying email recipients on a policy, if you enter a user name, QFS can automatically determine the full extension for that user using one of two methods:

– SMTP - Appends the domain name of your mail server.

– LDAP - Points to an exchange server that can resolve the correct email address for the user.

You specify the STMP domain name and the LDAP information on the Quota & File Sentinel Configuration dialog box Email Configuration and Misc. Options tabs respectively.

• Last Modified date time added to policies - Created date / time and last modified date / time added to General tab of every policy.

• Policy Owner / Last Modification - Policies now track who created the policy and who was the last person to change the policy. The Person who created the policy is the policy's "owner". This policy owner never changes. The "Last Modified by:" user is the login name of the person who last modified the policy.

• QFS Service Account - The QFS Service account is no longer automatically exempted from a policy. If you want QFS to specifically manage that account, you

What’s New in Quota & File Sentinel 4.0 15

can reference it on the Managed Users and Groups tab, or if you want to exempt it, you can place it on the Exempt Users and Groups tab for each policy.

• Quotas - Ability to create quotas relative to percent of volume and percent of other quotas. Ability to create file quota policies on directories and share.

• Reminder Messaging - You can now configure QFS to send daily reminder messages to users who have exceeded their quota limit.

• Right Click Menu - There is an enhanced right click menu available from any Policy type. The submenu gives you the option of creating a new: "Folder Policy Using Directories", "Folder Policy Using Shares", "File Policy Using Directories", and "File Policy Using Shares".

• Security enhancements - There is a Security Tab on the Quota & File Sentinel Configuration dialog box that lets you implement security restrictions on users and groups at many different levels within the EASE hierarchy. The three security options are "Full Control", "Read", and "No Control".

Also:

– Now when there is a security conflict between EASE & QFS, EASE wins.

– The Service account is exempt from security settings when logged on as a user.

– The owner of a policy always has full access to that policy, regardless of the security setting assigned him or her.

• Separated email / popup messaging - Email and popup text is now separated so you can enter a unique message for each of them.

• Tuning Properties - You now have control over how QFS sizes objects each time it starts (sizing refers to checking the size of each object managed by a QFS policy). The two options are "Low Impact Sizing" (for faster startups) and "High Impact Sizing" .


Chapter 2

Installing Quota & FileSentinel

This chapter tells you everything you need to know to install Quota & File Sentinel. It begins with preliminary information such as system requirements and some “before you install” notes. It then provides step-by-step instructions for installing Quota & File Sentinel. In addition to the basic installation instructions, this chapter also contains information for performing more advanced installation tasks, such as distributing Quota & File Sentinel and installing in a cluster environment.


• "Before You Install" on page 18

• "System Requirements" on page 18

Part I: Basic Installation

• "Installing EASE and Quota & File Sentinel" on page 19

• "Upgrading from Quota & File Sentinel (QFS) 3.0 to QFS 4.0" on page 26

Part II: Advanced Installation Tasks

• "Distributing Quota & File Sentinel" on page 28

• "Installing Quota & File Sentinel on a Microsoft Cluster Server" on page 31

• "Installing on a Cluster Server First" on page 32

• "Uninstalling Quota & File Sentinel" on page 33

• "Upgrading Evaluation Versions to Production Versions" on page 34


Before You Install

Quota & File Sentinel is integrated with Windows NT/2000 security environment so there is no need for you to perform pre-installation tasks. For example, if your environment includes primary and backup domain controllers, Quota & File Sentinel identifies them and automatically creates the proper service account during installation.

You must log on with an account that has Administrator privileges to install and administer Quota & File Sentinel. You can configure security within EASE Admin. For more information, see the EASE Admin Help.

About Service Accounts and Privileges

To ensure that you do not run into privilege problems between computers, we recommend that the EASE service account ID be the same on each of the EASE machines. This is a recommendation, not a requirement. When you install EASE on a server, the Setup program makes any changes to the account profile to ensure that EASE services can communicate with each other.

The Quota & File Sentinel service account can, but does not have to be, the same as the EASE service account. Quota & File Sentinel communication among machines is actually accomplished by EASE, therefore changes to account profiles are not required.

Quota & File Sentinel Setup ensures that the account you use as the Quota & File Sentinel Service account has the correct privileges. The Quota & File Sentinel Setup creates the new account if necessary and adds the service account to the Administrators group.

System Requirements

Make sure the system you install Quota & File Sentinel on meets the following minimum requirements:

Hardware: Intel 333 MHz processor

Operating System: Windows NT® 4.0 (SP6a recommended), Windows® 2000 (SP2 recommended, or Windows XP

Memory: 64 MB RAM recommended

Browser: Internet Explorer 4.01a (or later)

Resource Requirements for program files:

4.5MB disk space and 6MB memory for EASE4.5MB disk space and 4.5MB memory for Quota & File Sentinel

Part I: Basic Installation 19

Part I: Basic InstallationThis section contain basic installation instructions. After you successfully install Quota & File Sentinel on your primary server, you may want to proceed to some of the advanced installation tasks described in Part II on page 28.

Installing EASE and Quota & File Sentinel

This procedure assumes you are installing Quota & File Sentinel in a non-cluster environment. Refer to Installing Quota & File Sentinel on a Microsoft Cluster Server for instructions on installing in a Microsoft Cluster Server environment.

To install Quota & File Sentinel:

1 Log into your Windows NT or Windows 2000 server using an account with Administrator privileges.

2 Load the Quota & File Sentinel CD into the server’s CD-ROM drive.

After a few moments, the installation start window appears. If the window does not appear, it could mean that the autorun feature is disabled on your computer. To start the installation manually, in Windows Explorer, click the CD-ROM drive, and then double-click Setup.exe.

3 When the installation window opens, click Install NTP Software Quota & File Sentinel.

If you have not previously installed EASE on this machine, or if you have an older version of EASE installed, you will receive a dialog box prompting you to install EASE before continuing.


Installing EASE

4 Choose Yes to launch the EASE Setup program (only appears if EASE isn’t already installed or an older version of EASE is installed).

5 Follow the directions that appear in the EASE Setup program dialog boxes.

• Click Next to proceed to the next dialog box. Click Back to move to the previous dialog box.

• The EASE Setup lets you choose which EASE components to install. The default, and recommended action is to install the EASE Admin and the EASE Service, so just accept these if they are selected. Select them if they are not selected.


• The Service Account dialog box asks you to specify an account ID under which the EASE Service will run. The account ID you use for the Service Account must have Administrator privileges, including the right to log on as a service. Setup defaults to the current account ID. We recommend you specify new account information to ensure that the account has the correct permissions.

Note: EASE servers operate within your existing Windows security environment. EASE can operate within any NT domain model (single, master, multiple-master, complete trust) or within a hybrid model as long as the accounts that the EASE services run under have appropriate permissions to communicate with each other. To ensure communications between EASE machines, we recommend that you use a service account that is created in a master domain within the NT domain infrastructure.

• If you specified an Account name for the EASE Service account that does not exist, you receive the following prompt: “Do you wish to create the account: “account_name”? The account will be granted the following rights: Log on as a Service. The account will be added to the following groups: Administrators.” Click Yes.

Setup creates the new account and adds the new account to the Administrators group.


• Setup asks if this is an initial installation or an addition to an existing EASE network. If this is the first EASE installation on your network, choose First time installation in the enterprise.

To have this EASE installation join an existing EASE network, choose Adding to an enterprise installation, click Next, and specify the name of any other computer running EASE service. The existing EASE computer can be running Quota & File Sentinel or some other EASE application, but the EASE service must be running.

Note: If you are joining an existing EASE network, be prepared to wait while the installation process copies the EASE data from the remote EASE server. Depending on how much data you have, the process could take a few minutes.

• During an initial installation only, you are prompted for the name of the Organization you want to see at the top of your EASE hierarchy, and the Location, which becomes the name of the container beneath the organization


in the hierarchy. You can easily change these items at any time once you have EASE up and running.

Installing Quota & File Sentinel

After the EASE installation completes, the Quota & File Sentinel installation continues. As with the EASE installation, you can choose the Quota & File Sentinel components to install. Just accept the defaults to install both the Quota & File Sentinel Admin and the Quota & File Sentinel Service.

Note: If you are installing on a Windows NT system, you might be prompted to install ADSI (the Microsoft Active Directory Service Interfaces). Answer Yes to the prompt, because having ADSI installed is a requirement for Quota & File Sentinel. If you want more information on ADSI, go to http://www.microsoft.com/windows2000/techinfo/howitworks/activedirectory/adsilinks.asp.


• When you are prompted to enter your Quota & File Sentinel product serial number, enter the serial number that appears on your Quota & File Sentinel product registration card. If you enter alphabetic characters in lower-case, they are automatically converted to upper-case as you type them in.


• You are asked whether to specify an account to use, or use the built-in system account. Because the built in system account is local to this machine, the following features are disabled if you choose it:

• The ability to specify UNC paths in policies

• Active Directory / LDAP email address lookups

• User account lookups across domains

• The Quota & File Sentinel service account can, but does not have to be, the same as the EASE service account. The Setup program ensures that if you specify an account to use, it has the correct permissions for the Quota & File Sentinel Service. Also, if you specify an account that doesn’t exist, setup creates the new account, and adds the service account to the Administrators group.

If you chose “Specify an account to use”, when you are prompted for a service account ID, you can use the same account you used for the EASE service, or you can specify a new one.

6 Finish answering the questions about where to place the Quota & File Sentinel program group. Click Finish to complete the installation.


Upgrading from Quota & File Sentinel (QFS) 3.0 to QFS 4.0

The basic procedure for upgrading from QFS 3.0 to QFS 4.0 is as follows:

• Perform a complete QFS 4.0 upgrade on your primary QFS 3.0 server from the QFS CD.

• Install and run the EASE Upgrade Manager from the server you just upgraded and push EASE out to your other QFS servers (if you don't have the EASE Upgrade Manager, contact NTP Software Technical Support).

• Run QFS setup on the other QFS servers from the QFS CD.

Note: If you upgrade your primary QFS server, but not your other QFS servers, that primary server is no longer communicating correctly with the other servers. It's important that you upgrade all your QFS servers at the same time.

Upgrading your primary QFS 3.0 Server


2 Insert the Quota & File Sentinel CD into the server's CD-ROM drive.


3 Follow the directions that appear on screen to upgrade EASE and QFS.

Refer to "Installing EASE and Quota & File Sentinel" on page 19 for details about the installation process.

Installing and running the EASE Upgrade Manager

Note: If you don't have the EASE Upgrade Manager, contact NTP Software Technical Support.

From your primary QFS machine (the one where you just upgrade to QFS 4.0):


2 Run the Upgrade Manager's setup.exe program.

3 Follow the directions that appear on screen to complete the installation.

After the installation is complete, choose Program Files, NTP Software Quota & File Sentinel, EASE Upgrade Manager from the Start menu.


The Upgrade Manager main window appears.

The left side of the main window displays the other EASE servers in your hierarchy, and the version of EASE they're running.

4 Select the EASE servers you'd like to upgrade from the left hand list of Available Servers.

If you have many machines to upgrade, we recommend selecting three at a time. This way you don't tie up network bandwidth and you easily troubleshoot any issues that may arise during the upgrade.

5 Click the "right" arrow to move the servers to the "Servers Selected for Upgrade" list on the right hand side of the Upgrade Manager.

6 Click Upgrade All to start the upgrade.

Upgrading QFS on the rest of your servers

After pushing the EASE upgrade out to your QFS servers as described above, you can upgrade QFS as follows:

1 Log into each server using an account with Administrator privileges.

You must physically run the QFS setup program from each server.

2 Insert the Quota & File Sentinel CD into the server's CD-ROM drive.


3 Follow the directions that appear on screen to finish the QFS installation.

Refer to "Installing EASE and Quota & File Sentinel" on page 19 for details about the installation process.


Part II: Advanced Installation Tasks

This section contains instructions on how to perform more advanced installation tasks, such as distributing Quota & File Sentinel throughout your enterprise. Also included are instructions on how to install Quota & File Sentinel in a cluster environment.

Distributing Quota & File Sentinel

EASE Technology lets you install ("push") Quota & File Sentinel on remote network servers. It does not matter if those servers are located in the same room or halfway around the world. If the remote server is accessible through your network and you have the proper administrative privileges to install applications, you can install both EASE and Quota & File Sentinel on that computer.

Remote Installation Requirements and Notes:

• If you have configured (changed) EASE security, the account you use when you remotely install Quota & File Sentinel must have Write and Create Children permissions to the location in the EASE hierarchy where you are adding Quota & File Sentinel. For more information on EASE security, see the EASE online Help. If you have not changed any EASE security settings, then you do not have to do anything about these permissions because the defaults are set appropriately.

• You must have a corporate or evaluation license in order for remote versions of Quota & File Sentinel to work. If you have an individual Quota & File Sentinel License, you'll be able to remotely install QFS on other machines, you just won't be able to start it on those machines. Likewise, if you have a corporate license for, say, 50 machines, you'll be able to remotely install QFS to 51, 52, 53, etc machines, you just won't be able to run it on more than 50 machines at once.

• In order to "push" (install) QFS to a server in Domain B from a server in Domain A, where Domain B and Domain A have a 2-way trust with each other, you'll need to first do the following:

1. Add Domain B's Domain Administrator to Domain A's Domain Administrators group.

2. Log into Domain B as Domain Administrator from the Domain A server you are pushing from.

You can then proceed with the "push" installation as described in the instructions below. After the installation is complete, we recommend removing Domain B's Domain Administrator from Domain A's Domain Administrator group.

• In order to "push" (install) QFS to a server in Domain B from a server in Domain A, where Domain B and Domain A have no trust with each other, you'll need to login as a Domain B local administrator from Domain A before pushing QFS. When the EASE installation program prompts you for the name of the EASE Service account to use on the machine in Domain B, make sure you use the exact same account (name and password) you used for the EASE Service on the machine in Domain A. If the account doesn't exist on the Domain B machine, the installation program creates it for you.

Distributing Quota & File Sentinel 29

• The Quota & File Sentinel Report Module is not installed on a remote machine during a remote installation. To install the QFS Report Module on a remote machine, you'll need to run a full regular QFS installation at that machine.

Regardless of whether you install the report module on your remote machines, you'll still be able to generate reports about those remote machines by running the report module on the original QFS machine.

If the target machine (remote server) does not already exist in your EASE hierarchy, then the first step of the remote installation is to add the remote server to your EASE hierarchy. Creating the server in your EASE hierarchy initiates an installation of the EASE software.

To create a new server in the EASE hierarchy and install EASE on that server:

1 Right-click the container where you want to add the server.

2 From the popup menu, click Add, Server to open the New Server dialog.

3 In the New Server dialog, specify the name of the server and then click OK to start the EASE Deployment wizard.

4 Respond to the prompts for installing EASE. You need to specify the drive on the target computer where you want to install EASE and an account ID for EASE Service. If you specify an existing account ID, the installation process adds the privileges required by EASE.

Remotely Installing Quota & File Sentinel

When you install Quota & File Sentinel to a remote server, the remote installation process prompts you for the target drive on the remote server and service account information for Quota & File Sentinel Service. If you have already performed a remote installation, the service account information you used for that installation is the default service account choice.

To install Quota & File Sentinel on a remote EASE server:

1 Right-click on the container where you want to add the server and select New, Server.

2 In the New Server dialog, enter the name of the remote server and click OK.

3 You see “The remote computer “remote_computer_name” does not have the EASE service installed. Do you want to install the EASE service now?” Select Yes. The EASE installation begins. Refer to Installing Quota & File Sentinel for more information about answering the standard EASE setup prompts.

4 Next, you are prompted for a drive. Select a drive.

5 You are prompted for an EASE service account and password.


6 Once the target machine (remote server) appears in your EASE hierarchy (left pane), right-click on the server you just created and select New, Application, Quota & File Sentinel.

7 On the New Application dialog, accept “Quota & File Sentinel” in the name field by clicking OK.

8 You see the prompt “Do you want to install this application to the remote computer “remote_computer_name” now?”. Click Yes. You see the new Quota & File Sentinel application in the left pane.

Note: If you installed Quota & File Sentinel using the distribution CD Setup program, you can uninstall Quota & File Sentinel from that computer using the Windows Add/Remove programs feature on that computer or you can just delete the application from EASE Admin.

Installing Quota & File Sentinel on a Microsoft Cluster Server 31

Installing Quota & File Sentinel on a Microsoft Cluster Server

Quota & File Sentinel supports Microsoft Cluster Server in both Active-Active and Active-Passive cluster configurations. The instructions below assume you have already completed your initial Quota & File Sentinel installation on a non-cluster server. If you want to install Quota & File Sentinel on your cluster server first, go to Installing on a Cluster Server First.

To install Quota & File Sentinel on a Microsoft cluster server:

1 From the EASE Admin, create a container at an appropriate point in your EASE hierarchy with the same name as the cluster group. To do this:

i. Right-click on the organization or another container and select New, Container.

ii. Specify a Name for the container and an optional Description. Refer to the EASE online Help for more information about creating containers.

2 Now add each cluster node to the cluster container. To do this:

i. Highlight the cluster container, then right-click on it and select New, Server. Enter the name of one of the cluster nodes.

ii. Do the same as above for the second cluster node.

3 Add the Quota & File Sentinel application to the cluster container level by right-clicking on it and selecting New, Application, Quota & File Sentinel.

4 Remotely install the Quota & File Sentinel application to each computer in the cluster by node name. To do this:

i. Right-click on the server and select New, Application, Quota & File Sentinel.

ii. Answer the remote installation prompts.

Notes: When you are asked to choose a drive, make sure you choose a drive that is local to the target node, and not a shared cluster drive. This is a standard clustering configuration requirement. Also, do not remotely install Quota & File Sentinel out to the cluster group name, just the node names.

5 Create your Quota & File Sentinel (quota and file control) policies at the cluster container level (above the nodes). This enables you to enforce limits on the shared cluster drives, regardless of the node that owns the shared drive group(s).

The policies you create at the cluster container level are specific to directories and sharenames that exist on each of the nodes. They are not associated with (and therefore do not enforce limits on) sharenames that might be created under the name of the cluster. For this reason, you need to use directory-based (not sharename-based) disk quota and file control policies to restrict use of the shared disks attached to a cluster server.


Installing on a Cluster Server First

If you want your initial Quota & File Sentinel installation to be on a cluster server, follow these steps:

1 Install Quota & File Sentinel on your cluster server first. It does not matter which of the nodes in your cluster you decide to install on first.

To do this, simply follow the procedure for Installing Quota & File Sentinel.

Note: Do not install Quota & File Sentinel on any of the shared drives; you must install it on a local drive in each node.

2 Log on to your Windows NT or Windows 2000 server using an account with Administrator privileges, and start Quota & File Sentinel from the Start menu (Start, Programs, NTP Software EASE, Quota & File Sentinel).

3 Create an EASE container for the cluster group. To do this:

i. Right-click on the organization, or on another container, to display the popup menu, and then click New, Container to open the New Container dialog box.

ii. Specify a Name for the container and an optional Description. Refer to the EASE online help for more information about creating containers.

4 Create the Quota & File Sentinel application under this EASE container for the cluster group by selecting New, Application, Quota & File Sentinel. This installs the Quota & File Sentinel application.

5 Now move the first cluster node to the cluster container you just created.

6 Remotely install the Quota & File Sentinel application onto the next cluster node by doing this:

i. Right-click on the cluster container and select New, Server. Enter the name for the next node of the cluster and click OK. This installs EASE.

ii. Right-click on the server node and select New, Application, Quota & File Sentinel.

7 Now add any other cluster nodes (servers) to the cluster container in your EASE hierarchy.

Note: When you create your policies, make sure you create these at the container level, not at the server or application level. You must do this so that the settings are inherited from the appropriate level.

The policies you create at the cluster container level are specific to directories and sharenames that exist on each of the nodes. They are not associated with (and therefore do not enforce limits on) sharenames that might be created under the name of the cluster. For this reason, you need to use directory-based (not sharename-based) policies to restrict use of the shared disks attached to a cluster server.

Uninstalling Quota & File Sentinel 33

Uninstalling Quota & File Sentinel

EASE technology lets you remotely install and uninstall Quota & File Sentinel from your network servers. If you installed versions of Quota & File Sentinel throughout your enterprise using the EASE remote installation feature, you must uninstall those Quota & File Sentinel applications through the EASE Admin interface. Most importantly, you must uninstall the versions of Quota & File Sentinel that you have remote installed on other servers first, before you uninstall the original version of the application that you installed on your primary server using the distribution CD installation wizard.

To use EASE Admin to uninstall a “remotely installed” Quota & File Sentinel installation:

1 Right-click the Quota & File Sentinel installation you want to delete to display the popup menu.

2 From the popup menu, click Delete.

You will be prompted with Are you sure you want to delete “Quota & File Sentinel”?

3 Click Yes.

To uninstall a Quota & File Sentinel installation that was installed using the Quota & File Sentinel distribution CD installation wizard:

1 Make sure the Quota & File Sentinel application and the EASE application are closed.

2 Click Start, Settings, Control Panel, then double-click on the Add/Remove Programs icon.

3 Select Quota & File Sentinel and click Remove. (Note: You must remove this one first.)

4 Select EASE and click Remove. (Note: You must remove this one only after you have removed Quota & File Sentinel.)


Upgrading Evaluation Versions to Production Versions

Below is the order in which you should perform the tasks associated with upgrading evaluation versions of Quota & File Sentinel to production versions:

1 If you have distributed versions of Quota & File Sentinel by remotely installing (“pushing”) them onto other machines, you must remove these remotely installed versions using the Delete feature of the EASE Admin interface.

Because you are using the EASE delete feature, you can remove all of your remotely installed installations from the EASE Admin console, without having to physically go to those machines. See "Uninstalling Quota & File Sentinel" on page 33 for instructions.

2 For evaluation versions of Quota & File Sentinel that have been locally installed onto primary servers (or any machines) you do not need to uninstall these locally-installed evaluation versions. You can and should simply install the production version of Quota & File Sentinel (using the Setup program on the production CD) directly on top of locally installed evaluation versions without having to first uninstall Quota & File Sentinel.

3 Once successfully installed on your primary server, the next step is to distribute Quota & File Sentinel to other machines throughout your enterprise. See "Distributing Quota & File Sentinel" on page 28.

Chapter 3

Configuring Quota & FileSentinel

This chapter describes how to perform the preliminary configuration tasks that will ultimately enable you to use Quota & File Sentinel to its full extent. Some of these tasks you will not have to perform, either because they are not appropriate for your environment, or because they are features you do not wish to implement.


• "Overview of Configuring Quota & File Sentinel" on page 36

• "Configuring Mail Messaging" on page 36

• "Configuring Popup Messaging" on page 41

• "Enabling Daily Email Reminders" on page 39

• "Enabling the Directory Connector for Resolving and Forming Email Addresses" on page 39

• "Enabling Windows 95 and Windows 98 Popup Messages" on page 41

• "Enabling Windows NT Popup Messages" on page 41

• "Enabling Windows 2000 Popup Messages" on page 42

• "Configuring for SNMP" on page 42

• "Configuring System Security" on page 44

• "Fine Tuning Quota & File Sentinel for Maximum Performance" on page 45


Overview of Configuring Quota & File Sentinel

Before you begin using Quota & File Sentinel, you should make sure you understand how to use the EASE inheritance feature. This will help you simplify initial configuration and future maintenance. For example, you can define system-wide settings, such as email server information, SNMP configuration, and common policy definitions at the top of the EASE hierarchy where every Quota & File Sentinel server can inherit them without further configuration. For an overview of how EASE and Quota & File Sentinel work together, see "Understanding EASE" on page 103 or refer to the EASE online Help.

In a typical installation, you install Quota & File Sentinel on one server, create your EASE hierarchy, and configure your inheritance structure. Next, you remotely install EASE and Quota & File Sentinel to other servers in your network. Then, you make any server-specific changes required. You can create your Quota & File Sentinel policies at any level you want, as appropriate: top level (organization-wide), server level, or container level.

Configuring Mail Messaging

Quota & File Sentinel includes an internal mail client that lets it automatically send email notifications to recipients you specify. As a preliminary configuration task, you must configure certain SMTP settings in order for this mail client to function.

If you have a number of Quota & File Sentinel servers in your enterprise network, you can use the EASE inheritance feature to configure email settings once for all of your Quota & File Sentinel servers. For example, in the EASE hierarchy pictured below, you would fully configure the email settings in the organization level application, Quota & File Sentinel (directly under "My Organization"). Then the container level applications ("Quota & File Sentinel" under the "Container 1" container icon), would inherit these settings by default.

Configuring Mail Messaging 37

To make the Quota & File Sentinel application that exists at the server level ("Server 1") inherit these settings, you would do the same thing.

To configure email settings:

1 In the left pane of EASE Admin, right-click a Quota & File Sentinel application icon to display the popup menu.

Organization (top) level

Container level

Server level

Inheritance iconGreen capital letter ‘E’ (for EASE inheritance)


2 On the popup menu, click Quota & File Sentinel, Properties to open the Quota & File Sentinel Configuration dialog.

3 Click the Email Configuration tab and supply the necessary information. For information on the settings, refer to the table that follows.

4 (Optional) Click the Misc Options tab and supply the necessary information about email reminders and directory connector properties.

Note: Mail environments vary widely; some settings that are required in one environment might be optional in another environment.

Note: To completely disable email for this Quota & File Sentinel application, clear both the Inherit Email Configuration and the Enable Email Notifications check boxes.

Setting Description

Inherit Email Configuration Lets this server inherit its email configuration from a level higher in the EASE hierarchy. When this check box is enabled, this server ignores any local email configuration settings.

Enable Email Notifications Lets you enable and disable email notifications for this application. The Enable Email Notifications status affects this level and all levels lower in the EASE hierarchy that inherit their email settings from this application.

SMTP Server The mail server address Quota & File Sentinel should use to send notification email messages, typically your company mail server. You identify the server by its DNS name, for example, Mail1.Server.company.com, or by its IP address, for example 192.168.34.123.

SMTP Domain The domain name of your mail server, for example mycompany.com.

Sender's Address A valid mail address in the format sender@maildomain. Sender's Address is necessary in environments where the mail gateway is configured to prohibit anonymous mailings. You might be able to use a fictitious name and a valid domain. You might need to provide a valid name with the domain. You can create an account for this purpose or specify an existing account. One approach is to specify the Quota & File Sentinel administrator's email address or the address of your help desk. Then, if a user replies to a notification message, the reply goes to a real person.

Senders Password If a password is required for this sender’s email address, supply it here.

Configuring Mail Messaging 39

Think of this as the email “master switch” - when you clear these checkboxes, you are turning off all Quota & File Sentinel’s email capabilities.

Enabling Daily Email Reminders

Daily email reminders let you send daily email messages to users when they go above and back below their quota limits. You can configure the time of day at which to send the email reminder, and how long to send the daily reminders (7 days, 15 days, and so on).

Note: The daily reminder feature works in conjunction with the “Send to Triggering User” setting on the “General” tab of the “Threshold Properties” dialog box (see "Setting Triggering User Messages" on page 59). If you're not sending email notifications to triggering users when an object reaches its quota, this daily reminder setting has no effect, whether you've enabled it or not.

To set the daily email reminder for this server:

1 In the left pane of EASE Admin, right-click the Quota & File Sentinel application icon to display the popup menu.


3 Click the Misc. Options tab and do the following:

• Deselect the check box next to Inherit Daily Email Reminder Properties.

• Enter the time of day at which Quota & File Sentinel will mail out daily reminders.

• Set the maximum number of days for Quota & File Sentinel to send out the daily reminders.

Enabling the Directory Connector for Resolving and Forming Email Addresses

The directory connector settings determine how Quota & File Sentinel will form email addresses when you are using email messaging to inform users and administrators that an object is at or over quota. You can choose one of three methods for having Quota & File Sentinel form email addresses, each of which is described in the steps that follow:

Note: This option works in conjunction with the “Email Configuration” tab on the “Quota & File Sentinel Configuration” dialog box. If you disable email notifications on the “Email Configuration” tab, this feature is also disabled.

To set the method for resolving and forming email messages for users:




3 Click the Misc. Options tab and supply the necessary information:

Setting Description

Inherit Directory Connec-tor Properties

When you select this checkbox, this server inherits its directory connector properties from a level higher in the EASE hierarchy. When you deselect this checkbox, you can set the properties specifically for this server.

Use Active Directory Con-nector to retrieve email addresses

When a user reaches his or her quota threshold, and you're using email notification, QFS cross references the user's login ID with the Active Directory database on the server you specify here to find the user's email address.

You must specify a primary and secondary host on which to look when using this option, along with the port numbers for each host.

Use LDAP Connector to retrieve email addresses

This option lets you resolve email addresses if you're using LDAP and an LDAP compatible data source (such as Exchange) to manage your email accounts.

When using this option, you must specify a primary and secondary host on which to look, the port numbers for each host, and the LDAP Mail and Filter names.

The LDAP Mail Name is a variable that references the field containing user email addresses in your mail system's database. The LDAP Filter Name is a variable that references the field containing user login IDs in your mail system's database. The default variables in these fields are for use with an Exchange server database.

Append the SMTP Domain to form email addresses

When a user reaches his or her quota threshold, and you're using email notification, QFS forms the user's email address by simply appending the SMTP domain you specified on the “Email Configuration” tab to the user's login ID.

Configuring Popup Messaging 41

Configuring Popup Messaging

Quota & File Sentinel can send popup messages for certain events to selected recipients using text and variables you configure in the policies. To use Windows popups for notifications, you must make sure that the Windows Messenger service is running on the machine where the Quota & File Sentinel Service is running, and that popup messages are enabled on the client computers. Perform one of the tasks described below, depending on what’s appropriate for your environment.

Enabling Windows 95 and Windows 98 Popup Messages

Quota & File Sentinel uses the Windows Messenger service to send popup messages. To receive messages, Windows 95/98 clients must be running Winpopup.

To have Winpopup start automatically:

1 On the Windows Start menu, choose Settings and then Taskbar.

2 Click the Start Menu Programs tab.

3 Click Add.

4 On the Command Line field, type WINPOPUP.EXE.

5 Click Next.

6 Double-click the StartUp folder.

7 Type the name that you want to see on the Startup menu.

8 Click Finish.

9 Restart the computer to automatically load Winpopup.

Enabling Windows NT Popup Messages

Popup messaging uses the Windows Messenger service, which must be running on the Quota & File Sentinel Service machine and the Windows NT client machines that will receive notification messages.

To start the Messenger service:

1 Open Windows NT Control Panel and double-click the Services icon to open the NT Services dialog.

2 In the Services list, click the Messenger service.

3 If the Status column does not show Started for the Messenger service, click Start.

4 To make the Messenger service start automatically, click Startup, then click Automatic.


Enabling Windows 2000 Popup Messages

Popup messaging uses the Windows Messenger service, which must be running on the Quota & File Sentinel Service machine and the Windows 2000 client machines that will receive notification messages.

To start the Messenger service:

1 Open Windows Control Panel and double-click the Administrative Tools icon.

2 In the list of tools, double-click the Services icon to open the Services dialog.

3 In the Services list, find the Messenger service. The Status for the Messenger service should be Started and the Startup Type should be Automatic. If you need to change the settings, double-click the Messenger service icon to open the service Properties.

Configuring for SNMP

If your organization uses an SNMP-based network management program, you can configure Quota & File Sentinel to send notification messages (SNMP traps) to the management station. Quota & File Sentinel sends an SNMP trap for each threshold event. If your organization does not use SNMP network management, or if you do not want threshold event notification, you can leave Quota & File Sentinel's SNMP client disabled.

To configure the Quota & File Sentinel SNMP client:



3 Click the SNMP Configuration tab and supply the necessary information. For information on the settings available, refer to the table below.

Setting Description

Inherit SNMP Configuration Lets this server inherit its SNMP configuration settings from a level higher in the EASE hierarchy. When this check box is enabled, this server ignores any local SNMP configuration settings.

Enable SNMP Messages Enables and disables SNMP messages between Quota & File Sentinel and an SNMP management station. The Enable SNMP status affects this level and all levels lower in the EASE hierarchy that inherit their SNMP settings from this application.

Configuring for SNMP 43

Note: To disable SNMP for this Quota & File Sentinel application, you must clear both the Inherit SNMP Configuration and the Enable SNMP check boxes.

SNMP Console IP Address The IP address of the SNMP management station. Valid characters for an IP address are 0 through 255.

Community Name A password that authorizes communications between the SNMP management station and the client and specifies a level of access. Community names are defined within the management software. Your network manager should provide the community name. On most SNMP systems, the default community name is "public". Note that the community name is case-sensitive.


Configuring System Security

You can limit the ability of individual users and/or groups to create and modify local policies and inherited policies. You can also limit or restrict access to the Quota & File Sentinel configuration options.

To restrict individual user and group access to QFS policies and configuration options:

1 In EASE Admin, right-click a Quota & File Sentinel application icon to display the popup menu.

2 From the popup menu, click Quota & File Sentinel, Properties to open the Quota & File Sentinel Configuration dialog.

3 Click the Security tab and then do one of the following:

• To have this server inherit its security properties from a level higher in the EASE hierarchy, select the Inherit Security checkbox (this is the default setting).

• To set the security properties for this particular server, deselect the Inherit Security checkbox then select the Enable Security checkbox. Proceed with the rest of the steps.

4 Click Add to open the Choose Account dialog box.

Note: The Everyone group has full access by default.

5 Choose the users and/or groups you would like to add to the list then click OK.

Hold the Shift or Ctrl key down to select more than one user or group at a time. Use the Select Domain drop down to display a list of users and groups from a different domain.

6 Click on a user or group name in your list of names and set the permissions for that user or group.

You can restrict the user's or group's ability to create or modify local policies and inherited policies (policies inherited from further up the EASE hierarchy). You can also restrict their ability to change the QFS system properties.

• To give the user or group full access to create policies, modify policies, and change QFS configuration options, select Full Control straight across.

• To completely restrict the user or group from creating policies, modifying policies, and changing QFS configuration options, select None straight across.

• To let the user or group look at, but not change policies and QFS configuration options, select Read Only straight across.

You can set any combination of the above option for a user or group. For example, you could give a user Full Control to Local Policies, Read Only access to Inherited Policies, and no access to the QFS configuration options.

Fine Tuning Quota & File Sentinel for Maximum Performance 45

Notes: The policy permissions you set on this dialog box don't affect the owner of a policy (the person who created the policy).

The Owner and Last Modified by fields at the bottom of the dialog box show the name of the user who added the settings to QFS and the name of the user who last modified the settings.

Removing users and groups from the list

To remove users and groups from the list:

1 Select the user or group you would like to remove from the list.

2 Click remove.

Fine Tuning Quota & File Sentinel for Maximum Performance

Every time you restart your server, Quota & File Sentinel checks all the objects it’s managing to see what has changed. If you have a large number of objects under quota management, this check could be fairly resource intensive. Quota & File Sentinel includes “Tuning Properties” that let you specify the impact this resizing process has on your server's resources.

To set Quota & File Sentinel’s tuning properties:



3 Click the Misc. Options tab and set the Tuning Properties:

To minimize the impact, choose Low Impact Sizing. To make QFS's resizing process a high priority, choose High Impact Sizing.


Chapter 4

Using Quota & FileSentinel

Now that you have finished the basic configuration tasks described in Chapter 3, you are ready to begin creating policies. This chapter explains everything you need to know to create, configure, and manage disk quota policies and file control policies. It is divided into basic and advanced tasks.


Part I: Basic Tasks

• "Part I: Basic Tasks" on page 48

• "Creating Disk Quota Policies" on page 50

• "Creating File Control Policies" on page 65

• "Creating File Removal Policies" on page 71

• "Creating Server Policies" on page 80

Part II: Advanced Tasks

• "Suspending Policy Enforcement" on page 82

• "Using the Overdraft Feature (disk quota and file removal policies)" on page 84

• "Using Variables in Messages" on page 85

• "Setting Object Status Indicators" on page 87


Part I: Basic Tasks

This section provides step-by-step instructions for performing the basic Quota & File Sentinel tasks. The following topics are covered:

• "Creating Disk Quota Policies" on page 50

• "Setting General Properties" on page 52

• "Setting Quota Limits" on page 52

• "Setting Thresholds" on page 54

• "Setting General Threshold Properties" on page 55

• "Setting Other Recipients Messages" on page 57

• "Setting Owner Messages" on page 58

• "Setting Triggering User Messages" on page 59

• "Setting Threshold Commands" on page 61

• "Setting Directories or Shares" on page 63

• "Setting Users and Groups" on page 63

• "Creating File Control Policies" on page 65


• "Specifying the File Patterns to manage" on page 66

• "Setting Control Options" on page 67



• "Creating File Removal Policies" on page 71


• "Setting How Often to Remove Files (Lifetime Tab)" on page 72

• "Setting Thresholds" on page 73



• "Setting Other Recipients" on page 79

Overview of Creating Policies 49

Overview of Creating Policies

In Quota & File Sentinel, a policy refers to a set of storage management properties that direct certain monitoring activities. You will notice that there are three different types of policies you can create in Quota & File Sentinel - disk quota policies (or quota policies), file control policies, and file removal policies.

• Disk quota policies let you manage the amount of logical space, not physical space, users consume. There are two types of Disk Quota polices: Folder and File:

– A Folder policy is one where you apply quota limits to entire folders. For example, you could create a Folder policy that says "when the folder or share reaches 100 MB, deny writes"

– A File policy is one where you apply quota limits to the size of particular files or file types within a particular folder. For example, you could create a file disk quota policy on a directory called C:\users that limits the size of all .doc files within that directory to 100 MB.

• A file control policy lets you select one or more files or file patterns and implement certain actions against those files. For example, you could create a file control policy that blocks certain users from performing any WRITE activity on certain file patterns (for example, .VBS files).

• A file removal policy lets you automatically delete files from folders or shares that Quota & File Sentinel is managing after x hours, days, weeks, or months. This type of policy is especially useful for managing temporary contract workers. For example, you may have a contract employee who will only be working at your site for six weeks. After the six weeks, you want to clean up any files left behind by the user. You can create a File Removal Policy that will automatically remove the files after the six weeks are up AND that puts a quota restriction on the contractor for the duration of their stay.

You can configure certain options about the deletion. For example, you can choose to delete files based on their creation date, modified date, or their last accessed date. The quota policy begins the moment a user creates a file

The sections that follow describe how you create and configure each type of policy.


Creating Disk Quota Policies

There are two types of disk quota policies: Folder and File:

• A Folder policy is one where you apply quota limits to entire folders. For example, you could create a Folder policy that says "when the folder or share reaches 100 MB, deny writes"

• A File policy is one where you apply quota limits to the size of particular files or file types within a particular folder. For example, you could create a file disk quota policy on a directory called C:\users that limits the size of all .doc files within that directory to 100 MB.

The steps for creating both of these disk quota policies are the same, with two exceptions:

– When you create a disk quota file policy, there’s an extra tab where you enter the files and/or file times you want to place quota limits on.

– When you create a disk quota file policy, you can make the policy dependent on a disk quota folder policy.

Link a disk quota "file" policy or a file removal policy to a disk quota policy, thereby reducing the amount of time it takes to create and later update the dependent policies.

When you make a disk quota "file" policy or a file removal policy dependent on a disk quota policy, the dependent policy takes the following information from the disk quota policy: Directories to manage, Managed Users and Groups, Exempt Users and Groups, Other Recipients.

There are several methods available for creating a new policy. For disk quota policies, you can copy and paste or drag and drop the default policy (“Quota Default”) to create a new one. This has the advantage of carrying all the settings from the default policy over to the new policy where you can change them to suit your needs, or simply give the policy a new name and use the default settings. After you’ve created your own policies, you can also create new ones from them by cutting and pasting or dragging and dropping them.

For both disk quota and disk quota file policies, you can use the right-click popup menu to create a fresh policy from scratch. The following directions describe the “popup” menu method of creating a new policy, since you can use this method immediately to create both types of disk quota policies

Creating Disk Quota Policies 51

To create a new quota using the right-click popup menu:

1 Expand the EASE hierarchy to display the level where you want to put the new policy.

2 Right-click on Disk Quota Policies to display the following popup menu:

3 Select the type of disk quota policy you want to create (folder or file policy using directories or shares).

The New Quota Policy dialog box appears.

4 Configure all of the rules for the policy, such as the policy name, quota limit, thresholds, managed users, etc.

5 Click the Help button on any dialog box tab for information specific to that tab.

The rest of this section describes the settings on each of the disk quota policy dialog box tabs.


Setting General Properties

For Disk Quota Policies, the General tab lets you specify basic information about the policy, such as a name and an optional description.

Setting Quota Limits

The Quota tab on the Disk Quota Policy properties dialog lets you set the characteristics associated with the actual quota limit for this policy.

Setting Description

Policy Name: This is the name that appears in the EASE Admin hierarchy. After you create a policy, you cannot rename it from within this dialog. However, you can rename it in the right or left pane of EASE Admin. All policies must have unique names. Further-more, you cannot have the same name for a disk quota and a file control policy.

Description: Enter optional text to help you identify this policy.

This policy applies to (OS version):

Choose to apply this policy to either just workstations, just serv-ers, or to all servers and workstations (the default)

When more than 1 policy applies

“Always enforce this one”.

If more than one Disk Quota Policy or File Removal Policy is applied to the directory or share this policy is managing, use this policy.

Distinguished Name The full name and path of this policy, starting from the top of the EASE hierarchy. Click anywhere in this field and drag to the right to see the rest of path name. This field is read only.

Policy Owner The User ID of the person who created the policy. This field is read only.

Last Modified by The User ID of the person who last made changes to this policy. This field is read only.

Setting Description

Absolute Quota Limit of

The size limit in megabytes that each policy object is tracked against. All Quota & File Sentinel threshold actions (commands, notifications, Deny Write) are tied to the policy quota limit. Each policy threshold (set on the Thresholds tab) is a percentage of this number.


Relative Quota Limit of x % of Vol-ume Size

(Applies to Quota Folder Policies only)

Instead of an absolute number at which this policy hits its limit, you can specify the limit as a percentage of the total volume size. For example, you could say when the objects managed by this policy total 50 percent of the volume's size, take action (run commands, send notifications to users, Deny Writes, and so on). On a 2 Gig volume, this would be 1 Gig. All Quota & File Sentinel threshold actions are tied to this quota limit.

Relative Quota Limit of x % of Other Policy

(Applies to Quota Folder Policies only)

When you're managing an object shared by many users, this type of quota limit prevents any one user from causing the object to hit its limit.

For example, you may have an object called "D:\Users" for which you've created a quota policy with an absolute limit of 100Mb. Underneath "D:\Users", there are five sub-directories, each belonging to a different user (User1, User2, User3, User4, and User5). With just the one policy and an absolute quota of 100Mb on "D:\Users", it's conceivable that User1 and User2 could fill their directories with 50Mb each and cause the quota to hit its limit, thereby locking everyone else out.

To prevent this from happening, you could do the following:

• Create a policy (call it Policy A) that places an absolute limit of 100Mb on "D:\Users".

• Create a second policy (call it Policy B) that places a quota limit of 10% relative to Policy A on each user's directory ("D:\Users\*).

Now no one user can exceed 10Mb of space in their directory, and the total of all five user directories can still never exceed 100Mb. An added advantage of the "quota limit relative to another policy" method is that you can increase the quota limit on Policy A to increase the quota limit for each user under Pol-icy B. For example, if you raise the limit on Policy A to 200Mb, each user would now have 20Mb of disk space to work with. There's no need to address each user individually, which greatly simplifies your job.

Deny Writes at: The threshold at which Quota & File Sentinel blocks further WRITEs to the policy object. Quota & File Sentinel blocks any WRITE to a policy object if that WRITE will exceed the policy's Deny Write threshold. Typically, you set Deny Write at 100% (of your quota limit) but you can choose any percentage you want.


Setting Thresholds

In Quota & File Sentinel, a threshold is defined as a percentage of the disk quota policy's quota limit. On the Thresholds tab of a Quota Policy properties dialog, you can set a number of threshold levels for each policy (up to 200).

When a threshold level is reached, this is known as a threshold event and Quota & File Sentinel carries out the actions and notifications defined for that threshold. You define the actions and notifications.

The Thresholds tab lets you define the following:

• One or more thresholds for a quota policy. You can create up to 200 thresholds for each policy. You can set threshold percentages anywhere from 1% to 200%.

• The messaging options (popups or emails) for various types of users (owners, triggering users, and other recipients).

• For each threshold, you can configure different message text for owners, triggering users, and other recipients. You can also have different text for when a threshold is exceeded and when the object size returns to below the threshold.

• Commands (programs, batch files, or scripts) for each threshold that Quota & File Sentinel runs when a threshold level is reached. You can specify different commands for when a threshold is exceeded and when the object size returns to below the threshold.

To create a new threshold:

1 On the Thresholds tab of a quota policy’s properties dialog, click the Add button.

You can also create a new threshold based on the settings of an existing threshold, click the threshold that has the settings you want to use and then click the Copy button. The Threshold Properties dialog box appears so you can make the changes you need for the new threshold.

Allow an Overdraft of:

Enable this feature to let managed users continue WRITEing to policy objects even though the WRITE exceeds the disk quota policy's defined quota limit. This feature lets users exceed the Deny Write level for a defined period of time, and for a specified percentage over the Deny Write level. When you enable over-draft, you must also set the time limit (described below).

Overdraft Time Limit is:

You can choose to set an overdraft time limit if you have over-drafts enabled. The time limit can be between 1 and 9999 (min-utes). The time limit is the number of minutes the managed users have to continue to make changes (WRITES) that will exceed their quota limits defined in the disk quota policy.


2 Now configure the tabs associated with the Threshold Properties dialog (General, Other Recipients Messages, Owner Messages, Triggering User Messages, and Threshold Commands). Each of these tabs are described in the sections that follow.

Setting General Threshold Properties

The General tab on the Thresholds Properties dialog lets you define the kinds of thresholds you want to implement for this policy, and the types of messages that Quota & File Sentinel sends when the threshold event occurs.

Setting Description

Threshold Setting: To define this threshold, choose one of the four types of thresh-old settings listed below.

Percent of Quota: The percentage of the policy limit that trig-gers the actions defined for this threshold. A policy can have thresholds below, at, and above 100%, with different notifica-tion actions and message text for each level. You can create up to 200 thresholds for each policy. You can set threshold per-centages anywhere from 1% to 200%.

Quota Limit Threshold (100%): When this option is checked, messages are triggered when users reach 100% of the quota limit.

Deny Write Threshold: When this option is checked, mes-sages are triggered when users Deny Write percentage is some-thing other than 100% of the limit.

Overdraft Threshold: When this option is checked, messages are triggered when the “Allow an overdraft of __% over Deny Writes” value (set on the Quota tab of the Disk Quota Policies dialog) is reached.


Notification Mes-sages to send when threshold is reached:

The types of notifications that Quota & File Sentinel sends when this threshold is passed. Quota & File Sentinel can send notifica-tion messages using either popups or email messages to the fol-lowing:

Other Recipients: Optional notification recipients. In each policy, you can define a list of people who can receive notifica-tions of threshold events. Typically, you would add the Quota & File Sentinel administrator to the list, but you can add anyone you want.

Owner: Any account ID connected to a policy share that includes a policy object that passes a threshold. Only account IDs that are defined in the Managed users and Groups tab of the policy properties can receive Owner messages.

Triggering User: The account ID that causes a policy object to pass a threshold. Only account IDs that are defined in the Man-aged users and Groups tab of the policy properties can receive Triggering User messages.

You can also configure Quota & File Sentinel to send daily email reminders to users by selecting Send Reminders under “Send to Triggering User”. Before you can use daily email reminders, you must enable the option as described in "Enabling Daily Email Reminders" on page 39.

User Name Popup: When this option is selected, if a threshold is passed, Quota & File Sentinel sends popups only to the computer the user logged on to first.

Computer Name Popup:

When this option is selected, Quota & File Sentinel sends pop-ups to all computers that the triggering user is logged on to when a threshold is passed.

Note: For this feature to work the way it was intended, each computer the triggering user is logged into must have a drive let-ter mapped to the share that was affected. Therefore, only com-puters that the triggering user is logged into, and that have a drive letter mapped to the object (share) that the threshold crossed, will receive a popup message.

The advantage of Computer Name Popup over the User Name Popup option is that the user will get the notification no matter which computer he/she is currently using. Selecting User Name Popup will only send a notification to the computer the user logged onto first.

Note: Users using Terminal Server should not use the Com-puter Name Popup selection; they should use User Name Popup.


Note: Deny Write threshold actions occur differently from the other threshold actions. When Quota & File Sentinel blocks a WRITE because it will exceed the Deny Write threshold, Quota & File Sentinel sends the over threshold notification even though the limit was not actually exceeded. A below threshold action for the Deny Write threshold can occur only if the object passes below the Deny Write threshold because an overdraft setting allowed the threshold to be exceeded.

Setting Other Recipients Messages

When Other Recipients Messages are enabled (“Send to Other Recipients” on a threshold's General tab), Quota & File Sentinel sends the text defined on the Other Recipients Messages tab to users listed in the policy’s ' Other Recipients tab. You can create different text for Below Threshold messages (when an object exceeds and then returns to below the threshold's percentage) and for above threshold/deny write messages.

Note that members of the Other Recipients list receive notifications even if they are also listed as Exempt Users and Groups.

Setting Description

Below Threshold Message:

This is the message Quota & File Sentinel automatically sends to other recipients when a user managed by this policy falls (or returns) below a defined threshold. This message is to let the other recipients know that the managed user has returned to a state below the defined threshold.

Above or Write Denied Threshold Message:

This is the message Quota & File Sentinel automatically sends to other recipients when a user managed by this policy reaches or goes above a defined threshold (deny write). This message is to let the other recipients know that the managed user has reached the defined threshold.


Setting Owner Messages

When Owner Messages are enabled (“Send to Owner” on a threshold's General tab), Quota & File Sentinel sends the text defined on the Owner Messages tab to the NT owner of the policy object involved in the threshold event. The NT owner account ID must be specified in the Managed Users and Groups tab of the policy to receive Owner messages.

You can create different text for Below Threshold messages (when an object exceeds and then returns to below the threshold's percentage) and for above threshold/deny write messages.

Email Subject: Quota & File Sentinel uses the text you specify here as the sub-ject when it sends an email notification message for this thresh-old event.

Email and Popup Text:

Quota & File Sentinel uses the text you specify here as the body of emails and popup messages for threshold events. If you want, you can leave the default sample text or create your own message. Note that you can use variables in this message text. Refer to "Using Variables in Messages" on page 85.

Click the Edit Text button to open a separate text editor for composing your Email message. If you selected the "Send Emails in HTML Format" option on the Policy's Thresholds tab, you can use the text editor to apply formatting to your email messages.

Note: If you later deselect "Send Emails in HTML Format" on the Policy's Thresholds tab, QFS will continue to send this mes-sage in HTML format. To remove the HTML formatting, click the Clear button and re-enter your Email message without the formatting.

Also, the" Email Text" field (to the left of the Edit button) dis-plays either <email message is formatted as plain text> or <email message is formatted as HTML> regardless of what the actual message says.

Setting Description


This is the message Quota & File Sentinel sends automatically to the NT owner of a policy object when that policy object is involved in a below threshold event. (falls below or returns to a defined threshold). This message is to let the file owner know that the quota limit has returned to a state below the defined threshold.


Note: Deny Write threshold actions occur differently from the other threshold actions. When Quota & File Sentinel blocks a write because it will exceed the Deny Write threshold, Quota & File Sentinel sends the over threshold notification even though the limit was not actually exceeded. A below threshold action for the Deny Write threshold can occur only if the object passes below the Deny Write threshold because an overdraft setting allowed the threshold to be exceeded.

Setting Triggering User Messages

When Triggering User Messages are enabled (“Send to Triggering User” on a threshold's General tab), Quota & File Sentinel sends the text defined on the Triggering User Messages tab to the account ID that causes a threshold event (this is not necessarily the owner of the files involved). The NT account ID of the triggering user must be specified in the Managed Users and Groups tab of the policy to receive the triggering user messages.


This is the message Quota & File Sentinel sends automatically to the NT owner of a policy object when that policy object is involved in an above or write-denied threshold event. (reaches or goes above a defined threshold). This message is to let the file owner know that the quota limit has reached or gone above the defined threshold.



Quota & File Sentinel uses the text you specify here as the body of emails and popup messages for threshold events. If you want, you can leave the default sample text or create your own mes-sage. Note that you can use variables in this message text. Refer to "Using Variables in Messages" on page 85.





For example, a disk quota policy called PolicyA includes the share PUBLIC and a directory in PUBLIC called APPS. PolicyA has a 90% threshold with Triggering User messaging enabled. If someone performs a write to APPS that exceeds the 90% threshold, that account ID receives the Triggering User message.

You can create different text for Below Threshold messages (when an object exceeds and then returns to below the threshold's percentage) and for above threshold/deny write messages. You can also configure Quota & File Sentinel to send daily email reminders to users by selecting Send Reminders under “Send to Triggering User” on the Threshold’s “General” tab. Before you can use daily email reminders, you must enable the option as described in "Enabling Daily Email Reminders" on page 39.

Setting Description


This is the message Quota & File Sentinel sends automatically to the triggering user when a below threshold event occurs (falls below or returns to a defined threshold). Triggering user is defined as the account ID that causes the threshold event to occur (this is not necessarily the owner of the file). This mes-sage is to let the triggering user know that the quota limit has returned to a state below the defined threshold.


This is the message Quota & File Sentinel sends automatically to the triggering user when an above or write-denied thresh-old event occurs (reaches or goes above a defined threshold). This message is to let the triggering user know that the quota limit has reached or gone above the defined threshold.


Setting Threshold Commands

Quota & File Sentinel can launch batch files, programs, and scripts for a threshold event. You can configure separate commands (actions) for when a policy object exceeds its threshold and when it passes back below the threshold.

You do not have to enable commands; Quota & File Sentinel automatically executes any text that appears in the boxes on the Threshold Commands dialog. To disable a command, simply delete the text from the command box.

If the command results in a message being returned to Quota & File Sentinel, for example, an error message, Quota & File Sentinel writes the information to the Windows Event Log.

To set a command (action) for a particular threshold:

1 Double-click on the desired quota policy or create a new quota policy.

2 Click the Thresholds tab.

3 Double-click on the threshold you want to assign the command (action) to.

4 Click the Threshold Commands tab.

Email Subject: Quota & File Sentinel uses the text you specify here as the subject when it sends an email notification message for this threshold event.




Note: If you later deselect "Send Emails in HTML Format" on the Policy's Thresholds tab, QFS will continue to send this message in HTML format. To remove the HTML formatting, click the Clear button and re-enter your Email message with-out the formatting.



5 Enter the desired command into the appropriate box. Quota & File Sentinel can launch batch files, programs, and scripts.

6 Click OK.

Setting the Files and File Types to Manage (Disk Quota “File” Policies Only)

Use the Files tab The Files tab lets you identify particular files or file types on which to place quota restrictions. The restrictions affect all directories and shares under the policy's control.

To add a file pattern to the file patterns list:

1 Click the Add button to display a new edit box and Browse button.

If you are configuring a container-level application, the Browse button does not appear because there are no files associated with a container-level application. However, you can type an extension into the Add field.

2 Either enter the file name or file extension, or use the Browse button to choose a file or an extension.

3 Press Enter to add the item and close the edit box.

To edit an existing file pattern in the Patterns list:

1 Click the file pattern you want to edit.

2 Click the Edit button.

3 Either type the new path and file name or use the Browse button to choose a file type.

4 Press Enter to add the item and close the edit box.

To remove a file pattern from the Patterns list:

1 Click the file pattern you want to remove.

2 Click the Remove button.


Setting Directories or Shares

You define the directories or shares you want Quota & File Sentinel to manage using the Directories or Shares tabs on the Quota Policy properties dialog.

To define directories or shares for a particular disk quota policy:


2 Click the Directories or the Shares tab.

3 Click the Add button.

4 Type the path to and name of the directory you want to add, or use the Browse button to choose an existing directory. Note that this field also accepts directory names for directories that do not exist.

Note: If you are configuring a container-level application, the Browse button does not appear because there are no directories associated with a container-level application. However, you can type a path into the Add field. This field also accepts pathnames that do not exist.

5 Choose how you want to apply the quota limit.

The Individual limit option means that the policy limit is tracked and enforced on each policy object individually. The Combination of objects option means that the policy limit is tracked and enforced on the combined (total) size of all policy objects.

6 You can click the Size button to display the current size information on the specified directory.

Note About Mapped Drives: In disk quota policies managing mapped drives (drives specified in directory policies by UNC name), the size that Quota & File Sentinel (QFS) reports on for these drives can become out of sync with the actual sizes. QFS manages outgoing activity to UNC names, while regular directories specified in policies are managed on incoming activity. Since other workstations (not managed by QFS) may have the same UNC name mapped, these workstations can update files without passing through QFS. Therefore, sizes reflected in QFS may not always reflect actual size. To compensate for this, QFS automatically refreshes the UNC size information every 30 minutes.

Setting Users and Groups

In Quota & File Sentinel you use the Managed Users and Groups tab to define the users and groups you want to apply to any policy. The Exempt Users and Groups tab lets you define specific users and/or groups you want to be exempt from any policy.

To define users and groups for a policy:



2 Click the Managed Users and Groups tab.

3 Choose a strategy for managing the users.

– Choose "All Users Together" (everyone is under quota management) or Each User Individually (only the users listed are under quota management). When you select the All Users option, you won't be able to add individual users to the list.

4 If you're managing individual users, click the Add button to display an edit box.

5 Either type the name of the user account (or group), using the format domain\accountID, or click the Browse button and choose an account from the list.

Press Enter, or click the OK button, to add the item and close the edit box. (To cancel the add, click outside the edit box or press Esc.)

To specify users and groups you want to be exempt from a policy:

1 Click the Exempt Users and Groups tab on the desired policy.


3 Either type the name of the user account (or group), using the format domain\accountID, or click Browse and choose an account from the list.


Setting Other Recipients

The Other Recipients tab lets you specify which users should receive the messages you configured on the Other Recipients Messages tab for each Threshold associated with the policy.

To set Other Recipients for a policy:


2 Click the Other Recipients tab.

3 Click the Add button to display an edit box.



Creating File Control Policies 65

Creating File Control Policies

In Quota & File Sentinel, a file control policy is a set of configurable parameters that let you use Quota & File Sentinel to control which files and file patterns users may access. Through the file control policies properties dialogs, you can select various files or file patterns, then choose the users you want to subject to the rules of this file control policy. For controlling the access to these files or file patterns, you can choose to allow or deny read access, write access, or the ability to create certain files or file patterns.

To create a new file control policy:


2 Right-click on File Control Policies.

3 From the popup menu, choose New, Folder Policy Using Directories or New, Folder Policy Using Shares.

The New File Control Policy dialog lets you configure all of the rules associated with the policy, such as the files and file patterns you want to control, the kinds of access you want to allow or deny, managed users, etc. You also define things like a name for this file control policy, and, if desired, you can type in a brief description for it.

Note that the default file control policy lets you define directories only, not shares. To create a policy for controlling share locations, right-click on File Control Policies, then select New, Share Policy.

4 Click the Help button on any tab for information specific to that tab.

You can always create a new policy by copying any existing policy. Either copy and paste or drag-and-drop an existing policy to the location where you want the new policy. If you copy it to the same location, the policy properties dialog opens and you can specify a new name. All policies must have unique names. Furthermore, you cannot have a file removal policy, disk quota policy, and a file control policy with the same name; you will be prohibited from creating policies with the same names.



For file control policies, the General tab lets you specify basic information about the policy, such as a name and an optional description.

Specifying the File Patterns to manage

The File Patterns tab lets you identify particular files or file types you will allow users to read, write, or create those. This tab works in conjunction with the Control Options tab, which is where you specify whether users can read, write, or create the file types. For example, you could specify that .MP3 files do not get written to your disks. You could also specify that certain file types do not get created or even opened. The prohibition is in effect for directories and shares under the policy's control. Accounts listed in the Exempt Users and Groups tab can still write to prohibited files.

In the default file control policy, .GIF and .VBS file patterns are already selected. This is because these are some of the more common file patterns you may want to control usage on.

To choose the files and/or file patterns you want to control:

1 For the desired file control policy, click the File Patterns tab.


Setting Description

Policy Name: The name that appears in lists in EASE Admin. After you create a policy, you cannot rename it from within this dia-log. However, you can rename it in the right or left pane of EASE Admin. All policies must have unique names. Fur-thermore, you cannot have the same name for a disk quota and a file control policy.

Description: Type in optional text to help you identify this policy.


Choose to apply this policy to either just workstations, just servers, or to all servers and workstations (the default)





3 Either type the name of a file or a file pattern, or use the Browse button to select an existing one.

4 Click OK or press Enter to add the item and close the edit box.

Once files and file patterns are selected, go on to set the Control Options and other tabs to configure the kinds of access you want to allow or deny.

Note: If you are performing a software upgrade that affects files that are controlled by a file control policy, the upgrade will likely fail. Before upgrading controlled files, you must remove the file types from the policy, or suspend enforcement on the affected objects, or use an account ID that is listed on the Exempt Users and Groups tab of the policy that is enforcing the rule(s).

Setting Control Options

The Control Options tab lets you specify the actions that will be allowed on files and file patterns managed by Quota & File Sentinel file control policies. You can specify whether or not you want to allow certain files to be opened for read access, write access, or creation. You can also specify if you want to simply deny any or all of these actions.

By clicking the Message Text and Actions button, you can specify the exact text of the message you want the user to see when a file control event occurs.

Specify the file access actions (Open for read, Open for write, Create new) you want to allow or deny for this policy. You can also specify if you want Quota & File Sentinel to log messages to the Windows event log under certain circumstances, and/or send message prompts to certain user accounts under certain circumstances.

Setting Description

Open for read Choose Actions you want to occur whenever the user attempts to perform an Open for Read on one of the file pat-terns under this policy's control (*See options below). The default setting is Always Allow.

Open for write Choose Actions you want to occur whenever the user attempts to perform an Open for Write on one of the file pat-terns under this policy's control (*See options below). The default setting is Always Allow.

Create new Choose Actions you want to occur whenever the user attempts to create file type that are under this policy's control (*See options below). The default setting is Always Allow.


Notes:

1. Be aware that some applications (like Microsoft Word and Notepad, for example) are normally configured to automatically open for read/write access whenever opening files. Therefore, if you configure a file control policy to 'Always Deny' writes but 'Always Allow' reads for something like Microsoft Word files (or for Notepad .txt files), managed users will be denied from opening the file because of the deny on opening for write access. Many applications look for full write access upon opening and will not continue without such access.

2. Sometimes the act of simply copying a file from a source location causes that source file to be opened for read/write access. Therefore, if you have a file control policy configured to deny opens for reading or writing, the copy could be denied because the read or write access is denied. This issue is similar to the issue noted above, in that, the result is that you may receive a 'deny' notification, and in fact be denied from an open for read or write operation even if you have open for read or write access configured as 'allowed' in a file control policy.

Log Event: When you select Log Event for a read, write, or create action, a message is sent to the Windows event log whenever a user specified in this policy attempts to perform that action. You must have event logging enabled on the QFS Event Options tab for this to work (right-click the Quota & File Sentinel application icon in EASE to display the popup menu. Select Quota & File Sentinel, Properties to open the Quota & File Sentinel Configuration dialog).

Always Allow: When you select this action, the users speci-fied in this policy will always be "allowed" when they attempt to perform the selected action (read, write, and/or create).

Always Deny: When this action is selected, the users speci-fied in this policy will always be "denied" when they attempt to perform the selected action (read, write, and/or create).

Messages: Choose whether to have QFS send Email messages for this policy in HTML or Plain Text format. QFS provides you with an editor when you compose your email messages where you can apply formatting such as bold, underlining, italics, and colors to words to HTML messages when you choose the HTML option.

Click the Messages and Actions button to display the File Control Messages and Actions dialog. This dialog lets you specify a variety of characteristics about the messages and actions that can occur when users managed by this policy attempt to execute certain actions (reads, writes, creates) on managed files or folders.


Setting Directories and Shares

You define the directories or shares you want Quota & File Sentinel to manage using the Directories or Shares tabs on the File Control Policy properties dialog.

To define directories or shares for a particular file control policy:

1 Double-click on the desired file control policy or create a new file control policy.



4 Type the path to and name of the directory you want to add, or use the Browse button to choose a directory. This field also accepts directory names for directories that do not exist.



The Managed Users and Groups tab identifies the users and groups to which a policy applies. The Exempt Users and Groups tab identifies specific users and/or groups to exempt from a policy.


1 Double-click on the desired file control policy or create a new file control policy.



Choose "Restrict Everyone" (everyone is managed by the policy) or "Restrict Selected Users" (only the users listed are managed by the policy). When you select the Restrict Selected Users option, you won't be able to add individual users to the list.

4 If you chose Restrict Selected Users in step 3, click the Add button to display an add box and Browse button.


Press Enter, or click OK, to add the item and close the edit box.




2 Click the Add button to display the Add or Edit an Item dialog box.


Press Enter, or click OK, to add the item and close the edit box.

Creating File Removal Policies 71

Creating File Removal Policies

File removal polices let you automatically delete files from folders or shares that Quota & File Sentinel is managing after x hours, days, weeks, or months. You can configure certain options about the deletion. For example, you can choose to delete files based on their creation date, modified date, or their last accessed date. The quota policy begins the moment a user creates a file.

To create a file removal policy:


2 Right-click on File Removal Policies.

3 From the popup menu, choose New, Folder Policy Using Directories or New, Folder Policy Using Shares.

The New File Removal Policy dialog box lets you configure all of the rules associated with the policy, such as the directories you want to manage with this policy, the users managed by this policy, and how often to delete files from the managed directories.

4 Click the Help button on any tab for information specific to that tab.

You can always create a new policy by copying any existing policy. Either copy and paste or drag-and-drop an existing policy to the location where you want the new policy. If you copy it to the same location, the policy properties dialog opens and you can specify a new name. All policies must have unique names. Furthermore, you cannot have a disk quota policy and a file control policy with the same name; you will be prohibited from creating policies with the same names.


The General tab lets you specify basic information about the policy, such as a name and an optional description.

Setting Description

Policy Name: This is the name that appears in the EASE Admin hierarchy. After you create a policy, you cannot rename it from within this dialog. However, you can rename it in the right or left pane of EASE Admin. All policies must have unique names. Further-more, you cannot have the same name for a disk quota and a file control policy.

Description: Enter optional text to help you identify this policy.


Setting How Often to Remove Files (Lifetime Tab)

The Lifetime tab lets you specify when to delete files under the control of this File Removal Policy.

To specify how often to delete files:

1 For the desired file control policy, click the Lifetime tab.

2 Choose how often you want to remove files under this policies control.

Your choices are hours, days, weeks, or months. Select one of these options then enter a number in the “Duration is” field (every 2 days, every 4 weeks, etc).

3 Decide whether you want to delete files from the directory that existed before you created this policy.

If you select the "Delete files created before this quota existed", QFS will delete all files under the policy's control that were created before the date and time this policy was created.

4 Click Apply to add these settings to the policy.

Note: If you are performing a software upgrade that affects files that are controlled by a file control policy, the upgrade will likely fail. Before upgrading controlled files, you must remove the file types from the policy, or suspend enforcement on the affected objects, or use an account ID that is listed on the Exempt Users and Groups tab of the policy that is enforcing the rule(s).


Choose to apply this policy to either just workstations, just serv-ers, or to all servers and workstations (the default)

When more than 1 policy applies

“Always enforce this one”.

If more than one Disk Quota Policy or File Removal Policy is applied to the directory or share this policy is managing, use this policy.





Setting Thresholds

A file removal threshold lets you specify when to send a reminder that a policy is about to remove files from a directory. For example, you could have Quota & File Sentinel send email to an employee saying his or her files will be removed in 4 hours.

When a threshold level is reached, this is known as a threshold event and Quota & File Sentinel carries out the actions and notifications defined for that threshold. You define the actions and notifications.

The Thresholds tab lets you define the following:

• One or more thresholds for a quota policy. You can create up to 200 thresholds for each policy.

• The messaging options (popups or emails) for various types of users (owners, triggering users, and other recipients).

• For each threshold, you can configure different message text for owners, triggering users, and other recipients. You can also have different text for when a threshold is exceeded and when the object size returns to below the threshold.

• Commands (programs, batch files, or scripts) for each threshold that Quota & File Sentinel runs when a threshold level is reached. You can specify different commands for when a threshold is exceeded and when the object size returns to below the threshold.

To create a new threshold:

1 On a policy’s Thresholds tab, click the Add button.

You can also create a new threshold based on the settings of an existing threshold, click the threshold that has the settings you want to use and then click the Copy button. The Threshold Properties dialog box appears so you can make the changes you need for the new threshold.

2 Now configure the tabs associated with the Threshold Properties dialog (General, Other Recipients Messages, Owner Messages, Triggering User Messages, and Threshold Commands). Each of these tabs are described in the sections that follow.


Setting General Threshold Properties

The General tab on the Thresholds Properties dialog lets you define the kinds of thresholds you want to implement for this policy, and the types of messages that Quota & File Sentinel sends when the threshold event occurs.

Setting Description

Threshold Setting: To define this threshold, choose one of the following threshold settings:

Time Remaining: Sends an email or popup notification (which ever you specify) x hours before the file removal occurs.

Time Expires: Sends an email or popup notification (which-ever you specify) when the file removal policy reaches the dura-tion you set on the policy's Lifetime tab

Notification Mes-sages to send when threshold is reached:

The types of notifications that Quota & File Sentinel sends when this threshold is passed. Quota & File Sentinel can send notifica-tion messages using either popups or email messages to the fol-lowing:

Other Recipients: Optional notification recipients. In each policy, you can define a list of people who can receive notifica-tions of threshold events. Typically, you would add the Quota & File Sentinel administrator to the list, but you can add anyone you want.

Owner: Any account ID connected to a policy share that includes a policy object that passes a threshold. Only account IDs that are defined in the Managed users and Groups tab of the policy properties can receive Owner messages.

You can also configure Quota & File Sentinel to send daily email reminders to users by selecting Send Reminders under “Send to Triggering User”. Before you can use daily email reminders, you must enable the option as described in "Enabling Daily Email Reminders" on page 39.

User Name Popup: When this option is selected, if a threshold is passed, Quota & File Sentinel sends popups only to the computer the user logged on to first.


Setting Other Recipients Messages

When Other Recipients Messages are enabled (“Send to Other Recipients” on a threshold's General tab), Quota & File Sentinel sends the text defined on the Other Recipients Messages tab to users listed in the policy’s ' Other Recipients tab.

Note that members of the Other Recipients list receive notifications even if they are also listed as Exempt Users and Groups.

Setting Description








Setting Owner Messages

When Owner Messages are enabled (“Send to Owner” on a threshold's General tab), Quota & File Sentinel sends the text defined on the Owner Messages tab to the NT owner of the policy object involved in the threshold event. The NT owner account ID must be specified in the Managed Users and Groups tab of the policy to receive Owner messages.

Setting Threshold Commands

Quota & File Sentinel can launch batch files, programs, and scripts for a threshold event. You can configure separate commands (actions) for when a policy object exceeds its threshold and when it passes back below the threshold.

You do not have to enable commands; Quota & File Sentinel automatically executes any text that appears in the boxes on the Threshold Commands dialog. To disable a command, simply delete the text from the command box.

If the command results in a message being returned to Quota & File Sentinel, for example, an error message, Quota & File Sentinel writes the information to the Windows Event Log.

Setting Description



Quota & File Sentinel uses the text you specify here as the body of emails and popup messages for threshold events. If you want, you can leave the default sample text or create your own mes-sage. Note that you can use variables in this message text. Refer to "Using Variables in Messages" on page 85.





To set a command (action) for a particular threshold:


2 Click the Thresholds tab.

3 Double-click on the threshold you want to assign the command (action) to.

4 Click the Threshold Commands tab.

5 Enter the desired command into the appropriate box. Quota & File Sentinel can launch batch files, programs, and scripts.

6 Click OK.

Setting Directories or Shares

You define the directories or shares you want Quota & File Sentinel to manage using the Directories or Shares tab.

To define directories or shares for a file removal policy:

1 Double-click on the desired policy or create a new policy.



4 Type the path to and name of the directory you want to add, or use the Browse button to choose an existing directory. Note that this field also accepts directory names for directories that do not exist.


5 Choose how you want to apply the quota limit.

The Individual limit option means that the policy limit is tracked and enforced on each policy object individually. The Combination of objects option means that the policy limit is tracked and enforced on the combined (total) size of all policy objects.

6 You can click the Size button to display the current size information on the specified directory.

Note About Mapped Drives: In policies managing mapped drives (drives specified in directory policies by UNC name), the size that Quota & File Sentinel (QFS) reports on for these drives can become out of sync with the actual sizes. QFS manages outgoing activity to UNC names, while regular directories specified in policies are managed on incoming activity. Since other workstations (not managed by QFS) may have the same UNC name mapped, these workstations can update files without passing through QFS.


Therefore, sizes reflected in QFS may not always reflect actual size. To compensate for this, QFS automatically refreshes the UNC size information every 30 minutes.


Use the Managed Users and Groups tab to define the users and groups you want to apply to any policy. The Exempt Users and Groups tab lets you define specific users and/or groups you want to exempt from any policy.


1 Double-click on the desired policy or create a new policy.



– Choose "All Users Together" (everyone is under management) or Each User Individually (only the users listed are under management). When you select the All Users option, you won't be able to add individual users to the list.

4 If you're managing individual users, click the Add button to display an edit box.









Setting Other Recipients

The Other Recipients tab lets you specify which users should receive the messages you configured on the Other Recipients Messages tab for each Threshold associated with the policy.

To set Other Recipients for a policy:


2 Click the Other Recipients tab.

3 Click the Add button to display an edit box.




Creating Server Policies

A server policy enforces its rules on every volume on the server.

To create a server policy:

1 Expand the EASE hierarchy to display the level where you want to put the server policy.

2 Right-click a Quota & File Sentinel object (either a disk quota, a file control policy, or a file removal policy) to display the popup menu, then choose New, Directory Policy or New, Share Policy to open the New Policy dialog box.

3 Configure the policy settings on all tabs. (For detailed information about the items on each tab, click the Help button.

4 On the Directories or Shares tab, add a single entry of * or *.*.

Part II: Advanced Tasks 81

Part II: Advanced Tasks

This section contains instructions on how to perform some of the more advanced tasks associated with Quota & File Sentinel. Included in this section are:

• "Suspending Policy Enforcement" on page 82

• "Using the Overdraft Feature (disk quota and file removal policies)" on page 84

• "Using Variables in Messages" on page 85


Suspending Policy Enforcement

Occasionally, the size limits or file control restrictions set on network objects by your policies can interfere with someone's ability to get a job done. Therefore, you might occasionally need to turn off your policy rules temporarily. Quota & File Sentinel has the following features that let you do that:

• Suspending enforcement

• Suspending enforcement with timeout

The sections that follow describe each.

Suspending Enforcement

Suspending policy enforcement means that users can update policy objects even if the operation will violate the rules of the policy. For example, when you suspend enforcement on a disk quota policy, the managed users can perform actions that exceed the Deny Write threshold specified in the policy. Similarly, if you suspend enforcement on a file control policy, the managed users can perform actions that violate the Control Options rules specified in the policy.

For suspended disk quota policies, Quota & File Sentinel still tracks the quota limit but takes no actions when the policy rules are violated.

You can suspend policy enforcement at different levels of the EASE hierarchy. For example, you can suspend enforcement on a policy that is providing inherited properties for other policies lower in the hierarchy.

To suspend enforcement on a policy or a policy object:

1 Right-click the policy or the policy object for which you want to suspend to display the popup menu.

2 On the popup menu, click Suspend Enforcement.

Suspending Enforcement With Timeout

When you suspend enforcement with a timeout, you disable the policy enforcement for a fixed period of time. When the time period expires, or if you reboot the server, policy enforcement resumes automatically.

Note: The Suspend Enforcement with Timeout feature is dependent on the Quota & File Sentinel Service. If you start and stop the service, for example by rebooting the server, Suspend Enforcement with Timeout is canceled. This also means that you can Suspend Enforcement with Timeout only at server-level Quota & File Sentinel applications.

Suspending Policy Enforcement 83

To suspend enforcement with a timeout:

1 Right-click the policy or the policy object for which you want to suspend enforcement to display the popup menu.

2 On the popup menu, click Suspend Enforcement with Timeout.

3 A dialog appears with a prompt for the number of minutes for the timeout period. Specify a number from 1 to 1440 minutes (which equals 1 day), and then click OK.

Resuming Policy Enforcement

To resume enforcement on a policy or an object that has had policy enforcement suspended (or suspended with a timeout):

1 Right-click the object for which you want to resume policy enforcement to display the popup menu.

2 On the popup menu, click Resume Enforcement.


Using the Overdraft Feature (disk quota and file removal policies)

Use the overdraft feature to let managed users exceed a policy's Deny Write level for a defined period of time (in minutes), and for a certain percentage over the quota limit. For example, if a policy’s quota limit is set to 50MB, the Deny Write level is set to 100%, and the Overdraft is set to 10%, then the overdraft amount can be 10% above the quota limit (or 5 MB). This means users can go 5MB over their 50MB quota limit (so at 55MB, they would be denied).

Note: If an object is in overdraft mode, and you increase the overdraft value for the object, the new value will take effect only after the overdraft time limit expires, or someone brings the object under the overdraft level.

To configure an overdraft for an existing disk quota policy:

1 Double-click on the desired disk quota policy to display the properties dialog.

2 Click the Quota tab.

3 Select the Deny Writes at check box to enable the overdraft feature.

4 Select the Allow an Overdraft of check box and enter a number that represents the percentage over the Deny Write level you want to allow.

If the Deny Writes at level is set to 120%, and the Overdraft is set to 10%, then the overdraft amount can be12% above the limit.

5 Decide how long to allow the overdraft.

– Select No Time Limit on Overdrafts to let users remain in overdraft mode indefinitely.

– Restrict the amount of time users can remain in overdraft mode by selecting Overdraft Time Limit of and entering the number of minutes you want the overdraft rule to be in effect. You must enter a number between 1 and 9999.

Using Variables in Messages 85

Using Variables in Messages

You can use variables in the text of notification messages to include specific information, such as the name of the object with the limit. These variables can be used in the body of the email text as well as in the subject line. You can also use these variables in command line text. The table below lists the available variables. Variables are not case-sensitive.

Variable Value supplied in the message

%A For file control policies, this variable displays the file access mode (read, write, or create) currently blocked in this policy.

%C This variable displays the capacity of the drive in megabytes which con-tains the directory where the threshold event or file control event occurred.

%D For file removal policies, specifies the duration of the policy.

%E For file control events, this variable displays the file's extension without the dot.

%F For file control events, this variable displays the file name and extension without the path.

%L For disk quota policies, this variable displays the quota limit of the policy in megabytes.

%M For file removal policies, specifies the time re(M)aining before files are deleted.

%N For file removal policies, specifies the unit of time remaining before files are deleted (“Hours” or “Days”).

%O For disk quota policies, this refers to the NT owner of the file that caused a directory to cross a threshold.

%P For disk quota policies, this refers to the path or share name the threshold applies to (if any). For file control policies, this refers to the path or share name along with the file name for which the file control event occurred on.

%Q The disk quota or file control policy name.

%R The name (account ID) that the message is being sent to (the recipient)

%S This variable displays the server name of the Quota & File Sentinel ser-vice that sent the message.

%T For disk quota policies, the threshold percentage that has been passed.

%U For disk quota policies, the name of the user (account ID) that caused the directory to cross the threshold. For file control policies, the name of the user (account ID) that caused the file control event.


The following is an example of a notification message that uses variables:

%R, %U has caused %P to reach %T%% of its allowed limit of %L MB. Writes that exceed the limit will not be allowed. If you have questions, please call our Help Desk at extension 123.

%V This variable displays the volume label of the drive which contains the directory where the threshold event or file control event occurred.

%W Deny (W)rite percentage.

%X This variable displays the amount of extra space left on the drive (free space) in megabytes which contains the directory where the threshold event or file control event occurred.

%Y Displays the overdraft percentage for a disk quota or disk quota file policy.

%Z Displays the overdraft time period in minutes for a disk quota or disk quota file policy.

%% Inserts the percent sign (%) in the message text.

Setting Object Status Indicators 87

Setting Object Status Indicators

You can use font characteristics to show the status of objects in the right pane detail view. For example, you can specify that any file, directory, or share that is not included in a Quota & File Sentinel policy appear as 8 pt. red Arial. You can set font indicators for the following object conditions.

Non-policy objects - Directories and shares on this server that are not included in a Quota & File Sentinel policy, and therefore, not subject to limits.

Policy objects - Directories and shares on this server that are included in one or more Quota & File Sentinel policies.

Overlimit objects - Directories and shares on this server that are included in a Quota & File Sentinel quota policy and have exceeded the policy Deny Write threshold. (An object can exceed the Deny Write threshold only when overdrafts are enabled or when an exempt user adds data to the object.)

Suspended objects - Policies, directories, and shares on this server that have had limit enforcement manually suspended.


To set indicator fonts:

1 On the Options menu, click Appearance, and then choose the object category you want to configure. The Font dialog appears.

2 Specify the font characteristics for this category and then click OK.

The formatted fonts appear only in the Detail view. To display the right pane in the Detail view, click Details on the View menu.

Chapter 5

Creating Reports

This chapter explains how to use the Quota & File Sentinel Report Module. The Report Module that lets you create fully formatted reports which provide you with information on the status of your monitored disks.

With the Report Module, you can create custom-formatted printable documents, web-ready documents, and you can even export report data into formats suitable for import into other applications.

The Report Module is a separate program but it is installed automatically when you install the Admin client component of the Quota & File Sentinel application.


• "What Is the Report Module?" on page 90

• "Installing the Report Module" on page 90

• "Starting the Report Module" on page 91

• "Configuring the Report Module" on page 92

• "Creating New Reports" on page 93

• "Copying Reports" on page 96

• "Printing Reports" on page 97

• "Modifying Reports" on page 98

• "Exporting Report Data" on page 102


What Is the Report Module?

The Quota & File Sentinel Report Module lets you create a variety of preconfigured and custom reports showing data generated and tracked by the Quota & File Sentinel application. These reports can contain as much or as little detail as you need; you have complete control over what information to include. After creating a report, you can quickly update it and/or print it. You can also save reports for later viewing, or you can save reports directly to HTML format.

Here is a list of the preconfigured reports that are available from the Quota & File Sentinel Report Module:

All Quota Policies with Status Information - This report shows all disk quota policies sorted by percent full.

All Active Quota Policies - This report shows all disk quota policies with a status of active and sorted by name.

All Non-Active Quota Policies - This report shows all disk quota policies whose status is not-active (i.e. Suspended or Timed Suspended).

Quota Policies Over 75% Threshold - This report shows all disk quota policies whose percent full is 75% or greater of the limit, sorted by percent full.

Quota Policies over Quota - This report shows all disk quota policies that have exceeded their limit.

Usage by User - This report shows how much disk space users are currently consuming. This report shows the areas (directories and shares) and users controlled by Quota & File Sentinel disk quota policies.

You can use these reports as they are or tailor them to fit your needs.

Installing the Report Module

The Quota & File Sentinel Report Module is automatically installed whenever you install the Quota & File Sentinel application. You can also install just the Report Module onto a remote machine. This gives you the ability to run reports from a machine that does not have the full Quota & File Sentinel application installed on it.

To install the Report Module on a machine that does not have the full Quota & File Sentinel application on it, you must have the Admin software component of the Quota & File Sentinel application installed. Step-by-step instructions on how to do this are below.

To install the Report Module on a system that does not have the full Quota & File Sentinel application installed:

1 Insert the Quota & File Sentinel product CD into the CD-ROM drive and begin the Quota & File Sentinel installation procedure.

Starting the Report Module 91

2 When the installation wizard displays this prompt, click Yes.

3 At the EASE Select Components prompt, make sure only EASE Admin is selected. You should deselect the EASE Service component since it is not required.

4 Proceed with the EASE installation wizard.

5 At the Quota & File Sentinel installation wizard’s Select Components dialog, make sure only Admin is selected. Deselect the Service component.

This installs the Quota & File Sentinel Report Module.

Starting the Report Module

To start the Report Module:

Click Start, NTP Software, Quota & File Sentinel Report Module.

Deselect EASE service.

Only EASE Admin should be selected.


Configuring the Report Module

The Report Module has three configuration options you can set. They control certain behavior of the Report Module and they are available from the Options menu.

• Default file location – Lets you specify a default location to save your reports.

• Load previous reports – Lets you specify whether to display the names of the reports that were open the last time you closed the Report Module. If this option is enabled, the reports display in the left pane when you open the Report Module.

• Merge data cells on report – When this option is enabled, the Report Module merges common data cells in the report. For example, a report that looks like this with this option disabled.

Policy Name Directories

Policy 1 C:\Fonts

Policy 1 C:\My Documents

Policy 1 C:\Program Files

Policy 1 C:\Temp

Policy 1 C:\Work




Policy 1 C:\Temp

Policy 1 C:\Work

To access this dialog, click Reports,then Options from the Quota & File Sentinel menu bar.

C:\Program Files\NTPSoftware\Quota&File

Creating New Reports 93

... would look like this with when it is enabled

Creating New Reports

Selecting Active Servers

Although the Report Module is automatically installed on the machine where you install the Quota & File Sentinel application, you can also install the Report Module onto other machines. If you are running the Report Module on a machine that does not have a full installation of EASE software installed on it (the EASE Service and the EASE Admin), the Select Active Server feature lets you connect to a remote EASE installation. This way, you can run reports showing data retrieved from remote EASE installations.

If you are running the Report Module from an EASE-enabled machine, you can use the Select Active Server feature to specify a different (remote) EASE server from which to generate report data.

The Active Server defaults to the local machine (no prompt is given to choose a different server until the report is generated). Once the report has been defined, you can change the active EASE server for that report. Once changed, all the data for that report will come from the specified server.

If you create a new report, the active server defaults back to either the local machine, or to the server specified when the Report Module first starts. Note that each report you create can have a different active server for retrieving data.

Policy Name Directories

Policy 1 C:\Fonts

C:\My Documents

C:\Program Files

C:\Temp

C:\Work


C:\Temp


C:\Temp

C:\Work


Accessing the Select Active Server Feature

There are two ways you can access the Select Active Server feature. You can select it from the menu bar under Reports, or you are automatically prompted to select an active server if you attempt to create a report from a remote EASE machine.

To access the Select Active Server feature from the menu bar:

1 Click Reports from the menu bar.

2 Click Active Server from the popup menu. The Select Active Server dialog appears.

3 Enter the name of the desired EASE active server, or click the Browse button to navigate to it.

4 Click OK.

Creating a New Report

To create a new report:

1 On the File menu, click New (or click the button) to start the Report Wizard.

2 Respond to the Report Wizard dialogs to design your new report. The newly created report displays automatically.

You can create a filter to add to a report. For more information about adding a filter as you create your report, see “Creating a Filter” below.

If you want to save the report, select Save from the File menu (or click the button), or select Save As HTML if you want to save the report in a format suitable for publication on the web.

Creating a Filter

You can create filters to add to your Quota & File Sentinel reports. Adding a filter lets you tailor a report to show specific data. For example, you can create a filter that queries a specific server (or set of servers) and reports only on Service Watcher events.

Creating New Reports 95

The procedure below describes how to add a filter to a new report that you are about to create. For instructions on how to add a filter to an existing report, see "Adding a Filter to an Existing Report" on page 99.

To create a filter to add to a new report:

1 Select the type of report you want to create. Do this by clicking New on the File

menu (or click the button) to start the Report Wizard.

2 Access the Create Filter dialog automatically through the Report Wizard, or by

clicking Filters from the Report menu (or by clicking the button).

3 In the Create Filter dialog, construct the first line of the filter by selecting a report column field from the report column pull-down menu (example: Policy Type, etc.).

4 Select an operation from the operation pull-down menu (example: =, >=, >, etc.). The items in this pull-down menu change depending on what you selected in the report column field.

5 Select a value from the value pull-down menu or enter the appropriate data in this field. The items in this pull-down menu change depending on what you selected in the report column field. When appropriate, this field becomes a data-entry field and you type in the appropriate data.

6 If you want to include multiple variables in the filter, use the left and right parenthesis entry fields. These fields accept only the left and right parenthesis characters respectively. If you try to enter the wrong type of parenthesis, you get a message indicating that you have an open loop in the statement.

7 Click the Add button on the Create Filter dialog to add the first line of the filter. You can include as many lines in the filter as you like.

Note: To edit an existing line in a filter, highlight the line and click the Edit button. Re-enter the information using the pull-down menus and value entry fields at the top of

Report column Operation

Value

Left parenthesis entry field

pull-down pull-downpull-down

AND/ORpull-down

Right parenthesis entry field


this dialog, then click the Save button. To insert a new line between two existing lines, click the Insert button.

8 When the filter is finished, click OK to close the Filter dialog, and Finish to complete the Report Wizard.

The report generation completes and the finished report is automatically displayed.

Deleting a Report

To delete a report:

1 In the left pane of the Report Module, click the name of the report you want to delete.

2 On the File menu, click Delete (or click the button).

Copying Reports

You can create new reports by copying existing ones. There are two methods for copying reports: use the Report Wizard to “clone” and modify a report, or use the Copy command to make a quick duplicate of the active report.

Copying a Report Using the Report Wizard

To copy a report using the Report Wizard:

1 In the left pane, click the name of the report you want to copy. If the report does

not appear in the report list, click Open on the File menu (or click the button) to display the Open dialog. Choose a report, then click Open.

2 Select Wizard on the Report menu (or click the button) to display the first Report Wizard dialog.

3 Select Clone and modify an existing report, then click Next.

If you have more than one report open, choose the report you want to copy, then click Next.

4 Type a name and title for the new report, then click Next.

5 Continue through the Report Wizard dialogs, making changes as necessary, until you reach the last Report Wizard dialog.

6 Click Finish at any point to generate the report.

Printing Reports 97

7 If you want to save the report, select Save on the File menu (or click the button), or select Save As HTML to save the report in a format suitable for publication on the web.

You must rename the report to a different file name.

Copying a Report Using the Copy Command

To copy a report using the copy command:

1 In the left pane, click the name of the report you want to copy. If the report does

not appear in the report list, click Open on the File menu (or click the button) to display the Open dialog. Choose a report, and click Open.

2 Select Copy from the Report menu.

The Report Module creates a copy of the report and gives the copy a filename of the old filename preceded by “Cpy.” Use Save As to copy this file to a new file name if you like.

3 If you want to save the report, select Save on the File menu (or click the button), or select Save As HTML to save the report in a format suitable for publication on the web.

You must rename the report to a different file name.

Printing Reports

Previewing a Report

Before printing a report, you should preview it. The preview window shows you exactly how the report will look if you print it.

1 Click the name of the report you want to preview. If the report does not appear in

the report list, click Open on the File menu (or click the button) to display the Open dialog. Choose a report, then click Open.

2 Select Print Preview on the File menu (or click the button).

If the report columns do not fit on one page, try changing the page layout to landscape by clicking . Or you can remove and resize some of the columns or change the report's margin settings. (See "Modifying Reports" on page 98.)

3 You can print the report from the preview window by clicking .


Printing a Report

To print a report:

1 Click the name of the report you want to print in the left pane. If the report does


2 If necessary, refresh the data in the report by clicking Refresh on the Report menu,

or click the button or press F5. (See "Refreshing (Updating) Report Data" on page 98.)

3 Click Print on the File menu (or click the button).

Modifying Reports

After creating or copying a report, you can modify it in any of the following ways:

• Refresh the information displayed

• Add a filter to an existing report

• Change the title

• Add or remove columns of data

• Rearrange or resize columns

• Add or remove servers from which to gather information

• Change the sort order of the information displayed

• Change the fonts

• Change the page setup (margins and orientation)

Refreshing (Updating) Report Data

When you open an existing report, you see the information from the time the report was created or last updated. If you created the report a few days ago, that data is two days old. To see current information, you must refresh the report information. You can quickly update a report by doing the following:

1 Click the name of the report you want to update in the left pane. If the report does

not appear in the report list, click Open on the File menu (or click the button) to display the Open dialog. Choose a report then click Open.

Modifying Reports 99

2 Select Refresh on the Report menu, or click the button, or press the F5 button on your keyboard.

Adding a Filter to an Existing Report

Once you have created a report, you can then add a filter to it if you want. Adding a filter to an existing report allows you to filter the report for very specific data.

To add a filter to an existing report:

1 Select and open the desired report.

2 Access the Create Filter dialog by clicking Filters from the Report menu or by

clicking the button.

3 Create a new filter, or edit the existing one. (See "Creating a Filter" on page 94.)

4 When the filter is finished, click OK.

5 Now update the report by selecting Refresh on the Report menu, or click the button, or press the F5 button on your keyboard. (See "Refreshing (Updating) Report Data" on page 98.)

The report generation completes and the finished report is automatically displayed.

Changing the Title of a Report

To change a report’s title:

1 In the left pane, click the name of the report you want to modify. If the report does


2 Select Title on the Edit menu to open the Edit Report Title dialog.

3 Type a new title for the report and click OK.

4 Select Save on the File menu (or click the button) to save the report, or select Save As HTML to save the report in a format suitable for publication on the web.

Adding or Removing Columns of Data

1 Click the name of the report you want to modify in the left pane. If the report does


2 Right-click on a column heading to display a popup menu.


3 On the popup menu, select Insert Column or Delete Column.


Rearranging or Resizing Report Columns

To rearrange or resize report columns:

1 Click the name of the report you want to modify in the left pane. If the report does


2 To rearrange (move) a column, click and drag on a column's title. To resize a column, put the cursor over a column's title box boundary until the cursor changes to a . Then click and drag to resize the column.

3 Click Save on the File menu (or click the button) to save the file, or click Save As HTML to save the report in a format suitable for publication on the web.

Adding or Removing Servers from a Report

To add or remove servers from a report:



2 Click Servers on the Report menu (or click the button) to open the Servers dialog.

3 Select the servers you want to add or remove, then click the arrow button to move them, then click OK.


Changing the Sort Order of Report Data

To change the sort order of report data:



Modifying Reports 101

2 Click Sorting on the Edit menu (or click the button) to open the Sorting dialog.

3 Select the columns by which to sort the report by moving them to the Sort Columns side of the dialog.

4 Select one column at a time in the Sort Columns side of the dialog, then click Ascending or Descending.

After you designate a column as a Sort Column, you can change its sort order by right-clicking the column's heading to display a popup menu. Next select Ascending or Descending.


Changing Report Fonts

To change a report’s font:



2 Click Font on the Edit menu to open the Font dialog.

3 Click the font, font style, or size you want, then click OK to update the report.


Changing Report Page Setup

You can change the top, bottom, left and right margins for a report. You can also change the report's orientation to either portrait or landscape.



2 Select Page Setup on the File menu to open the Page Setup dialog.

3 Change the settings, then click OK.

4 Specify margin settings in the Margins tab. Click the Orientation tab and select Portrait or Landscape.



Exporting Report Data

You can export the data from any Quota & File Sentinel report you created into a comma delimited format. This is useful for importing the resulting .csv file into other applications.

To export report data into a comma delimited format:

1 Click the name of the report you want to export in the left pane. If the report does

not appear in the report list, click Open on the File menu (or click the button) to display the Open dialog. Choose a report and then click Open.

2 Select Export on the File menu.

3 Give the report a new name or leave the report name as it is; make sure the file extension is .csv.

Chapter 6

Understanding EASE

This chapter explains the administrative environment in which NTP Software Quota & File Sentinel operates—Enterprise Application Services Extension (EASE). You will learn that after you install Quota & File Sentinel, you can create a management hierarchy for your Quota & File Sentinel servers. Using the EASE principle of property inheritance, you can easily manage a large number of servers. One of the main purposes of EASE is to enable you to more easily configure and manage multiple EASE-enabled applications that are distributed throughout your enterprise.


• “What Is EASE?" on page 104

• “Hierarchy Configuration" on page 108

• "Remote Installation" on page 110

• “Managing the Hierarchy" on page 111

• “Managing Security" on page 115

• “Managing EASE Networks" on page 117


What Is EASE?

If you have only one server on your network, application management is simple—you log on to the server, make changes to your applications, and the server uses the new settings. But what if you have 100 servers or 500 servers? In the traditional world of service management, changing a setting on all the services is a tedious job of managing one service at a time.

Quota & File Sentinel moves beyond traditional Windows service management by employing Enterprise Application Services Extension (EASE), a hierarchical administrative model for distributed configuration management. You create a management hierarchy and use property inheritance to manage all of your Quota & File Sentinel servers, as well as other EASE-enabled applications, from a single interface.

Each installation of Quota & File Sentinel shares its configuration data with every other Quota & File Sentinel installation through a replicated data store. If you change a setting for one Quota & File Sentinel server, that information is replicated to every Quota & File Sentinel installation. No matter where you log on in your network, you see current information for all of your Quota & File Sentinel servers.

What Is EASE? 105

The EASE Admin and the Administrative Hierarchy

You manage Quota & File Sentinel through the EASE Admin program. The EASE Admin interface is a two-pane window.

Quota & File Sentinel in the EASE Admin

After you install Quota & File Sentinel, you start with a default hierarchy, which you can then customize to suit your needs.

The title bar, menus, and toolbar change according to the type of object you select. When you select an EASE object, such as a container, the EASE application becomes active and you see EASE menus and buttons. When you select a Quota & File Sentinel object, the Quota & File Sentinel application becomes active and you see Quota & File Sentinel menus and buttons.

The left pane shows your administrative hierarchy, with Explorer-like navigation elements.

The right pane shows information about the selected left pane object. You can display large icons, small icons, a list view or a detail view. You can drag-and-drop network objects, display object contents, and delete objects.


The following list describes each of the major components of an EASE administrative hierarchy.

The Organization is the top level. Your hierarchy can have only one organization. You can rename it to something more appropriate such as your company name. The organization functions like a container; that is, it holds other EASE objects.

Below the organization is a Container, which is simply a logical grouping of other objects. It can be referred to as an “organizational unit.” A container can hold other containers as well as servers and applications. An EASE hierarchy must have at least one container, and a container can have properties, such as EASE security properties.

Every machine where you install Quota & File Sentinel appears as a Server under a container. Each time you install Quota & File Sentinel, the new server and application automatically appear in the hierarchy. If you manually add a server to your EASE hierarchy, the EASE software is remotely installed on that computer. (For more information on remote installation, see “Remote Installation" on page 110.

Quota & File Sentinel appears as an Application under a server icon. An application can also reside under the organization or a container to provide

What Is EASE? 107

inherited properties to applications lower in the hierarchy. An application under a server represents a service running on a machine.

A Basic Administrative Hierarchy

The Hierarchy and Property Inheritance

Before you decide how to arrange your hierarchy, you should understand EASE property inheritance. Stated simply, if an application has a property defined at the server level, it uses that property. If the property does not exist at the server level, the application inherits that property from the next higher level in the hierarchy where the property is defined.

Property inheritance allows you to define application properties that apply to a number of different servers by defining those properties at the appropriate place in the EASE hierarchy. For example, you can define policies at a container level application and use

......

..

My CompanyQuota & File Sentinel

running at theorganization level

(configuration settings)

Quota & File Sentinel


+

+

........+

........

........

......

..+

........ EASE System Manager

......

.....

.....+

........

........

......

.. Quota & File Sentinelrunning at the

container level(configuration settings)

+....

....

(active applications)

Quota & File Sentinelrunning at theserver level

Server 1

Container 1



those settings for servers running below that container, as illustrated in the following hierarchy:

An Administrative Hierarchy with an Application at the Container Level

By placing containers and Quota & File Sentinel applications at multiple levels, you can create a complex and sophisticated hierarchy. For example, if you have servers at different geographical locations, you might want to have them inherit some site-specific properties and some company-wide properties.

Hierarchy Configuration

The default hierarchy structure includes an organization and one container. Within the container is the server where you installed Quota & File Sentinel and under the server is the Quota & File Sentinel application. If you want to use property inheritance, you must create a hierarchy of containers and Quota & File Sentinel applications, and configure the Quota & File Sentinel properties at the appropriate levels.

After you create your inheritance hierarchy, you define the application properties. A property that you define at the server level applies to the application running on that server only. A property at the organization or container level can be inherited by applications running lower in the hierarchy, but only if that property is not already defined at the server level. For example, if all of your Quota & File Sentinel servers will

An application does not have to belong to a server. You can put an application at the organization level or at a container level.

Quota & File Sentinel properties defined at the container level can be inherited by Quota & File Sentinel services running at lower levels.

Example: This application inherits its settings from the Quota & File Sentinel application above it at the container level.

......

..

My Company


Server 1


+

+

........+

........

........

......

..

+

........ EASE System Manager

......

.....

.....

Container 1

+

........

........

......

..

+....

....


What Is EASE? 109

use the same mail server for email notifications, you can configure that property at the top of your hierarchy so that all of your EASE servers can use the same setting.

Navigating and Rearranging the Hierarchy

EASE Admin displays the EASE hierarchy in the left pane and the contents of the selected EASE object in the right pane. You can expand an object by double-clicking it or by clicking the symbol and collapse it by clicking the symbol.

You can quickly rearrange hierarchy objects using drag-and-drop or cut and paste, which move the selected object and all objects lower in the hierarchy to the new location.

Note: When you rearrange an EASE hierarchy, you might affect property inheritance. An application may behave differently because it may have inherited new properties based on the new hierarchy object (server or container) it now inherits from. EASE Admin displays a warning message whenever you move an object to alert you of this behavior. You can enable and disable the warnings by enabling or disabling Show Move Warnings on the Options menu.

You can right-click icons and background areas to display a context-sensitive popup menu. The menu items are the same ones that you can access from the menu bar or Toolbar.

Menus and buttons are context-sensitive. If you click an application object, EASE Admin shows application buttons and menus. If you click an EASE object, such as a container, EASE Admin shows EASE buttons and menus.

Connecting to an EASE Server

When you start EASE through the Windows Start menu, you connect to the EASE service that is running on that computer. Any changes you make to EASE are written to the EASE data store on that computer, and then replicated to the other EASE data stores on the network. However, you can connect directly to an EASE service that is running on a different computer.

To connect directly to a different EASE server:

1 Click a hierarchy object to display the EASE menu bar.

2 On the File menu, click Active Server to open the Active Server dialog.

3 Type a server name or click the Browse button to choose an EASE server.


Enabling and Disabling Property Edits

You can enable and disable object property editing. When editing is disabled, you cannot edit hierarchy object properties.

To enable or disable edit mode:

1 Click a hierarchy object to display the EASE menu bar.

2 On the menu bar, click Options, Read Only Mode.

Remote Installation

After you install EASE on one computer, you can use EASE remote installation to “push” EASE, and any EASE-enabled applications (like Quota & File Sentinel) installed on that computer, to other computers on your network.

EASE technology allows you to remotely install EASE and any EASE-enabled applications on network servers. It does not matter if those servers are located in the same room as the source computer or halfway around the world. If the target server is accessible through your network and you have the proper administrative privileges to do a remote installation, you can remotely install both EASE and EASE-enabled applications on that computer.

Notes: 1. A remote installation installs the EASE components (EASE Admin and EASE service) that are installed on the source computer. If you need to select the components to install, (for example, install only the EASE Service) you must run the Setup program locally on the target computer, and make appropriate selections on the EASE installation Wizard’s Select Components dialog.

2. If you have configured EASE security, the account you use when you remotely install must have Write and Create Children permissions to the location in the EASE hierarchy where you are performing the remote installation. For more information on EASE security, see “Managing Security" on page 115.

Adding a Server

If a network server does not already exist in your EASE hierarchy, you may add it. Creating the server in your EASE hierarchy installs the EASE software on that server.

To create a new server in the EASE hierarchy and install EASE on that server:

1 Right-click the container where you want to add the server.

2 From the popup menu, click New, Server to open the New Server dialog.

Managing the Hierarchy 111

3 In the New Server dialog, specify the name of the server using the format \\domain\servername, and then click OK to start the EASE installation wizard.

4 Respond to the prompts for installing EASE. You need to specify the drive on the target computer where you want to install EASE and an account ID for EASE Service. If you specify an existing account ID, the installation process adds the privileges required by EASE.

Remotely Installing an EASE-enabled Application

When you install an EASE-enabled application on a remote server, the remote installation process prompts you for the target drive on the remote server and service account information for the application. If you have already performed a remote installation, the service account information you used for that installation is the default service account choice.

To install an EASE-enabled application on a remote EASE server:

1 Right-click the server to display the popup menu.

2 From the popup menu, click New, Application, <application name>.

3 Respond to the remote installation prompts.

Managing the Hierarchy

Adding, Removing and Changing Object Properties

The organization, containers, and servers each have a set of properties. Properties for these hierarchy objects cannot be inherited.

Note: The Options menu in EASE allows you to enable and disable property editing. Before you try to edit a property, make sure that Read Only Mode is disabled.

To add an object property:

1 Right-click the object to display the popup menu, and then click Properties.

2 On the Basic tab of the properties dialog, click Add Property.

To remove an object property:


2 On the Basic tab of the properties dialog, click Delete Property.


To change an object property:


2 On the Basic tab of the properties dialog, click Delete Property.

3 On the Basic tab of the properties dialog, click Add Property, and then recreate the property with the new value.

Moving an Object

You can rearrange hierarchy objects using drag-and-drop or cut and paste to move objects. A move operation moves the selected object and all objects lower in the hierarchy to the new location.

Note: When you rearrange an EASE hierarchy, you might affect property inheritance. An application may behave differently because it may have inherited new properties based on the new hierarchy object (server or container) it now inherits from. EASE Admin displays a warning message whenever you move an object to alert you of this behavior. You can enable and disable the warnings by enabling or disabling Show Move Warnings on the Options menu.

Creating a Container

As stated before, a container is simply a logical grouping of other objects. It can be referred to as an “organizational unit.” A container can hold other containers as well as servers and applications. An EASE hierarchy must have at least one container, and a container can have properties, such as EASE security properties.

To create a container:

1 Right-click the Organization or another container to display the popup menu, and then click New, Container to open the New Container dialog.

2 Specify a Name for the Container and an optional Description.

Removing a Container

You can delete hierarchy objects but you cannot delete an object that contains other objects.

To delete an object:

1 Right-click the object to display the popup menu, and then click Delete.

2 When prompted to verify, click Yes.

Managing the Hierarchy 113

Creating an Application

An application’s Setup program adds the application to the EASE hierarchy when you install the application. By default, the Setup program adds the following components:

• The server where you installed the software if that server does not already exist in the EASE hierarchy

• An application under the server

You can manually create new applications. For example, to create a new inheritance structure you might create a new container level application to define inherited properties. Note that with Quota & File Sentinel, to create a version of the Quota & File Sentinel application at the server level, you use the Quota & File Sentinel install agent feature.


To create an application at a container or organization level:

1 Right-click the organization, container, or server to display the popup menu, and then click New, Application, Quota & File Sentinel.

2 Optionally, right-click the object to display the popup menu and then click Rename.

Application Rules and Tips

• An application running under a server represents a service running on a machine. But you can place an EASE application anywhere in the EASE hierarchy, at the organization, container, or server levels. Organization and container level applications let you specify the properties that can be inherited by applications lower in the hierarchy.

Creating a Server

When you install Quota & File Sentinel, EASE adds the server to the EASE hierarchy. If you manually add a server, the EASE software is automatically installed on that server. For more information, see “Remote Installation" on page 110.

Server Rules and Tips

• A server represents a physical machine. EASE does not manage hardware, just the individual EASE-enabled application services running on the server.

• Each time you add a server or install an EASE-enabled application using the program’s setup or EASE remote installation, the EASE environment is installed on that server, and the new configuration data is automatically replicated to all EASE servers in the network.

• A server can hold applications only.

• A server can have properties, however, these properties cannot be inherited by other servers.

• You must add a server to a container. You cannot add a server to the organization.

Managing Security 115

Managing Security

When you install EASE for the first time, any account ID that can log on and start the EASE Admin program has full access to the EASE hierarchy. Once you define “allow” rights to a user or group, all other users and groups have no access unless it is explicitly granted. You set EASE security properties on individual EASE objects. These properties define who can read information about that object, write data to that object, and create other objects lower in the hierarchy.

Security extends downwards. You can allow a permission at one level, and then change it at a lower level. For example, if you give read access to UserA at the organization level, UserA has read access throughout the hierarchy. However, you can create a “deny read” property for UserA at an individual server. UserA can read data above the server, but cannot access data at the server level and below.

Note: The EASE Options menu, available from the menu bar, allows you to enable and disable property editing. Before you try to edit a property, make sure that Read Only Mode is disabled on the Options menu. By default, Read Only Mode is enabled.

To set security on an object in the EASE hierarchy:

1 In EASE Admin, right click an object to display the popup menu.

2 On the popup menu, click New, Property to open the New Property dialog.

3 In the Name field, type one of the EASE security properties listed in the table below.


Notes: 1. When creating a security property, spelling counts! However, property names are not case-sensitive.

2. In the case of conflicting permissions, “deny” has priority. For example, if you define “allow write” and “deny write” to userA at the same object, the “deny write” property has priority.

3. The rights described below are independent of each other. For example, write access does not inherently permit the user to read object info or create new objects.

4 For the Value field, specify an account ID, a local Group, or a global Group using the format

domain\accountID (or domain\accountID1; domain\accountID2; etc.)

5 Entering a Description is optional.

Security Property Notes

allow read Allows read access to the object and everything below it in the hierarchy that does not have a different property defined.

allow write Allows write access to the object and everything below it in the hierarchy that does not have a different property defined. Write access does not permit the user to read object info or create new objects.

allow create children Allows the user to create new objects (containers, servers, applications, and properties). Does not allow read or write access.

deny read Restricts all read access to the object and everything below it in the hierarchy that does not have a different property defined.

deny write Restricts write access to the object and everything below it in the hierarchy that does not have a different property defined.

deny create children Restricts the user from creating new objects (containers, servers, applications, and properties).

Managing EASE Networks 117

Managing EASE Networks

EASE servers do not discover each other. When you install EASE, you are prompted for the name of an EASE server, and then the new EASE server communicates with the named server, learns about the existing EASE network configuration, and joins the EASE network. (If you select the installation option that indicates that this is the first EASE server, then this EASE server will not be able to communicate with other EASE servers.) Once the network is established, EASE servers communicate with each other to maintain consistent data throughout the network.

The Networks view in the left pane of EASE Admin displays your EASE Network, that is, all of the machines in your network that are running the EASE service. EASE servers communicate with each other using default settings. You can change the communications behavior of an EASE server by creating specific network properties for that server. You can also affect the behavior of the whole network by creating the property on the network icon instead of the server.

Adding Network Properties

To change EASE server communications behavior:

1 Click an EASE object to enable the EASE menu.

2 On the Options menu, click View Networks.

3 In the Network view, right-click a Network or Server icon to display the popup menu.

4 From the popup menu, click Properties.

5 In the Name field, type one of the EASE network properties listed in the table below.

Network Property Notes

ReplicationWaitInterval The number of seconds EASE service waits after a change before it sends the update to its replication partners. A higher number results in less network traffic when large amounts of changes occur. A lower number allows changes to appear faster throughout the network, but results in more network traffic when large amounts of changes are made. You can set this property on a single server or on a network of servers. The default value is 120 seconds.


ReplicationInterval The number of minutes between advertisements of this server’s sequence number. Replication partners use the sequence number to determine if replication needs to occur. This property ensures that servers remain in sync. You can set this property on a single server or on a network of servers. The default value is 20 minutes.

ReplicationUpdateDelay The default is 30 seconds. This is the amount of time the EASE service waits between sending its sequence number out to each of its replication partners. The value is specified is seconds.

ReplicationPriority The default is medium. Valid values are low, medium, and high. This setting is used to specify how much cpu cycles the EASE service uses during replication.

DisableReplication When present, this property disables all data replication events. It prevents an EASE server from replicating its changes to other EASE servers or from accepting changes from other EASE servers. This property is evaluated by its presence alone and its value is irrelevant. This property has meaning only when set on a server.

DatastoreRebuildTime The hour of the day (1 - 24) when this EASE service reclaims unused space from deleted entries in its data store. This property has meaning only when set on a Server. The default value is 2, which causes database rebuilds to begin sometime between 2:00am and 2:59am. If you change this value you should choose a time when there is little chance of EASE configuration activity. The data store rebuild operation requires exclusive access to the data store. Setting DatastoreRebuildTime to 0 disables the rebuild.


Managing EASE Networks 119

6 For the Value field, specify an appropriate value.

7 Entering a Description is optional.

DatastoreCompressAtStartup

This network property value can be added to a server object. The values for this property are Partial and Full. This property performs compression (clean-up) operations on the underlying codebase database. A partial compression compresses the dbf files which removes deleted items, recovers lost space, and re-indexes the database. A full compression performs compressions of the fpt database files which removes deleted items and recovers lost space (in addition to a partial compression). Note: The fpt files are where the majority of the data is actually stored and tend to grow quicker than the dbf files. Also, the databases go through a full compression between 2 and 3 AM each night by default. This value is configurable through the DatastoreRebuildTime property.

AdvancedLogging Enables the EASE service to send detailed logging information to the Event Viewer. This property does not need a value; its presence alone enables advanced logging. This property has meaning only when set on a server.



121

Index

Symbols8

.csv file 102

AActive Server dialog 109Active-Active cluster configuration 31Active-Passive cluster configurations 31adding

EASE object properties 111network properties 117

AdvancedLogging 119allow create children 116allow read 116allow write 116appearance 88application level 106applications

creating 113EASE-enabled applications 103, 111

Bbatch files 54, 61, 73, 76Below Threshold Message 57box contents 7browser requirements 18

CCD-ROM 7changing

EASE object properties 111cluster configurations 31comma delimited format 102commands 54, 73community name 43components

EASE 91Computer Name Popup 56configuration tasks 35configuring

mail messaging 36overview 36

container level 106containers

creating 112removing 112

Control Options tab 67create children permissions 110creating

a container 112an EASE server 114applications 113

customer support 8

Ddata store 13, 104DatastoreCompressAtStartup 119DatastoreRebuildTime 118default hierarchy 108deny create children 116deny read 116deny write 116deny write level 52description 52Detail view 88directories

setting for disk quota policies 63, 77setting for file control policies 69

Directories tab 63, 77Directory policy

file control policies 71file removal policies 65

DisableReplication 118disabling

email 38notifications 38

disk quota policiescreating 50description 10Directories tab 63Exempt Users and Groups tab 64, 78General tab 52Managed Users and Groups tab 63, 78Quota tab 52setting thresholds 54suspending 82Thresholds tab 54, 73

disk space 10drag-and-drop 13, 109dynamic quotas 11

EEASE 13, 105

122

connecting to an EASE server 109data store 104definition 103EASE networks 117EASE-enabled applications 103, 111installing 21options 110property edits 110security properties 110, 115

EASE Admin 13, 90, 91description 105illustration 105uninstalling remote installations 33

email addressNTP Software 8

Email Configuration tab 38email settings

configuring 37enabling 41enterprise configuration 104Enterprise Service Applications

Extension 103, 104evaluation version 34Event Log 61, 76Exempt Users and Groups tab

file control policies 70exporting

reports 102

Ffile access 10file control policies

Control Options tab 67creating 65description 10, 11Exempt Users and Groups tab 69General tab 66Manages Users and Groups tab 69suspending 82

File Patterns tab 66filters

adding to reports 94reports 94, 99

font characteristics 87Font dialog 88

GGeneral tab

file control policies 66

Hhierarchy

default 108HTML

saving reports as 90, 94, 97, 99, 100, 101, 102

Iindicators 87inheritance 114

in EASE hierarchy 107inheriting email configurations 38installation 17

Report Module 90installation wizard 33installing

before you install 18EASE 21Quota & File Sentinel 17, 19remotely installing Quota & File Sentinel 29

Lleft pane 105lifetime 52limit strategy 52load previous reports 92logical space 49

Mmail client 36Managed Users and Groups tab

disk quota policies 63, 78file control policies 69

mapped drives 63, 77memory requirements 18merging data cells on reports 92Messenger service 41, 42moving

an EASE object 112

Nnavigating

EASE hierarchy 109network objects 11network properties

adding 117AdvancedLogging 119DatastoreRebuildTime 118

123

DisableReplication 118ReplicationInterval 118ReplicationWaitInterval 117

notifications 11, 36, 56, 74enabling for SNMP 42using variables 85

Oobject status indicators 87operating system requirements 18options

EASE 110organization level 106organizational unit 112Other Recipients 56, 74Other Recipients Messages 57, 75overdrafts 52, 55, 84Owner 56, 74Owner Messages 58, 76

Ppermanent 52permissions

create children permission 110create children permissions 110write permissions 110

replication 114policies

file control 11overview 49server policy 80suspending 82

policy name 52, 66pop-up menu 109popup messages

configuring 41privileges 18processor requirements 18production version 34Professional Services 8programs 54, 61, 73, 76property edits 111

enabling and disabling in EASE 110property inheritance 107

QQuota & File Sentinel

distributing 28installing on a cluster 31remotely installing 29uninstalling 33

Quota & File Sentinel box contents 7Quota & File Sentinel Service 13quota limit 52quota policies

cluster container level 31

RRead Only Mode

for property editing 110, 111, 115refresh

reports 98registration form 7remote installation 13, 33, 110remotely installing 28removing

containers 112EASE object properties 111

replication 104, 114ReplicationInterval 118ReplicationPriority 118ReplicationUpdateDelay 118ReplicationWaitInterval 117Report Module 12, 91

about 90installing 90starting 91

reportsadding filters 94comma delimited format 102copying 96creating 94default file location 92exporting 102merging data cells 92modifying 98moving columns 100Options menu 92previewing 97printing 98Report Wizard 94, 96selecting Active Servers 93sorting 100updating (refreshing) 98

124

requirementsQuota & File Sentinel 18

resuming policy enforcement 83right pane 105

Sscripts 54, 61, 73, 76security properties 110, 115

descriptions 115selecting Active Servers 93server

adding 110server level 37, 106server policy 80servers

creating 114service

Quota & File Sentinel Service 13service account 21service accounts 18setting 54setting actions 61, 76Share policy

file control policy 65shared disks 31shares

setting for disk quota policies 63, 77setting for file control policies 69

Shares tab 63, 77Size button 63, 77size limits 82SMTP domain 38SMTP server 38SNMP

community name 43configuring 42console/monitor IP address 43enabling messages 42inheriting configuration 42SNMP Configuration tab 42

sortingreports 101

starting 91suspending policy enforcement 82

suspending policy enforcement with timeout 82

Ttelephone number

NTP Software 7temporary 52Terminal Server 56threshold

creating 54, 73definition 54

thresholdssetting command 61, 76

Thresholds Properties dialogGeneral tab 55, 74

trademarks iitraining 8Triggering User 56Triggering User Messages 59

Uuninstalling

Quota & File Sentinel 33upgrading evaluation to production

versions 34URL for NTP Software 8User Name Popup 56, 74

Vvariables

in messages 85View menu 88View Networks 117

Wweb site

NTP Software 8Windows 2000 popup messages 42Windows 95 popup messages 41Windows 98 popup messages 41Windows Event Log 61, 76Windows NT popup messages 41WINPOPUP.EXE 41write permissions 110

Date post:	11-Oct-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times