Release Notes for McAfee Encrypted USB v1.4.0

About this document

Thank you for using McAfee Encrypted USB (EUSB) v1.4.0. This document contains important information about this release. We strongly recommend that you read the entire document.

About this release

McAfee Encrypted USB is a scalable software solution for managing large and small deployments of McAfee's portable security USB devices. McAfee Encrypted USB includes a management console, a client component, and an administration utility (optional). It controls the USB devices’ life cycle including initialization, personalization, usage, rescue, recovery, and recycling.

McAfee Encrypted USB drives are secure, portable storage drives that incorporate built-in user access control and strong data encryption, ensuring that sensitive data remains secure wherever it travels. Data is encrypted with virtually no performance loss or special training required by the end user. It also provides personal and corporate credentials protection and validation, ensuring that identities remain secure.

Build : 2011 February 09 - 1.4.0.28 (EUSB 1.4.0)

EUSB v1.4.0 Features

  • Support for Windows 7 (32/64 bit)
  • Supports following version 2 devices
      1) Gen-II Biometric USB drive
      2) Gen-II HDD Biometric
      3) Gen-II HDD Non-Biometric
  • Added NTFS support for Gen-II HDD

Upgrading from previous versions

Upgrading from previous versions: The EUSB 1.4.0 can be applied to all EUSB 1.0/1.1/1.3 versions. After downloading the EUSB 1.4.0 package, check in the required packages for the v1.4.0 extension into ePO, then install the extension. Create a client task and schedule it to run to upgrade the clients with the EUSB 1.4.0 client files.

Note : Please make sure to carefully follow the upgrade instructions described in the EUSB Upgrade Guide

Known Issues

Known issues in this release of EUSB v1.4.0 are listed below:

  • Uninstalling EUSB 1.4.0 - Removal of EUSB v1.4.0 does not completely remove the EUSB client folder.
  • Online Help - The Online Help is not integrated in ePO server.
  • No Backup with Malware Protection - User is unable to perform Backup with "Malware Protection" enabled.
  • Screen Resolution - Minimum screen resolution should be 1024 X 768.
  • Antivirus DAT Update - DAT Update will not work when Windows Firewall is on.
  • Backup on Network Location - Backup on a Network Location does not happen if not logged into the network location.
  • Concurrent device usage - It is not possible to use multiple EUSB devices concurrently on a single client computer.
  • Retry limit - The value shown for the password or biometric retry limit in EUSB Client is always one less than the actual value set in the authentication policy.
  • Remote desktop - The EUSB Client does not detect EUSB device in a remote desktop environment.
  • Virtual systems - The EUSB Client may not always work properly on virtual systems.
  • Logout - Sometimes Logout operations fails when performed from the "Manage Device" page or window. Workaround: Remove the device forcefully.
  • NTFS and On-Access Scan - NTFS and On-Access scan are in conflict. With NTFS, the AV handle on the private drive cannot be released. Workaround: Disable On-Access scan.
  • Portable Content Manager - Portable Content Manager is not supported for Gen-II Devices.
  • Initialization - Initialization will fail if read only partition size is set to half or more than the total capacity of the device.
  • Initialization - During initilization process a popup window is displayed with message "Format Drive ....." . Workaround: Press "Cancel" button in the popup window.
  • Upgrade - Device revoked in 1.1 cannot be reinstated in 1.4.0 after client upgrade.
  • Upgrade - No notification to the user after successful upgrade.
  • Upgrade - Sometimes NaPrdMgr.exe gets restarted after performing the client upgrade from 1.1 to 1.4.0, during that policy enforcement does not happen. Workaround: Perform an policy enforcement again.
  • Upgrade - Combining device upgrade and policy change on the device will not work. Workaround: First upgrade the device then modify and apply the policy.
  • Upgrade - When device is upgraded from 1.1 AV/Non-AV to 1.4.0 AV with default size (120MB), upgrade fails. Workaround: Set the read-only partion size for the initialization policy to 250MB (Mininum) in 1.4.0 and reinitilize the device.
  • Device Ejection - Sometimes the Eject operation fails when performed from "Managed Device" page.

COPYRIGHT