1.1.1 Data Location

Dynamic File Services 2.0 stores program software and the data files it creates in the following locations by default when you accept the default install location:

The following data folders and their contents are now set up in the C:\ProgramData\Dynamic File Services folder:

• audit
• LocalDrives
• Pairs
• Policies
• Schedules
• SnapShot

For upgrades to version 2.0 from earlier releases, if the software is currently installed in the default location of C:\Program Files\Dynamic File Services, the program data files and audit log files are automatically relocated to the C:\ProgramData\Dynamic File Services folder.

You can use the Custom option during the install to specify a different location for the installation. Both the program files and program data are stored in the custom location. If you are installing Dynamic File Services in a cluster, you use the Custom option to specify the shared disk as the target location during the installation.

1.1.2 Product Evaluation and License Key Registration

Dynamic File Services 2.0 is installed in evaluation mode. Most product features will function normally. However, you are limited to one pair and one policy at a time until a key is registered on the system. You must register a key on each computer where the Service component is installed.

You can obtain a license key from the Novell Customer Center. The license key code is delivered in an .html file that is named with a globally unique ID (GUID).

You can enter a license key at any time after you install Dynamic File Services. After a successful key registration, all features of the product are immediately available. You do not need to reinstall the product. The policy and pair created during evaluation remain in effect, as do any configuration settings you have made to the Service.

For information about registering a license key, see Registering the License Key in the Dynamic File Services 2.0 Administration Guide.

1.1.3 Policy Schedules

Dynamic File Services 2.0 separates the Schedule function from the policy. If you upgrade to version 2.0 from an earlier version, the existing policies’ schedules are automatically created and associated with their original policies. A policy can have only one schedule at a time associated with it.

For information about creating schedules, see Creating and Managing Policy Schedules in the Dynamic File Services 2.0 Administration Guide.

1.1.4 Notification Events

Dynamic File Services 2.0 allows you to set Notification events for each configured e-mail address and Twitter account. Previously, events were set globally. If you upgrade from an earlier version, each user is automatically set to receive all events. For information about configuring events for each recipient, see Configuring the Notification Service in the Dynamic File Services 2.0 Administration Guide.