Searching available Encryption Providers

[tonyb99]

Is that eepc 6.2 manual install then?

Have you tried upgrading to 7.01 once its activated?

[tcox8]

Not a manual install. I just pushed 7.0.1 Agent as a task and then pushed 6.2 as a task.

I did successfully upgrade to 7.0.1 after it activated and while it was encrypting.

That's still weird that 6.2 will activate but 7.0.1 does not.

[tonyb99]

well its not ideal but it will keep us going for a while..

Guess I still better log a case for it or it will never get seen to

[Reiner]

Hello,

you may want to raise a case here so it can be fully investigated. It seems though the issue might be related to the OPAL provider (test it by renaming EpeOpalEncryptionProviderPlugin.dll and reboot).  Add a full MER to the case and let it be checked - maybe Hotfix 882104 is applicable here.

Hope this helps,

[tonyb99]

Which hotfix is that? do you have a KB as I can't find anything on that one.

[Reiner]

Tony99,

this is only available on request so you will need to open a case with support  (and it needs to be checked whether it is actually applicable).

HTH,

[tonyb99]

It should still have a KB page even if its only on limited release, otherwise you wouldnt have any idea if it was applicable.

[Reiner]

Hi tony99,

If you call support they will be able to explain and continue from there.

[tonyb99]

Its logged Reiner

[tcox8]

As I said earlier in a post... I have a case opened with Gold Support. I received an email from them last night with the same instructions as said by Reiner. First they said to try downloading the latest IRRT drivers from intel via this link:

http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Software+Products&ProductLi...

If that didn't work (which it didn't on all my test machines) they said to try renaming these two files:

C:\Program Files\McAfee\Endpoint Encryption\EpeOpalATASec4SATA.dll

C:\ProgramFiles\McAfee\EndpointEncryption\EpeOpalEncryptionProviderPlugin.dll

After doing that encryption went through smoothly on all test machines. Looks like something with the Opal provider is goofing this up. Interesting that it would happen to all three variations of my test machines.