EERM protected USB problem with computer with EEFF installed

Asked By 0 points N/A Posted on -

I am testing EERM and have configured a policy that protects the entire USB drive and makes it read only if not protected. Everything works as fine except that it appears Autorun may be required to be enabled on a machine with EEFF (including EERM) installed.

I asked because, with autorun enabled, inserting the USB drive produces a password prompt and if the correct password is entered, everything is ok. If Cancel is clicked at the password prompt, the drive looks just like it does on a machine without EEFF installed. However, attempting to execute MfeEERM.exe on the machine with EEFF installed produces the following error.

McAfee Endpoint Encryption for Removable Media

The viewer application cannot be started from this location.

If the encrypted contents of the medium cannot be viewed using the operating system explorer, try to remove and then re-introduce the medium to the system. You may have to supply your credentials again depending on the authentication details set for the medium.

If authentication cannot be performed, due to lost credentials, or any other reason, a recovery can be tried. The recovery option should be present in the tray menu or from the password authentication dialog.

If everything else fails, take the medium to a computer where Endpoint Encryption is not installed and launch the viewer application from there.


Is there something missing with my work?

Answered By 5 points N/A #86558

EERM protected USB problem with computer with EEFF installed


Myrna Cajinde Hello,

This is one of the errors where an embarrassing situation occurs for the McAfee group.

Surprised! But actually this is one of the errors where most of the time you will receive the response to turn off / disable your AntiVirus. What happens is that the McAfee Antivirus blocks the proper installation of EEFF, but surprisingly it is not logged or recorded by the installation program, and installation failure notice does not pop up.

Now to test this theory, you can simply Re-name the installer program to  EFFsetup.exe, as an exception is available in the Access protection for ???setup.exe. BUT please keep in mind that in such a case UNINSTALLER will not work as it is called SbCeSetup.exe.

Now this is the embarrassing area, one product of McAfee is causing their other product to malfunction.

So the actual work around comes back to the generic response I mentioned above, and that is turn off the antivirus, before installation.


Related Questions