search
Ctrlk
SupportDashboard

Registry Values Guide

hashtag
What is the Windows Registry?

Think of the Windows Registry as a central database where Windows and many installed applications store their settings and configuration options. It's like a big settings panel, but organized in a hierarchical structure.

The FenixPyre Tool uses the Registry to store its operational settings. Making changes directly in the Registry is generally for advanced users, but understanding what these settings mean can be helpful.

circle-exclamation

Important: Incorrect changes to the Registry can cause problems with your system or applications. Only modify these settings if you are instructed to do so by technical support or documentation.

hashtag
FenixPyre Standalone Encryption Utility Registry Location

The settings for the FenixPyre Tool are stored in the following location within the Windows Registry:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\FPEncDecTool

hashtag
Configuration Settings Explained

Here's a breakdown of the settings you might find in this location and what they do:

1. Action

  • Purpose: Tells the utility what job it needs to perform.

  • Possible Values:

    • ENCRYPT: Encrypt files to make them unreadable without a key.

    • DECRYPT: Decrypt files back to their original readable state.

    • REPORT: Generate a report about the files (without changing them).

    • LOADKEYS : Import file keys provided by FenixPyre Support into the local database for offline decryption.s

  • Status Updates: The utility updates this setting to show its progress, like ENCRYPT_IN_PROGRESS (encryption started) or DECRYPT_DONE (decryption finished).

2. AgentId

  • Purpose: This is a unique identification code assigned to this specific installation of the FenixPyre Standalone Encryption Utility on your computer.

  • How it's set: It's automatically generated the first time the tool starts and registers itself.

3. AgentKey

  • Purpose: This stores a secret code (like a password or key) that the tool uses for secure communication or operations.

  • Security: The key itself is stored in an encrypted (scrambled) format for security.

  • How it's set: It's automatically generated when the tool first registers.

5. DetailedStatus

  • Purpose: Provides a more detailed, technical status update about the task the tool is currently performing or has just completed.

  • Format: The information is often stored in JSON format, which is a structured way to represent data.

6. FolderPath

  • Purpose: Specifies exactly which folder(s) on your computer or network the tool should work on (encrypt, decrypt, or report).

  • Multiple Folders: You can list more than one folder here.

7. LogLevel

  • Purpose: Controls how much detail the tool records in its activity logs. Logs help troubleshoot problems.

  • Levels (More detail = Higher number):

    • 0 (Error): Only records errors.

    • 1 (Info): Records basic information about operations.

    • 2 (Debug): Records more detailed information useful for diagnosing issues.

    • 4 (Verbose): Records the most detailed information possible.

8. OrgId

  • Purpose: An identification code for the organization that this installation of the FenixPyre tool belongs to.

9. PreserveFileSecurityInfo

  • Purpose: Decides whether to keep the original file's security settings (like who has permission to access it) after encrypting or decrypting.

  • Options:

    • 1: Keep the original security settings (Enabled).

    • 0: Do not keep the original security settings (Disabled).

  • Default: If not specified, the tool defaults to 1 (Enabled), keeping the security information.

10. PreserveFileTimestamps

  • Purpose: Decides whether to keep the original file's date and time information (like 'Date Created' and 'Date Modified') after encrypting or decrypting.

  • Options:

    • 1: Keep the original timestamps (Enabled).

    • 0: Do not keep the original timestamps; the file will get new timestamps based on when the encryption/decryption happened (Disabled).

  • Default: If not specified, the tool defaults to 1 (Enabled), keeping the original timestamps.

12. Status

  • Purpose: Provides a brief, simple status update on the current task (e.g., "Encrypting...", "Completed", "Error"). This is less detailed than DetailedStatus.

13. ThresholdDays

  • Purpose: Defines how "old" a file needs to be (based on its 'Date Modified') to be considered "old data" (which might trigger settings like ReuseEncryptionKeysForOldData).

  • Value: You set a number of days.

  • Default: If not specified, files older than 365 days are considered old.

  • Maximum: Can be set up to 1825 days (5 years).

14. Username

  • Purpose: Stores the user's email address associated with this FenixPyre tool installation, used during registration.

15. NumThreads

  • Purpose: Controls how many simultaneous processes (threads) the tool can use to perform tasks like encryption or decryption. More threads can speed up the process on computers with powerful processors, but using too many can also slow things down.

  • Value: A number representing the threads.

  • Maximum: Can be set up to 1024 threads.

16. ChunkSize

  • Purpose: When the tool processes files using multiple threads (see NumThreads), this setting defines how many files each thread should grab and work on at a time (a "chunk").

  • Value: A number representing the files per chunk.

  • Maximum: Can be set up to 10,000 files per chunk.

17. FileKeyDbTtlSecs

  • Purpose: Controls how long (in seconds) an individual file's encryption key (FileKey) is kept readily available in a temporary cache or database ("time to live" or TTL). This can speed up repeated access to recently processed files.

  • Default: If not specified, keys are kept for 3600 seconds (1 hour).

  • Maximum: Can be set up to 86400 seconds (1 day).

18. FileKeySyncBatchSize

  • Purpose: When the tool needs to synchronize file key information with a central service, this setting determines how many keys are sent together in one batch.

  • Default: If not specified, the batch size is 100 keys.

  • Maximum: Can be set up to 300 keys per batch.

19. MonitoringLogBatchSize

  • Purpose: Similar to FileKeySyncBatchSize, but this controls the batch size for sending monitoring or activity log information to a central service.

  • Default: If not specified, the batch size is 100 log entries.

  • Maximum: Can be set up to 300 log entries per batch.

20. IgnoredExtensions

  • Purpose: Allows you to specify types of files that the tool should completely ignore and not encrypt, decrypt, or report on. This is usually used for system files or application files that shouldn't be modified.

  • Format: You list the file extensions, including the dot (e.g., .dll, .exe, .log, .tmp).

Last updated

Was this helpful?