The new docs.trellix.com features a modernized UI and AI-powered conversational search. Content is currently available in English, with additional languages launching in early November 2026. We hope you enjoy the updated experience.

Product Settings policy

Prev Next

The Product Settings policy options are organized into these tabs: General, Encryption, Log On, Recovery, Boot Options, Theme, Out-of-Band, Encryption Providers, and Companion Devices.

General tab

Option

Definition

Enable policy

Enables the set policies on the client computers.

  • Only activate if health check (Drive Encryption: Go) passes —Select this option to activate Drive Encryption on client systems only when the Drive Encryption: GO health check passes.

Note

You can enable this option only if the DEGO extension 7.x is installed in ePO - On-prem and 7.x DEGO client package is installed in the clients. However, the DEGO Extension/Client package will no longer be provided as part of the Drive Encryption 8.x or later release.

Self Protection

Provides protection against modification of files, folders, and registries related to Trellix Drive Encryption.

Disable Self-Protection (Not recommended): Removes existing protection that stops modification of files, folders, and registries pertaining to Trellix Drive Encryption.

Uninstall Self-Protection: Allowed only after disabling Self-Protection. Removes/Uninstalls Self-Protection software from the client system, as viewed from Trellix Drive Encryption's perspective.

Logging level

Allows the administrator to set a different logging level for each client computer that has the specific policy setting assigned.

Note

To overwrite the logging level defined in ePO - On-prem, the LoggingLevelOverride registry key needs to be set on the client system.

  • None — Does not create any log for the client system managed by ePO - On-prem.

  • Error — Logs only error messages.

  • Error and Warnings — Logs the error and warning messages.

  • Error, Warnings, and Informational — Logs the error and warning messages with more descriptions.

  • Error, Warnings, Informational and Debug — Logs the error, warning, and debug messages.

Expire users who do not login

Allows the administrator to control and manage the users who have not logged on to the client system. This option forces the user account, which is not initialized, to expire after a number of hours as set in the policy.

Allow users to create endpoint info file

Allows the user to collect client system details such as the list of assigned users, policy settings, recovery, and Drive Encryption status.

After enabling this option, the Save Machine info button appears in:

  • Windows — Trellix Agent Tray → Quick Settings → Show Drive Encryption Status.

You can click this button and save the text file for later reference.

Enable logging for Credential provider

Select this option to enable or disable credential provider logging.



Encryption tab

Option

Definition

Encrypt

Allows you to select the required encryption type and to set the encryption priority.

Encryption type

The type of encryption:

  • None — Does not encrypt any disk.

  • All disks — Encrypts all disks in a system.

  • Boot disk only — Encrypts only the boot disk.

  • Selected partitions — Allows you to select the required partitions of the client system and select them to be encrypted. You can select the required partitions by specifying the Windows drive letters/volume names. Partition level encryption is not applicable to client systems using OPAL encryption.

    Note

    Do not assign a drive letter to the Windows 7 hidden system partition on your client system. Doing so prevents activation of the Drive Encryption software on the client system.

    This table also lists the available encryption providers (PC Software and PC Opal) available. You can change and set the encryption priority by moving the encryption provider rows up and down, as appropriate.

    By default, software encryption is used on both Opal and non-Opal systems in this version of Drive Encryption. To ensure that Opal technology is chosen in preference to software encryption, we recommend that you always set Opal as the default encryption provider, by moving it to the top of the list on the Encryption Providers page. This ensures that Opal locking will be used on Opal drives.

    Note

    Make sure that you select the required encryption type, as appropriate. Policy enforcement might fail on client systems if you select an unsupported encryption type.

  • All disks except boot disk — Encrypts all disks except the boot disk (not recommended)

The Encryption type options None, All disks except boot disk, and Selected partitions are not applicable to self-encrypting drives in Opal mode.



Log On (Drive Encryption) tab

Option

Definition

Enable automatic booting

When enabled, the client system boots automatically without prompting for a preboot authentication. The expiration date for auto-booting can also be set.

If required, the user can select the UTC time standard option.

Important

If you enable this option without requiring the use of TPM for automatic booting, the Drive Encryption product does not protect the data on the drive when it is not in use.

  • Disable and restart system after 3 (1–10) failed logons or unlocks (Windows only, Vista onwards) — This feature is an enhancement of the primary Enable automatic booting feature. Select this option to disable the autoboot after a specific number (defaulted to 3 or specify from 1-10) of failed Windows logons.

    On the Windows authentication screen, if the user fails to authenticate the defined number of times, a message appears indicating that the maximum number of failed operating system logons was reached, and that pre-boot authentication is enabled on the machine. Upon clicking OK, the client system restarts and PBA screen appears. Once the user authenticates through PBA and Windows successfully, autoboot is enabled.

    Note

    This feature is available for password, smart cards, and biometric tokens, and only for Windows Vista or later operating systems.

Allow temporary automatic booting

Allows you to turn (on or off) the PBA screen, with a client-side utility. This eliminates the need to modify the policy in ePO - On-prem, and allows for client-side automation during patching and other client management scenarios.

Use of TPM for automatic booting

Select one of these options:

  • Never — The encryption key is written to a plain-text file, which is unencrypted. The system is not secure.

  • If available — If the TPM is available, the encryption key is written to a plain-text file, which is encrypted. The system is secure.

    If the TPM is not available, the encryption key is written to a plain-text file, which is unencrypted. The system is not secure.

  • Required (Note: if TPM is not available on the system, automatic booting will not be enabled) — If the required TPM is available, the encryption key is written to a plain-text file, which is encrypted. The system is secure.

    If the required TPM is not available, automatic booting will not be enabled and the user will see the PBA screen to authenticate. The system is secure.

Note

This option is applicable only for systems installed with Drive Encryption 7.3.0 or later. If you apply a policy to the earlier versions of Drive Encryption with automatic booting enabled and use of TPM set to 'Required', it will leave the client system in an unprotected state since autoboot will be enabled with no protection of the disk encryption key.

TPM autoboot is designed to display the preboot logon screen, if the TPM measurements change. This can occur due to firmware or operating system updates. It is recommended to use temporary autoboot during the deployment of updates, even when TPM autoboot is enabled. For more information about TPM autoboot, see KB79784.

prevent automatic booting when the disk moves system (UEFI only)

This prevents autoboot from functioning when a disk is moved between the systems.

Pre-boot power management: Automatically shutdown pre-boot after a period of inactivity: 1-60 minutes

The client system will shut down automatically after the set time at pre-boot.

Log on message

Type a message that appears to the client user.

Do not display previous user name at log on

Prevents the client system from automatically displaying the user name of the last logged on user on all Drive Encryption logon dialog boxes.

Enable on screen keyboard

Enables the pre-boot On-Screen Keyboard (OSK) and the associated Wacom serial pen driver. When this option is enabled, the pen driver finds supported pen hardware (Panasonic CF-H1 and Samsung Slate 7) and displays the OSK.

Note

If you do not select this option, the BIOS uses mouse emulation. In such a situation, the BIOS treats the digitizer as a standard mouse, which might lead to the cursor being out of sync with the stylus on USB-connected Wacom pen digitizers.

  • Always display on screen keyboard — Forces the preboot to always display a clickable on-screen keyboard, whether the pen driver finds suitable hardware or not.

    Note

    When the option Enable on screen keyboard is turned on, if there is a serial digitizer device for which we have support on BIOS systems, then the OSK is displayed. Otherwise, on both BIOS and UEFI systems, if there is a requirement to display the OSK, then you must also select the option Always display on screen keyboard. This forces the OSK to be displayed without looking for any serial digitizer devices under BIOS.

Add local domain users (and tag with 'TDE:ALDU')

  • Disabled — Selecting this option does not add any local domain users to the client system.

  • Add all previous and current local domain users of the system —Domain users who have previously and are currently logged on to the system can authenticate through the preboot, even if the administrator has not explicitly assigned the user to the client system.

  • Only add currently logged on local domain user(s); activation is dependent on a successful user assignment — Only the domain users who are logged on to the current Windows session are added to the system and hence Drive Encryption is activated, even if the administrator has not explicitly assigned the user to the client system.

    Note

    If you select this option, at least one user should be added to the client system for a successful Drive Encryption activation on the client. The activation doesn't happen until a user logs on to Windows.

Enable accessibility

Select this option to sound a beep as a signal when the user moves the focus from one field to the next using mouse or keyboard in the preboot environment. This option is helpful to visually challenged users.

The USB audio functionality allows visually impaired users to hear an audio signal (spoken word) as guidance when the user moves the cursor from one field to the next in the preboot environment. The USB speakers and headphones can be used to listen to the audio signal.

For more details, see Enable Accessibility (USB audio devices) in the preboot environment.

Disable pre-boot authentication when not synchronized

Blocks a user from logging on to PBA in the client system, if the client system is not synchronized with the ePO - On-prem server for the set number of days.

The user is blocked from logging on to PBA, and can then request the administrator to perform Administrator Recovery to unlock the client system. This allows the client system to boot and communicate with the ePO - On-prem server.

Note

The client system continues to block the user from logging on to the system until synchronization with ePO - On-prem.

Read username from smartcard

Automatically retrieves the available user information about the client system from the inserted smartcard; hence the Authentication window does not prompt for a user name. The user can then authenticate by typing the correct PIN.

You need to enable the matching rules that are required for matching smartcard user principle name (UPN) names with Drive Encryption user names.

  • Disable pre-boot authentication when not synchronized Match certificate user name field up to @ sign — Matches the certificate user name up to the @ sign of the user name. For example, if the UPN is SomeUser@SomeDomain.com and the Drive Encryption user name is SomeUser, a match is found.

  • Hide user name during authentication — The Drive Encryption user name does not appear in the Authentication window.

Note

This feature is supported on the Gemalto .Net V2+ tokens, and PIV and CAC tokens.

Lock workstation when inactive: After x number of minutes

The client system is locked automatically when it is inactive for the set time.



Option

Definition

V7.2 Onwards

Third-party credential providers:

  • Allow integrated third-party credential providers to override the Drive Encryption credential provider — Enable this option to make sure that the Drive Encryption credential provider does not load and allow a compatible third-party credential provider to override the existing credential provider.

Single sign-on (SSO):

  • Provide a single sign-on experience for Drive Encryption users (SSO) — Enable this option to allow the user to log on to the system with a single authentication process. It allows automatic log on to the operating system once the user authenticates through the preboot authentication page.

    • Allow the capturing of smart card PINs for SSO replay — Enable this option to allow Drive Encryption to capture the smart card PIN for SSO.

Password synchronization:

  • Update the Drive Encryption user password to match the Windows user password (during Windows logon, or password changes) — Enable this option to synchronize the Drive Encryption password to match the Windows password when the Windows password is changed on the client system. For example, if users change their password on the client, the Drive Encryption password is also changed to the same value.

    • Ignore Drive Encryption password rules and history when updating the Drive Encryption password — Enabling this option allows you to ignore Drive Encryption password rules and history when synchronizing the Drive Encryption password.

      Warning

      This may result in a reduction of password strength for Drive Encryption users.

    • Periodically check domain credentials for changes and ask the user to re-capture the Drive Encryption password if required — Enabling this option allows you to periodically check the domain credentials for any changes and also inform the user to re-capture the Drive Encryption password, if required.

      Warning

      This will result in an increased load on the domain server that manages the endpoint.

      • Polling interval (minutes) __ (5-480) — Enter the time in minutes within the set limit to periodically check the domain credentials for any changes.

Preboot user options

  • Allow user to cancel SSO and password synchronization — Enable this option to allow the user to cancel SSO and password synchronization.

Windows username matching

  • The Windows username must match the username of the Drive Encryption user before capturing SSO or synchronizing passwords — Ensures the SSO details are captured only when the user’s Drive Encryption and Windows user names match. This ensures that the SSO data captured is replayed for the user for which it was captured.

Credential provider bitmap

  • Do not display Trelix shield on Windows logon tiles — Enabling this option allows you to hide the Trellix shield on Windows logon titles.

Require Drive Encryption logon (only supported on V6 clients) — This requires you to mandatorily log on to PBA for EEPC 6.x.x systems, thereby disabling the SSO functionality.

  • Require log on when token is removed — This requires you to mandatorily log on when the token is removed.

    Note

    This option is available for selection only if the Require Drive Encryption logon (only supported on V6 clients) option is enabled.

Recovery tab

Option

Definition

Enabled

The Recovery option is enabled by default. This activates the Administrator Recovery option in the client system.

Administrator recovery

  • Key size — The recovery key size options. The recovery Response Code size depends on this recovery key size. This does not affect the size of the challenge code.

    • Low — A recovery key size that creates a short Response Code for the recovery.

    • Medium — A recovery key size that creates a medium size Response Code for the recovery.

    • High — A recovery key size that creates a lengthy Response Code for the recovery.

    • Full — A recovery key size that creates a Response Code, with the maximum number of characters, for the recovery.

  • Message — Displays a text message when you select Recovery. This can include information such as your help desk contact details.

Self-recovery

Allow users to re-enroll self-recovery information at PBA — Allows the client user's self-recovery details can be reset. The user must then re-enroll their self-recovery details with new self-recovery answers.

Note

Before resetting the self-recovery questions on the client system, make sure that you have enabled the Enable Self Recovery option under User Based Policy | Self-recovery.

When this option is enabled, the preboot authentication (user name) screen includes the Reset self-recovery option. On selecting Reset self-recovery , the user is prompted for a password, then self-recovery enrollment.

Note

Only initialized users can reset their self-recovery details.

DETech disaster recovery (v7.3 Onwards, UEFI only)

Allow users to perform disaster recovery using DETech — Allows the user to perform disaster recovery using the option Trellix Drive Encryption Recovery within the boot menu.

Note

DETech disaster recovery will be enabled by default for Fresh install and will be disabled on upgrades.



Theme tab

Option

Definition

Select theme

Contains the options for selecting a theme.

Preview

Displays the preview of the selected theme. The preview is not available for shared policies from another ePO - On-prem.



Encryption Providers tab

Option

Definition

PC Software

  • Use compatible MBR (BIOS only) — Causes Drive Encryption to boot a built-in fixed MBR instead of the original MBR that was on the system after preboot logon.

    Note

    It is used to avoid problems with some systems that had other software that runs from the MBR and no longer work if Drive Encryption is installed.

  • Fix OS boot record sides (BIOS only) — Some boot records report an incorrect number of sides. Selecting this option fixes this on the client system. This is available only when you install the Drive Encryption extension.

  • Use windows system drive as boot disk — Maintains the compatibility with some systems where the disk 0 is not the boot disk. Selecting this option forces the users product to assume that the boot disk is the one that contains the Windows directory but not disk 0.

  • Enable Pre-Boot Smart Check (BIOS based systems only) — Modifies the Drive Encryption activation sequence and creates a pre-activation stage, where hardware compatibility checks are performed prior to actual activation and subsequent encryption.

  • Force system restart once activation completes — This option is selected by default when you select Enable Pre-Boot Smart Check (BIOS based systems only) to restart your system after activation.

Opal

Require all disks to be Opal — Requires all the drives in your client system to be Opal drives for the PC Opal encryption provider to be activated.



Companion Devices tab

Option

Definition

Enable Companion Device Support

Allows for the use of smartphone recovery on the system.

Note

To enable smartphone recovery on the system for a user, it must also be enabled in the corresponding user-based policy.

Note

The Companion Device application is now known as Trellix Endpoint Assistant.