H.0 Glossary

Action Block: A feature of File Dynamics that allow the sharing of specific policy options between multiple policies.

Admin Client: The management interface for File Dynamics.

Associated policy: A policy specifically assigned to a container, group, or user through the Associations settings in the Policy Editor.

Auxiliary policy: A policy associated with a User Home Folder policy that creates auxiliary storage for a user (along with the user home folder that is created from a user home folder policy) when a new user is created in Active Directory.

Auxiliary storage: Home folders associated to a user in addition to the regular network home folder. Depending on the storage policy, auxiliary storage can be made accessible or unaccessible to the associated user.

Blocking policy: A policy designed to block other File Dynamics policies from affecting members of organizational units, members of groups, or even individual users.

Consistency check: This Management Action notifies you of inconsistencies or potential problems pertaining to user and group storage being managed through File Dynamics. These potential problems might be missing storage quotas, inconsistent directory attributes, missing home directories, inconsistent file paths, and more.

Container: A synonym for organizational unit in the Micro Focus File Dynamics documentation.

Content Control policy: Similar to identity-driven file grooming, Target-Driven Content Control policies remove files according to file type, age, size, last accessed date, and more. From any file path, you can either vault files to a new location or delete the files altogether.

Collaborative storage: A shared storage area where a group of people in an organization can collaborate by accessing files. File Dynamics lets you easily create collaborative storage areas through collaborative storage policies that you can assign to Group objects or to an organizational unit.

Cross-Empire Data Migration: Separately-purchased subsystems of File Dynamics that allow for the movement of file system data, along with associated permissions, and metadata, between storage infrastructures on different platforms or different Active Directory forests. There is a Cross-Empire Data Migration offering from eDirectory to Active Directory, and another from Active Directory to Active Directory.

Data Location policy: These policies are the means of copying folders and their contents to a target parent folder. There is an option to remove the files from the source location after they have been copied.

Data Owner: An individual assigned by a network administrators to be notified of access permission changes, perform data recovery, or perform remediation of data located on High-Value Targets. Data Owners are normally assigned based on a user’s association with a folder or share that is classified as a High-Value Target.

Data Store: A designated share on the network where Epochs are stored and from which files and folders can be recovered. As a best practice, the data store should be set up so that only the filedynamicsproxyrights and filedynamicsadmins groups have access.

Deferred delete event: The scheduled deletion of a managed path, but has not yet taken place because the number of days in the Cleanup Storage parameter of the policy has not been met.

Dynamic Template Processing: Within File Dynamics, the process that creates personal folders in a collaborative storage folder.

Effective policy: A policy that is applied by default to a group, user, or subcontainer when no associated policy is specifically assigned.

Enumeration operation: The process of locating and displaying all objects.

Epoch: A representation of a High-Value Target at a point in time. An Epoch includes the directory structure and associated metadata, stored as an element of a Collection.

Epoch Data Protection Policies: A Target-Driven policy in File Dynamics that governs the operation, options, and schedule of how Epoch Data Protection is applied and used against a High-Value Target.

File Store: A storage repository for files in a Collection, referenced by one or more Epochs.

High-Value Target (HVT): A file system folder/directory deemed to hold valuable information. A High-Value Target might benefit from coverage by an Epoch Data Protection policy. Administrators or Data Owners in an organization can classify a folder as a High-Value Target based on appropriate evaluation. Thus, High-Value Target folders can be large or small.

Identity Map: Within the Cross-Empire Data Migration subsystem, the mechanism that lets you make security and ownership associations between the source and the target.

Identity-Driven Policies: Automated storage management tasks that are enacted through an association with Active Directory users and groups.

Managed Path: A location that File Dynamics manages in an automated fashion for any of the following: Home folder, Profile path, Remote Desktop Services Home folder, Remote Desktop Services Profile path, Collaborative storage (group and container), and Auxiliary storage.

Management Action: A manual action that allows you to enact a setting from a policy on existing users.

Nearline: An intermediate storage location that provides fast access to the data, but is not a generally accessible storage location on the network. Nearline storage inherently provides some level of security and data integrity.

Personal folder: A user-specific folder in a collaborative storage area.

Phoenix Agent: An agent that generates Epochs driven by Epoch Data Protection policies that are managed by the Engine.

Policy: Rules and settings within File Dynamics that indicate what storage-specific actions to enact when an event in Active Directory takes place. These actions include creating user storage when a new user is added to Active Directory, moving storage when a user is moved from one organizational unit to another, and archiving or deleting storage when a user is removed.

Policy weight: When a user is a member of multiple groups and each group has a separate policy, File Dynamics uses this setting to determine which policies to apply. File Dynamics applies the policy with the largest numerical weight.

Quota Manager: A Web browser-based management interface for designated users such as help desk administrators or support personnel that enables them to adjust quota on user home folder or collaborative storage areas without needing rights to the file system. Quota Manager can also provide select storage information such as total number of files and file types in a home folder.

Security Fencing Policies: Target-Driven policies that let you set limits on how access permissions can change over time by specifying containers, groups, or users that can be given access permissions and others that should never be given access permissions.

Security Lockdown Policies: Target-Driven policies that let you establish the baseline permissions for a high-value target. When unauthorized access permissions are made, the new permissions are removed and the baseline permissions are restored.

Security Notification Policies: Policies that allow you to analyze and be notified of the changes in security permissions for a selected target path. Notifications are sent via email and specify the added, modified, or removed permissions for users and groups.

Target-Driven Policies: Policies that manage and perform tasks through direct association with a network share or folder. Target-Driven policies include Data Location policies, Content Control policies, Epoch Data Protection policies, Workload policies, Security Notification policies, Security Lockdown policies, and Security Fencing policies.

Target Path: The path to the network share where managed paths are hosted.

Template: If you want to have subfolders and documents provisioned in a home folder, auxiliary storage folder, or collaborative storage folder when they are created, you can use an existing path in the file system as a template.

View: A representation of the contents of the file system of a High-Value Target at a point in time.

Work Log: An optional mechanism that maintains a history of File Dynamics events. The Work Log contains summary records for events that have reached the processed state; in other words, those for which an effective policy has been calculated and run to completion or have been aborted by administrative action.

Workload Policy: Policies that provide the ability to import externally-generated files and be enacted through a Data Owner via the Data Owner Client.